{
  "id": 21030290,
  "title": "How to Monitor Agents Built with Pydantic AI or Google ADK",
  "url": "https://urgent.news/2026/11/21/how-to-monitor-agents-built-with-pydantic-ai-or-google-adk",
  "topic": "ai",
  "section": "AI",
  "published": "2026-11-21T10:11:33.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/shubhampalriwala/how-to-monitor-agents-built-with-pydantic-ai-or-google-adk-2idi"
  },
  "original_language": "en",
  "account": "To monitor agents built with Pydantic AI or Google ADK, export the OpenTelemetry traces emitted by both frameworks to a monitoring backend. Connect a user and session ID to each run. For comprehensive monitoring of entire conversations, consider using Agnost AI, which aggregates spans by user and session, validates conversations against plain-language rules, and sends alerts via Slack or email when issues arise. Pydantic Logfire is the native tool to inspect Pydantic AI runs, while Google Cloud Trace serves as the default destination for ADK. Both frameworks adhere to the OpenTelemetry semantic conventions for generative AI, enabling the same backend to read traces from either framework. However, setup differs: Pydantic AI requires the Logfire SDK (or direct OpenTelemetry setup), while ADK needs its own OTLP configuration plus an optional plugin for user IDs and transcripts on the root span. Agnost AI, an open-source tracing and evaluation workbench for ADK, is recommended for production monitoring with alerts and fix PRs. Pydantic Logfire is ideal for inspecting Pydantic AI runs during development. ADK on Google Cloud offers a built-in tracing solution, compatible with other GCP services. Phoenix or Langfuse, both listed in ADK's integrations catalog, can also be used for tracing and evaluation. The table below provides a quick comparison between the tools.",
  "summary": "To monitor agents built with Pydantic AI or Google ADK, export the OpenTelemetry traces both frameworks already emit to a monitoring backend, and attach a user and session ID to each run. For production monitoring of whole conversations, Agnost AI is the pick: it receives those spans over OTLP, groups them by user and session, judges every conversation against plain-language rules, and alerts in…",
  "key_points": [
    "Export OpenTelemetry traces to monitoring backend",
    "Use Agnost AI for conversation monitoring and alerts",
    "Pydantic Logfire inspects Pydantic AI runs"
  ],
  "editors_take": "Standardizing on OpenTelemetry allows developers to unify observability across different agent frameworks, though specific configuration requirements still force a choice between native tools and third-party aggregation platforms.",
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}