MySQL Resources Test
This test measures the effect of query execution on the disk and memory resources of 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
|
Parameter |
Description |
|---|---|
|
Test Period |
How often should the test be executed. |
|
Host |
The IP address of the MySQL server. |
|
Port |
The port at which the specified host listens. |
|
Database |
Specify the name of a database on the target MySQL database server being monitored |
|
Username 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 For the MySQL Bin Log test to run, the user should additionally possess the following privileges. To configure the above-mentioned user with the specific privileges, issue the commands given below: GRANT REPLICATION CLIENT on *.* to '<username>'@'<IP_address_of_eG_agent>'; GRANT REPLICATION SLAVE on *.* to '<username>'@'<IP_address_of_eG_agent>'; GRANT EXECUTE on *.* to '<username>'@'<IP_address_of_eG_agent>'; |
|
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. |
|
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 |
|---|---|---|---|
|
Open files |
Indicates the number of files that were opened during the last measurement period. |
Number |
|
|
Created temporary files |
Indicates the number of implicit temporary files that were created on the tables of the disk, while executing statements during the last measurement period. |
Number |
|
|
Ratio of created temp tables on disk |
Indicates the percentage of temporary tables that were created on the disk, while executing statements on this node. |
Percent |
|
|
Opened tables cache hits |
Indicates the number of hits for open tables cache lookups. |
Number |
|
|
Opened tables cache misses |
Indicates the number of misses for open tables cache lookups. |
Number |
|
|
Opened tables hit ratio |
Indicates the percentage of hits for open tables cache lookups. |
Percent |
Compare the value of this measure across nodes to figure out the node on which maximum percentage of hits for open tables cache lookups were noticed. |
|
Delayed insert threads |
Indicates the number of delayed insert handler threads that are in use. |
Number |
|
|
Slow launch threads |
Indicates the number of threads that have taken more than slow_launch_time for creation on the database, during the last measurement period. |
Number |
A high value for this measure could cause excessive delay in processing new connection requests to the database server. |
|
Threads active |
Indicates the number of threads that are currently active. |
Number |
A high value for this measure is indicative of a high load on each node of the target cluster database server. |
|
Threads cached |
Indicates the number of threads in the thread cache of the database currently. |
Number |
|
|
Threads spawned |
Indicates the number of threads newly created to handle new connections on the database during the last measurement period. |
Number |
Where possible ensure that the number of total threads is not set to be much larger than the maximum number of simultaneous requests expected for the server. |
|
Open threads |
Indicates the number of threads that were opened on the database during the last measurement period. |
Number |
|
|
Thread usage |
Indicates the percentage of threads that were in use during the last measurement period. |
Percent |
|