-
Notifications
You must be signed in to change notification settings - Fork 199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prefer w3c traceparent header over legacy elastic-apm-traceparent #963
Conversation
Switch the order of precedence, preferring the W3C 'traceparent' header over 'elastic-apm-traceparent'.
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪 |
module/apmot/tracer.go
Outdated
// the value if not set already. | ||
traceparentHeaderValue = val | ||
case apmhttp.ElasticTraceparentHeader: | ||
// The W3C header value always trumps the ElastiC one, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Liking the stylized ElastiC
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
heh, thanks :)
* Give precedence to W3C 'traceparent' header Switch the order of precedence, preferring the W3C 'traceparent' header over 'elastic-apm-traceparent'. * Update changelog * Update module/apmot/tracer.go
Switch the order of precedence, preferring the W3C 'traceparent' header over 'elastic-apm-traceparent'.
See elastic/apm#442