feat: add zipkin b3 header propagation#1110
Merged
agrawroh merged 1 commit intoenvoyproxy:mainfrom Apr 19, 2026
Merged
Conversation
We unfortunately chose the wrong path down the tech tree many years ago and now we are stuck on zipkin header propagation throughout our service call stack. Configure the tracer here to parse and propagate zipkin's b3 headers in addition to the more standard otel/w3c ones. This isn't gated behind configuration as I think the risk is small; this could only break someone's usage if they were already propagating both sets of headers to this service, and those headers conflicted. Given that Envoy is the typical client of this service, and I don't think you can even configure Envoy to do multiple types of propagation simultaneously, I think the risk is low. (There is no risk the other way as this service doesn't propagate headers to any place.) Signed-off-by: Ian Kerins <[email protected]>
agrawroh
approved these changes
Apr 19, 2026
Contributor
Author
|
Thanks! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We unfortunately chose the wrong path down the tech tree many years ago and now we are stuck on zipkin header propagation throughout our service call stack. Configure the tracer here to parse and propagate zipkin's b3 headers in addition to the more standard otel/w3c ones.
This isn't gated behind configuration as I think the risk is small; this could only break someone's usage if they were already propagating both sets of headers to this service, and those headers conflicted. Given that Envoy is the typical client of this service, and I don't think you can even configure Envoy to do multiple types of propagation simultaneously, I think the risk is low. (There is no risk the other way as this service doesn't propagate headers to any place.)