Skip to content

feat(gql): Gate GraphQL data collection behind data_collection option #6889

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.

Sign up for GitHub

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

Open
ericapisani wants to merge 4 commits into from
+158 −2
Open

feat(gql): Gate GraphQL data collection behind data_collection option #6889

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
9562fff
feat(graphene): Gate GraphQL data collection behind data_collection o…
ericapisani Jul 24, 2026
a6055cd
feat(strawberry): Gate GraphQL data collection behind data_collection…
ericapisani Jul 24, 2026
058e048
feat(gql): Gate GraphQL data collection behind data_collection option
ericapisani Jul 24, 2026
4225d03
Merge branch 'master' into py-2585-gql
ericapisani Jul 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 32 additions & 2 deletions sentry_sdk/integrations/gql.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,7 @@
from sentry_sdk.utils import (
ensure_integration_enabled,
event_from_exception,
has_data_collection_enabled,
parse_version,
)

Expand Down Expand Up @@ -54,12 +55,18 @@


def _data_from_document(document: "DocumentNode") -> "EventDataType":
client_options = sentry_sdk.get_client().options
try:
operation_ast = get_operation_ast(document)
data: "EventDataType" = {"query": print_ast(document)}

if operation_ast is not None:
data["variables"] = operation_ast.variable_definitions
if has_data_collection_enabled(client_options):
if client_options["data_collection"]["graphql"]["variables"]:
data["variables"] = operation_ast.variable_definitions
elif should_send_default_pii():
data["variables"] = operation_ast.variable_definitions

if operation_ast.name is not None:
data["operationName"] = operation_ast.name.value

Expand Down Expand Up @@ -147,7 +154,30 @@
}
)

if should_send_default_pii():
client_options = sentry_sdk.get_client().options
if has_data_collection_enabled(client_options):
if client_options["data_collection"]["graphql"]["document"]:
if GraphQLRequest is not None and isinstance(
document_or_request, GraphQLRequest
):
# In v4.0.0, gql moved to using GraphQLRequest instead of
# DocumentNode in execute
# https://github.com/graphql-python/gql/pull/556
document = document_or_request.document
else:
document = document_or_request

request["data"] = _data_from_document(document)

@cursor cursor Bot Jul 28, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Variables require document collection

Medium Severity

graphql.variables is only consulted inside _data_from_document, which runs only when graphql.document is enabled. With document off and variables on, variable data is never attached. The Strawberry integration and its tests treat these flags as independent under the same data_collection contract.

Additional Locations (1)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 058e048. Configure here.

contexts = event.setdefault("contexts", {})
response = contexts.setdefault("response", {})
response.update(

Check warning on line 173 in sentry_sdk/integrations/gql.py

View check run for this annotation

@sentry/warden / warden: find-bugs

GraphQL response context sets 'type' to self-referential dict 

The response context's 'type' key is set to the response dictionary itself, creating a circular reference instead of a type identifier string. The event serializer detects cycles and replaces them with the string '<cyclic>', so serialization does not fail, but the resulting 'type' value is useless instead of a meaningful context identifier.
{
"data": {"errors": errors},
"type": response,

@sentry sentry Bot Jul 28, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: The response context dictionary is updated with a self-reference ("type": response), which will cause a ValueError during JSON serialization, preventing event capture.
Severity: CRITICAL

Suggested Fix

The value for the "type" key in the response context dictionary should be a string literal, such as "response", instead of the dictionary object itself. This will prevent the circular reference and allow the event to be serialized correctly.

Prompt for AI Agent 
Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: sentry_sdk/integrations/gql.py#L176

Potential issue: In the `processor` function, when GraphQL data collection is enabled
and an error occurs, the `response` context is updated with a self-referential key:
`response.update(..., "type": response)`. This creates a circular reference within the
dictionary. When the Sentry SDK attempts to serialize the event to JSON using
`json.dumps()`, it will encounter this circular reference and raise a `ValueError`,
causing the event capture to fail. This affects any user who enables the new GraphQL
document collection feature.

Also affects:

  • sentry_sdk/integrations/gql.py:180~183

Did we get this right? 👍 / 👎 to inform future reviews.

}
)

