fix(dotnet): Clarify that EnableLogs doesn't gate SentrySdk.Logger

[sentry-junior]

DESCRIBE YOUR PR

The .NET logs docs say EnableLogs = true is required to use the SentrySdk.Logger APIs. That stopped being true in 6.10.0 (getsentry/sentry-dotnet#5512). The option now only controls logs captured by the logging integrations (Microsoft.Extensions.Logging, Serilog, NLog, log4net). Logs created directly through SentrySdk.Logger "are always sent" (SentryOptions.cs L610–620 @ 6.12.0).

This removes the claim everywhere it appears in the .NET logs docs:

• Options: the plain .NET EnableLogs description now says it controls integration-captured logs, not SentrySdk.Logger.
• Options: the Microsoft.Extensions.Logging filter note no longer says EnableLogs = true "keeps the SentrySdk.Logger APIs available."
• Setup: the intro explains that SentrySdk.Logger needs no extra configuration, and integrations need EnableLogs = true.
• Setup (plain .NET): the SentrySdk.Init snippet no longer sets EnableLogs, and the note says you only need it with a logging integration.
• Setup (ASP.NET Core, AWS Lambda, Azure Functions, Blazor, MAUI): the note no longer says EnableLogs enables SentrySdk.Logger; it enables the Microsoft.Extensions.Logging integration.
• Usage: the intro no longer says the feature must be enabled before using SentrySdk.Logger.

Integration-based setup snippets still set EnableLogs = true, since every integration path still requires it.

IS YOUR CHANGE URGENT?

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

PRE-MERGE CHECKLIST

• 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

via Junior system actor event.

--

View Junior Session [Sentry]

[vercel]

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

Project	Deployment	Actions	Updated
sentry-docs	Ready	Preview	Oct 6, 2026 8:46am UTC

1 Skipped Deployment

Project	Deployment	Actions	Updated
develop-docs	Ignored	Preview	Oct 6, 2026 8:46am UTC

[cursor]

The plan checks page failures, HTTP 5xx, and client errors on the changed logs pages. An issue escalates when those pages fail or client errors rise.

Rollout complete

Services: sentry-docs.

Plan

What changed

Readers of the .NET logs pages now see that EnableLogs only gates logging integrations. Direct SentrySdk.Logger calls always send logs from SDK 6.10.0.

This is live after a production deploy of sentry-docs. The pages are /platforms/dotnet/logs/ and each /platforms/dotnet/guides/<guide>/logs/ page that includes these snippets.

Risk

A broken include can hide Setup or Options text on those pages. It can also crash the platform selector there. Wrong wording can lead users to skip EnableLogs for logging integrations. Then those integration logs never reach Sentry.

Intended effect

This is a docs wording change. Sentry does not record the new sentences. There is no queryable production signal for the intended effect. Report intended_effect as unknown. Absent would be live pages that still say EnableLogs is required for SentrySdk.Logger. Telemetry cannot show that.

Regression watch

Watch the changed .NET logs pages only. Transaction names are /:path*?, so filter on url.path. User traces are sampled at 30 percent. Traffic on these pages was low in the baseline window. One failed span would move failure rate off zero.

Signal	Baseline	Window	Source	Rule
Pageload and navigation failure rate on .NET logs pages	0	2026-10-05T08:14:05Z to 2026-10-06T08:14:05Z	Sentry project docs. Query: environment:production AND (span.op:pageload OR span.op:navigation) AND url.path:*platforms/dotnet* AND url.path:*/logs/	Hold at 0. Escalate if the rate rises above 0.
HTTP 5xx on those paths	0	2026-10-05T08:14:05Z to 2026-10-06T08:14:05Z	Sentry project docs. Query: environment:production span.op:http.server http.status_code:>=500 url.path:*platforms/dotnet/* url.path:*logs/*	Hold at 0. Escalate if any 5xx span appears.
Client error events on those URLs	0-2 events	2026-10-05T08:14:05Z to 2026-10-06T08:14:05Z	Sentry project docs. Query: environment:production url:*platforms/dotnet* url:*logs*	Hold in 0-2 events in a matching 24h window. Escalate if the count rises above 2. Sampled page spans in this window were 13. Do not treat 2/13 as an error rate.

If failure rate or 5xx rises, check client errors on the same URLs. Look for platform selector or code tab failures. Unresolved issues on these URLs were none in the baseline window.

Not observable

The live page wording is not in Sentry. Unsampled page volume is not in Sentry. Latency on these pages is not stable. Thirteen sampled spans in 24h showed p95 from 393ms to 11.9s. Do not use that p95 as a regression rule.

[cursor]

Verified in production

• Sampled .NET logs page traffic after the ship stayed at zero failures, and the new EnableLogs wording is live.