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
If an operation encounters an error (and enters the Faulted state) it should log an error message.
However there's an issue that can cause the operation to silently fail (never logging the error), this occurs when:
An egress provider is used for the operation
The exception thrown by the operation isn't one of the following: ArgumentException, DiagnosticsClientException, InvalidOperationException, OperationCanceledException, MonitoringException, ValidationException, UnauthorizedAccessException
This is due to us incorrectly re-using ActionContextExtensions.InvokeAsync for egress operations, which does filtering on the exception thrown of an arbitrary action to determine if it should be logged or not:
Description
If an operation encounters an error (and enters the
Faulted
state) it should log an error message.However there's an issue that can cause the operation to silently fail (never logging the error), this occurs when:
ArgumentException
,DiagnosticsClientException
,InvalidOperationException
,OperationCanceledException
,MonitoringException
,ValidationException
,UnauthorizedAccessException
This is due to us incorrectly re-using
ActionContextExtensions.InvokeAsync
for egress operations, which does filtering on the exception thrown of an arbitrary action to determine if it should be logged or not:dotnet-monitor/src/Microsoft.Diagnostics.Monitoring.WebApi/ActionContextExtensions.cs
Lines 43 to 78 in 84b2424
The text was updated successfully, but these errors were encountered: