Agents Administration - Tests
 

Default Parameters for PgRpoTest

In a high availability setup, this test auto-discovers the replica servers connecting to the target PostgreSQL database server (which is the master) and for each replica server, reports the amount of data that is yet to be synced from the master. Using this test, administrators can figure out the replica server that is more vulnerable to data loss in case of potential server crash and fine-tune backup schedules accordingly.

This page depicts the default parameters that need to be configured for the PgRpoTest.

  • The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

  • In order to monitor a PostgreSQL server, you need to manually create a special database user account in every PostgreSQL database instance that requires monitoring. When doing so, ensure that this user is vested with the superuser privileges. The sample script we recommend for user creation for eG monitoring is:

    CREATE ROLE eguser LOGIN

    ENCRYPTED PASSWORD {‘eguser password’}

    SUPERUSER NOINHERIT NOCREATEDB NOCREATEROLE;

    Specify the name of this user in the USERNAME text box.

  • Specify the password in the PASSWORD text box, associated with the above USERNAME (can be ‘NULL’). Here, ‘NULL’ means that the user does not have any password.

  • Confirm the Password (if any) by retyping it in CONFIRM PASSWORD text box.

  • In the DB NAME text box, specify the name of the database to connect to. The default is “postgres”.

  • If the PostgreSQL server being monitored is an SSL-enabled server, then set the SSL flag to Yes. If not, then set the SSL flag to No.

  • Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz*” and $port will be changed to “80” when configuring a test.