We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As I understand it tracecontext and baggage are complementary, but today the documented idiom here is
(from https://docs.rs/opentelemetry/latest/opentelemetry/global/fn.set_text_map_propagator.html)
global::set_text_map_propagator(TraceContextPropagator::new());
however, tracecontext and baggage are meant to both be used together e.g. https://medium.com/jaegertracing/embracing-context-propagation-7100b9b6029a and w3c/baggage#10 (comment) and also https://w3c.github.io/baggage/#baggage-http-header-format - SHOULD be passed on - means that having to write a Composite Propogator by hand is needed.
The text was updated successfully, but these errors were encountered:
nevermind, I just did not manage to find it in the docs. :/
Sorry, something went wrong.
No branches or pull requests
As I understand it tracecontext and baggage are complementary, but today the documented idiom here is
(from https://docs.rs/opentelemetry/latest/opentelemetry/global/fn.set_text_map_propagator.html)
however, tracecontext and baggage are meant to both be used together e.g. https://medium.com/jaegertracing/embracing-context-propagation-7100b9b6029a and w3c/baggage#10 (comment)
and also https://w3c.github.io/baggage/#baggage-http-header-format - SHOULD be passed on - means that having to write a Composite Propogator by hand is needed.
The text was updated successfully, but these errors were encountered: