Repository navigation
docs(python): Clarify that manual AI span attributes aren't filtered - #20131
Conversation
The manual AI and MCP instrumentation pages implied that prompt, response, and tool content set by hand 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 say that instead.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
|
The change tells readers that hand-set span attributes are not filtered. The plan checks client errors on the two changed pages and client errors on Python pages. An issue escalates when those page errors leave zero or Python page errors rise. Services: PlanWhat changedTwo Python pages now say the SDK does not filter hand-set span attributes. RiskReaders may send PII in hand-set attributes after they follow the new copy. A bad MDX render can fail those two pages. Code comments in fenced blocks can break code tabs. Other Python pages share the same catch-all route. The JavaScript manual instrumentation page shares the Intended effectTelemetry cannot see the new sentences. Confirm the live HTML after deploy. Absent means the old
Sampled middleware volume on the MCP page was 300 spans in the 48h window 2026-10-19T12:23:53Z to 2026-10-21T12:23:53Z. That volume shows the page is reached. It does not prove the new copy. Regression watchA render or code-tab break on these pages would show as client errors on the same URLs. Watch Python page errors as the sibling path on the same route.
Client traces sample at 30%. Middleware span counts are sampled. Error events are not. Not observableThe Python-only page-view rate for |
|
Verified in
|
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 onsend_default_piiordata_collection, so this updates the pages to say that.send_default_piiclaim, and point the privacy reference atdata_collectionRelated: #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-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: