Skip to content

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

Merged
merged 1 commit into from
Oct 10, 2023

Conversation

JamesNK
Copy link
Member

@JamesNK JamesNK commented Oct 3, 2023

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 to error.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 to error.type.

Fixes #51029

Customer Impact

The HTTP metrics in ASP.NET Core follow the OTEL convention.

Regression?

  • Yes
  • No

[If yes, specify the version the behavior has regressed from]

Risk

  • High
  • Medium
  • Low

The PR changes a name. Nothing in .NET or ASP.NET Core depends on the name.

Verification

  • Manual (required)
  • Automated

Correct tag name was manually verified by running dotnet-counters monitor:

image

Packaging changes reviewed?

  • Yes
  • No
  • N/A

When servicing release/2.1

  • Make necessary changes in eng/PatchConfig.props

@JamesNK JamesNK added this to the 8.0 milestone Oct 3, 2023
@JamesNK JamesNK requested a review from noahfalk October 3, 2023 00:31
@ghost ghost added the area-middleware Includes: URL rewrite, redirect, response cache/compression, session, and other general middlewares label Oct 3, 2023
@JamesNK JamesNK added the Servicing-consider Shiproom approval is required for the issue label Oct 3, 2023
@ghost
Copy link

ghost commented Oct 3, 2023

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.

Copy link

@lmolkova lmolkova left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

@danmoseley
Copy link
Member

Thanks James. When ready please mail tactics for approval.

@wtgodbe wtgodbe modified the milestones: 8.0, 8.0.0 Oct 3, 2023
@ghost ghost added the area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework label Oct 3, 2023
@mkArtakMSFT mkArtakMSFT added Servicing-approved Shiproom has approved the issue and removed Servicing-consider Shiproom approval is required for the issue labels Oct 4, 2023
@ghost
Copy link

ghost commented Oct 4, 2023

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.

@danmoseley
Copy link
Member

@wtgodbe can we merge this?

@wtgodbe wtgodbe merged commit 7ffeb43 into release/8.0 Oct 10, 2023
@wtgodbe wtgodbe deleted the jamesnk/metrics-error-type branch October 10, 2023 22:25
@ghost ghost modified the milestone: 8.0.0 Oct 10, 2023
@halter73 halter73 mentioned this pull request Nov 21, 2023
10 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework area-middleware Includes: URL rewrite, redirect, response cache/compression, session, and other general middlewares Servicing-approved Shiproom has approved the issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants