opentelemetry-instrumentation-graphql doesn't follow GraphQL semantic conventions

[SonjaChevre]

• This only affects the JavaScript OpenTelemetry library
• This may affect other libraries, but I would like to get opinions here first

Hi! in the process of writing a blog post about GraphQL & OpenTelemetry, I have noticed that the GraphQL instrumentation doesn't respect the current (basic) GraphQL semantic convention.

A couple of findings:

• One example: using graphql.source for the query and not graphql.document
• On the other side, opentelemetry-instrumentation-graphql provides lots of insights that could be standardised to the semantic conventions
• Last, adding information about GraphQL errors on the spans (missing from the instrumentation and the semantic conventions) could have a lot of value for users - see here: https://tyk.io/blog/observing-graphql-errors-with-opentelemetry/

Making a note here, to let you know I have created an issue to suggest working on better semantic conventions for GraphQL: open-telemetry/semantic-conventions#182 - would welcome anybody that join this initiative.

Thanks,
Sonja

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days.

[github-actions]

This issue was closed because it has been stale for 14 days with no activity.