You can monitor any version of PostgreSQL with Database Visibility.
|Create New Collector
|The database type that you want to monitor.
|The Database Agent that manages the collector.
|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.
|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,
dbc:postgresql://. You can also specify a custom connection string, which is useful for setting custom authentication options.
|Username and Password
|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.
|The password of the user who is connecting to and monitoring the database through the Database Agent.
|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.
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.
|Click to add a new JDBC connection property or edit an existing property for relational databases.
|Click if your PostrgreSQL database installation is an EnterpriseDB distribution.
|The databases that you want to exclude, separated by commas.
|Monitor Operating System
|See Configure the Database Agent to Monitor Server Hardware.
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
get_sa() function and
pg_stat_statements by calling the
get_querystats( ) function respectively. The script must be executed by the superuser.
Ensure that you create the
pg_stat_statements extension by using the command,
create extension pg_stat_statements.
CREATE FUNCTION get_sa()
RETURNS SETOF pg_stat_activity LANGUAGE sql AS
$$ SELECT * FROM pg_catalog.pg_stat_activity; $$
CREATE VIEW pg_stat_activity_allusers AS SELECT * FROM get_sa();
GRANT SELECT ON pg_stat_activity_allusers TO public;
CREATE FUNCTION get_querystats()
RETURNS SETOF pg_stat_statements LANGUAGE sql AS
$$ SELECT * FROM pg_stat_statements; $$
CREATE VIEW pg_stat_statements_allusers AS SELECT * FROM get_querystats();
GRANT SELECT ON pg_stat_statements_allusers TO public;
The monitoring user must also be able to connect remotely to the PostgreSQL instance from the AppDynamics for Databases machine.