You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If there's replica with slave delay, then warn/crit are checked against slavedelay+warn or slavedelay+crit. return(check_levels(lag, warning + slaveDelays[host_node['name']], critical + slaveDelays[host_node['name']], message))
That makes sense as we don't need to change warn/crit level for every replica we add no matter what slaveDelay is configured
But perfdata shows warn/crit without slaveDelay, making perfdata absolutely useless for graphing.
For example, slaveDelay is 3600, warn 200 and crit 4000 OK - Lag is 3602.0 seconds |replication_lag=3602.0;200.0;400.0
Everything is ok, because 3600 is less that 3800/4000
But on the graph it would look like lag is way over warn/crit
If there's replica with slave delay, then warn/crit are checked against slavedelay+warn or slavedelay+crit.
return(check_levels(lag, warning + slaveDelays[host_node['name']], critical + slaveDelays[host_node['name']], message))
That makes sense as we don't need to change warn/crit level for every replica we add no matter what slaveDelay is configured
But perfdata shows warn/crit without slaveDelay, making perfdata absolutely useless for graphing.
For example, slaveDelay is 3600, warn 200 and crit 4000
OK - Lag is 3602.0 seconds |replication_lag=3602.0;200.0;400.0
Everything is ok, because 3600 is less that 3800/4000
But on the graph it would look like lag is way over warn/crit
The text was updated successfully, but these errors were encountered: