feat: add graphql.processing.type attribute for programmatic span identification#64
Merged
PascalSenn merged 1 commit intomainfrom Mar 4, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Telemetry consumers currently have no reliable way to programmatically identify which span represents which processing activity (e.g. parsing vs execution) without relying on span name string matching.
Following the OTel semantic convention pattern established by messaging.operation.type and gen_ai.operation.name, this adds a graphql.processing.type enum attribute to all internal spans. Each span declares exactly one value (parse, validate, variable_coercion, plan, execute, step_execute, resolve, dataloader_dispatch, dataloader_batch), enabling consumers to filter and route spans by type using a single attribute query.
The server span is excluded as it is already identifiable via SpanKind.