-
Notifications
You must be signed in to change notification settings - Fork 869
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
Automatically append baggage entries to span attributes #4520
Comments
hey @trask, I'm slightly confused. Is the feature of baggage item propagation in general available or not. The two discussions referenced are contradicting each other? Best |
Baggage is automatically propagated, but is not automatically attached as span attributes when exporting |
Thanks for confirming. If you can give me a hint in which direction I should search, I would give it a try to implement. |
just out of curious, should this be done on the sdk side or the instrumentation side? |
OpenTelemetry SDK only includes specced components. This feature (appending baggage as span attributes) probably fits either this repo or contrib more (contrib seems to be a somewhat more suitable place now that I think of it; cause it's not an instrumentation). |
A span processor has been added in contrib with this PR: open-telemetry/opentelemetry-java-contrib#1290, so it might be a matter of reusing it in the agent. |
Hi,
like we were discussing about adding configuration for adding baggage entries as span attributes to every span in #4518 or #4351. It would be great to have some configuration for turning on or off adding baggage entries to spans.
Currently we are not able to propagate baggage entries. Except for creating custom extension.
Actually we are not able to create some analytical solution without these baggage entries.
Thank you
The text was updated successfully, but these errors were encountered: