Repository navigation
Remove automatic propagator setup from OTLPIntegration #6732
Description
Activity
- moved this from Waiting for: Product Owner to No status in GitHub Issues with 👀 3
on Jul 27, 2026 - moved this from Waiting for: Product Owner to No status in GitHub Issues with 👀 3
on Aug 4, 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.
- moved this from Waiting for: Product Owner to No status in GitHub Issues with 👀 3
on Sep 15, 2026
The OTLP integration currently sets up a Sentry propagator by default. This injects
sentry-traceandbaggageheaders on outgoing requests alongside, or instead of, the standard W3Ctraceparentheader.Per the OTLP integration spec, the integration must not set up an automatic propagator. Cross-service trace propagation should be handled by
propagateTraceparentor 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.