This test tracks the currently executing queries on an MySQL server and determines the number of queries that have been running for a long time. You can also use the detailed diagnosis of this test to drill down to the exact queries that have been running for an unreasonably long time, and thus isolate the resource-intensive queries to the database.

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

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

• Specify the name of a database on the MySQL server in the DB text box.

• Provide the credentials of the user who has server-wide PROCESS and SELECT privileges on the monitored MySQL server in the USERNAME text box.

• Enter the password that corresponds to the specified USERNAME in the PASSWORD text box.

• Confirm the password by retyping it in the CONFIRM PASSWORD text box.

• In the ELAPSED TIME text box, specify the duration (in seconds) for which a query should have executed for it to be regarded as a long running query.

• To make diagnosis more efficient and accurate, the eG Enterprise suite 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 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 normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

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