Repository navigation
feat(python): Add versioned span streaming pages for 3.0 - #19831
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
|
The change splits custom tracing docs into a current-version page and an older-version copy. The plan checks page loads on both paths, runtime 404 warnings, and client errors. An issue escalates when default pages stop loading, versioned pages 404, or client errors appear. Monitoring in Services: Mention PlanWhat changedRequests to the unversioned streamed-spans pages now describe stream mode as always on. Readers who pick the older SDK version get the prior opt-in API pages. Those versioned copies live at the RiskA missing new MDX file returns 404 when a reader picks the older version. A bad versioned link can send readers to a missing page. A render failure can break code tabs or the version picker on this path. Wrong copy can tell older-SDK readers to call APIs that do not exist yet. Intended effectThe rewrite itself has no content signal. Use page loads to see that the pages still render. The new
Regression watchThis diff can 404 the new versioned files or throw on the version picker and code tabs. Watch client errors on this path first. Also watch the Python tracing sibling paths. A quiet success metric does not cover a 404.
Not observableThe rendered API text is not in telemetry. A reader can still see the wrong version with healthy page loads. The |
The top-level Python SDK API for custom tracing instrumentation will be rewired to span streaming in the upcoming 3.0 major. Create a versioned copy of the relevant pages, once with the old API (<3.0), and one for 3.0+.
Direct link to preview:
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:
LEGAL BOILERPLATE
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.
EXTRA RESOURCES