MySQL Cluster Connectivity Test

This test reports the availability and responsiveness of each node in the cluster, and collects statistics pertaining to the query execution time on each node.

Target of the test : A MySQL Cluster

Agent deploying the test : An external agent

Outputs of the test : One set of results for each node on the target MySQL Cluster database server being monitored.

Configurable parameters for the test
Parameter	Description
Test Period	How often should the test be executed
Host	Specify Host name of the server for which the test is to be configured in this text box.
Port	Specify the port to which the specified host listens in this text box.
Database(DB)	Specify the name of a database on the target MySQL Cluster database server being monitored in the Database text box.
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 Cluster database server in the Username and Password text boxes. To know how to create such a user, refer to Pre-requisites for Monitoring the MySQL Cluster
Confirm Password	Confirm the Password by retyping it in the Confirm Password text box.
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 Cluster server is not SSL-enabled by default. To enable the test to connect to an SSL-enabled MySQL Cluster server, set the SSL flag to Yes.
Verify CA	If the eG agent is required to establish an encrypted connection with the target MySQL Cluster 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 Cluster 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.
Include Available Nodes	In the Include Available Nodes text box, provide a comma-separated list of all the available nodes to be included for monitoring. This way, the test monitor and collect metrics from all the available nodes in the cluster. By default, this parameter is set to none. The format of this configuration is: HOSTNAME:PORT, for example, 172.16.8.136:3306,172.16.8.139:3306
Display Nodes	If you want the test to report metrics individually for each node configured in the Include Available Nodes parameter then set Display Nodes value to Yes. In this case, each node in the cluster will be a descriptor of this test. By default, this value is set to No, indicating that this test reports metrics for only a Summary descriptor revealing the database connection availability of the cluster.
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
Database connection availability	Indicates whether the database connection to this node is available or not. For the Summary descriptor this measure reveals the database connection availability of the target cluster.	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 Node 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.
Database connection response time	Indicates the time taken to connect to the cluster node.	Seconds	This measure is not reported for Summary descriptor. A high value could indicate a connection bottleneck. Whenever the Node response time measure soars, you may want to check the value of this measure to determine whether a connection latency is causing the poor responsiveness of the node.
Query processor availability	Indicates whether the query to this node is executed successfully or not.	Percent	This measure is not reported for Summary descriptor. 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 Node 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 node unavailability.
Query execution time	Indicates the time taken for query execution on this node.	Seconds	This measure is not reported for Summary descriptor. A high value could indicate that one/more queries to the node are taking too long to execute. Inefficient/badly designed queries to the database often take too long to execute. If the value of this measure is higher than that of the Connection time measure, you can be rest assured that long running queries are causing the node to respond slowly to requests.
Number of records	Indicates the number of records fetched from the database for this node.	Number	This measure is not reported for Summary descriptor. The value 0 indicates that no records are fetched from the database.
Average Response Time	Indicates the average time taken by the cluster to respond to a query.	Seconds	This measure is reported only for the Summary descriptor. A sudden increase in response time is indicative of a potential performance bottleneck on the database cluster.