> 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/system-health.md).

# System Health

See how much CPU, memory and storage your Tellius deployment is using right now, the content you own, and the jobs that are running.

Under **Settings → System → Monitoring → System Health**, you see how busy your Tellius deployment is right now. Every user can open this page, so anyone can check why their own work is slow. The figures update while the page is open, and **Updated a few seconds ago** at the top of the first card shows how fresh they are.

<figure><img src="https://1702728550-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FC5PhRxmOjkQZJEO6F9Zw%2Fuploads%2FHKcOXuvxxIyPMiYOyo2G%2Fsystem-health-64.png?alt=media&amp;token=d6777a89-c7bb-481d-9c02-ffb4e8277e82" alt="The top of the System Health page with the Current Compute and Memory Utilization card and the Total Storage Utilization ring" width="563"><figcaption></figcaption></figure>

### Current Compute & Memory Utilization

* **CPU Utilization:** the share of processing capacity in use, as a percentage, with the number of cores available to Tellius at the top right.
* **RAM:** the memory in use, in GB, out of the total memory available. The bar under it shows the memory in use, with a legend for **Caching**, **Processing** and **Free**.

### Total Storage Utilization

The ring shows the storage in use, in GB, out of the total, and the percentage used below it. It includes stored data such as the files you upload or import, and metadata.

{% hint style="info" %}
**Storage almost full?** Before a job starts, Tellius checks the disk storage in use, and a job doesn't start when the share in use is above the threshold set on **Storage & Cache**. If the ring is close to full, archive or delete datasets you no longer need, or ask your administrator to review that threshold. See [Storage & Cache](/tellius-6.4/settings/storage-and-cache.md).
{% endhint %}

<figure><img src="https://1702728550-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FC5PhRxmOjkQZJEO6F9Zw%2Fuploads%2FY6hJ7WLaOWUTMfULQQE7%2Fsystem-health-content-jobs.png?alt=media&amp;token=926d663a-7280-4f06-bada-a5a9ddf24916" alt="The User Content card listing Datasets, Vizpad, Insight and Model with Manage links, and the Running jobs card with View all jobs" width="563"><figcaption></figcaption></figure>

### User Content

A snapshot of the objects you own. Each row has a **Manage** link that opens the list where you work with them:

* **Datasets:** the size of your datasets, in GB. **Manage** opens **Data → Dataset**.
* **Vizpad:** the number of Vizpads you own. **Manage** opens the Vizpads list.
* **Insight:** the number of Insights you own. **Manage** opens Insights.
* **Model:** the number of machine learning models you own. **Manage** opens Predict.

### Running jobs

The jobs that are running at this moment. When nothing is running, the card says so. **View all jobs** opens the full list of jobs in notifications.

{% hint style="success" %}
**Reading the page.** High CPU together with many running jobs usually means the system is busy with refreshes or other heavy work, and things speed up once they finish. If memory stays close to the total for a long time, raise it with your administrator.
{% endhint %}

### Related pages

* [Monitoring](/tellius-6.4/settings/monitoring.md)
* [Storage & Cache](/tellius-6.4/settings/storage-and-cache.md)
* [Monitoring usage and system resources](/tellius-6.4/getting-started/admin-guide/monitoring-usage-and-system-resources.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/system-health.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.