> For the complete documentation index, see [llms.txt](https://docs.interactive.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.interactive.ai/governance/analytics.md).

# Analytics

Analytics is the infrastructure view of **everything you have deployed:** agents, services, and databases alike. Where Observability records what an agent did, Analytics records how the containers behind it behaved: how much traffic they took, what they returned, how fast, and what they consumed.

### Traffic and response time

**Total requests per domain** breaks volume down by workload over time. **Total requests per status code** does the same by response class, and the **status codes per workload** table gives those same counts per workload, which is the quicker way to see *which* workload is failing rather than *when*. Response time is plotted as p50, p95, and p99 across whatever workloads you have selected.

<div data-with-frame="true"><figure><img src="/files/TlbvQhIa5fbTn0EV4FY3" alt=""><figcaption></figcaption></figure></div>

### CPU and memory

Usage is charted per workload over the selected range, with a table underneath pairing it against what each workload was allocated.

<div data-with-frame="true"><figure><img src="/files/i4P7JRPkhjYBIAb8emK3" alt=""><figcaption></figcaption></figure></div>

{% hint style="info" %}
Analytics shows how deployed workloads behaved. To see what an agent did inside a request, see [Observability](/governance/observability.md). For raw container output, see [Logs](/governance/logs.md).
{% endhint %}


---

# 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.interactive.ai/governance/analytics.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.