MySQL Slave replication lag critical
>>>
( (
mysql_slave_status_seconds_behind_master
-
mysql_slave_status_sql_delay
) and ON (instance)
mysql_slave_status_master_server_id
> 0 ) > 30
The rule calculates each replica's effective lag as mysql_slave_status_seconds_behind_master minus any configured mysql_slave_status_sql_delay, but only for instances that have a non‑zero mysql_slave_status_master_server_id (i.e., are actively replicating). If this adjusted lag is greater than 30 seconds, the alert is triggered.
Exporters Used
Related Alerts
MySQL High QPS
MySQL InnoDB Force Recovery is enabled
MySQL InnoDB history_len too long
MySQL InnoDB log waits
MySQL Slave IO thread not running
MySQL Slave SQL thread not running
MySQL down
MySQL high prepared statements utilization (> 80%)
MySQL high threads running
MySQL restarted
MySQL slow queries
MySQL too many connections (> 80%)
MySQL too many open files
MySQLDown
MySQLGaleraDonorFallingBehind
MySQLGaleraNotReady
MySQLGaleraOutOfSync
MySQLInnoDBLogWaits
MySQLReplicationLag
MySQLReplicationLag
MySQLReplicationNotRunning