-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Baggage is not propagated by OpenTracing bridge #2793
Comments
Hi , Can I take this bug ? |
@MrAlias @MadVikingGod |
@bboreham |
You tried the test at the commit I linked? |
Thanks @bboreham , Now i am able to reproduce this. |
The following fixes the example given in bboreham@c162bdd - otel.SetTextMapPropagator(propagation.TraceContext{})
+ otel.SetTextMapPropagator(propagation.NewCompositeTextMapPropagator(propagation.TraceContext{}, propagation.Baggage{})) This is expected behaviour, I've written a test in #4776 to cover this. No changes needed, happy to close this |
@bboreham Can you please check #2793 (comment)? |
Thanks, TIL. I do think this could be better documented; I did a search of a hundred or so repos I work with and think they were about 70/30 whether they added baggage or not. |
Description
When using BridgeTracer, after Inject the Carrier has no entries for baggage.
After Extract the resulting SpanContext has nil in the baggage field.
Environment
go1.17.1 darwin/arm64
Steps To Reproduce
Starting with the test from #2141, add some baggage:
bboreham@c162bdd
Observe the test now fails:
Expected behavior
Baggage should be propagated.
Commentary
There are lines in
BridgeTracer.Inject
andExtract
aimed at doing something with baggage:opentelemetry-go/bridge/opentracing/bridge.go
Line 648 in 1884de2
opentelemetry-go/bridge/opentracing/bridge.go
Line 667 in 1884de2
However the propagator Inject and Extract methods do not seem to line up with this code's expectations.
The text was updated successfully, but these errors were encountered: