> For the complete documentation index, see [llms.txt](https://help.tellius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tellius.com/tellius-6.4/settings/monitoring/performance-monitoring.md).
# Performance Monitoring
Set thresholds and email alerts for query performance (TQL) and for LLM validation, so administrators hear about slow or failing queries early.
Under **Settings → System → Monitoring → Performance Monitoring**, super users set when Tellius sends alerts about the performance of TQL, the Tellius query service, and about LLM validation. When a threshold is crossed, Tellius emails the people you list. The page has two tabs, **TQL** and **LLM**.
{% hint style="info" %}
**Save works one tab at a time.** **Save** at the top right saves the settings of the tab you're on. If you change both tabs, save each one while it is open. **Cancel** restores the saved values. If you leave the page with unsaved changes, Tellius asks whether to keep editing or discard them.
{% endhint %}
### TQL tab
**Enable TQL Monitoring:** turns monitoring of the TQL API on or off. When it is on, Tellius checks the thresholds below and sends alerts when they are exceeded. Turning it on shows all the fields. Turning it off hides them.
Each number field has an information icon, up and down arrows, and a note with its allowed range. A value outside the range is brought within it.
| Field | What it sets | Range | Starting value |
| --------------------------- | ---------------------------------------------------------------------- | ------------ | -------------- |
| Check Interval (minutes) | How often Tellius runs the checks | 1 to 60 | 10 |
| Monitoring Window (minutes) | The span of time each check looks back over | 1 to 120 | 15 |
| Error Rate Warning (%) | The share of failed requests that raises a warning | 0 to 100 | 5 |
| Error Rate Critical (%) | The share of failed requests that raises a critical alert | 0 to 100 | 10 |
| Minimum Sample Count | The fewest requests in the window before an error-rate alert can fire | 0 to 10,000 | 2 |
| P95 Latency Critical (ms) | The 95th percentile query time that raises a critical alert | 0 to 600,000 | 120,000 |
| P99 Latency Critical (ms) | The 99th percentile query time that raises a critical alert | 0 to 600,000 | 180,000 |
| Slow Query Threshold (ms) | How long a query runs before it counts as slow | 0 to 600,000 | 120,000 |
| Slow Query Count Critical | The number of slow queries in the window that raises a critical alert | 0 to 1,000 | 10 |
| Query Volume Critical | The total number of queries in the window that raises a critical alert | 0 to 10,000 | 300 |
| Alert Cooldown (minutes) | The least time between two alerts for the same condition | 1 to 1,440 | 30 |
| Alert Recipients | The email addresses that receive the alerts, separated by commas | | |
The fields are grouped under **Error Rate Thresholds**, **Latency Thresholds**, **Slow Query Thresholds**, **Query Volume Thresholds** and **Alerting Configuration**. Error rates move in steps of 0.5, and the time fields in steps of 1,000 ms (one second).
{% hint style="success" %}
**Tuning the thresholds.** Start with the starting values and watch for a week. If alerts arrive for short spikes nobody notices, raise **Minimum Sample Count** or widen **Monitoring Window**. If the same alert repeats too often, raise **Alert Cooldown**. Set **Query Volume Critical** above your normal busy hour, so it flags unusual load rather than a normal Monday morning.
{% endhint %}
### LLM tab
**Enable LLM Validation Monitoring:** turns monitoring of LLM validation processes on or off. When it is on, Tellius checks them and sends alerts. Turning it on shows three fields:
* **Check Interval (minutes):** how often Tellius runs the checks, from 1 to 60. The starting value is 10.
* **Alert Cooldown (minutes):** the least time between two alerts for the same condition, from 1 to 1,440. The starting value is 1.
* **Alert Recipients:** the email addresses that receive the alerts, separated by commas.
{% hint style="info" %}
**Use a shared mailbox.** Send alerts to a team address, such as your data platform team, rather than to one person, so alerts are still seen when someone is away.
{% endhint %}
### Who can see this page
Only super users see **Performance Monitoring** in Settings. A custom role reaches it with **Manage system** under **Administration**. See [Custom roles](/tellius-6.4/settings/users-and-access/custom-roles.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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.tellius.com/tellius-6.4/settings/monitoring/performance-monitoring.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
