Repository navigation
Remove automatic propagator setup from OTLPIntegration #6732
Description
The OTLP integration currently sets up a Sentry propagator by default. This injects sentry-trace and baggage headers on outgoing requests alongside, or instead of, the standard W3C traceparent header.
Per the OTLP integration spec, the integration must not set up an automatic propagator. Cross-service trace propagation should be handled by propagateTraceparent or by user-configured OpenTelemetry propagators.
Docs:
Update docs to reflect the breaking change and manual propagator configuration path. The planned removal notice is already present in the OTLP docs.
Migration path:
Users who still need Sentry-specific headers in mixed Sentry-native and OpenTelemetry environments can configure propagators manually via the OpenTelemetry propagation API.
Activity
linear-code commentedon Jul 2, 2026
PY-2574
IgorGanapolsky commentedon Jul 24, 2026
Epsilon006 commentedon Sep 6, 2026
Hi! I'd be interested in working on this.
I checked the current implementation and confirmed that the automatic
SentryOTLPPropagatorsetup is still present on bothmasterandmajor/3.0.Since this issue is labeled
Breaking change/Next Major, should a contribution targetmajor/3.0directly?My proposed scope would be to remove the automatic propagator setup from
OTLPIntegration, update the related tests, and adjust the migration/documentation path as needed.I'll wait for maintainer guidance before starting the implementation.