Configuration of PgDeadLocksTest

This test reports the number of deadlocks that occured and also the maximum waiting time, which helps administrators to detect and resolve the bottleneck condition before it affects the performance of the server.

This page depicts the default parameters that need to be configured for the PgDeadLocksTest 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.

• In the PORT text box, specify the port on which the server is listening. The default port is 5432.

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

• Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD FREQUENCY.

• To make diagnosis more efficient and accurate, the eG Enterprise 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 for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enabled/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 normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

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