Agents Administration - Tests
 

Configuration of 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.

The default parameters associated with this test are:

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

  • In the HOST text box, specify the IP address of the host for which this test is to be configured.

  • In the PORT text box, specify the port at which the specified HOST listens. The default port is 5432.

  • 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.

  • To make diagnosis more efficient and accurate, eG embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test, by default, for a particular server, choose the On option against DETAILED DIAGNOSIS. To disable the capability, click on the Off option.

    The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

    • The eG manager license should allow the detailed diagnosis capability.

    • Both the bad and normal frequencies configured for the detailed diagnosis measures should not be 0.

  • If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

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

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of “none” in the parameter value indicates that the corresponding parameter value can be changed if required.