cd /news/ai-tools/pydantic-ai-observability-monitoring… · home topics ai-tools article
[ARTICLE · art-44198] src=signoz.io ↗ pub= topic=ai-tools verified=true sentiment=↑ positive

Pydantic AI Observability & Monitoring with OpenTelemetry

Pydantic AI has introduced observability and monitoring for its AI agents using OpenTelemetry, enabling users to export logs, traces, and metrics to SigNoz for real-time visibility into latency, error rates, and usage trends. The integration allows developers to instrument Pydantic AI applications with minimal code changes, leveraging SigNoz dashboards and alerts to debug issues and optimize performance.

read7 min views1 publishedJun 29, 2026

Overview

This guide walks you through setting up observability and monitoring for Pydantic AI API using OpenTelemetry and exporting logs, traces, and metrics to SigNoz. With this integration, you can observe model and agent performance, capture request/response details, and track system-level metrics in SigNoz, giving you real-time visibility into latency, error rates, and usage trends for your Pydantic AI applications.

Instrumenting Pydantic AI in your AI applications with telemetry ensures full observability across your AI workflows, making it easier to debug issues, optimize performance, and understand user interactions. By leveraging SigNoz, you can analyze correlated traces, logs, and metrics in unified dashboards, configure alerts, and gain actionable insights to continuously improve reliability, responsiveness, and user experience.

Prerequisites

  • A SigNoz Cloud accountwith an active ingestion key - Internet access to send telemetry data to SigNoz Cloud Pydantic AIintegrated into your Python application.- For Python: pip

installed for managing Python packages and*(optional but recommended)*a Python virtual environment to isolate dependencies

Monitoring Pydantic AI

For more detailed info on instrumenting your Pydantic AI applications click here.

No-code auto-instrumentation is recommended for quick setup with minimal code changes. It's ideal when you want to get observability up and running without modifying your application code and are leveraging standard instrumentor libraries.

Step 1: Install the necessary packages in your Python environment.

pip install \
  opentelemetry-distro \
  opentelemetry-exporter-otlp \
  httpx \
  opentelemetry-instrumentation-httpx \
  pydantic-ai

Step 2: Add Automatic Instrumentation

opentelemetry-bootstrap --action=install

Step 3: Instrument your Pydantic AI application

After setting up the OpenTelemetry configurations for traces, logs, and metrics, initialize Pydantic AI instrumentation by calling Agent.instrument_all()

:

from pydantic_ai.agent import Agent

Agent.instrument_all()

This call enables automatic tracing, logs, and metrics collection for all Pydantic AI agents in your application.

📌 Note: Ensure this is called before any Pydantic AI related calls to properly configure instrumentation of your application

Step 4: Run an example

from pydantic_ai import Agent, RunContext
import asyncio

Agent.instrument_all()

roulette_agent = Agent(
    'openai:gpt-4o',
    deps_type=int,
    system_prompt=(
        'Use the `roulette_wheel` function to see if the '
        'customer has won based on the number they provide.'
    ),
    instrument=True
)

@roulette_agent.tool
async def roulette_wheel(ctx: RunContext[int], square: int) -> str:
    """check if the square is a winner"""
    return 'winner' if square == ctx.deps else 'loser'

async def main():
    success_number = 18
    result = await roulette_agent.run('Put my money on square eighteen', deps=success_number)
    print(result.output)

if __name__ == '__main__':
    asyncio.run(main())

📌 Note: Pydantic AI supports a

[variety of model providers]for LLMs. In this example, we're using OpenAI. Before running this code, ensure that you have set the environment variableOPENAI_API_KEY

with your generated API key.

Step 5: Run your application with auto-instrumentation

OTEL_RESOURCE_ATTRIBUTES="service.name=<service_name>" \
OTEL_EXPORTER_OTLP_ENDPOINT="https://ingest.<region>.signoz.cloud:443" \
OTEL_EXPORTER_OTLP_HEADERS="signoz-ingestion-key=<your-ingestion-key>" \
OTEL_EXPORTER_OTLP_PROTOCOL=grpc \
OTEL_TRACES_EXPORTER=otlp \
OTEL_METRICS_EXPORTER=otlp \
OTEL_LOGS_EXPORTER=otlp \
OTEL_PYTHON_LOG_CORRELATION=true \
OTEL_PYTHON_LOGGING_AUTO_INSTRUMENTATION_ENABLED=true \
opentelemetry-instrument <your_run_command>

is the name of your service<service_name>

<region>

: YourSigNoz Cloud region<your-ingestion-key>

: Your SigNozingestion key- Replace <your_run_command>

with the actual command you would use to run your application. For example:python main.py

Using self-hosted SigNoz? Most steps are identical. To adapt this guide, update the endpoint and remove the ingestion key header as shown in Cloud → Self-Hosted.

Code-based instrumentation gives you fine-grained control over your telemetry configuration. Use this approach when you need to customize resource attributes, sampling strategies, or integrate with existing observability infrastructure.

Step 1: Install the necessary packages in your Python environment.

pip install \
  opentelemetry-api \
  opentelemetry-sdk \
  opentelemetry-exporter-otlp \
  opentelemetry-instrumentation-httpx \
  opentelemetry-instrumentation-system-metrics \
  pydantic-ai

Step 2: Import the necessary modules in your Python application

Traces:

from opentelemetry import trace
from opentelemetry.sdk.resources import Resource
from opentelemetry.sdk.trace import TracerProvider
from opentelemetry.sdk.trace.export import BatchSpanProcessor
from opentelemetry.exporter.otlp.proto.http.trace_exporter import OTLPSpanExporter

Logs:

from opentelemetry.sdk._logs import LoggerProvider, LoggingHandler
from opentelemetry.sdk._logs.export import BatchLogRecordProcessor
from opentelemetry.exporter.otlp.proto.http._log_exporter import OTLPLogExporter
from opentelemetry._logs import set_logger_provider
import logging

Metrics:

from opentelemetry.sdk.metrics import MeterProvider
from opentelemetry.exporter.otlp.proto.http.metric_exporter import OTLPMetricExporter
from opentelemetry.sdk.metrics.export import PeriodicExportingMetricReader
from opentelemetry import metrics
from opentelemetry.instrumentation.system_metrics import SystemMetricsInstrumentor
from opentelemetry.instrumentation.httpx import HTTPXClientInstrumentor

Step 3: Set up the OpenTelemetry Tracer Provider to send traces directly to SigNoz Cloud

from opentelemetry.sdk.resources import Resource
from opentelemetry.sdk.trace import TracerProvider
from opentelemetry.sdk.trace.export import BatchSpanProcessor
from opentelemetry.exporter.otlp.proto.http.trace_exporter import OTLPSpanExporter
from opentelemetry import trace
import os

resource = Resource.create({"service.name": "<service_name>"})
provider = TracerProvider(resource=resource)
span_exporter = OTLPSpanExporter(
    endpoint= os.getenv("OTEL_EXPORTER_TRACES_ENDPOINT"),
    headers={"signoz-ingestion-key": os.getenv("SIGNOZ_INGESTION_KEY")},
)
processor = BatchSpanProcessor(span_exporter)
provider.add_span_processor(processor)
trace.set_tracer_provider(provider)

is the name of your service<service_name>

→ SigNoz Cloud trace endpoint with appropriateOTEL_EXPORTER_TRACES_ENDPOINT

region:https://ingest.<region>.signoz.cloud:443/v1/traces

→ Your SigNozSIGNOZ_INGESTION_KEY

ingestion key

Using self-hosted SigNoz? Most steps are identical. To adapt this guide, update the endpoint and remove the ingestion key header as shown in Cloud → Self-Hosted.

Step 4: Setup Logs

import logging
from opentelemetry.sdk.resources import Resource
from opentelemetry._logs import set_logger_provider
from opentelemetry.sdk._logs import LoggerProvider, LoggingHandler
from opentelemetry.sdk._logs.export import BatchLogRecordProcessor
from opentelemetry.exporter.otlp.proto.http._log_exporter import OTLPLogExporter
import os

resource = Resource.create({"service.name": "<service_name>"})
logger_provider = LoggerProvider(resource=resource)
set_logger_provider(logger_provider)

otlp_log_exporter = OTLPLogExporter(
    endpoint= os.getenv("OTEL_EXPORTER_LOGS_ENDPOINT"),
    headers={"signoz-ingestion-key": os.getenv("SIGNOZ_INGESTION_KEY")},
)
logger_provider.add_log_record_processor(
    BatchLogRecordProcessor(otlp_log_exporter)
)
handler = LoggingHandler(level=logging.INFO, logger_provider=logger_provider)
logging.basicConfig(level=logging.INFO, handlers=[handler])

logger = logging.getLogger(__name__)

is the name of your service<service_name>

→ SigNoz Cloud endpoint with appropriateOTEL_EXPORTER_LOGS_ENDPOINT

region:https://ingest.<region>.signoz.cloud:443/v1/logs

→ Your SigNozSIGNOZ_INGESTION_KEY

ingestion key

Using self-hosted SigNoz? Most steps are identical. To adapt this guide, update the endpoint and remove the ingestion key header as shown in Cloud → Self-Hosted.

Step 5: Setup Metrics

from opentelemetry.sdk.resources import Resource
from opentelemetry.sdk.metrics import MeterProvider
from opentelemetry.exporter.otlp.proto.http.metric_exporter import OTLPMetricExporter
from opentelemetry.sdk.metrics.export import PeriodicExportingMetricReader
from opentelemetry import metrics
from opentelemetry.instrumentation.system_metrics import SystemMetricsInstrumentor
from opentelemetry.instrumentation.httpx import HTTPXClientInstrumentor
import os

resource = Resource.create({"service.name": "<service-name>"})
metric_exporter = OTLPMetricExporter(
    endpoint= os.getenv("OTEL_EXPORTER_METRICS_ENDPOINT"),
    headers={"signoz-ingestion-key": os.getenv("SIGNOZ_INGESTION_KEY")},
)
reader = PeriodicExportingMetricReader(metric_exporter)
metric_provider = MeterProvider(metric_readers=[reader], resource=resource)
metrics.set_meter_provider(metric_provider)

meter = metrics.get_meter(__name__)

SystemMetricsInstrumentor().instrument()
HTTPXClientInstrumentor().instrument()

is the name of your service<service_name>

→ SigNoz Cloud endpoint with appropriateOTEL_EXPORTER_METRICS_ENDPOINT

region:https://ingest.<region>.signoz.cloud:443/v1/metrics

→ Your SigNozSIGNOZ_INGESTION_KEY

ingestion key

Using self-hosted SigNoz? Most steps are identical. To adapt this guide, update the endpoint and remove the ingestion key header as shown in Cloud → Self-Hosted.

📌 Note: SystemMetricsInstrumentor provides system metrics (CPU, memory, etc.), and HTTPXClientInstrumentor provides outbound HTTP request metrics such as request duration. Pydantic AI additionally exposes LLM specific metrics as part of their SDK. If you want to add custom metrics to your Pydantic AI application, see

[Python Custom Metrics].

Step 6: Instrument your Pydantic AI application

After setting up the OpenTelemetry configurations for traces, logs, and metrics, initialize Pydantic AI instrumentation by calling Agent.instrument_all()

:

from pydantic_ai.agent import Agent

Agent.instrument_all()

This call enables automatic tracing, logs, and metrics collection for all Pydantic AI agents in your application.

📌 Note: Ensure this is called before any Pydantic AI related calls to properly configure instrumentation of your application

Step 7: Run an example

from pydantic_ai import Agent, RunContext
import asyncio

roulette_agent = Agent(
    'openai:gpt-4o',
    deps_type=int,
    system_prompt=(
        'Use the `roulette_wheel` function to see if the '
        'customer has won based on the number they provide.'
    ),
    instrument=True
)

@roulette_agent.tool
async def roulette_wheel(ctx: RunContext[int], square: int) -> str:
    """check if the square is a winner"""
    return 'winner' if square == ctx.deps else 'loser'

async def main():
    success_number = 18
    result = await roulette_agent.run('Put my money on square eighteen', deps=success_number)
    print(result.output)

if __name__ == '__main__':
    asyncio.run(main())

📌 Note: Pydantic AI supports a

[variety of model providers]for LLMs. In this example, we're using OpenAI. Before running this code, ensure that you have set the environment variableOPENAI_API_KEY

with your generated API key.

View Traces, Logs, and Metrics in SigNoz

Your Pydantic AI commands should now automatically emit traces, logs, and metrics.

You should be able to view traces in Signoz Cloud under the traces tab:

When you click on a trace in SigNoz, you'll see a detailed view of the trace, including all associated spans, along with their events and attributes.

You should be able to view logs in Signoz Cloud under the logs tab. You can also view logs by clicking on the “Related Logs” button in the trace view to see correlated logs:

When you click on any of these logs in SigNoz, you'll see a detailed view of the log, including attributes:

You should be able to see Pydantic related metrics in Signoz Cloud under the metrics tab:

When you click on any of these metrics in SigNoz, you'll see a detailed view of the metric, including attributes:

Dashboard

You can also check out our custom Pydantic AI dashboard here which provides specialized visualizations for monitoring your Pydantic AI usage in applications. The dashboard includes pre-built charts specifically tailored for LLM usage, along with import instructions to get started quickly.

── more in #ai-tools 4 stories · sorted by recency
── more on @pydantic ai 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
Live at https://your-agent.zahid.host
Get free account → Pricing
from €0/mo · no card required
LIVE [news/pydantic-ai-observab…] indexed:0 read:7min 2026-06-29 ·