Repository navigation
Conversation
An empty commit, so the dotnet-v7 collection PR can be opened against master. The .NET docs PRs for 7.0.0 merge into this branch once they're approved, and the branch merges into master when 7.0.0 ships. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
1 of 3 tasks
This was referenced Nov 9, 2026
> [!NOTE] > This targets `dotnet-v7`, which collects the .NET docs for sentry-dotnet 7.0.0. #20641 merges that branch into `master` when 7.0.0 ships, so this PR can merge into `dotnet-v7` as soon as it's approved. ## DESCRIBE YOUR PR Adds a Generic Host guide for `Sentry.Extensions.Hosting`, which sentry-dotnet 7.0.0 adds (getsentry/sentry-dotnet#5739). In 7.0.0, `Logging.AddSentry()` no longer initializes the SDK. Worker services, console apps on the generic host, Windows services and Azure Functions (isolated) apps call `UseSentry` from this package instead. The page is written for 7.x. The docs aren't versioned, so this goes live with the rest of the 7.0.0 docs. The guide follows the quick start template from #19990 and covers: - `UseSentry` on `IHostApplicationBuilder` and `IHostBuilder`, the `Sentry` and `Logging:Sentry` sections, and why not to call `Logging.AddSentry()` as well - the host environment, `"Dsn": ""`, and when the SDK starts (`Build()`) and closes (`ApplicationStopped`) - `ClearProviders()` ordering (getsentry/sentry-dotnet#5772, getsentry/sentry-dotnet#5776, getsentry/sentry-dotnet#5789, getsentry/sentry-dotnet#5821) - ASP.NET Core and MAUI apps, and the static `UseSentry` call that Aspire's `AddServiceDefaults` needs - the .NET Framework gap, with the `SentrySdk.Init` and `Logging.AddSentry()` fallback and its `HubAdapter.Instance` registrations (getsentry/sentry-dotnet#5740) - replacing `SentrySdk.Init`, briefly. The migration guide (#20143) covers upgrades. It also adds `platform-includes/configuration/config-intro/dotnet.extensions-hosting.mdx`, so the guide's Options page starts with `UseSentry` instead of `SentrySdk.Init`. Closes getsentry/sentry-dotnet#5707 ### Notes for review - **Registration.** A new .NET guide only needs its `index.mdx`. The platform key `dotnet.extensions-hosting` comes from the folder name, guides without `sidebar_order`, like the other .NET guides, are listed by title, and the icon falls back to the .NET one, as for the Microsoft.Extensions.Logging, Serilog and NLog guides. The page is new, so it needs no redirects. - **Package version.** The install snippets use `packages.version('sentry.dotnet')`, because the release registry has no `sentry.dotnet.extensions.hosting` entry yet. Until 7.0.0 is out, the preview shows 6.12.1, which doesn't exist for this package. Once the registry has the package, switch to its own key. The `sdk:` frontmatter already uses `sentry.dotnet.extensions.hosting` (from `Constants.cs`). Without a registry entry, the page just has no package details box. - **Shared includes that render wrongly for `dotnet.extensions-hosting`.** I left them alone, since other PRs own them: - `platform-includes/logs/setup/dotnet.mdx` falls into the `SentrySdk.Init` section instead of `UseSentry` with `EnableLogs`. #19925 is adding the key to the host sections. - `platform-includes/logs/options/dotnet.mdx` shows the generic `EnableLogs` text and leaves out "Configure Microsoft.Extensions.Logging Filters". Same PR. - `platform-includes/logs/usage/dotnet.mdx` shows only the `SentrySdk.Logger` APIs. The key belongs in the `ILogger` section too. - `platform-includes/logs/requirements/dotnet.mdx` says logs need SDK version 5.14.0. This package starts at 7.0.0. - **Additions to the brief from the `version7` source:** - `"Dsn": ""` turns the SDK off, but `SENTRY_DSN` still wins over an empty `Dsn` (`SettingLocator.GetDsn`). The page says so. - `Logging:Sentry` only accepts `LogLevel`, `MinimumBreadcrumbLevel` and `MinimumEventLevel`. Any other key makes `Build()` throw `NotSupportedException`. With no DSN anywhere, `Build()` throws `ArgumentNullException`. - Calling `Sentry.AspNetCore`'s `UseSentry` twice still sends each error twice (a follow-up in getsentry/sentry-dotnet#5739). The Aspire section says not to call it again in `Program.cs`. - **Azure Functions** gets one line in the intro. The Azure Functions guide still shows `logging.AddSentry(...)`. #19925 owns it. - **Links to add once the other PRs merge:** - Microsoft.Extensions.Logging guide: send generic host apps here, from the "If you use a host integration such as ASP.NET Core or MAUI" paragraph. Its `Sentry.Samples.GenericHost` sample link belongs here too, since the sample now calls `UseSentry`. - Azure Functions guide: link here from the `UseSentry` setup. - `platform-includes/logs/integrations/dotnet.mdx`: add Generic Host to the list. - `docs/product/logs/getting-started/index.mdx` and `docs/product/metrics/getting-started/index.mdx`: add Generic Host to the .NET lists. - Migration guide, "Generic Host Apps Call UseSentry": link to this page. - The sample link points at `main`, where `Sentry.Samples.GenericHost` keeps the 6.x setup until `version7` is merged. - The C# snippets compile against `version7`, on net10.0, and on net48 for the `IHostBuilder` example and the .NET Framework fallback. On net48, `UseSentry` on `HostApplicationBuilder` fails with CS1929, as the page says. ## 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. - [x] Urgent deadline (GA date, etc.): 2026-11-30 - [ ] Other deadline: YYYY-MM-DD - [ ] No deadline: Not urgent, can wait up to 1 week+ 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Ricardo Colombo Oliveira <github@ricoliv.com>
…20642) > [!NOTE] > This targets `dotnet-v7`, which collects the .NET docs for sentry-dotnet 7.0.0. #20641 merges that branch into `master` when 7.0.0 ships, so this PR can merge into `dotnet-v7` as soon as it's approved. ## DESCRIBE YOUR PR The MAUI guide doesn't say which .NET and OS versions `Sentry.Maui` supports, and it still lists Tizen, which the SDK dropped in 4.0. This adds a Supported Versions section for 7.x and removes Tizen from the feature list. The docs aren't versioned, so the section is written for 7.x, with a "Changed in Version 7.0.0" note that sends 6.x readers to the migration guide. The new section lists: - .NET 10 and .NET 11 - the minimum Android API level and the minimum iOS, Mac Catalyst and Windows versions for each - the Xcode version, which the .NET iOS and Mac Catalyst workloads set. It links to the dotnet/macios releases, which name it for each release. Closes getsentry/sentry-dotnet#5714 ### Notes for review - The values come from `Directory.Build.props` on `version7` (51e7d99f). They match the `SupportedOSPlatform` attributes in the 7.0.0-rc.2 `Sentry.Maui` assemblies, and the platform table in the migration guide's "Supported .NET Versions and Platforms" section, which has no Windows row. - James asked on the issue to [ship this with the 7.0 docs](getsentry/sentry-dotnet#5714 (comment)), so the page only shows the 7.x values. - The 6.x note names only the .NET versions. The iOS minimum changed during 6.x, from 13.0 in 6.0.0 to 15.0 by 6.5.0, so one set of 6.x minimums would be wrong for part of 6.x. - The page doesn't pin an Xcode version. The Sentry packages don't check it, and the required Xcode changes between workload releases for the same .NET version. .NET 10 has workload releases for both Xcode 27.0 and 27.1, for example. - #20240 adds a line under the intro saying `Sentry.Maui` 6.x needs .NET MAUI 9 or later. Once it's on `master` and merged into `dotnet-v7`, that line should go, since this section covers it. - The issue mentions that the .NET guides for Apple and Android have the same gap. This PR only covers the MAUI guide, which is what the issue scopes. ## 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. - [x] Urgent deadline (GA date, etc.): 2026-11-30 - [ ] Other deadline: YYYY-MM-DD - [ ] No deadline: Not urgent, can wait up to 1 week+ Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
1 of 6 tasks
Brings in #20240. Dropped its Sentry.Maui 6.x version line, which the Supported Versions section already covers for 7.0.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1 of 3 tasks
….0 (#19960) > [!NOTE] > This targets `dotnet-v7`, which collects the .NET docs for sentry-dotnet 7.0.0. #20641 merges that branch into `master` when 7.0.0 ships, so this PR can merge into `dotnet-v7` as soon as it's approved. ## DESCRIBE YOUR PR Documents how the .NET SDK resolves its default release and environment from 7.0.0 on (getsentry/sentry-dotnet#5671 and getsentry/sentry-dotnet#5703). The .NET docs aren't versioned, so the text is written for 7.x, with a short "Before version 7.0.0" note where a 6.x reader would otherwise be misled. - **Options > `Release`**: `SENTRY_RELEASE` is read first, then the app package on Android, iOS and Mac Catalyst, or the entry assembly elsewhere. Removes the JavaScript SDK's `window.SENTRY_RELEASE` aside. - **Options > `Environment`**: the precedence (code or configuration, `SENTRY_ENVIRONMENT`, then the host environment in ASP.NET Core, Blazor WebAssembly and Google Cloud Functions, then `debug`/`production`), the casing rule and `AdjustStandardEnvironmentNameCasing`, and that `Scope.Environment` now applies to every kind of telemetry, with `null` clearing it. - **Releases page** (`set-release` include): adds the Android, iOS and Mac Catalyst default, `<package-id>@<version>+<build>`, and where its parts come from. - **Environments page** (`set-environment` include): points to the option for the defaults, and shows overriding the environment on the scope. Closes getsentry/sentry-dotnet#5709 ### Notes for review All of this was checked against the `version7` source rather than the issue text. Where the two differ: - The app-package release default also applies on **Mac Catalyst**, not just Android and iOS. It sits behind `#if ANDROID || __IOS__`, and the Mac Catalyst SDK defines `__IOS__`. - The issue says `Scope.Release` and `Scope.Distribution` going away means release and distribution "can only be set on `SentryOptions`". That's not quite right: `SentryEvent`, transactions and check-ins still have their own `Release`. These pages don't cover that, and the removal belongs in the migration guide (getsentry/sentry-dotnet#5710). - The host-environment mapping covers every ASP.NET Core `UseSentry` overload, including the `ISentryBuilder` ones that gRPC apps use, so the docs just say "ASP.NET Core". Generic Host apps (worker services) are listed ahead of getsentry/sentry-dotnet#5572, which is expected to map the host environment the same way and merge before 7.0.0. Check that it does before merging this. MAUI still falls back to `debug`/`production`. Left unchanged: - The Google Cloud Functions guide already says "Environment is automatically set (IHostingEnvironment)". That wasn't true in 6.x, but it is from 7.0.0. The ASP.NET Core guide's Environment section is also correct for 7.x. The Blazor WebAssembly guide doesn't mention the environment, and there's no gRPC page. - There's no "Before version 7.0.0" note for Blazor WebAssembly, Google Cloud Functions and the `ISentryBuilder` overloads starting to read the host environment. Add one if you think 6.x readers need it. - Edits to `options.mdx` stay inside the `Release` and `Environment` entries, so they shouldn't conflict with #19897 (Hooks) or #19898 (tracing options). ## 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. - [x] 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](https://github.com/orgs/getsentry/teams/docs) 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Ricardo Colombo Oliveira <github@ricoliv.com> Co-authored-by: ric-oliv <ric-oliv@users.noreply.github.com>
…#19961) > [!NOTE] > This targets `dotnet-v7`, which collects the .NET docs for sentry-dotnet 7.0.0. #20641 merges that branch into `master` when 7.0.0 ships, so this PR can merge into `dotnet-v7` as soon as it's approved. ## DESCRIBE YOUR PR In sentry-dotnet 7.0.0 the Microsoft.Extensions.Logging integration no longer initializes the SDK (getsentry/sentry-dotnet#5595). Generic host apps call `UseSentry` from the new `Sentry.Extensions.Hosting` package instead, which has its own guide (#20311). This updates the parts of getsentry/sentry-dotnet#5706 that #19925 leaves out: - **Microsoft.Extensions.Logging guide**: - Generic host apps, ASP.NET Core and MAUI skip this setup and go to their own guides. The note names generic host apps that used `builder.Logging.AddSentry(...)` on 6.x. - Apps without a host call `SentrySdk.Init`, then `AddSentry()`, on a `LoggerFactory` or their own `ServiceCollection`. If they inject `IHub`, `ISentryClient` or `Func<IHub>`, they register them with `HubAdapter.Instance`, because `AddSentry()` no longer does (getsentry/sentry-dotnet#5740). .NET Framework apps on `Host.CreateApplicationBuilder()` are pointed to the Generic Host guide's .NET Framework section. - Structured logs are always sent on this page, and Configure says how to send fewer. - Removes the DSN in `AddSentry(...)`, `InitializeSdk`, and SDK settings under `Logging:Sentry`. Documents what `Logging:Sentry` still accepts, and `AddLogEntryFilter`. - **Generic Host guide**: the `AddLogEntryFilter` link pointed at `#filters`, which this page no longer has. "Replacing SentrySdk.Init" now says `UseSentry` leaves structured logs off until `EnableLogs` is set. - **ASP.NET Core guide**: `SentryAspNetCoreOptions` now extends `SentryHostOptions`, not `SentryLoggingOptions`. Closes getsentry/sentry-dotnet#5706 ### Notes for review - Checked against `origin/version7` (51e7d99fb), which includes getsentry/sentry-dotnet#5869: - Every C# snippet on the Microsoft.Extensions.Logging guide compiles on net10.0 with only `Sentry.Extensions.Logging` referenced. - With `SentrySdk.Init` and `AddSentry()`, every `ILogger` entry is sent as a structured log without `EnableLogs`. - `Logging:Sentry`, added with `AddConfiguration`, is read: `MinimumEventLevel` applies, and a category entry under `LogLevel` drops only that category's structured logs. A `Dsn` key there throws `NotSupportedException` from `LoggerFactory.Create`. - Without the `HubAdapter` lines, a service that injects `IHub` fails with `Unable to resolve service for type 'Sentry.IHub' while attempting to activate ...`. - `ClearProviders()` moved out with the generic host content. It applies to ASP.NET Core's `UseSentry` too, which the ASP.NET Core guide doesn't mention yet. - `Filters` was always internal. The page shows `AddLogEntryFilter`. - The ASP.NET Core paragraph leaves out namespaces. `SentryHostOptions` is still in `Sentry.Extensions.Logging` on `version7`. - On 6.x, `AddSentry()` after `SentrySdk.Init` initializes the SDK again without a DSN, and that throws. That's why the 7.0.0 note tells 6.x users to set the DSN in `AddSentry(...)` instead. - #20240 also edits this page, against 6.x. Whichever merges second needs a merge from `master`. This PR leaves the `Sentry` prefix alert alone, which #20240 rewrites. ## 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. - [x] Urgent deadline (GA date, etc.): 2026-11-30 - [ ] Other deadline: YYYY-MM-DD - [ ] No deadline: Not urgent, can wait up to 1 week+ 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Ricardo Colombo Oliveira <github@ricoliv.com>
> [!NOTE] > This targets `dotnet-v7`, which collects the .NET docs for sentry-dotnet 7.0.0. #20641 merges that branch into `master` when 7.0.0 ships, so this PR can merge into `dotnet-v7` as soon as it's approved. ## 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** (#5560 was backported in getsentry/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. - [x] 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](https://github.com/orgs/getsentry/teams/docs) 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: ric-oliv <5938598+ric-oliv@users.noreply.github.com>
> [!NOTE] > This targets `dotnet-v7`, which collects the .NET docs for sentry-dotnet 7.0.0. #20641 merges that branch into `master` when 7.0.0 ships, so this PR can merge into `dotnet-v7` as soon as it's approved. ## DESCRIBE YOUR PR Updates the .NET logging docs for sentry-dotnet 7.0.0. In 7.0.0, `SentryOptions.EnableLogs` and `SentryOptions.EnableMetrics` are removed, Serilog, NLog and log4net send logs as soon as they're added, and the Serilog, NLog, log4net and Microsoft.Extensions.Logging integrations no longer initialize the SDK. The pages are written for 7.x. The docs aren't versioned, so this goes live with the rest of the 7.0.0 docs. - **Logs setup, options and usage** (`platform-includes/logs/*/dotnet.mdx`): `EnableLogs` is only documented on the host options (ASP.NET Core, AWS Lambda, Azure Functions, Blazor Server, Blazor WebAssembly, MAUI). The Serilog, NLog, log4net and Microsoft.Extensions.Logging snippets call `SentrySdk.Init` and add the integration without a switch. The host and Serilog/NLog/log4net sections explain when `EnableLogs` sends each log twice. - **Serilog, NLog and log4net guides**: initialize Sentry first, then add the sink/target/appender. Removed initializing through the integration, `InitializeSdk`, and the DSN, environment, release and `<options>` settings on the NLog target and log4net appender. Documented Serilog's `UseSerilog()` and the one-time standard-error warning. - **NLog includes**: removed `dsn` from the set-tag and set-user variants, including the `options.Dsn` that #19990 added to the set-tag snippet. Deleted the set-environment, set-release and config-intro variants, so the NLog guide uses the generic .NET pages, which set these on the options passed to `SentrySdk.Init`. - **Blazor WebAssembly**: removed `builder.Logging.AddSentry(o => o.InitializeSdk = false)`, which no longer compiles and was already redundant with `UseSentry`. - **Azure Functions**: installs `Sentry.Extensions.Hosting` instead of `Sentry.Extensions.Logging`, and starts Sentry with `.UseSentry(options => ...)` on the `HostBuilder` chain instead of `logging.AddSentry(options => ...)`. `EnableLogs = true` stays in the snippet, now on `SentryGenericHostOptions`. Apps with the ASP.NET Core integration (`ConfigureFunctionsWebApplication()`) call the same `UseSentry`. The "Changed in Version 7.0.0" alert covers 6.x, which has no hosting package. - **ASP.NET**: removed `EnableLogs` from the `SentrySdk.Init` snippet and from the list of features the snippet turns on. Send Logs now says the Serilog, NLog and log4net integrations send logs as soon as they're added, and points to `SetBeforeSendLog` for dropping them. - **Metrics options**: `EnableMetrics` was removed in 7.0.0. Kept the advice to return `null` from `SetBeforeSendMetric`. Closes getsentry/sentry-dotnet#5698 Part of getsentry/sentry-dotnet#5706 ### Notes for review - The Serilog, NLog and log4net guides each have a new "Capturing Startup Crashes" subsection for apps that want crashes from before `UseSentry` starts Sentry (getsentry/sentry-dotnet#5844). Each calls `SentrySdk.Init` before the builder; the Serilog one does it alongside Serilog's two-stage initialization. The companion samples, getsentry/sentry-dotnet#5847 and getsentry/sentry-dotnet#5866, link to them. - Merged `master` after #19990, which moved the .NET guides to the new quick start template. The Azure Functions and Blazor WebAssembly changes now sit on that template, which already uses `UseOtlp()` for Azure Functions. - The Microsoft.Extensions.Logging snippet on the logs setup page uses `SentrySdk.Init` plus `builder.Logging.AddSentry()`, and says in one sentence that generic-host apps use `UseSentry` from `Sentry.Extensions.Hosting` instead. The Microsoft.Extensions.Logging guide page is updated in #19961, so this PR only partly covers #5706. - Azure Functions follows getsentry/sentry-dotnet#5739. It adds `Sentry.Extensions.Hosting` with `UseSentry`, and says Azure Functions (isolated) apps use it, also with the ASP.NET Core integration. Checked against `version7`: `SentryGenericHostOptions.EnableLogs` defaults to `false`, and `UseSentry` registers Sentry's `ILogger` providers. `ConfigureFunctionsWorkerDefaults()` and `ConfigureFunctionsWebApplication()` return `IHostBuilder`, so the snippet binds to `UseSentry(IHostBuilder, Action<SentryGenericHostOptions>)`. The SDK starts in `Build()` and closes when the host stops. The `version7` sample makes the same call. getsentry/sentry-dotnet#5740 stops `Logging.AddSentry()` from registering `IHub`, so `UseSentry` is now also what puts it in DI. - The logs setup and options includes list `dotnet.extensions-hosting` in the `UseSentry` + `EnableLogs` sections, the `appsettings.json` tab and the Serilog/NLog/log4net expandables. That's the platform key of the generic-host guide coming in a separate PR, so that PR doesn't need to edit these files. Nothing links to it yet, since the page doesn't exist on this branch. Azure Functions isn't in the Serilog/NLog/log4net expandables: their snippets use `builder.Services` and `builder.Logging`, which a `HostBuilder` chain doesn't have. - "Before 7.0.0" notes appear only where a 6.x reader following the page would silently get no logs, or replace their SDK setup: the Serilog/NLog/log4net and Microsoft.Extensions.Logging sections of the logs setup page, the `EnableLogs` option, and the Azure Functions guide. - #5698 says an ASP.NET Core app that also uses the Serilog sink sends each log twice with `EnableLogs` on. That only happens when `ILogger` entries reach both Sentry's provider and Serilog. I checked against `version7`: one `LogInformation` call was sent once with `builder.Host.UseSerilog()`, which replaces the logger factory, and twice with `builder.Logging.AddSerilog()`. The same applies to NLog and log4net when they're registered as `ILogger` providers. So the docs name that case, registering the framework as an `ILogger` provider (for example `builder.Logging.AddSerilog()`), and say to leave `EnableLogs` off then. - #5706 describes `UseSerilog()` as the replacement for `ApplySerilogScopeToEvents()`. On `version7` it's optional: if the app doesn't call it, the sink registers the scope processor itself once it's running, so only events captured before then miss the `LogContext` properties. The guide says so. - Changes beyond the two issues: - `dotnet.blazor-server` added to the `EnableLogs` sections. It uses `Sentry.AspNetCore`'s `UseSentry`, but it fell into the plain `SentrySdk.Init` section, which now says logging integrations need no switch. - log4net logs usage no longer mentions `SentryAppender.Environment`, which 7.0.0 removes (getsentry/sentry-dotnet#5592). - The NLog set-user snippet used `new User`. That type doesn't exist, so it's now `SentryUser`. - The Azure Functions snippet drops `TracesSampleRate` and `DisableSentryHttpMessageHandler`, which the `version7` sample still sets. Under `UseOtlp()` Sentry creates no transactions of its own, so `TracesSampleRate` has no effect. `SentryHttpMessageHandler` already skips span creation, so disabling it would only stop it propagating `sentry-trace`. #19924 documents both. - The C# and F# snippets I added or changed compile against the `version7` sources. The Azure Functions and `UseSentry` ones compile against the 7.0.0-rc.2 packages, whose public API matches `version7`. ## 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. - [x] Urgent deadline (GA date, etc.): 2026-11-30 - [ ] Other deadline: YYYY-MM-DD - [ ] No deadline: Not urgent, can wait up to 1 week+ 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
… SDK 7.0.0 (#20715) > [!NOTE] > This targets `dotnet-v7`, which collects the .NET docs for sentry-dotnet 7.0.0. #20641 merges that branch into `master` when 7.0.0 ships, so this PR can merge into `dotnet-v7` as soon as it's approved. ## DESCRIBE YOUR PR Adds a "Clearing Logger Providers" section to the ASP.NET Core guide, matching the one in the Generic Host guide (#20311). ASP.NET Core's `UseSentry` registers Sentry's logger providers the same way, so `ClearProviders()` after it removes them and `ILogger` entries stop reaching Sentry. The section says to call `UseSentry` after `ClearProviders()`, or to add the providers back with `builder.Logging.AddSentry()`. Closes getsentry/sentry-dotnet#5911 ### Notes for review - Checked with a web app on `Sentry.AspNetCore` 7.0.0-rc.3. `version7` hasn't changed this code since rc.3. - `ClearProviders()` before `UseSentry`: a logged warning becomes an event. - `ClearProviders()` after `UseSentry`: the SDK starts, but the warning doesn't reach Sentry. With `Debug` on, the SDK logs the "logger providers were removed" warning during `StartAsync`. - `AddSentry()` after `ClearProviders()`: the warning becomes an event again, using `MinimumEventLevel` from the `UseSentry` options. - Both snippets compile on net10.0. - The Generic Host guide says the warning comes "during `Build()`". Here it's "when the app starts", because ASP.NET Core starts the SDK when the host starts (getsentry/sentry-dotnet#5815). - The snippet uses `builder.WebHost.UseSentry()` to match the rest of this page, which doesn't use the 7.0 `builder.UseSentry()` overload yet. ## 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. - [x] Urgent deadline (GA date, etc.): 2026-11-30 - [ ] Other deadline: YYYY-MM-DD - [ ] No deadline: Not urgent, can wait up to 1 week+ 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Ricardo Colombo Oliveira <github@ricoliv.com>
…s.Logging for SDK 7.0.0 (#20752) <!-- Keep the urgency section so automation can prioritize this PR. You may delete other sections you don't need. --> ## DESCRIBE YOUR PR On .NET Framework, `Sentry.Extensions.Logging` brings in `Microsoft.Extensions.Logging` 2.1. That version has no `LoggerFactory.Create`, and the app doesn't get `ServiceCollection` either, so neither setup example on the MEL page compiles there. Installing the `Microsoft.Extensions.Logging` package fixes both. This adds a line saying so under Install. getsentry/sentry-dotnet#5921 sends callers of `ILoggerFactory.AddSentry()` to `LoggerFactory.Create`, so those apps end up on this page. It targets `dotnet-v7`, so it goes live with the rest of the 7.0.0 docs in #20641. Refs getsentry/sentry-dotnet#5921 ## 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. - [x] Urgent deadline (GA date, etc.): the .NET SDK 7.0.0 release, with #20641 - [ ] 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](https://github.com/orgs/getsentry/teams/docs) ## EXTRA RESOURCES - [Sentry Docs contributor guide](https://docs.sentry.io/contributing/) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
<!-- Keep the urgency section so automation can prioritize this PR. You may delete other sections you don't need. --> ## DESCRIBE YOUR PR getsentry/sentry-dotnet#5913 added `MinimumLogLevel` to the NLog target. It defaults to `Info`, and `enableLogs="false"` now turns logs off. The NLog pages on `dotnet-v7` were written before it merged, so they still said the target sends every entry it receives as a log and that `enableLogs` has no effect. This documents the new option in the NLog guide and on the logs page, says that logs start at `Info`, and fixes the `enableLogs` lines in the migration guide. The migration guide also notes that 6.x sent every entry once logs were on, so apps that want `Trace` or `Debug` logs need to lower `minimumLogLevel`. With `Info` as the default, the NLog snippets go back to a plain `config.AddSentry()`. It targets `dotnet-v7`, so it goes live with the rest of the 7.0.0 docs in #20641. Refs getsentry/sentry-dotnet#5913 ## 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. - [x] Urgent deadline (GA date, etc.): the .NET SDK 7.0.0 release, with #20641 - [ ] 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](https://github.com/orgs/getsentry/teams/docs) ## EXTRA RESOURCES - [Sentry Docs contributor guide](https://docs.sentry.io/contributing/) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…or SDK 7.0.0 (#20742) > [!NOTE] > This targets `dotnet-v7`, which collects the .NET docs for sentry-dotnet 7.0.0. #20641 merges that branch into `master` when 7.0.0 ships, so this PR can merge into `dotnet-v7` as soon as it's approved. ## DESCRIBE YOUR PR #20311 added the Generic Host guide (`/platforms/dotnet/guides/extensions-hosting/`). Only the Microsoft.Extensions.Logging guide linked to it. This adds links from the other pages that tell generic host apps to call `UseSentry`: - **Azure Functions guide**: links the guide for the options `UseSentry` takes. - **Logs**: the Generic Host paragraph in the Microsoft.Extensions.Logging logs setup, and a Generic Host entry in the .NET logs integrations list. - **Logs and Metrics getting-started pages**: a Generic Host entry in the .NET lists. - **7.0 migration guide**: the overview, "Generic Host Apps Call UseSentry", and the Generic Host row of the table in "Logging Integrations No Longer Initialize Sentry". - **Environment option**: links ".NET Generic Host". Closes getsentry/sentry-dotnet#5912 ### Notes for review - "Update All Sentry Packages Together" names `Sentry.Extensions.Hosting` too, but it already links to "Generic Host Apps Call UseSentry", which now links the guide. I left it alone rather than add a second link in the same paragraph. - `dotnet.extensions-hosting` has no entry in `platformIcon.tsx`, so the new list entries fall back to the .NET icon, the same as Microsoft.Extensions.Logging. ## 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. - [x] Urgent deadline (GA date, etc.): 2026-11-30 - [ ] Other deadline: YYYY-MM-DD - [ ] No deadline: Not urgent, can wait up to 1 week+ 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
|
Getting ready to monitor this change · Rollout details
|
1 of 6 tasks
## DESCRIBE YOUR PR This gets the 6.x to 7.x migration guide for the Sentry SDK for .NET ready for 7.0.0, following #20143. It targets `dotnet-v7`, so it goes live with the rest of the 7.0.0 docs in #20641. - Removes the release candidate alert. Its note about restore error NU1605 still applies to .NET 11 apps on 7.0.0, so it moves to "Supported .NET Versions and Platforms". - Adds "Category Log Levels No Longer Filter Breadcrumbs and Events", for getsentry/sentry-dotnet#5869. Entries under `Logging:Sentry:LogLevel` now only filter logs, so an app that silenced a category gets that category's breadcrumbs and events. The section shows `AddLogEntryFilter` for apps that want the old filtering. - Adds `GetInternalSentryOptions` to "Other Removed and Internal APIs", for getsentry/sentry-dotnet#5862, and points to the new `GetDiagnosticLogger()` extension on `IHub`. - Links the Generic Host guide from #20311 and the MAUI guide's supported versions from #20642, which are both on `dotnet-v7`. These two SDK PRs are the only changes merged on `version7` since 7.0.0-rc.3 that affect people upgrading from 6.x. Two things depend on how 7.0.0 ships: - The NU1605 note assumes the `net11.0` builds depend on the stable .NET 11 packages. On `version7` today, they depend on .NET 11 RC 3. - The `LogLevel` fix also landed on 6.x in getsentry/sentry-dotnet#5872, which isn't released yet. The section says "6.12.1 and earlier", so it stays correct whether or not a 6.x release ships first. Refs getsentry/sentry-dotnet#5710 ## 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. - [x] Urgent deadline (GA date, etc.): 2026-10-10 - [ ] 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](https://github.com/orgs/getsentry/teams/docs) 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: James Crosswell <jamescrosswell@users.noreply.github.com> Co-authored-by: Alex Krawiec <alex.krawiec@sentry.io>
…tions package for SDK 7.0.0 (#20780) <!-- Keep the urgency section so automation can prioritize this PR. You may delete other sections you don't need. --> ## DESCRIBE YOUR PR Three fixes I found reviewing #20641 against the 7.0.0 packages: - The Serilog guide said `Log.CloseAndFlush()` flushes Sentry. The 7.0.0 sink doesn't own the SDK anymore, so it doesn't. The guide now says to dispose what `SentrySdk.Init` returns or call `SentrySdk.Flush()`, like the migration guide's "Logging Frameworks No Longer Close Sentry". - The Serilog snippet for apps that call `UseSentry` didn't compile (CS1061 on `AddSerilog` and `UseSerilog`) without `using Serilog;` and `using Sentry.Serilog;`. It shows on the Serilog guide and on every host's logs page. - The Azure Functions sidebar showed the deprecated `Sentry.Azure.Functions.Worker` 5.16.2. The guide installs `Sentry.Extensions.Hosting` now, so the sidebar points there. It targets `dotnet-v7`, so it goes live with the rest of the 7.0.0 docs in #20641. ## 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. - [x] Urgent deadline (GA date, etc.): the .NET SDK 7.0.0 release, with #20641 - [ ] 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](https://github.com/orgs/getsentry/teams/docs) ## EXTRA RESOURCES - [Sentry Docs contributor guide](https://docs.sentry.io/contributing/) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…ppet The guide's Verify section says to dispose the object that SentrySdk.Init returns before a short-lived app exits. The Configure snippet now keeps that object with using var, like the startup-crash snippet on the same page and the migration guide. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…for SDK 7.0.0 (#20781) - The .NET tabs in the get-started logs and metrics guides used APIs that don't exist in any SDK version. They now use LogInfo, LogWarning and LogError with a SentryLog callback, and EmitCounter, EmitGauge and EmitDistribution with an attributes dictionary. The development configuration no longer sets EnableLogs, which 7.0.0 removed from SentryOptions. - TraceIgnoreStatusCodes shows the 7.0.0 default and an appsettings.json example. - The OpenTelemetry install note says 1.12.0, the version Sentry.OpenTelemetry depends on. - The ASP.NET Core options page no longer shows an ASP.NET Core 2.3 on .NET Framework setup, which fails to restore with NU1202. - The Azure Functions options page shows UseSentry instead of the generic SentrySdk.Init example. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Member
Author
|
This one is ready for review and merge now, @getsentry/docs 🙏 |
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ric-oliv
enabled auto-merge (squash)
November 13, 2026 19:16
jamescrosswell
approved these changes
Nov 15, 2026
jamescrosswell
left a comment
Collaborator
There was a problem hiding this comment.
Everything here has been reviewed/approved prior to being merged into this branch.
Any pending PRs targeting this branch can retarget master, now that the version 7.0.0 release is out (no need to queue these up anywhere).
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
DESCRIBE YOUR PR
This updates the .NET docs for sentry-dotnet 7.0.0, which has been on NuGet since 2026-11-12. Each change was reviewed in its own PR against the
dotnet-v7branch, so the 7.x docs go live together:Issues this closes
Closes getsentry/sentry-dotnet#5710
The other docs issues for 7.0.0 were closed when their PRs merged into
dotnet-v7.Before merging
includes/dotnet-v7-migration-overview.mdx.masteris merged intodotnet-v7, and the Vercel preview looks right.Closesline for every issue that's still open.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-DDwith the due date. You can update this information later by editing the PR description.