> For the complete documentation index, see [llms.txt](https://docs.crobox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.crobox.com/how-to-guides/sagent/monitoring.md).

# Monitoring

Track your Sagent's health with built-in monitoring widgets, filters, and conversation-level signals.

The **Monitoring** tab helps you spot changes in Sagent health after launch. It surfaces conversation-level signals and trends that may require investigation.

Use monitoring to identify unexpected responses, catalog gaps, and shifts in shopper behavior. Review it regularly after configuration or catalog changes.

Monitoring lives inside each Sagent. It has two tabs:

* [Overview](/how-to-guides/sagent/monitoring/overview.md) tracks quality, tool performance, and flagged-conversation trends.
* [Conversations](/how-to-guides/sagent/monitoring/conversations.md) lets you inspect individual sessions and their metadata.

Monitoring is an operational health view. It does not measure purchases, revenue, or overall site traffic.

### Related guides

Start with [Setup](/how-to-guides/sagent/setup.md), [Data](/how-to-guides/sagent/data.md), and [Deploy](/how-to-guides/sagent/deploy.md) if you are still configuring Sagent.


---

# 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.crobox.com/how-to-guides/sagent/monitoring.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.