-
Notifications
You must be signed in to change notification settings - Fork 890
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
Add semantic conventions for GraphQL #2456
Conversation
specification/trace/semantic_conventions/instrumentation/graphql.md
Outdated
Show resolved
Hide resolved
specification/trace/semantic_conventions/instrumentation/graphql.md
Outdated
Show resolved
Hide resolved
specification/trace/semantic_conventions/instrumentation/graphql.md
Outdated
Show resolved
Hide resolved
specification/trace/semantic_conventions/instrumentation/graphql.md
Outdated
Show resolved
Hide resolved
specification/trace/semantic_conventions/instrumentation/graphql.md
Outdated
Show resolved
Hide resolved
Thanks for creating this @laurit ! |
specification/trace/semantic_conventions/instrumentation/graphql.md
Outdated
Show resolved
Hide resolved
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.
does anyone have thoughts on dropping operation
from the attribute names, e.g.
graphql.name
graphql.type
graphql.body
I would keep it, there are other things in graphql that might have a name, type or body (not an expert on that, but by quickly reading the GraphQL spec I saw that there are also things like type definitions, fragments, response. Also, their spec could extend to contain other objects worth collecting) While those other things are not yet specified here, one might do it in the future and naming it |
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
/unstale @yurishkuro @svrnm @jamesmoessis any other thoughts on this? |
@trask, thanks, I was under the assumption that this was closed already. I'm fine with it! |
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
@laurit please resolve the conversations and rebase from main to prepare for merging. @open-telemetry/specs-approvers we have the minimum required number of approvals so unless I see objections I am going to merge this. |
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
@laurit looks like there's a merge conflict |
…ql.md Co-authored-by: Trask Stalnaker <[email protected]>
@trask thanks, rebased. |
@open-telemetry/technical-committee I think this is ready to be merged, thx! |
Add semantic conventions for GraphQL span name and attributes. Related issues open-telemetry#1670
Add semantic conventions for GraphQL span name and attributes. Related issues open-telemetry#1670
Add semantic conventions for GraphQL span name and attributes. Related issues open-telemetry#1670
Changes
Add semantic conventions for GraphQL span name and attributes.
Related issues #1670