This dashboard provides information about replica sets and their members.
This metric provides an overview of database replication operations by type and makes it possible to analyze the load on the replica in more granular manner. These values only appear when the current host has replication enabled.
This metric shows the role of the selected member instance (PRIMARY or SECONDARY).
This metric the number of members in the replica set.
This metric how long ago the last election occurred.
This metric shows the current replication lag for the selected member.
This metric shows the storage engine used on the instance
This metric shows how long it takes to write to the oplog. Without it the write will not be successful.
This is more useful in mixed replica sets (where instances run different storage engines).
This metric shows the time range in the oplog and the oldest backed up operation.
For example, if you take backups every 24 hours, each one should contain at least 36 hours of backed up operations, giving you 12 hours of restore window.
This metric shows the delay between an operation occurring on the primary and that same operation getting applied on the selected member
Elections happen when a primary becomes unavailable. Look at this graph over longer periods (weeks or months) to determine patterns and correlate elections with other events.
This metric shows how long various members were in PRIMARY and SECONDARY roles.
This metric shows the heartbeat return times sent by the current member to other members in the replica set.
Long heartbeat times can indicate network issues or that the server is too busy.
This metric can show a correlation with the replication lag value.
- Page updated 2021-01-11