# system\_stats

{% hint style="info" %}
This extension is **OPTIONAL** and should be considered solely when you decide to employ the [Agentless approach](https://docs.datasentinel.io/manual/features/other-features/agentless-monitoring) for monitoring your PostgreSQL instances**.**
{% endhint %}

### Installation

{% hint style="warning" %}
To be installed in the internal database named **postgres**
{% endhint %}

For detailed installation instructions of the extension, please consult the GitHub repository <https://github.com/EnterpriseDB/system_stats><br>

You need to grant the role monitor\_system\_stats to the monitoring user.

```sql
// example
GRANT monitor_system_stats to datasentinel;
```

### Monitored metrics

When the **system\_stats** extension is installed, Datasentinel (using the [agentless method](https://docs.datasentinel.io/manual/features/other-features/agentless-monitoring)) starts gathering system metrics directly from PostgreSQL clusters at regular intervals. This is achieved by running SQL queries, which enables Datasentinel to collect detailed system metrics without needing a local agent on each server. <br>

{% hint style="info" %}
With this setup, you can browse and analyze these metrics with the same level of precision and granularity as you would expect if a local agent were installed.\
\
Refer to [Cluster & System Metrics](https://docs.datasentinel.io/manual/features/key-features/cluster-and-system-metrics) for more details.
{% endhint %}

**Metrics**:

* System information
* CPU load
* CPU usage
* Memory usage
* Network usage
* Swap usage
* I/Os statistics
* File-systems usage


---

# Agent Instructions: 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:

```
GET https://docs.datasentinel.io/manual/getting-started/postgresql-clusters/extensions/system_stats.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.