Document the OpenTelemetry plugin on the Python observability page - #5305
Open
DABH wants to merge 1 commit into
Open
Document the OpenTelemetry plugin on the Python observability page#5305DABH wants to merge 1 commit into
DABH wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
📖 Docs PR preview links
|
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
1 participant
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.
The Python observability page's tracing section only covered the
TracingInterceptor, while the SDK has shippedOpenTelemetryPluginandcreate_tracer_provider()for several releases and the AI integration pages already build on them.This change rewrites the "Set up tracing" section into two subsections. The plugin subsection shows the replay-safe tracer provider, registering the plugin on the Client, the
add_temporal_spanstoggle, a custom span created from Workflow code, what happens on replay and Worker restart, and a note that the API is experimental. The interceptor subsection keeps the existing guidance, explains why its Workflow-side spans have no duration, and points tocompleted_span(). It also adds the exporter install line, sincetemporalio[opentelemetry]does not include one.Ran
vale --config .vale-ci.inion the page: clean. Follows up on the Arize integration work (AI-411).