Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GrapheneIntegration: Track operation name for tracing #2704

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

keithhackbarth
Copy link

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.

@keithhackbarth keithhackbarth changed the title Track operation name for tracing GrapheneIntegration: Track operation name for tracing Feb 5, 2024
@czyber
Copy link
Contributor

czyber commented Feb 21, 2024

Hi @keithhackbarth, i would love to see this change!
Mind if I look into writing tests for it on the weekend?

czyber added a commit to czyber/sentry-python that referenced this pull request Feb 24, 2024
… query getsentry#2704

This commit adds a missing test for the graphene integration, so that we can be sure that a transaction with the corresponding query name is captured.
… query getsentry#2704

This commit adds a missing test for the graphene integration, so that we can be sure that a transaction with the corresponding query name is captured.

--amend
@czyber
Copy link
Contributor

czyber commented Feb 24, 2024

Hey @keithhackbarth, i added a test and made a PR on your fork 😄

czyber added a commit to czyber/sentry-python that referenced this pull request Mar 8, 2024
… query getsentry#2704

This commit adds a missing test for the graphene integration, so that we can be sure that a transaction with the corresponding query name is captured.

--amend
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.

None yet

2 participants