Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve MetricEventSource error message #55319

Merged
merged 1 commit into from
Jul 8, 2021

Conversation

noahfalk
Copy link
Member

@noahfalk noahfalk commented Jul 8, 2021

The Error event wasn't capturing inner exception info in its message. Switching from Exception.Message to
Exception.ToString() captures more useful messages. We no longer split out the stack separately, but that
wasn't important. The error messages are likely only useful for humans anyway.

A failure showed up in CI and it appears the exception is missing inner exception info that would help track it down. The next time this fails we should get better diagnostics.

The Error event wasn't capturing inner exception info
in its message. Switching from Exception.Message to
Exception.ToString() captures more useful messages.
We no longer split out the stack separately, but that
wasn't important. The error messages are likely only
useful for humans anyway.
@ghost
Copy link

ghost commented Jul 8, 2021

Tagging subscribers to this area: @tarekgh, @tommcdon, @pjanotti
See info in area-owners.md if you want to be subscribed.

Issue Details

The Error event wasn't capturing inner exception info in its message. Switching from Exception.Message to
Exception.ToString() captures more useful messages. We no longer split out the stack separately, but that
wasn't important. The error messages are likely only useful for humans anyway.

A failure showed up in CI and it appears the exception is missing inner exception info that would help track it down. The next time this fails we should get better diagnostics.

Author: noahfalk
Assignees: -
Labels:

area-System.Diagnostics.Tracing

Milestone: -

@noahfalk
Copy link
Member Author

noahfalk commented Jul 8, 2021

@tommcdon
cc @dotnet/dotnet-diag @tarekgh

@noahfalk
Copy link
Member Author

noahfalk commented Jul 8, 2021

The failures in crypto and com interop appear very unlikely to be related to this change. Given this change is itself trying to help diagnose CI failures we are probably better having it than not.

@noahfalk noahfalk merged commit 5f689e2 into dotnet:main Jul 8, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Aug 7, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants