-
Notifications
You must be signed in to change notification settings - Fork 855
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
Add Jaeger propagator #967
Comments
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. |
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 |
We need to support iteration of keys in the |
Assigning this to me as this will be part of the over all updates for |
Similar to #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.
The text was updated successfully, but these errors were encountered: