> For the complete documentation index, see [llms.txt](https://docs.healthuniverse.com/overview/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.healthuniverse.com/overview/observability/sdk-integration.md).

# SDK Integration

The Observer aggregates production traces from your deployed agents into a single monitoring [dashboard](/overview/observability/dashboard.md). 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/output
* **LLM 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](/overview/building-apps-in-health-universe/developing-your-health-universe-app/working-with-a2a-agents/observability.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.healthuniverse.com/overview/observability/sdk-integration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.