-
Notifications
You must be signed in to change notification settings - Fork 182
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
feat!: Update GraphQL span name convention #1389
feat!: Update GraphQL span name convention #1389
Conversation
Due to concerns about high cardinality with the current span name format use only the <graphql.operation.type> attribute for the span name. The higher cardinality attribute, <graphql.operation.name> can still be used in queries, as it is an attribute on the span. The original fallback, "GraphQL Operation" is preserved.
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
Provide an path for a config option to add {graphql.operation.name} to the span name, but with a clear warning around high cardinality.
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!
…emantic-conventions into update-graphql-span-name
It seems like the wayback machine is down at the moment, causing the markdown-link-check job to fail: https://github.com/open-telemetry/semantic-conventions/actions/runs/11263374842/job/31321102055?pr=1389#step:4:10 |
Co-authored-by: Joao Grassi <[email protected]> Co-authored-by: Liudmila Molkova <[email protected]>
Fixes #1361
Changes
Due to concerns about high cardinality with the current span name format, use only the
graphql.operation.type
attribute for the span name. The higher cardinality attribute,graphql.operation.name
can still be used in queries, as it is an attribute on the span. The original fallback span name,GraphQL Operation
, is preserved.Merge requirement checklist
[chore]