MySQL Uptime Test
MySql uptime refers to the duration the MySql database remains operational without interruption, ensuring high availability, reliability, and minimal downtime for critical applications and services in enterprise environments.
Monitoring MySql uptime ensures database availability, detects issues early, and minimizes downtime. It helps maintain service reliability, meet SLAs, support business continuity, and optimize performance by identifying trends, failures, or maintenance needs before they impact users or operations.
The MySql Uptime Test monitors the total uptime, time since last restart etc. These metrics help administrators understand the performance implications of uptime and take preventive actions before the database performance drops.
Target of the test : A MySQL Database server
Agent deploying the test : An internal/remote agent
Outputs of the test : One set of results for the MySQL server being monitored
| Parameter | Description |
|---|---|
|
Test Period |
How often should the test be executed. |
|
Host |
The IP address of the MySQL Database server. |
|
Port |
The port on which the server is listening |
|
Database |
Specify the name of the database that is to be monitored on the target MySQL Database server |
|
User and 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 |
|
Confirm Password |
Confirm the password by retyping it here. |
|
Allow Public Key |
By default, the Allow Public Key flag is set to No. But, if the specified USER is created with caching_sha2_password as the authentication plugin, then the eG agent can connect to the target database cluster using RSA public key. To this effect, you have to set Allow Public Key flag to Yes. |
|
SSL |
By default, the SSL flag is set to No, indicating that the target MySQL database server is not SSL-enabled by default. To enable the test to connect to an SSL-enabled MySQL database server , set the SSL flag to Yes. |
|
Verify CA |
If the eG agent is required to establish an encrypted connection with the target MySQL database server by authenticating the server's identity through verifying the server CA certificate, set Verify CA flag to Yes. By default, this flag is set to No. |
|
Truststore Password |
This parameter is applicable only if the Verify CA parameter is set to Yes. To verify the target server certificate, provide the password of the truststore file which contains the server CA certificate in the Truststore Password text box. By default, this parameter is set to none. |
|
Confirm Password |
Confirm the Password by retyping it in the Confirm Password text box. |
|
Keystore Password |
This parameter is applicable only if the Verify CA parameter is set to Yes. To establish a connection with the target MySQL database server , the eG agent needs to have access to the client certificate. For this provide the password of the keystore file which contains the client certificate in the Keystore Password text box. By default, this parameter is set to none. |
|
Confirm Password |
Confirm the Password by retyping it in the Confirm Password text box. |
|
Idle Time |
Specify the time duration (in seconds) above which the processes that are waiting in the database will be regarded as idle. |
|
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:
|
| Measurement | Description | Measurement Unit | Interpretation | ||||||
|---|---|---|---|---|---|---|---|---|---|
|
Has server restarted? |
Indicates whether the database server has been rebooted during the last measurement period or not. |
Number |
If this measure shows 1, it means that the server was rebooted during the last measurement period. By checking the time periods when this metric changes from 0 to 1, an administrator can determine the times when the server was rebooted. |
||||||
|
Uptime since last measure |
Indicates the time period that the database server has been up since the last time this test ran. |
Sec |
If the server has not been rebooted during the last measurement period and the agent has been running continuously, this value will be equal to the measurement period. If the server was rebooted during the last measurement period, this value will be less than the measurement period of the test. For example, if the measurement period is 300 secs, and if the server was rebooted 120 secs back, this metric will report a value of 120 seconds. The accuracy of this metric is dependent on the measurement period - the smaller the measurement period, greater the accuracy. |
||||||
|
Uptime |
Indicates the total time that the server has been up since its last reboot. |
Sec |
This measure displays the number of years, months, days, hours, minutes and seconds since the last reboot. Administrators may wish to be alerted if a server has been running without a reboot for a very long period. Setting a threshold for this metric allows administrators to determine such conditions. |
||||||
|
Is under maintenance? |
Indicates whether/not the server is under maintenance. |
|
The values reported by this measure and their numeric equivalents are available in the table below:
Note: By default, this measure reports the above-mentioned Measure Values while indicating whether the server is under maintenance or not. However, in the graph of this measure, states will be represented using the corresponding numeric equivalents only - i.e., 0 or 1. |