Add semantic conventions for GraphQL

[laurit]

Changes

Add semantic conventions for GraphQL span name and attributes.

Related issues #1670

[svrnm]

Thanks for creating this @laurit !

[trask]

does anyone have thoughts on dropping operation from the attribute names, e.g.

• graphql.name
• graphql.type
• graphql.body

[svrnm]

does anyone have thoughts on dropping operation from the attribute names, e.g.

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 graphql.name|type|body would be limiting that effort.

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 7 days.

[trask]

/unstale

@yurishkuro @svrnm @jamesmoessis any other thoughts on this?

[svrnm]

@trask, thanks, I was under the assumption that this was closed already. I'm fine with it!

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 7 days.

[tigrannajaryan]

@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.

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 7 days.

[trask]

@laurit looks like there's a merge conflict

[laurit]

@trask thanks, rebased.

[trask]

@open-telemetry/technical-committee I think this is ready to be merged, thx!