Repository navigation
Add the Arize integration page for Python - #5306
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
📖 Docs PR preview links
|
…use a live trace screenshot
|
@DABH following up on the Arize integration handoff: this docs PR and samples-python#365 are still drafts, and the docs body notes the sample must merge first. Is there any specific input needed from the Arize side to finish the sample/docs review? For the eventual evaluation references, the current URLs are https://arize.com/guides/ai-agent-handbook/agent-evaluation/ and https://arize.com/resources/llm-evaluation/. Happy to keep tracking the dependency rather than reopening #5210. |
|
Hey Dat, sorry for the slow reply here! Nothing is blocked on the Arize side - both PRs have been drafts since I found a few tracing bugs in the OpenAI Agents plugin while building the agents scenario, and in the meantime that plugin moved out of the SDK into the standalone |
…egration-docs # Conflicts: # docs/develop/python/platform/observability.mdx
Install the agents variant from the standalone package, describe the single-worker span-parenting bug as fixed upstream but unreleased, note that the Arize AX exporter settings were not exercised live, and add Arize's evaluation guides to Resources.
1.1.0 ships the span-parenting fix, so the caution about running Workflows and Activities in separate Worker processes and the note about the "Failed to detach context" log filter no longer apply. The install step now asks for 1.1.0 or later, and the agents plugin snippet matches the sample without its worker-role switch.
…egration-docs # Conflicts: # docs/develop/python/index.mdx # sidebars.js # vale/styles/Temporal/Headings.yml
Arize validated the sample against an AX space, so the note that the AX path was not exercised is gone. Add what they observed: AX lists a trace with a failed attempt as an error, a stopping Worker logs a harmless "Failed to detach context" traceback, and after a reset the reapplied update's HandleUpdate span reuses the original RunWorkflow span id, which Phoenix drops and AX shows as a duplicated subtree.
Snipsync coverageSDK code lines in
All sectionsAll languages: 50.1% (24,434 of 48,782 lines).
Compared with |
|
Thanks for running this against AX, Juston - that's exactly the coverage we were missing, and the reset finding is a real bug. I reproduced it locally with an in-memory exporter: the reapplied |
|
@DABH, one update while tracking the paired docs/sample PRs: SDK issue #2070 is closed, and the single-batch fix in temporalio/sdk-python#2081 merged November 3. The earlier run-ID proposal #2071 closed without merge. The latest published Python SDK release I can see is still 1.35.0 (October 28), which predates #2081, so I am not treating the fix as released or the sample as revalidated. Could you confirm the intended SDK version/workaround wording and review route for this docs PR and samples-python#365? The one-line suggestion above also points the existing agent-evaluation resource directly to its current URL; the old URL still redirects. No partner branch was changed, and no new authenticated AX/Phoenix run is claimed. AI-assisted status check and follow-up by OpenAI Codex at Dat’s request. |
Require 1.36.0 in the install step, replace the known-defect paragraph with the fixed-version note, and match the worker snippet to the sample.
temporalio/samples-python#365 merged, so the five snippets on the Arize page now come from main instead of the pre-filled copies. The sample's condensing pass shortened docstrings and comments; the prose around each snippet still matches.
Dat suggested the current address on the PR; the old one still redirects.
|
Thanks for the check. Status as of today: temporalio 1.36.0 shipped on November 11 with the single-batch fix from sdk-python#2081, the sample merged this morning as samples-python#365 on 1.36.0, and this page now requires 1.36.0 and no longer describes a reset workaround. The PR is out of draft and with the Docs team for review. I also took your link suggestion |
- Use Workflow ID, drop the validation process note, and shorten the reset paragraph to the version requirement and its symptom - Move the Agents bridge Public Preview note into a caution at the top of its section - Tie the lost-spans window to schedule_delay_millis instead of the sample's 500 ms - Rename the heading to Workflow retries so it doesn't read as Activity retries - Require temporalio-openai-agents 1.1.0 on the OpenAI Agents OpenTelemetry install line, with the span parenting warning


Adds
docs/develop/python/integrations/arize.mdx, a guide to sending Temporal traces to Arize Phoenix or Arize AX with the Python OpenTelemetry plugin and the OpenInference conventions, plus the sidebar entry, the IntegrationsGrid card, the Python index bullet, and a pointer from the observability page. Vale gainsArize,OpenAI,OpenInference,OTLP, andPhoenixas heading exceptions.The page covers the tracer provider and exporter setup, Client and Worker configuration, LLM calls in Activities (including the OpenAI Agents SDK bridge from the standalone
temporalio-openai-agentspackage), the OpenInference attributes that make traces group by Workflow Id, and how replay, retries, Worker crashes, Workflow Task failures, Continue-As-New, and resets appear in Arize. Every behavior described was verified against a local Phoenix with the sample's runbook; the Arize AX path was validated by Arize against an AX space.The sample merged as temporalio/samples-python#365, so the snippets are synced from
mainand the GitHub links resolve. Replaces the closed #5210 card. Vale CI config andyarn buildare clean;yarn check:orphansreports two pre-existing pages unrelated to this change.