You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently when OtelContext.with or OtelContext.get is called with context key opentelemetry-baggage-key (defined in io.opentelemetry.api.baggage.BaggageContextKey#KEY)
null is returned.
Setup:
Java agent running with DD_TRACE_OTEL_ENABLED=true
This key seems to be used by otel to set or get an instance of io.opentelemetry.api.baggage.Baggage.
In order to be able to use baggage with open-telemetry this context key needs to be handled.
The text was updated successfully, but these errors were encountered:
We currently don't support baggage with our OTel instrumentation.
It is mainly due to the lack of support for the Context lifecycle.
So even if you were able to store baggage, you won't retrieve any meaningful value when needed.
It is identified as a compatibility issue on our OTel support roadmap though.
We really appreciate if you can open a feature request on our support page so we can make sure to keep track of it, and our support team will be able to learn more about you and your context.
Don't hesitate to link this issue as reference.
Currently when
OtelContext.with
orOtelContext.get
is called with context keyopentelemetry-baggage-key
(defined inio.opentelemetry.api.baggage.BaggageContextKey#KEY
)null is returned.
Setup:
Java agent running with
DD_TRACE_OTEL_ENABLED=true
This key seems to be used by otel to set or get an instance of
io.opentelemetry.api.baggage.Baggage
.In order to be able to use baggage with open-telemetry this context key needs to be handled.
The text was updated successfully, but these errors were encountered: