-
-
Notifications
You must be signed in to change notification settings - Fork 222
WIP: Logs for Sentry.Extensions.Logging
and integrations for Sentry.AspNetCore
and Sentry.Maui
#4193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: feat/logs-initial-api
Are you sure you want to change the base?
WIP: Logs for Sentry.Extensions.Logging
and integrations for Sentry.AspNetCore
and Sentry.Maui
#4193
Conversation
|
||
_ = logging.AddFilter<SentryAspNetCoreLoggerProvider>( | ||
"Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware", | ||
LogLevel.None); | ||
_ = logging.AddFilter<SentryAspNetCoreStructuredLoggerProvider>(static (string? categoryName, LogLevel logLevel) => | ||
{ | ||
return categoryName is null |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
are these guaranteed to be all of the categories we add?
I wonder if there's some "Constant" or something with these, we could reflect on and write a test to make sure we filter all of them out
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm fairly certain ... not quite positive though.
Those are the ILogger<T>
usages that I found in our packages.
I definitely have to add a test for that ... probably as an ASP.NET Core integration test ... I see we have the infrastructure already setup via the "TestUtils" project.
Initial implementation for
Sentry.Extensions.Logging
Initial integrations for
Sentry.AspNetCore
Sentry.Maui
Logs: https://develop.sentry.dev/sdk/telemetry/logs/