#CONFIGURE POSTGRESQL PASSWORD#
#CONFIGURE POSTGRESQL ZIP#
#CONFIGURE POSTGRESQL DOWNLOAD#

Select a location from the dropdown list. It must contain 8 to 128 characters from three of the following categories: English uppercase letters, English lowercase letters, numbers (0 through 9), and non-alphanumeric characters (for example, !, $, #, %).

#CONFIGURE POSTGRESQL PASSWORD#

It can't start with pg_ and these values are not allowed: azure_superuser, azure_pg_admin, admin, administrator, root, guest, or public.Ī new password for the server admin user. Select Backup only if you were restoring from a geo-backup of an existing server.Įnter your server admin username. Select None to create a new server from scratch.

The server can contain only lowercase letters, numbers, and the hyphen (-) character. The domain name is appended to the server name that you provide. The script must be executed by the superuser.A new or an existing resource group from your subscription.Ī unique name that identifies your Azure Database for PostgreSQL server. 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 monitoring user must either have a role of superuser or be granted access to the pg_stat_activity table using the technique described below. See Configure the Database Agent to Monitor Server Hardware. The databases that you want to exclude, separated by commas. However, note that deleting the custom cluster collector will delete all its historical data.Ĭlick to add a new JDBC connection property or edit an existing property for relational databases.Ĭlick if your PostrgreSQL database installation is an EnterpriseDB distribution. If you want to monitor a standalone database, delete the entire custom cluster collector and create a fresh standalone collector.

You cannot convert a custom cluster collector to a standalone collector.

If you want to specify different parameters for the sub–collectors, while creating or editing the collector configuration, you can do that only via the Create Collector API.

#CONFIGURE POSTGRESQL ZIP#

Then, you must copy the JAR file to the lib directory of the database agent zip file.Īll connection parameters other than the hostname or IP address, and port details of the sub-collector are the same as the main collector.

#CONFIGURE POSTGRESQL DOWNLOAD#

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. When CyberArk is enabled, information about Application, Safe, Folder, and Object is required to fetch the username and password for your database. The password of the user who is connecting to and monitoring the database through the Database Agent.Ĭlick to enable CyberArk for database username and password. The user should have the permissions described in User Permissions for PostgreSQL. The name of the user who is connecting to and monitoring the database through the Database Agent. You can also specify a custom connection string, which is useful for setting custom authentication options.

The JDBC connection string generated by the database agent, for example, dbc:postgresql://. The TCP/IP address of the port on which your database communicates with the Database Agent. The hostname or IP address of the machine that your database is running on. The name you want to identify the collector by. The Database Agent that manages the collector. The database type that you want to monitor.

Configure postgresql