On this page:
On this page:
|Database Type||The database type that you want to monitor.|
|Database Agent||The Database Agent that manages the collector.|
|Name||The name you want to identify the collector by.|
|Hostname or IP Address||The hostname or IP address of the machine that your database is running on.|
|EnterpriseDB||Click if your PostrgreSQL database installation is an EnterpriseDB distribution.|
|Listener Port||The TCP/IP address of the port on which your database communicates with the Database Agent|
|Custom JDBC Connection String||The JDBC connection string generated by the database agent, for example, |
|Username||The name of the user who is connecting to and monitoring the database through the Database Agent. The user should have the permissions described in User Permissions for PostgreSQL.|
|Password||The password of the user who is connecting to and monitoring the database through the Database Agent.|
Click to monitor multiple database instances in a consolidated view, and aggregate metrics of multiple databases. To monitor a custom cluster, you can add additional hostname or IP address, and port details for each sub-collector. You can add up to a total of 29 sub-collectors. Thereby, 30 databases can be monitored in a custom cluster. In addition to the licenses consumed by the main collector, each sub-collector consumes one or more licenses, depending on the database type.
|Connection Properties||Click to add a new JDBC connection property or edit an existing property for relational databases.|
|CyberArk||Click to enable CyberArk for database username and password. When CyberArk is enabled, information about Application, Safe, Folder, and Object is required to fetch the username and password for your database. To use CyberArk with Database Visibility, you must download the JavaPasswordSDK.jar file from the CyberArk web site and rename the file to cyberark-sdk-9.5.jar. Then, you must copy the JAR file to the lib directory of the database agent zip file.|
|Exclude Databases||The databases that you want to exclude, separated by commas.|
|Logging Enabled||Click to enable verbose mode logging, which logs all communications between the Controller and the Collector. Enable only during troubleshooting because logging consumes a lot of disk space. If you have enabled logging, you can click the logging icon in the Log column of the Collector Administration window to view the log file. The log files are located in the <db_agent_home>\agent directory and have the format <CollectorName>_out.log and <CollectorName>_err.log.|
User Permissions for PostgreSQL
The monitoring user must either have a role of superuser or be granted access to the pg_stat_activity table using the technique described below.
The following script allows you to create a SECURITY DEFINER function that is owned by the superuser, and runs the query you want, thus allowing non-superusers to see the contents of
pg_stat_activity by calling the
The script must be executed by the superuser.
The monitoring user must also be able to connect remotely to the PostgreSQL instance from the AppDynamics for Databases machine.