Similar to https://github.com/open-telemetry/opentelemetry-java/issues/853 but for Jaeger clients.
Does OTEL client support exporting/injecting of TraceContext/SpanContext into two formats? At the same time use W3C TraceContext and Jaeger? The use case is to allow gradual migration of existing deployments using Jaeger prop. format to W3C.
Related #718 "No way to change HttpTextFormat"
Hi, I can take a look into this if nobody is already working on it
Go ahead @jarebudev
We need to support baggage in the Jaeger format to close this one.
i can take a look at this, should have a bit more spare time to help out
I should have a PR ready this week time permitting.
To confirm - is this for inject only, or both inject and extract?
Unless there's some reason I don't understand, I think we'd want both inject and extract.
Unless there's some reason I don't understand, I think we'd want both inject and extract.
Finally got back to this.. :)
I have made changes so that JaegerPropagator injects baggage items and is ready for a PR.
For extracting baggage from Jaeger, unless I've missed something, I was wondering how we'd extract a baggage item when the HTTP headers uberctx-{baggage-key} passed to the propagator are not fixed and we can only get 'known' headers (e.g. uber-trace-id) using the HttpTextFormat.Getter.get() method? Do we need an additional method on the Getter interface to return all keys?
@jarebudev
We need to support iteration of keys in the Getter - see this (on my queue, and it's also marked as "required-for-ga"). Hope to work on that next week, and once that is done, you will be able to complete this task ;)
Assigning this to me as this will be part of the over all updates for Getter.Keys(). Hope that is fine @jarebudev 馃槄
Most helpful comment
i can take a look at this, should have a bit more spare time to help out