fix mongodb help

This commit is contained in:
Colin Gagnaire 2019-06-12 15:31:00 +02:00
parent dbec7823b1
commit 4efce54a3a
1 changed files with 3 additions and 3 deletions

View File

@ -107,7 +107,7 @@ sub set_counters {
closure_custom_threshold_check => \&catalog_status_threshold, closure_custom_threshold_check => \&catalog_status_threshold,
} }
}, },
{ label => 'lag', nlabel => 'replication.lag.seconds', set => { { label => 'replication-lag', nlabel => 'replication.lag.seconds', set => {
key_values => [ { name => 'lag' }, { name => 'name' } ], key_values => [ { name => 'lag' }, { name => 'name' } ],
output_template => 'Replication Lag: %s s', output_template => 'Replication Lag: %s s',
perfdatas => [ perfdatas => [
@ -239,12 +239,12 @@ Set critical threshold for members status (Default: '%{health} !~ /up/').
Can used special variables like: %{name}, %{state}, %{health}, Can used special variables like: %{name}, %{state}, %{health},
%{slave_delay}, %{priority}. %{slave_delay}, %{priority}.
=item B<--warning-instance-lag-seconds> =item B<--warning-instance-replication-lag-seconds>
Threshold warning for replication lag between primary and secondary members. Threshold warning for replication lag between primary and secondary members.
Must not be over 0 (between minus slaveDelay and 0). Must not be over 0 (between minus slaveDelay and 0).
=item B<--critical-instance-lag-seconds> =item B<--critical-instance-replication-lag-seconds>
Threshold critical for replication lag between primary and secondary members. Threshold critical for replication lag between primary and secondary members.
Must not be over 0 (between minus slaveDelay and 0). Must not be over 0 (between minus slaveDelay and 0).