\.NET 6: Ensuring Scoped Log Levels Apply to All Logging Providers

The direct answer

ILogger.BeginScope does not change the minimum log level. It only attaches ambient state (key/value data) to log entries. Whether that state is honored at all is up to each provider: the built-in console provider includes scopes in output only when IncludeScopes = true, and no built-in provider in .NET 6 interprets scope contents as a level filter. So there is no switch that makes "scoped log levels" apply to all providers — you have to implement the filtering yourself, either in a wrapper provider or via log filtering rules.

What is confirmed vs. assumed

Confirmed, well-established behavior: scopes flow through ILogger.BeginScope to every provider that opts in to reading them; filtering in Microsoft.Extensions.Logging is category/provider-based via LoggerFilterOptions, not scope-based. I'm assuming you're on the stock Microsoft.Extensions.Logging stack (console/debug providers), not Serilog/NLog, which have their own enrichment models. If you're actually on Serilog, the answer changes — say so.

Recommended strategy

Don't try to make scopes control levels. Instead:

1. Use category-based filtering for noise suppression. This is honored by every provider that goes through ILoggerFactory:

builder.Logging.AddFilter("MyApp.NoisyComponent", LogLevel.Warning);
builder.Logging.AddFilter("Microsoft.EntityFrameworkCore", LogLevel.Warning);

1. For block-scoped suppression, wrap the provider. Create a custom ILoggerProvider that decorates the real logger, reads a level value out of the current scope via ISupportExternalScope/scope state, and drops messages below it. Register it early in Program.cs before the host builds the service provider. Keep it simple: store the threshold in an AsyncLocal<LogLevel?> set by a small helper that mimics BeginScope semantics, and check it in IsEnabled/Log.
2. Never suppress Error/Critical. Hard-code a floor in the wrapper so critical alerts always pass regardless of the scoped threshold.

DiagnosticSource notes

Your constraints are correct: DiagnosticSource.AllListeners subscriptions must be registered before the sources you care about start emitting — effectively at process startup, before the host runs. Subscribe with a predicate so you only pay for relevant sources, and route those events through ILogger at Information or higher so they respect your normal filter rules instead of bypassing them.

Verification

In a scratch console app: configure AddFilter("*", LogLevel.Warning), log at Debug inside and outside a BeginScope, and confirm output is identical — proving scopes don't filter. Then add your wrapper and confirm scoped suppression works and that an Error log inside the scope still appears. Also verify scopes are disposed (no growing scope chain) under load.