Closed
Description
I noticed that our DSC/propagation context usage in @sentry/opentelemetry
is not fully correct. Basically, we don't fully cascade the lookup to include spans, which we need to fix. Also we currently lookup the fallback context from the OTEL context, not the scope - we should align this, as otherwise doing scope.setPropagationContext()
will not do anything.
So the updated propagator should:
- Put the DSC etc. into the span context (which in OTEL can even exist if there is no span!)
- Read DSC/propagation context from active span, if it exists
- Else, fall back to reading it from scope, if it has one
- Else, fall back to reading it from span context, if it has one
- Else, use from client
Metadata
Metadata
Assignees
Labels
No labels