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

Address incorrect operation tag value #519

Merged
merged 1 commit into from Aug 7, 2021
Merged

Conversation

berngp
Copy link
Contributor

@berngp berngp commented Aug 6, 2021

Fixes #515.
Looks like the most accurate approach on resolving both the operation
and operation name values is via the Instrumentation.beginExecutionStrategy.

Fixes #515.
Looks like the most accurate approach on resolving both the `operation`
and `operation name` values is via the `Instrumentation.beginExecutionStrategy`.
@berngp berngp merged commit b48f832 into master Aug 7, 2021
@berngp berngp deleted the feature/fix-operation-tag branch October 20, 2022 01:49
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.

bug: The gql.resolver metric has an incorrect tag value for gql.operation on mutations.
1 participant