GraphQL Connected Services

[smeubank]

Background

We want to provide better GraphQL support with Sentry SDKs, frontend to backend. Work has already begun on some mobile platforms. There is also already some implementations for GraphQL server and client side. With the current work we want to ensure that the strategy to ensure proper connected errors and grouping works from backend to frontend. Java already has an integration for GraphQL.

Proposal

Python SDK should set context for GraphQL on errors same as what is done for Mobile SDK to ensure the value add from Frontend to Backend

Definition of Done TBC:

• GraphQL Context

Further context:

getsentry/sentry#50230

• feat(graphql): Add special rendering logic for graphql requests sentry#50764

[sentrivana]

Reopening this since the implementation will have to be reworked.

The original implementation was capturing client errors by inspecting requests/responses done by the three HTTP clients we provide integrations for (standard library, httpx, aiohttp). This proved too brittle since it tampered with low-level HTTP internals. A better approach would be to add integrations for common GraphQL clients which already recognize GraphQL errors and create Sentry events from those.