search

getsentry / sentry

Developer-first error tracking and performance monitoring
https://sentry.io
Other
39.3k stars 4.21k forks source link

Improve GraphQL Request Grouping by Extracting Query Endpoints in Request Insights #79216

Open serglom21 opened 1 month ago

serglom21 commented 1 month ago

Problem Statement

Currently, Sentry's request insights module groups all GraphQL requests together under a single /graphql endpoint, even though these requests contain different query endpoints. This grouping makes it difficult to quickly identify latency or performance issues for specific GraphQL queries, requiring users to open the group and manually inspect each trace. This hampers efficiency in debugging and monitoring application performance. Image

Solution Brainstorm

Extract and display the specific query endpoints from the available request data in the traces. Instead of grouping all GraphQL requests under a single /graphql group, list each unique query endpoint separately in the request insights view. This will allow users to quickly identify performance issues related to specific GraphQL queries, improving the speed and accuracy of debugging and performance monitoring.

Product Area

Insights

getsantry[bot] commented 1 month ago

Routing to @getsentry/product-owners-insights for triage ⏲️

getsantry[bot] commented 1 month ago

Routing to @getsentry/product-owners-performance for triage ⏲️

getsantry[bot] commented 1 month ago

Assigning to @getsentry/support for routing ⏲️

bcoe commented 1 month ago

@mjq this should be addressed by using integrations: [Sentry.graphqlIntegration({ useOperationNameForRootSpan: true })], which would split their GraphQL transactions up by operation name?

What if we keep this ticket open until we add documentation here.