fix: update GraphQL span name to follow semantic conventions

[karmingc]

The semantic convention for GraphQL spans is specified here: https://opentelemetry.io/docs/specs/semconv/graphql/graphql-spans/. This will also resolve https://github.com/open-telemetry/opentelemetry-ruby-contrib/issues/560.

[arielvalentin]

Where the names always wrong?

I will have to take a look at the spec but are there any expectations around backward compatibility like there is with HTTP or Messaging semantics?

cc: @rmosolgo

[kaylareopelle]

Where the names always wrong?

I will have to take a look at the spec but are there any expectations around backward compatibility like there is with HTTP or Messaging semantics?

cc: @rmosolgo

@arielvalentin, all the GraphQL semantic conventions for spans are experimental. Breaking changes are allowed.

[github-actions[bot]]

👋 This pull request has been marked as stale because it has been open with no activity. You can: comment on the issue or remove the stale label to hold stale off for a while, add the keep label to hold stale off permanently, or do nothing. If you do nothing this pull request will be closed eventually by the stale bot

[kaylareopelle]

Hi @karmingc! Whew, this has been a journey! I appreciate your patience.

We brought these questions to the semantic conventions repo. After some discussion, the decision was to change the span name to be graphql.operation.type by default, and to allow instrumentation authors to add a configuration option to append graphql.operation.name to the span name if a user opts in.

With this in mind, are you interested in updating this PR to fit with the new semantic convention? https://github.com/open-telemetry/semantic-conventions/pull/1389

[karmingc]

Hi @karmingc! Whew, this has been a journey! I appreciate your patience.

We brought these questions to the semantic conventions repo. After some discussion, the decision was to change the span name to be graphql.operation.type by default, and to allow instrumentation authors to add a configuration option to append graphql.operation.name to the span name if a user opts in.

With this in mind, are you interested in updating this PR to fit with the new semantic convention? open-telemetry/semantic-conventions#1389

Hi, I haven't had the chance to comment/reply for a while given that I am no longer involved on Ruby-related applications at work. However, I'm still open to fixing these! I'll try to update in the upcoming weeks if possible.

If somebody needs this to be prioritized, feel free to pick it up as well.