You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default the package should exclude an internal error log from EF Core. It logs as error (with a stack trace that is not helpful) right before throwing.
The user code would anyway log that error once it captures the exception. Or Sentry would log that anyway if unhandled.
@bruno-garcia This might need an integration test (we'd want to monitor the behaviour inside an asp.net core request both with and without a try-catch in the Action), but I believe there isn't one set up currently so this might be a problem.
Yes. The Sentry SDK is doing it's job and logging something as it was provided to it. EF Core though is logging in the middle which doesn't include the stack trace. This issue suggest just dropping that log entry altogether (since it'll be logged once rethrown)
Please mark the NuGet packages used:
By default the package should exclude an internal error log from EF Core. It logs as error (with a stack trace that is not helpful) right before throwing.
The user code would anyway log that error once it captures the exception. Or Sentry would log that anyway if unhandled.
Thanks @kanadaj for raising and proposing the filter.
The text was updated successfully, but these errors were encountered: