[ric-oliv]

After UseSentry and then ClearProviders(), builder.Logging.AddSentry() now adds back the logger providers that UseSentry registered, so logger.LogError(...) reaches Sentry again. Until now, AddSentry() saw the marker that ClearProviders() left behind, installed two NullLoggerProviders and logged a warning telling people to remove the call. Reordering the calls was the only way out.

AddSentry() rebuilds the host's own providers rather than falling back to the plain SentryLoggerProvider pair. That way the host's options still apply, such as MinimumEventLevel set in UseSentry, and so do the filter rules that target the host's provider types, which ClearProviders() doesn't remove. In ASP.NET Core, one of those rules keeps the logger from capturing exceptions that UseExceptionHandler logs, so SentryMiddleware reports them with the right mechanism (#1284). Rebuilding the ASP.NET Core provider also starts the SDK during Build(), the same as without the clear.

To make that possible, each host integration now registers its providers through HostLoggerProviders, which replaces HostLoggerProvidersMarker. It keeps the provider factories and the exact descriptors it added. When AddSentry()'s providers are created, it checks the captured service collection for those descriptors, so calling AddSentry() before UseSentry still sends each error once. ASP.NET Core, Google Cloud Functions and MAUI now register their providers through factories instead of by type, and no extra provider joins the logging pipeline.

Two smaller changes, both logged through the SDK's diagnostic logger:

• The warning for a redundant AddSentry() no longer tells people to remove the call. It says the call has no effect and its options are ignored.
• A new warning says when the options passed to AddSentry() are ignored because it rebuilt the host's providers.

Apps that send logs through NLog or log4net and don't call Logging.AddSentry() are unaffected. UseSentry followed by ClearProviders() without AddSentry() still drops the ILogger integration without a word. A diagnostic warning for that comes next.

This is part 2 of the plan in #5755. It builds on #5772, which starts the SDK during Build().

Refs #5755

[codecov]

Codecov Report

❌ Patch coverage is 96.15385% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 76.22%. Comparing base (2194c92) to head (49f5090).
⚠️ Report is 2 commits behind head on version7.

Files with missing lines	Patch %	Lines
...try.Extensions.Logging/LoggingBuilderExtensions.cs	88.88%	0 Missing and 2 partials ⚠️
...c/Sentry.Extensions.Logging/HostLoggerProviders.cs	94.73%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##           version7    #5776      +/-   ##
============================================
+ Coverage     76.17%   76.22%   +0.04%     
============================================
  Files           526      528       +2     
  Lines         19265    19307      +42     
  Branches       3729     3734       +5     
============================================
+ Hits          14676    14716      +40     
  Misses         3734     3734              
- Partials        855      857       +2     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.