Platform
Installation completes within minutes, ensuring that all components are operational upon completion.
Last updated
Installation completes within minutes, ensuring that all components are operational upon completion.
Last updated
To upgrade an existing platform, please refer to
The platform is available exclusively on linux systems:
RHEL8, Rocky linux 8, AlmaLinux 8
RHEL9, Rocky linux 9, AlmaLinux 9
Debian Bullseye
A license key is required to use Datasentinel.
Obtain a Datasentinel license key:
Users who want to try Datasentinel can obtain a
Existing customers can obtain their license key from support:
Refer to the documentation for instructions on updating the to enable the license key.
The sizing of the machine (cpus, memory, storage) to be provisioned, will depend on the number of PostgreSQL instances to monitor as well as the data retention chosen. Default sizing recommendations with a retention of 14 days
1 to 10
8GB
25GB
11 to 50
16GB
50GB
51 to 100
32GB
75GB
101 to 200
64GB
100G
>200
96GB
150GB
For enhanced memory management on a server hosting Datasentinel, it is advised to set the swappiness parameter to a value of 5.
You can confirm the current value:
Here are the firewall settings necessary for Datasentinel
The listening port of the platform server must be accessible to connect to the GUI. The port is the https port 443 by default and can be changed.
1. Agent-based mode
The listening port of the platform server must be accessible in both directions (PUSH and PULL) from the agents' servers.
Each agent listens on port 8282 by default (updatable). The platform server must be able to communicate with the agent servers on this port (PUSH and PULL)
2. Agentless mode
The platform connects directly to PostgreSQL instances. The listening port of each PostgreSQL instance must be accessible from the platform
2025-02-21
2025.02
During installation, you will need to be logged in as the root account. However, this is the only time this account is required. After installation, all modules and future updates will be executed using the defined application account.
Uncompress the downloaded file to create two files:
init_datasentinel.sh
and datasentinel-platform.tar.gz
The script executes in less than 2 minutes and performs multiple actions:
Requests user input for the application username (default is datasentinel). The user can be pre-created with bash as the default shell.
Requests the application listening port (default is 443)
Creates the /datasentinel directory if it doesn't already exist
Decompresses datasentinel-platform.tar.gz to install all components
Creates entries in bash_profile
and crontab
Deploys services for automatic restart
Starts all components.
At the end of the installation, the platform should be up and running.
The listening port must be opened and accessible.
Also, be careful with your firewall configuration (SELinux, firewalld) if any.
nginx is the entry component for Datasentinel, listening on port 443 by default for all incoming communications from other servers.
It communicates locally with other components via their respective listening ports. Config file /etc/nginx/conf.d/datasentinel.conf
If a 502 error appears on the graphical interface despite all components being up and running, it’s worth checking the firewall settings, such as SELinux
The on-premises platform utilizes a self-signed certificate configured with NGINX.
The self-signed certificate is located in the /etc/nginx/certs
directory.
If desired, you can replace it with your own certificate. To do so:
Generate a certificate for the platform machine.
Replace the existing files cert_datasentinel.pem
and key_datasentinel.pem
with the real certificate
Restart NGINX or reload it: /usr/sbin/nginx -s reload
Datasentinel utilizes the following components:
Nginx web server
Timeseries database InfluxDB
Grafana Frontend, which includes a PostgreSQL database and Datasentinel Frontend as a plugin.
Another method to check the status of the platform is by querying its API using the following curl command
Datasentinel generates logs, which are located in the /datasentinel/log
directory, except for the NGINX log file
/var/log/https_datasentinel.log
Nginx log access (by default, access log is off)
datasentinel.log
Backend log file
dispatcher.log
Agentless feature log file
alerting.log
Alerting and Notification log file
scheduler.log
Scheduler log file
backend_to_influx.log
Log data copied to influxdb database in case of errors
grafana.log
Grafana log access
The platform is packaged as a single file, install-datasentinel-platform-<<OS>>-latest.tar.gz, which includes all necessary .
Prior to starting the installation process, it is necessary to install , as it serves as the initial entry point for Datasentinel.
To begin using Datasentinel, you must update the license by following the instructions on .
Datasentinel
Datasentinel dispatcher ( feature)