MySQL Replication Slave Status Test

In a high availability environment, the replica servers should always be in sync with the master database instance. If the replication fails even for a brief period or if the replica servers are not connected to the master, the replica servers will not have updated data. To avoid this, it is essential to periodically monitor whether/not the replica server is in sync with the master MySQL database instance. The MySQL Replication Slave Status test helps administrators in this regard!

This test auto-discovers the replica servers/slaves connected to the target MySQL database server instance and reports whether/not each replica server/slave is in sync with the master MySQL database server instance.

Target of the test : A MySQL server

Agent deploying the test : An internal/remote agent

Outputs of the test : One set of results for each slave/replica server connected to the target database being monitored

Configurable parameters for the test

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 topic. For this 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>';
Confirm Password	Confirm the password by retyping it here.
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
Is slave sync with master?	Indicates whether/not this replica server/slave is in sync with the master MySQL database server.		The values reported by this measure and its numeric equivalents are mentioned in the table below: Measure Value Numeric Value Yes 1 No 0 Note: By default, this measure reports the Measure Values listed in the table above to indicate whether/not this replica server/slave is in sync with the master MySQL database server. The graph of this measure however, is represented using the numeric equivalents only i.e., 0 or 1. By comparing this measure across replica servers, administrators can figure out the replica server that is frequently not in sync with the master MySQL database server instance. The detailed diagnosis of this measure lists the Session ID, Replication status, Host name and the Replication state of each replica server.