Skip to content

Look for errors in the graphql response for metric tagging#2162

Merged
jjacobs44 merged 4 commits intomasterfrom
gql-iserror
Jul 7, 2025
Merged

Look for errors in the graphql response for metric tagging#2162
jjacobs44 merged 4 commits intomasterfrom
gql-iserror

Conversation

@jjacobs44
Copy link
Collaborator

@jjacobs44 jjacobs44 commented May 22, 2025

Pull Request type

  • Bugfix
  • Feature
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Other (please describe):

Changes in this PR

It's possible to manually craft a DataFetcherResult and place errors within the error field. In the previous implementation, if your datafetcher were to catch all of its own exceptions and do this manual creation of a DataFetcherResult, those requests would not properly get tagged as a request which contained an error in metrics.

This changes the implementation to inspect the actual graphql result to check if it contains errors on top of just looking for exceptions.

@jjacobs44 jjacobs44 merged commit 9d73764 into master Jul 7, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants