Update logs behavior to follow the same opt-in model as `enableMetrics`: * Users are considered opted-in when: * They call the equivalent of `Sentry.logger.*`, or * They explicitly enable a logging integration. * Change default: set enable logs to `true`. * Audit all logging integrations to ensure: * No logs are emitted unless the integration is explicitly enabled. * Update documentation: * Explain new default behavior of `enableLogs`. * Clarify requirement to explicitly enable logging integrations.
Activity
linear-code commentedon May 4, 2026
NET-668
bitsandfoxes commentedon May 6, 2026
As per #5189 (comment), this comes as part of the next mayor at the end of the year.
UseSentryare ignored by the logger providers #5639test(serilog): Log from an app category in the ASP.NET Core test (#5641)
test(serilog): Log from an app category in the ASP.NET Core test (#5641)
feat(logging): Add EnableLogs to SentryHostOptions
chore(samples): Set EnableLogs again in the framework samples
feat(logging): Add EnableLogs to SentryHostOptions
chore(samples): Set EnableLogs again in the framework samples
feat(logging)!: Move EnableLogs to the ASP.NET Core, MAUI and Blazor …
feat!: EnableLogs moves from SentryOptions to ASP.NET Core, MAUI and …