Skip to content

Ensure errored node GraphQL requests result in spans with errored status #16649

Closed

Description

@memcorrupt

Problem Statement

Currently, all GraphQL spans are reported with successful span statuses.

Solution Brainstorm

Make spans that return errors (incl. ApolloError/GraphQLError) get marked with a failed span status.

Activity

  1. moved this to Waiting for: Product Owner in GitHub Issues with 👀 3on Jun 18, 2025
  2. AbhiPrasad commented on Jun 19, 2025

    @AbhiPrasad
    Contributor

    Hey @memcorrupt thanks for writing in! Are you referring to graphql client spans or server spans? What SDK (and SDK version) are you using?

  3. moved this from Waiting for: Product Owner to No status in GitHub Issues with 👀 3on Jun 19, 2025
  4. moved this to Waiting for: Community in GitHub Issues with 👀 3on Jun 20, 2025
  5. memcorrupt commented on Jun 21, 2025

    @memcorrupt
    Author

    @AbhiPrasad Server spans. Currently using "@sentry/node": "^9.11.0".

  6. moved this from Waiting for: Community to Waiting for: Product Owner in GitHub Issues with 👀 3on Jun 21, 2025
  7. self-assigned this
    on Jun 23, 2025
  8. changed the title [-]GraphQL instrumentation: report failing spans (returning GraphQLError/ApolloError)[/-] [+]Ensure errored node GraphQL requests result in spans with errored status[/+] on Jun 23, 2025
  9. github-actions commented on Jun 23, 2025

    @github-actions
    Contributor

    A PR closing this issue has just been released 🚀

    This issue was referenced by PR #16678, which was included in the 9.31.0 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions