Repository navigation
docs(python): Add data_collection alternatives to integration docs - #20128
Conversation
Integration and AI agent pages only described send_default_pii. Document the data_collection key that controls each behavior instead: - Web frameworks: mention data_collection next to send_default_pii - Django, Flask: user_info - Redis, PyMongo, clickhouse-driver: database_query_data - GQL, Graphene, Ariadne, Strawberry: graphql and http_bodies - MCP and agent tracing: gen_ai, and that include_prompts is ignored when data_collection is set - Rust Tracing: data_collection doesn't affect include_tracing_fields Also fix the http_bodies docs in Data Collected: outgoing_response is a valid body type and part of the default.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
… removal Wherever a page mentions both options, describe data_collection first and send_default_pii as the alternative, and note that send_default_pii will be removed in the next major version of the SDK. Also update the Options, Data Collected and Sensitive Data pages, which said send_default_pii would only be deprecated eventually.
data_collection alternatives to integration docs
|
The change documents a new Python SDK option on existing pages. An issue escalates when those pages 404 or throw client errors. Page load volume on the changed paths is the population for those checks. Services: PlanWhat changedPython docs pages now describe data_collection and say some AI tool data is collected by default. They still mention send_default_pii and say SDK 3.0 will remove it. sentry-docs must deploy before this wording is live. Vercel production maps this repo to sentry-docs. The change does not add routes. RiskBroken MDX can 404 a page or throw in the browser. That reaches readers of the changed Python pages. Shared layout code did not change. A failed Vercel build would block the ship. Wrong default-collection wording can hide that tool arguments are sent. That SDK effect is not visible on this site. Intended effectThis is a docs wording change. No counter increments when the new text is live. Absence looks like the pages still loading with only send_default_pii copy. Absence also looks like AI pages omitting the default tool-data note. Telemetry cannot confirm the new wording. Regression watchWatch the changed Python docs paths. Pair each failure signal with docs.page.load on those paths. Existing Algolia insights fetch TypeErrors are noise. Do not count them as this change. 2026-10-18 had a 53% error rate. Treat that day as an outlier.
If the error rate rises, inspect new titles on those URLs. Ignore Algolia insights fetch failures. Not observableLive HTML for the new data_collection wording is not in telemetry. The 7-day pageload failure-rate series timed out in Sentry. Traces are sampled at 30% and cannot form a band here. |
Without send_default_pii or data_collection, AI integrations don't record prompts, messages, or responses, but some still attach tool data: tool definitions, LangChain and Google GenAI tool calls, and MCP tool and prompt arguments. Document this per integration, along with how to remove it with data_collection's gen_ai key. Google GenAI tool inputs and outputs are attached regardless of either option, so note that as well.
## DESCRIBE YOUR PR Replace `send_default_pii=True` in Python init snippets with a `data_collection` example, using the key that fits each page. `send_default_pii` will be removed in version 3.0 of the SDK. - `user_info`: shared getting-started/config includes, general pages, web frameworks, logging, feature flags, etc. - `gen_ai`: AI agent tracing pages and MCP - `queues`: Celery, RQ - `database_query_data`: aiomysql - `graphql`: Strawberry Snippets demonstrating `include_prompts`, `event_scrubber`, or Rust Tracing's `include_tracing_fields` keep `send_default_pii`, since those only work with it. The GQL, Graphene, Ariadne, and second Strawberry snippets are left alone because #20128 keeps them as the `send_default_pii` alternative. Related: #20128 ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. Select exactly one option. For deadlines, replace `YYYY-MM-DD` with the due date. You can update this information later by editing the PR description. - [ ] Urgent deadline (GA date, etc.): YYYY-MM-DD - [ ] Other deadline: YYYY-MM-DD - [x] No deadline: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've supplied a deadline. Thanks in advance for your help! ## PRE-MERGE CHECKLIST _Make sure you've checked the following before merging your changes:_ - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs)
…20131) ## DESCRIBE YOUR PR The manual AI and MCP instrumentation pages implied that prompt, response, and tool content you set yourself is only captured with `send_default_pii=True`. The SDK doesn't filter manually set attributes based on `send_default_pii` or `data_collection`, so this updates the pages to say that. - Manual Instrumentation: replace the `send_default_pii` claim, and point the privacy reference at `data_collection` - MCP custom instrumentation: align the tool-argument comment with the prompt examples on the same page Related: #20128 ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. Select exactly one option. For deadlines, replace `YYYY-MM-DD` with the due date. You can update this information later by editing the PR description. - [ ] Urgent deadline (GA date, etc.): YYYY-MM-DD - [ ] Other deadline: YYYY-MM-DD - [x] No deadline: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've supplied a deadline. Thanks in advance for your help! ## PRE-MERGE CHECKLIST _Make sure you've checked the following before merging your changes:_ - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs)
|
Verified in
|
DESCRIBE YOUR PR
The Python integration and agent tracing pages only describe
send_default_pii. This adds thedata_collectionalternative, naming the specific key that controls each behavior.data_collectionnext tosend_default_piiuser_infodatabase_query_datagraphqlandhttp_bodies(also fixes a typo on the Strawberry page claiming body capture was on by default)gen_ai, and thatinclude_promptsis ignored whendata_collectionis setdata_collectiondoesn't affectinclude_tracing_fieldsoutgoing_responseis a validhttp_bodiestype and part of the default (used by Ariadne and Strawberry)data_collectionbeforesend_default_piieverywhere, and note thatsend_default_piiwill be removed in version 3.0 of the SDK (also updates Options, Data Collected and Sensitive Data, which said it would only be deprecated eventually)Init snippets still use
send_default_pii=True; that'll be handled separately.IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
Select exactly one option. For deadlines, replace
YYYY-MM-DDwith the due date. You can update this information later by editing the PR description.SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes: