-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Rename metrics tag exception.type to error.type #51084
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
Conversation
Hi @JamesNK. Please make sure you've updated the PR description to use the Shiproom Template. Also, make sure this PR is not marked as a draft and is ready-to-merge. To learn more about how to prepare a servicing PR click here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
Thanks James. When ready please mail tactics for approval. |
Hi @JamesNK. This PR was just approved to be included in the upcoming servicing release. Somebody from the @dotnet/aspnet-build team will get it merged when the branches are open. Until then, please make sure all the CI checks pass and the PR is reviewed. |
@wtgodbe can we merge this? |
Fixes #51029
Rename metrics tag exception.type to error.type
There has been a late change to OpenTelemetry conventions to rename the
exception.type
attribute toerror.type
. Because we are doing our best to follow the OTEL conventions, we want ASP.NET Core to use the right name.This change should be done now before the metrics are in a GA release.
Description
Rename the
exception.type
attribute toerror.type
.Fixes #51029
Customer Impact
The HTTP metrics in ASP.NET Core follow the OTEL convention.
Regression?
[If yes, specify the version the behavior has regressed from]
Risk
The PR changes a name. Nothing in .NET or ASP.NET Core depends on the name.
Verification
Correct tag name was manually verified by running
dotnet-counters monitor
:Packaging changes reviewed?
When servicing release/2.1