eG Monitoring
 

Measures reported by MySQLRpSlvStTest

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 MySQLRpSlvStTest 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.

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

Descriptor: Slave/replica server

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
isSlaveSyncWithMaster 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.