docs(tracing): route Python to the posthog span API - #399
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This was referenced Sep 18, 2026
🧙 Wizard CIRun the Wizard CI and test your changes against wizard-workbench example apps by replying with a GitHub comment using one of the following commands: Test all apps:
Test all apps in a directory:
Test an individual app:
Show more apps
Test against a wizard branch:
Add Results will be posted here when complete. |
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
gewenyu99
approved these changes
Sep 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
posthogfor Python gains a native span API in PostHog/posthog-python#957. The tracing skill (#391) told agents onlyposthog-nodecould send spans without OpenTelemetry, so a Python install would always add an OTel exporter pipeline.posthog>= 7.58.0, thetracesoption on the synchronousPosthogclient (orposthog.traces),with posthog.start_span(...).AsyncPosthoghas no span API, so it stays on OpenTelemetry.traces["service_name"]), scrubbing (before_span_send), and the person/session join (new_context()withidentify_context()/set_context_session(), or the Django contexts middleware).The
tracing-pythonvariant already exists and reads/docs/distributed-tracing/installation/python.md, which PostHog/posthog.com#20285 rewrites for the new route. Merge after the SDK release and #20285.scripts/lib/tests/tracing-skills.test.jspasses locally.🤖 Generated with Claude Code