MySQL Test

This test monitors the availability and responsiveness of the MySQL database server by emulating a client connecting and executing queries on the MySQL server.

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

MySQL server availability:

Indicates the availability of the server to execute a user query.

Percent

The availability is 100% when the server does respond to a request and 0% when it is not. Availability problems may be caused by a misconfiguration / malfunctioning of the database server, or if the server has not been started.

Besides the above, this measure will report that the server is unavailable even if a connection to the database instance is unavailable, or if a query to the database fails. In this case, you can check the values of the DB connection availability and Query processor availability measures to know what is exactly causing the database instance to not respond to requests - is it owing to a connection unavailability? or is it due to a query failure?

Connection time to database server:

 

Indicates the time taken to connect to the database server.

Secs

A dramatic increase in this value may be because the server has reached its connection handling capacity.

Query execution time:

Indicates the time taken to execute a database query.

Secs

A dramatic increase in this value could indicate a processing bottleneck with the database server.

Total response time:

Indicates the time taken by the database server to respond to a user query. This is the sum of the connection and query execution times.

Secs

A sudden increase in response time is indicative of a bottleneck with the database server.

DB connection availability:

Indicates whether the database connection is available or not.

Percent

If this measure reports the value 100 , it indicates that the database connection is available.  The value 0 on the other hand indicates that the database connection is unavailable. A connection to the database may be unavailable if the database is down or if the database is listening on a port other than the one configured for it in the eG manager or owing to a poor network link. If the MySQL server availability measure reports the value 0, then, you can check the value of this measure to determine whether/not it is due to the unavailability of a connection to the server.

Query processor availability:

Indicates whether the database query is executed successfully or not.

Percent

If this measure reports the value 100, it indicates that the query executed successfully.  The value 0 on the other hand indicates that the query failed. In the event that the MySQL server availability measure reports the value 0, check the value of this measure to figure out whether the failed query is the reason why that measure reported a server unavailability. 

Records fetched:

Indicates the number of records fetched from the database.

Number

The value 0 indicates that no records are fetched from the database