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
{{ message }}
This repository has been archived by the owner on Jun 10, 2020. It is now read-only.
Is it possible to use an ExceptionTelemetry instance in the case where an exception is present? Exception telemetries provide a nicer experience in UI's such as Visual Studio and the Azure portal.
The text was updated successfully, but these errors were encountered:
This new behavior actually makes less sense if someone uses a global exception filter where all exceptions are tracked in a unified way.
With this new version, I get two exception telemetries (one at the LogError and one in my global exception filter. Of course, in the model I am using (using a global exception filter), I can change my .TrackException() into .LogError()...
I would have considered this as a bigger change than what makes into a .1 upgrade...
When you log an error with an exception through the
ILogger
interface like this:it will use a
TraceTelemetry
instance.Is it possible to use an
ExceptionTelemetry
instance in the case where an exception is present? Exception telemetries provide a nicer experience in UI's such as Visual Studio and the Azure portal.The text was updated successfully, but these errors were encountered: