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 have a try/catch and in the catch I'm calling _trace.Error($"Error loading user '{emailAddress}'", ex) so the exception is shown as such in the console while debugging. Because of how the webjobs extension pulls out errors to send this is triggering handled exceptions to be logged as if they were unhandled.
I don't think this is a bug but rather something that just catches you off guard when you run across it.
In v3 of the webjobs sdk logging is a first class feature now of which Application Insights has an out of the box implementation. I haven't had a chance to look through this though to see how exceptions are being dealt with.
The text was updated successfully, but these errors were encountered:
I have a try/catch and in the catch I'm calling
_trace.Error($"Error loading user '{emailAddress}'", ex)
so the exception is shown as such in the console while debugging. Because of how the webjobs extension pulls out errors to send this is triggering handled exceptions to be logged as if they were unhandled.I don't think this is a bug but rather something that just catches you off guard when you run across it.
In v3 of the webjobs sdk logging is a first class feature now of which Application Insights has an out of the box implementation. I haven't had a chance to look through this though to see how exceptions are being dealt with.
The text was updated successfully, but these errors were encountered: