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

Use grouped operation name in application insights telemetry #1807

Merged
merged 2 commits into from Apr 27, 2024

Conversation

mirecad
Copy link
Contributor

@mirecad mirecad commented Apr 18, 2024

Application insights request telemetry on DOTVVM pages is identified by request URL. If there are path variables app insights considers them as different operations and does not apply grouping. Results are hard to read with tables consisted of many rows pointing to the same route.

image

I was inspired by Web API where operation name ignores variables and used DOTVVM route URL as new name. I was also considering DOTVVM route name, but from my experience URL is always provided by problem reporter (imagine non IT users as reporters) but route name can be more problematic to guess at first look.

image

As you can see on second screenshot "vyuctovanie" was grouped and I can see overal behavior of this page.

Copy link
Member

@exyi exyi left a comment

Choose a reason for hiding this comment

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

Thanks! I agree about using the URL template instead of route name (I'll consider including them in our OpenTelemetry metric labels too)

@tomasherceg tomasherceg merged commit 7a170a2 into riganti:main Apr 27, 2024
13 of 14 checks passed
@tomasherceg
Copy link
Member

Many thanks for the contribution!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants