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

# Monitor

**Monitor** is where a live agent reveals what testing missed. Users ask unexpected questions. They use unfamiliar wording. Their data changes after you build the agent.

Use Monitor to inspect individual executions, score live conversations, and turn reviewed corrections into learning cases. Apply what you learn in [Build](/agent-builder/build.md), such as clearer instructions, a missing skill, or a knowledge gap.

### Review executions

Monitoring lists the agent's execution history. Each row represents one invocation, whether from the embedded widget, an API call, or a trigger.

Open **Manage Agent → Monitoring** to inspect an agent's production activity. The table includes stable identifiers for each execution and its conversation.

| Column              | What it shows                                                                             |
| ------------------- | ----------------------------------------------------------------------------------------- |
| **Execution ID**    | A unique run identifier. Select the copy icon to copy its full value.                     |
| **Agent Name**      | The agent that ran.                                                                       |
| **Conversation ID** | The conversation containing the execution. A conversation can include several executions. |
| **Created At**      | When the execution started.                                                               |

Use the agent filter above the table to inspect another agent in your tenant. This helps trace executions when one agent calls another.

#### Inspect an execution

Select a table row to open its execution trace. Review these details:

* **Skill selection** — Confirm the planner selected skills that match the request.
* **Skill results** — Find authentication errors, timeouts, and schema mismatches.
* **Guardrail results** — See which guardrail handled the execution and why.
* **Step timing** — Identify slow skill calls that increase agent latency.

Sample executions regularly to confirm expected behavior. When someone reports an unexpected response, use the Execution ID or Conversation ID to locate the exact trace.

### Improve production behavior

* [Online-Eval](/agent-builder/monitor/online-eval.md) — Score live conversations after release.
* [Reinforcement Learnings](/agent-builder/monitor/reinforcement-learnings.md) — Turn reviewed production feedback into reusable learning cases.

{% hint style="info" %}
Learning cases do not enter agent memory automatically. Each one is reviewed and approved by a person first — auto-approval is intentionally disabled, so a bad or malicious input cannot quietly teach the agent the wrong thing.
{% endhint %}

***

Validate improvements with [Evals](/agent-builder/test/evals.md) before rolling them out more broadly.

### Use account-wide governance

Monitor focuses on one agent's runs. Use [Governance](/governance/governance.md) and [Control Center](/start-here/control-center.md) to investigate activity across your account.

* [Observability](/governance/observability.md) — Review conversation volume, duration, and outcomes.
* [Evaluation & Quality](/governance/evaluation-and-quality.md) — Monitor quality scores and review low-confidence results.
* [Controls & Audit](/governance/controls-and-audit.md) — Review guardrail results, emergency controls, and account changes.
* [Logs & Data](/governance/logs-and-data.md) — Trace model calls, API requests, and database operations.


---

# 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.uptiq.ai/agent-builder/monitor.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.