GrapheneIntegration: Track operation name for tracing #2704
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.
It is helpful to have the operation's name if trying to track the individual performance of GraphQL transactions using Sentry. This PR implements the approach suggested in this article, as part of the GrapheneIntegration()
Note: I looked and wasn't initially sure how to write a good test for this and also wasn't sure if this PR is even a good idea in the first place. So leaving a light version here for feedback.