-
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
Create a combined B3 Propagator that handle both single and multi-header cases #1684
Comments
Won't |
It might, but the spec says when you enable the B3 propagator, it should handle both cases, which we don't at the moment. Are you thinking that this should be implemented in the agent, rather than propagator itself? |
I think we should still have this as a single |
i can pick this one up |
I don't know if this is the proper place but I think that https://github.com/open-telemetry/opentelemetry-java/blob/master/extensions/trace_propagators/src/main/java/io/opentelemetry/extensions/trace/propagation/B3PropagatorInjectorSingleHeader.java is not really working exactly as it should. If there's a parent span id it should also get appended to the the single b3 header. You can check how they do it in Brave https://github.com/openzipkin/brave/blob/4a4d8bf49318ae049669c5ccc8e451102e826cca/brave/src/main/java/brave/propagation/B3SingleFormat.java#L114-L139 Example in Brave traceId - spanId - sampled - parentSpanId Example in Brave without traceId - spanId - sampled - parentSpanId how it's done in OTel traceId - spanId - sampled |
See the recently updated spec: https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/context/api-propagators.md#b3-requirements
The text was updated successfully, but these errors were encountered: