> 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.md).

# Monitoring

Watch the health of your Tellius deployment: compute, memory and storage, query performance alerts, service log levels and the logs of scheduled jobs.

**Settings → System → Monitoring** brings together the pages for keeping an eye on your Tellius deployment and for troubleshooting it with Tellius Support. Each page covers one part:

| Page                                                                                 | What it's for                                                                                | Who sees it |
| ------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------- | ----------- |
| [System Health](/tellius-6.4/settings/monitoring/system-health.md)                   | CPU, memory and storage in use right now, the content you own, and the jobs that are running | Every user  |
| [Performance Monitoring](/tellius-6.4/settings/monitoring/performance-monitoring.md) | Thresholds and email alerts for query performance and LLM validation                         | Super users |
| [Runtime Log Level](/tellius-6.4/settings/monitoring/runtime-log-level.md)           | How much detail each Tellius service writes to its logs, changed without a restart           | Super users |
| [Scheduled Job Logs](/tellius-6.4/settings/monitoring/scheduled-job-logs.md)         | The logs of each run of a schedule, to preview or download                                   | Super users |

{% hint style="success" %}
**Where to start when Tellius feels slow.** Open **System Health** first. High CPU or memory, or many running jobs, often explain a slow moment. If a scheduled refresh or report failed, look up its run in **Scheduled Job Logs**. Change log levels in **Runtime Log Level** only when Tellius Support asks for more detail.
{% endhint %}

For usage reports built from the Tellius metadata database, such as dataset growth and user activity, see [Monitoring usage and system resources](/tellius-6.4/getting-started/admin-guide/monitoring-usage-and-system-resources.md).

### In this section

* [System Health](/tellius-6.4/settings/monitoring/system-health.md)
* [Performance Monitoring](/tellius-6.4/settings/monitoring/performance-monitoring.md)
* [Runtime Log Level](/tellius-6.4/settings/monitoring/runtime-log-level.md)
* [Scheduled Job Logs](/tellius-6.4/settings/monitoring/scheduled-job-logs.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.md?ask=<question>&goal=<user_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.