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
I'm using your library along with ElasticAPM and the unfortunate combination of both is causing all my handled exceptions to be logged in elastic. I only want unhandled exceptions to be logged so actual exceptions that need attention aren't lost in the noise. Unfortunately the app I work on throws and handles more exceptions that I'd like, and the likelihood of a system wide refactoring anytime soon is unlikely.
The culprit is line 126 of Hellang.Middleware.ProblemDetails.ProblemDetailsMiddleware:
Because the elastic apm automatically adds the AspNetCoreErrorDiagnosticsSubscriber (non-negotiable) then the IsEnabled always returns true and the diagnostic write is always executed.
Is there a workaround for this? or is there scope for this library to accomodate this and allow for this to be toggled on/off? thanks!
The text was updated successfully, but these errors were encountered:
I'm using your library along with ElasticAPM and the unfortunate combination of both is causing all my handled exceptions to be logged in elastic. I only want unhandled exceptions to be logged so actual exceptions that need attention aren't lost in the noise. Unfortunately the app I work on throws and handles more exceptions that I'd like, and the likelihood of a system wide refactoring anytime soon is unlikely.
The culprit is line 126 of Hellang.Middleware.ProblemDetails.ProblemDetailsMiddleware:
Because the elastic apm automatically adds the
AspNetCoreErrorDiagnosticsSubscriber
(non-negotiable) then the IsEnabled always returns true and the diagnostic write is always executed.Is there a workaround for this? or is there scope for this library to accomodate this and allow for this to be toggled on/off? thanks!
The text was updated successfully, but these errors were encountered: