SDK Integration
The Observer aggregates production traces from your deployed agents into a single monitoring dashboard. This page covers how trace data flows into the Observer.
Data Sources
The Observer collects traces from two sources:
Navigator — the platform's AI orchestration engine. Navigator traces are collected automatically with no configuration required.
A2A Agents — any agent you deploy using the Health Universe A2A SDK. Traces are captured automatically when the agent runs in production on Health Universe.
Traces are filtered to production data only and scoped to your workspace. Data is cached and refreshes at intervals ranging from 2 minutes to 1 hour depending on the widget type.
What Gets Traced
The SDK automatically captures:
Agent execution — every
process_message()call with duration, metadata, input/outputLLM calls — model name, token usage, latency (via OpenTelemetry instrumentation)
Document operations — list, download, write operations as child spans
Inter-agent communication — calls to other agents via
call_agent()
For full details on trace structure and adding custom instrumentation, see the A2A Observability guide.
Last updated
Was this helpful?