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

• AWS RDS

• Google Cloud SQL

• Google AlloyDB

• Microsoft Azure database

• Kubernetes

• Docker

• Any other cloud managed database

A hybrid architecture that integrates both agent-based and agentless methods is feasible.

Agentless Architecture

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 is installed.

Add Connection

Through API

Please consult the API documentation for further information

Connection API

Through UI

Open tools menu:

Click on Agentless settings:

Then

Adding a connection through the User Interface

Limit configuration

Table and query monitoring limits can be configured for monitored PostgreSQL instances (since version 2025.11)

Datasentinel monitors table and index activity only if the number of tables in the connected instance is below the configured limit. Query activity is also tracked, with each unique query assigned an ID and stored in a daily cache. If the number of collected queries exceeds the set limit, query monitoring is automatically disabled for the remainder of the day to manage resource usage.

Limits use default values if not set. (Refer to Agent limit settings section for more details).

To set custom values:

1

^{Edit configuration file}

/datasentinel/soft/datasentinel_backend/config/datasentinel.yml

2

^{Set desired values}

agent:
  tables-monitoring-limit: 5000
  query-monitoring-limit: 15000

3

^{Restart dispatcher service}

sudo systemctl stop datasentinel_dispatcher
sudo systemctl start datasentinel_dispatcher

Custom limits apply to all monitored instances using the agentless method.