MySQL Long Running Queries Test

This test tracks the currently executing queries on a 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.

Target of the test : A MySQL server

Agent deploying the test : An internal/remote agent

Outputs of the test : One set of results for the database being monitored

Configurable parameters for the test
  1. TEST PERIOD – How often should the test be executed
  2. Host – The IP address of the MySQL server
  3. Port – The port on which the server is listening
  4. db – the name of a database on the server
  5. Usernameand password - The eG agent has to be configured with the credentials of a user who has server-wide process and select privileges on the monitored MySQL server. To know how to create such a user, refer to Pre-requisites for Monitoring the MySQL Server topic.
  6. Confirm password – Confirm the password by retyping it here.
  7. elapsed time - 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. The default value is 10.
  8. EXCLUDE USER - Specify the user you want to exclude from the list of long running queries. By default, this parameter is set to "none". However, you have the option to configure this parameter if they want to exclude specific users.
  9. EXCLUDE COMMAND - Specify the command you want to exclude from the list of long running queries. For example “backup” queries are included in the long-running queries list, they will be automatically excluded based on this parameter. As a result, only balance queries will be displayed in the UI. By default, this parameter set to “NONE”.

  10. DETAILED DIAGNOSIS – 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 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.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

Long running queries:

Indicates the number of queries currently executing on the database server that have been running for more time than the configured ELAPSED TIME.

Number

The detailed diagnosis for this measure indicates the exact queries and which user is executing the queries. This information can be very useful in identifying queries that may be candidates for optimization.

Maximum elapsed time

Indicates the maximum time taken by the queries to this database.

Secs

 

Average elapsed time

Indicates the average time taken by queries to execute on this database.

Secs

If the value of this measure is very high, it could either indicate that the database is unable to process the queries quickly or that one/more queries to the database are taking too long to execute. Improper indexing and fragmented tables in the database are common causes for slowdowns at the database-level. Besides the above, queries that are improperly structured can also take time to execute. The longer a query executes on the database, higher would be the resource consumption of that query. It is therefore imperative that such resource-intensive queries are quickly isolated and fine-tuned, so as to prevent degradations in the performance of the database server.

The detailed diagnosis for the Long running queries measure indicates the exact queries and which user is executing the queries. This information can be very useful in identifying queries that may be candidates for optimization.

DDlongrunqueries

Figure 1 : The detailed diagnosis of the Long running queries measure