> For the complete documentation index, see [llms.txt](https://docs.datasentinel.io/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datasentinel.io/manual/features/tips-and-hints/agentless-and-system-metrics.md).
# Agentless & System Metrics
One of the features of Datasentinel is its ability to offer comprehensive monitoring of PostgreSQL clusters without the need for installing agents on your database servers.
This [Agentless Approach](/manual/features/other-features/agentless-monitoring.md) simplifies the setup and reduces the overhead on your systems. However, a common misconception is that agentless monitoring limits the ability to gather detailed system metrics.
To address this and enhance your monitoring capabilities, Datasentinel supports the integration of the `system_stats` extension.
{% content-ref url="/pages/ucW3vLylxbehbTpefoYg" %}
[system\_stats](/manual/getting-started/postgresql-clusters/extensions/system_stats.md)
{% endcontent-ref %}
When installed on your PostgreSQL server, this extension empowers Datasentinel to collect a wide range of system metrics.
This includes crucial information like CPU usage, memory consumption, disk I/O, and more, providing a deeper insight into the server's performance.
{% hint style="info" %}
Once the metrics are collected, they are displayed in an identical format across both collection methods: agent-based or agentless.
{% endhint %}
---
# 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://docs.datasentinel.io/manual/features/tips-and-hints/agentless-and-system-metrics.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.
