Comment on page
The agent is not supported on Windows systems.
// CLI example
datasentinel set port <<port_number>>
Alternatively, you can directly modify the port number in the configuration file situated at
- After altering the port number, it's essential to restart the agent for the changes to take effect.
- Once the agent is restarted, you can communicate with the agent API on the newly configured port.
Yes, you can automate the installation of the agent using various deployment tools and scripts. This allows you to streamline and replicate the installation procedure across multiple systems efficiently. The agent is provided as a
tar.gzexecutable file. (Refer to Agent installation section). The process involves decompressing this file and then configuring it using either the Agent CLI or the Agent API.
Agents require an access token for authentication and seamless communication with the platform. These tokens come with an expiration date.
Here's what you need to keep in mind:
- Token Distribution: The support team will provide you with a valid token when needed. This token must be employed to update the Datasentinel platform.
- Automated Token Download: Agents are designed to automatically download the new token. This process ensures that agents remain authorized to communicate effectively with the platform.
No, the agent does not store data within the individual PostgreSQL instances it monitors. It acts as a bridge to relay metrics and information securely to the platform, where the data is stored and processed for monitoring and analysis purposes.
SELECT current_database(), extname FROM pg_extension WHERE extname ='pg_stat_statements';
The output should display as follows:
current_database | extname
postgres | pg_stat_statements
This query will indicate whether the pg_stat_statements extension is installed in the internal postgres database.
$ps -ef | grep "datasentinel start agent" | grep -v grep
postgres 29213 1 1 14:00 ? 00:00:00 datasentinel start agent
CLI is showing a negative reply
$datasentinel status agent
Copyright 2023 (c) datasentinel- All rights reserved www.datasentinel.io
Agent not started
By default, the agent operates on port 8282, which is used for communication with the CLI.
Here are steps to diagnose and resolve potential issues:
- 1.Firewall Check: Ensure there are no firewall restrictions preventing communication between the CLI and the agent.
- 2.Server Name Resolution: Confirm that the server name is resolved correctly. You can use the following commands as an example:ping `hostname`
- 3.Curl and Telnet Test: Use the following commands to verify connectivity:curl -v telnet://`hostname`:8282This should provide information about successful connection.About to connect() to pg-sales-3420 port 8282 (#0)* Trying 127.0.0.1...* Connected to pg-sales-3420 (127.0.0.1) port 8282 (#0)If you encounter proxy errors due to the https_proxy environment variable, you can disable it:
remove_proxy_os_env: truein the
agentsection of the parameter file
- Restart the agent after making this change.
These steps should help you diagnose and troubleshoot any issues related to the communication between the agent and the CLI. If problems persist, consider referring to the documentation or contacting support for further assistance.
Is it possible to compel the agent to use a specific server name that will be recognized in the platform?
By default, the agent employs the system's default hostname to register on the platform. However, in cases where the server name is unknown, such as when it's not listed in DNS servers, you can utilize an environment variable to manage this scenario effectively.
Before initiating the agent and utilizing the CLI, set the following environment variable:
export DATASENTINEL_AGENT_HOST=<<ip>> or <<hostname>> or <<fqdn>>
You have the flexibility to define this variable with the appropriate IP address, hostname, or fully qualified domain name (FQDN) based on your needs. This approach enables precise control over server name registration when standard hostname resolution is unavailable.