[jamescrosswell]

Warning

Do not merge before sentry-dotnet 7.0.0 is released (planned 2026-11-30).

DESCRIBE YOUR PR

Updates the .NET OTLP page for sentry-dotnet 7.0.0. From 7.0.0, AddSentryOtlpExporter no longer installs SentryPropagator, and the defaultTextMapPropagator parameter is gone from it and from UseOtlp (getsentry/sentry-dotnet#5319).

• Replaces the SentryPropagator bullet and the "Planned Removal" alert with a Trace Propagation section. It covers what gets propagated by default, how to add SentryPropagator for services that rely on sentry-trace, and when PropagateTraceparent helps. A short note covers the pre-7.0.0 behavior.
• Removes the defaultTextMapPropagator option.
• Raises the OpenTelemetry floor in Supported Versions to 1.12.0.
• Replaces the note saying not to set TracesSampleRate with a Sampling section. With UseOtlp() the SDK creates no transactions, so TracesSampleRate and TracesSampler are never read, and the OTLP exporter installs no OpenTelemetry sampler. Sampling is configured on the TracerProvider. This is true for 6.x as well.

Closes getsentry/sentry-dotnet#5546

Notes for review

Where the page differs from the issue, it follows the source on sentry-dotnet's version7 branch:

• PropagateTraceparent doesn't help the OTLP service itself. OpenTelemetry's default propagator (W3C trace context plus baggage, which the OTel SDK installs) and the .NET runtime already send traceparent. OTel's HttpClient instrumentation also overwrites any traceparent that SentryHttpMessageHandler adds first. A local run against a version7 build sent identical headers with and without the option. The page recommends it for the Sentry-traced services that call the OTLP service, as /concepts/otlp/sentry-with-otel/ already does.
• sentry-trace doesn't disappear completely. UseOtlp() stops SentryHttpMessageHandler from creating spans, but its header propagation still runs (SentryMessageHandler.PropagateTraceHeaders). Sentry adds the handler to IHttpClientFactory clients when it's set up through DI. Other requests only carry sentry-trace if the app configures SentryPropagator.
• The 1.12.0 floor already shipped in 6.11.1 (remove weird usages of non breaking space <0xa0> #5560 was backported in chore(deps): raise the OpenTelemetry floor to 1.12.0 sentry-dotnet#5588), so that line is correct today and has no "before 7.0.0" note.
• SentryPropagator is still public in Sentry.OpenTelemetry.Exporter on version7, so the snippet doesn't need the deprecated Sentry.OpenTelemetry package. It derives from BaggagePropagator, which is why the composite doesn't list that one separately. The snippet compiles against the version7 build with OpenTelemetry 1.12.0.

IS YOUR CHANGE URGENT?

Help us prioritize incoming PRs by letting us know when the change needs to go live.
Select exactly one option. For deadlines, replace YYYY-MM-DD with the due date. You can update this information later by editing the PR description.

• Urgent deadline (GA date, etc.): 2026-11-30
• Other deadline: YYYY-MM-DD
• No deadline: Not urgent, can wait up to 1 week+

SLA

• Teamwork makes the dream work, so please add a reviewer to your PRs.
• Please give the docs team up to 1 week to review your PR unless you've supplied a deadline.

Thanks in advance for your help!

PRE-MERGE CHECKLIST

Make sure you've checked the following before merging your changes:

• Checked Vercel preview for correctness, including links
• PR was reviewed and approved by any necessary SMEs (subject matter experts)
• PR was reviewed and approved by a member of the Sentry docs team

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
sentry-docs	Ready	Preview	Oct 13, 2026 3:22am UTC

1 Skipped Deployment

Project	Deployment	Actions	Updated
develop-docs	Ignored	Preview	Oct 13, 2026 3:22am UTC

[cursor]

The plan checks client errors on the changed page, overall error volume, and pageload duration. An issue escalates when the changed page emits errors or error volume leaves the measured band.

Services: sentry-docs.

Mention @change-monitor in a comment to update the plan.

Plan

What changed

The live .NET OTLP page now documents SDK 7.0.0 propagator behavior. AddSentryOtlpExporter no longer installs SentryPropagator and no longer accepts defaultTextMapPropagator. The page shows a CompositeTextMapPropagator snippet for readers who still need sentry-trace headers. sentry-docs must deploy before this change is live.

Risk

New MDX can throw in Alert, code tabs, or PlatformLink during render. That failure hits this page first. A shared code-tab failure can also break other pages. Wrong text can make readers drop sentry-trace propagation after they upgrade.

Intended effect

This change is documentation text. Telemetry cannot show that the new wording is live. Absent means the page still shows the old Planned Removal warning. Do not treat missing page views as absent intended effect.

Regression watch

Watch client failures on this page first. Then watch docs-wide error volume and pageload duration on the shared renderer.

Signal	Baseline	Window	Source	Rule
Error events with url:*opentelemetry-otlp*	0-1 events/hour. Measured 0 events/hour in this window. The prior 7 days held 20 events, all titled Event captured as promise rejection.	2026-10-12T03:00:00Z to 2026-10-13T03:00:00Z	Sentry org sentry, project docs. Query url:*opentelemetry-otlp*	Hold in 0-1 events/hour. A new error title or a rise above 1 event/hour is a regression.
Error events in project docs	0-22 events/hour. Complete-hour min 0 at 2026-10-12T04:00:00Z. Max 22 at 2026-10-12T13:00:00Z.	2026-10-12T03:00:00Z to 2026-10-13T03:00:00Z	Sentry org sentry, project docs. Query project:docs	Hold in 0-22 events/hour. A rise above 22 events/hour is a regression.
p95 span.duration for span.op:pageload	6.7-23.7s. Complete-hour min 6.7s at 2026-10-12T08:00:00Z. Max 23.7s at 2026-10-13T01:00:00Z. 24h aggregate p95 was 11.2s on 10253 sampled pageloads, mostly transaction /:path*?.	2026-10-12T03:00:00Z to 2026-10-13T03:00:00Z	Sentry org sentry, project docs. Query span.op:pageload	Hold in 6.7-23.7s. A rise above 23.7s is a regression. If this p95 rises, inspect error events on url:*opentelemetry-otlp* next.

Not observable

Page-level pageload duration is not separable. Almost all pages share transaction /:path*?. An http.url filter for this path returned zero pageload spans. Whether the published HTML contains the 7.0.0 snippet is not in Sentry. Reader SDK misconfiguration is not visible on the docs site.

[ric-oliv]

PR looks good! We should probably keep it as a Draft until the v7.0.0 to avoid any premature merge risk.

[jamescrosswell]

We should probably keep it as a Draft until the v7.0.0 to avoid any premature merge risk

I've left it ready for review as a way to track what's actually complete vs still needs work on all the docs PRs we're planning for v7.

I've added an alert warning at the to of the description instead - I think just you and me, we should be able to avoid merging anything by accident.