elif should_send_default_pii():
if GraphQLRequest is not None and isinstance(
document_or_request, GraphQLRequest
):
Expand Down
126 changes: 126 additions & 0 deletions tests/integrations/gql/test_gql.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,6 +58,30 @@ def _execute_mock_query_with_keyword_document(response_json):
return client.execute(document=query)


@responses.activate
def _execute_mock_query_with_variables(response_json):
url = "http://example.com/graphql"
query_string = """
query Example($id: ID!) {
example(id: $id)
}
"""

# Mock the GraphQL server response
responses.add(
method=responses.POST,
url=url,
json=response_json,
status=200,
)

transport = RequestsHTTPTransport(url=url)
client = Client(transport=transport)
query = gql(query_string)

return client.execute(query, variable_values={"id": "1"})


_execute_query_funcs = [_execute_mock_query]
if GQL_VERSION < (4,):
_execute_query_funcs.append(_execute_mock_query_with_keyword_document)
Expand Down Expand Up @@ -147,3 +171,105 @@ def test_real_gql_request_with_error_with_pii(

assert "data" in event["request"]
assert "response" in event["contexts"]


@pytest.mark.parametrize("execute_query", _execute_query_funcs)
@pytest.mark.parametrize(
"init_kwargs,expect_data",
[
pytest.param({}, False, id="no_pii_no_data_collection"),
pytest.param({"send_default_pii": True}, True, id="legacy_pii_on"),
pytest.param(
{"_experiments": {"data_collection": {}}},
True,
id="data_collection_defaults",
),
pytest.param(
{"_experiments": {"data_collection": {"graphql": {"document": True}}}},
True,
id="data_collection_document_on",
),
pytest.param(
{"_experiments": {"data_collection": {"graphql": {"document": False}}}},
False,
id="data_collection_document_off",
),
pytest.param(
{
"send_default_pii": True,
"_experiments": {"data_collection": {"graphql": {"document": False}}},
},
False,
id="data_collection_takes_precedence_over_send_default_pii_on",
),
pytest.param(
{
"send_default_pii": False,
"_experiments": {"data_collection": {"graphql": {"document": True}}},
},
True,
id="data_collection_takes_precedence_over_send_default_pii_off",
),
],
)
def test_real_gql_request_with_error_data_collection(
sentry_init, capture_events, execute_query, init_kwargs, expect_data
):
"""
Integration test verifying that the GQLIntegration honours the
``data_collection`` configuration when deciding whether to attach the
GraphQL document to the event.
"""
sentry_init(integrations=[GQLIntegration()], **init_kwargs)

event = _make_erroneous_query(capture_events, execute_query)

if expect_data:
assert "data" in event["request"]
assert "query" in event["request"]["data"]
assert "response" in event["contexts"]
else:
assert "data" not in event["request"]
assert "response" not in event["contexts"]


@pytest.mark.parametrize(
"init_kwargs,expect_variables",
[
pytest.param({"send_default_pii": True}, True, id="legacy_pii_on"),
pytest.param(
{"_experiments": {"data_collection": {}}},
True,
id="data_collection_defaults",
),
pytest.param(
{"_experiments": {"data_collection": {"graphql": {"variables": True}}}},
True,
id="data_collection_variables_on",
),
pytest.param(
{"_experiments": {"data_collection": {"graphql": {"variables": False}}}},
False,
id="data_collection_variables_off",
),
],
)
def test_real_gql_request_with_error_data_collection_variables(
sentry_init, capture_events, init_kwargs, expect_variables
):
"""
Integration test verifying that the GQLIntegration honours the
``data_collection`` ``graphql.variables`` toggle for queries that
define variables.
"""
sentry_init(integrations=[GQLIntegration()], **init_kwargs)

event = _make_erroneous_query(capture_events, _execute_mock_query_with_variables)

assert "data" in event["request"]
assert "query" in event["request"]["data"]

if expect_variables:
assert event["request"]["data"].get("variables")
else:
assert not event["request"]["data"].get("variables")
Loading