Default Parameters for PgWaitEventTest

By analyzing wait events and their wait times, administrators can receive quick and objective evidence of performance bottlenecks and their probable causes. The PgWaitEventTest enables this analysis. For every type of wait event that is currently experienced by the database server, this test reports the number, and duration of waits, thereby leading you to the specific wait event that may have contributed to a general slowdown/deterioration in server performance.

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

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

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

• The PASSWORDPROFILE list box appears only if one or more password profiles are created for the target host. Typically, to protect the critical servers/services from malicious attacks by online predators, administrators of secured IT environments frequently change the access credentials for the critical servers and services. Once a password is changed, all tests that take that password as a parameter will stop working, until such time the administrator manually reconfigures each test and changes the password. To avoid such anomalies and save administrators the time and effort involved in manually changing the password of tests, eG Enterprise allows the creation of one/more password profiles. With the password profiles, administrators no longer need to manually configure the credentials; instead, they only need to select the Password Profile that contains the credentials to be passed to the test. This means that if a password changes/expires subsequently, it would suffice to change the corresponding Password Profile alone. All the tests configured with that Password Profile will automatically assume the new password.

  Once, you select a password profile from the Password Profile list box, the user credentials will be automatically populated in the corresponding text boxes that follow the Password profile list box. If you do not want to use the password profiles, then, you can ignore selecting the password profile from the list box and manually configure the user credentials.

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

• In the PASSWORD text box, specify the password 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 the CONFIRM PASSWORD text box.

• The DB NAME is 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 above values are provided, click on the UPDATE button to 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.