Give precedence to w3c traceparent header#1821
Conversation
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
SylvainJuge
left a comment
There was a problem hiding this comment.
LGTM, do we have a few examples when this would be problematic to be a bit more clear why this change was required ? (probably @AlexanderWert might have an idea on this one also).
|
Whenever there is something in the middle (let's say a reverse proxy) of two services being monitored by our agent. And the proxy uses the W3C headers to create own spans (--> thus sends modified traceparent header to the downstream service), but passes our proprietary header as is. In this case the downstream service has a conflict, especially if it prefers the proprietary header over the W3C header, resulting in wrong parent child relationship. |
❕ Build Aborted
Expand to view the summary
Build stats
Trends 🧪Log outputExpand to view the last 100 lines of log output
|
What does this PR do?
Implements elastic/apm#442
Checklist