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
Is your feature request related to a problem? Please describe the problem.
Follow up to #46280 which added IExceptionHandler to support addressing various kinds of app exceptions in a centralized way. The partner that made this request also has observability requirements. There's already a .NET counter for the number of exceptions being thrown, but what's missing is how they were handled.
The current logic uses the new tag feature to flow the exception down to the host.
A metric that indicates which of these three things happened:
An exception handler handled the exception. (which?)
Exception handling was skipped because the response was already started.
No exception handlers were able to handle the exception. (Unhandled).
This likely needs a new metric rather than contributing to an existing one (hosting), there are limits to the number of dimensions you should add to a metric (25?).
Is there an existing issue for this?
Is your feature request related to a problem? Please describe the problem.
Follow up to #46280 which added IExceptionHandler to support addressing various kinds of app exceptions in a centralized way. The partner that made this request also has observability requirements. There's already a .NET counter for the number of exceptions being thrown, but what's missing is how they were handled.
The current logic uses the new tag feature to flow the exception down to the host.
aspnetcore/src/Middleware/Diagnostics/src/DiagnosticsTelemetry.cs
Line 18 in c2488ee
Describe the solution you'd like
A metric that indicates which of these three things happened:
This likely needs a new metric rather than contributing to an existing one (hosting), there are limits to the number of dimensions you should add to a metric (25?).
Additional context
CC: @JamesNK
The text was updated successfully, but these errors were encountered: