Skip to content
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

Use Zipkin as propagator, and don't have parent span id #7693

Closed
neo-ytx opened this issue Jan 31, 2023 · 1 comment
Closed

Use Zipkin as propagator, and don't have parent span id #7693

neo-ytx opened this issue Jan 31, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@neo-ytx
Copy link

neo-ytx commented Jan 31, 2023

Is your feature request related to a problem? Please describe.
When I send a header "b3={TraceId}-{SpanId}-{SamplingState}-{ParentSpanId}" to the service with javaagent, it won't send parentSpanId to the next service. I want to know why to design this?
I saw the doc said "MUST NOT propagate X-B3-ParentSpanId as OpenTelemetry does not support reusing the same id for both sides of a request." But i don't understand it.

@neo-ytx neo-ytx added the enhancement New feature or request label Jan 31, 2023
@mateuszrzeszutek
Copy link
Member

Hey @lvqytx ,

OpenTelemetry does not use the parent span id anywhere; it's an optional part of the B3 header, we chose to not implement it.
For more context, take a look at open-telemetry/opentelemetry-specification#1004 and open-telemetry/opentelemetry-specification#1045; perhaps they'll explain the reason why it works the way it does. If you have further questions, please open an issue in the spec repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants