docs(dotnet): Document TraceIgnoreStatusCodes

[jamescrosswell]

DESCRIBE YOUR PR

Documents SentryOptions.TraceIgnoreStatusCodes for the .NET SDK. The option shipped in 6.4.0 (getsentry/sentry-dotnet#5034), but the .NET docs don't mention it. In 7.0.0 its default changes from an empty list to 301, 305–399 and 401–404 (getsentry/sentry-dotnet#5632), so ASP.NET Core and ASP.NET apps will stop sending transactions for those responses.

• Adds an SdkOption entry to the Tracing Options on the shared .NET options page. It covers what the option filters, how to set codes and ranges, the 7.0.0 default and why 302/303 aren't in it, how to trace everything again, and appsettings.json.
• Adds a short mention, linking to the option, to the server integration sections of the ASP.NET Core and ASP.NET tracing pages.

Notes for review:

• The docs aren't versioned, so the entry describes 6.x (empty default) and says the default changes in 7.0.0. It's accurate today and can merge before 7.0.0 ships.
• The entry is wrapped in a PlatformSection for the guides that run Sentry's ASP.NET or ASP.NET Core integration: ASP.NET, ASP.NET Core, Blazor Server, AWS Lambda and Google Cloud Functions. The option has no effect elsewhere.
• "Outgoing HttpClient requests aren't affected" holds from 6.12.0 (getsentry/sentry-dotnet#5643). From 6.4.0 to 6.11.x, an app using UseOpenTelemetry that set the option could also lose root http.client transactions whose downstream status matched. I left that fixed bug off the page.
• With UseOtlp, spans go straight to Sentry's OTLP endpoint and never reach the SDK's transaction processors, so the option doesn't apply. The page says so in one line.
• The [] vs [0] caveat for appsettings.json only matters from 7.0.0, when the default is non-empty, and is worded that way. Configuration can't express ranges yet (getsentry/sentry-dotnet#5644).
• The code sample uses a collection initializer rather than a collection expression, because ASP.NET apps on .NET Framework default to C# 7.3. It was compiled and run against Sentry 6.12.0.

Closes getsentry/sentry-dotnet#5708

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.): YYYY-MM-DD
• Other deadline: 2026-11-30 (planned sentry-dotnet 7.0.0 release)
• No deadline: Not urgent, can wait up to 1 week+

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 14, 2026 10:12pm UTC

1 Skipped Deployment

Project	Deployment	Actions	Updated
develop-docs	Ignored	Preview	Oct 14, 2026 10:12pm UTC

[cursor]

The plan checks client errors on the changed pages, page-load counts, and error logs from those routes. An issue escalates when client errors rise or those pages stop loading.

Monitoring in production

Services: sentry-docs.

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

Plan

What changed

The .NET options page now documents TraceIgnoreStatusCodes for inbound HTTP tracing. The ASP.NET and ASP.NET Core tracing pages now say which status codes skip transactions. sentry-docs must deploy to production before this text is live.

Risk

A broken MDX block can fail the options page for every .NET guide. New code samples can throw in the client code tabs. A static build failure stops the deploy before users see the pages.

Intended effect

This change is a documentation edit. Telemetry cannot show that the new text is on the page. Confirmed means the three live pages include TraceIgnoreStatusCodes. Absent means those pages still omit the option.

The pages are /platforms/dotnet/configuration/options/, /platforms/dotnet/guides/aspnet/tracing/included-instrumentation/, and /platforms/dotnet/guides/aspnetcore/tracing/instrumentation/automatic-instrumentation/.

Regression watch

This diff can break MDX render and code tabs on the .NET options page and on inherited guide copies of that page.

Signal	Baseline	Window	Source	Rule
Production errors whose transaction or http.url contains /platforms/dotnet	5 events in 24h. That is about 1.1 percent of 463 docs.page.load events.	2026-10-11T22:24:43Z to 2026-10-12T22:24:43Z	Sentry sentry/docs query environment:production (transaction:*/platforms/dotnet* OR http.url:*/platforms/dotnet*)	Hold in the 0-5 events band. Escalate if the 24h count rises above this band while page loads hold.
Error logs whose message contains /platforms/dotnet	13 messages in 24h. These messages may include noise that is not from these pages.	2026-10-11T22:24:43Z to 2026-10-12T22:24:43Z	Sentry sentry/docs query severity:error sentry.environment:production message:*/platforms/dotnet*	Hold in the 0-13 messages band. Escalate if the 24h count rises above this band.
docs.page.load on /platforms/dotnet/configuration/options/	10 loads in 24h	2026-10-11T22:24:43Z to 2026-10-12T22:24:43Z	Sentry sentry/docs metric docs.page.load with path:/platforms/dotnet/configuration/options/	Hold. Escalate if this count falls to 0 while other /platforms/dotnet paths still load.
docs.page.load on all /platforms/dotnet paths	463 loads in 24h	2026-10-11T22:24:43Z to 2026-10-12T22:24:43Z	Sentry sentry/docs metric docs.page.load with path:*platforms/dotnet*	Hold. Escalate if this family drops sharply while the rest of the site still loads.

If error counts rise, inspect client exceptions on the options page and on the two tracing pages. Check code tabs and platform-section render first.

Not observable

Correctness of the new option text has no telemetry. Page-load latency for these routes is not available. Client transactions do not use the URL path as the transaction name. The 404 metric stores only the first two path segments, so it cannot isolate these pages.

[ric-oliv]

Nice! Just added a few suggestions inline, nothing blocking though.

Two things outside the diff:

• The note in the PR description says the []/[0] caveat is worded as 7.0.0-only, but 6ca5bdc dropped that qualifier. The text is still true on 6.x, so only the description needs updating.
• The .NET migration guide has no 7.x section yet. The Migration section in getsentry/sentry-dotnet#5632 is ready to copy. Worth tracking before the 7.0.0 release.