docs(integrations): add Pydantic AI tracing page#671
Open
SuhaniNagpal7 wants to merge 2 commits into
Open
Conversation
Add a TraceAI integration page for Pydantic AI under /docs/integrations/traceai/pydantic_ai, wired into both the Tracing and Integrations sidebars plus both overview grids. Verified end-to-end: the example code runs against the live FAGI tracer and the agent run span lands in the dashboard.
Restore the /docs/tracing/auto/pydantic_ai page so the auto-tracing surface has its own canonical entry matching the rest of the framework sibling pages. Repoint the Tracing sidebar entry and the auto-tracing overview card at it. The Integrations sidebar and overview continue to link to /docs/integrations/traceai/pydantic_ai.
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
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.
Summary
/docs/integrations/traceai/pydantic_ai, following the 5-section sibling template (Install → Env vars → register → instrument → run)./docs/tracing/auto,/docs/integrations). Both nav entries point at the same file, matching then8nprecedent innavigation.ts.FI_API_KEY/FI_SECRET_KEY) rather than theregister(api_key=...)form shown in the upstreamtraceAIrepo example, becausefi_instrumentation.register()does not accept anapi_keykwarg and that call would raiseTypeErrorat runtime.What changed
src/pages/docs/integrations/traceai/pydantic_ai.mdx@agent.toolexample)src/lib/navigation.tssrc/pages/docs/integrations/index.mdxPydantic AIcard in the TraceAI gridsrc/pages/docs/tracing/auto/index.mdxPydantic AIcard in the auto-instrumentation gridVerification
astro devcompiled the new MDX with zero errors / zero browser console errors. Page returns200, titles + H2s + code blocks + sidebar entry + prev/next nav all render.api.futureagi.com: ran the literal Step 2-5 code from the page usingFI_API_KEY/FI_SECRET_KEY+OPENAI_API_KEY. Theregister()call succeeded,PydanticAIInstrumentorinstrumented,agent.run_sync(...)returned the expected tool-backed answer, and the trace landed in thePYDANTIC_AI_APPproject (1 trace, status OK,gpt-4o/openai/ 181 tokens / $0.0007 captured with fullgen_ai.*+llm.*attributes).curlto expose the new card / nav entry.Test plan
astro devand confirm/docs/integrations/traceai/pydantic_airenders with the 5 sections./docs/tracing/autoand/docs/integrationsoverview grids.