-
Notifications
You must be signed in to change notification settings - Fork 452
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
Ensure compliance with b3 propagator spec #314
Comments
I think we almost dodge all the bullets on this one. 😂 The only difference with spec is
When extract we will follow users' choice on encoding. But if user select The rest of the change should already be covered. See details below
We set the sampled and debug flag in SpanContext, opentelemetry-rust/src/sdk/propagation/b3.rs Line 135 in dbe57cc
I think we use the result of extraction as remote span context, so we will always generate new span for operation in the application opentelemetry-rust/src/sdk/propagation/b3.rs Line 282 in dbe57cc
We don't inject this header opentelemetry-rust/src/sdk/propagation/b3.rs Lines 235 to 254 in dbe57cc
|
See the clarification of the spec here open-telemetry/opentelemetry-specification#1045
The text was updated successfully, but these errors were encountered: