> 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/other-features/agentless-monitoring.md).
# Agentless Monitoring
Datasentinel offers an agentless approach for remote monitoring of PostgreSQL clusters, eliminating the need for local agent installations.
## How it works
Within the Agentless architecture, the platform establishes remote connections to PostgreSQL clusters through internal agents and gathers data using the PULL method.
This becomes particularly advantageous for monitoring cloud-managed clusters as well as PostgreSQL instances running in containers such as:
* [AWS Aurora](https://aws.amazon.com/rds/aurora/)
* [AWS RDS](https://aws.amazon.com/rds/)
* [Google Cloud SQL](https://cloud.google.com/sql/postgresql)
* [Google AlloyDB](https://azure.microsoft.com/en-us/products/postgresql)
* [Microsoft Azure database](https://azure.microsoft.com/en-us/products/postgresql)
* [Kubernetes](https://kubernetes.io/)
* [Docker](https://www.docker.com/)
* Any other cloud managed database
{% hint style="info" %}
A hybrid architecture that integrates both agent-based and agentless methods is feasible.
{% endhint %}
Agentless Architecture
{% hint style="warning" %}
Using this approach, system metrics like CPU usage, memory usage, swap, network activity, and I/O operations are not monitored unless the [system\_stats extension](/manual/getting-started/postgresql-clusters/extensions/system_stats.md) is installed.
{% endhint %}
## Add Connection
### Through API
Please consult the API documentation for further information
{% content-ref url="/pages/QzfvS4NlK6uuNUarhtfv" %}
[Connection](/manual/implementation/platform-usage/api-reference/connection.md)
{% endcontent-ref %}
### Through UI
Open tools menu:
Click on **Agentless settings:**
Then
Adding a connection through the User Interface
## Limit configuration
The collection settings of the agentless instances are set once for the whole platform, in the `agent` section of the backend configuration file: table and query monitoring limits, query identifier and query monitoring filters.
Refer to [Backend configuration: Agentless agents](/manual/implementation/platform-usage/configuration/backend.md#agentless-agents) for the list of parameters and how to change them.
---
# 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/other-features/agentless-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.
