Browse Source

node-mixins/config: Switch fsAvailable warning and critical thresholds

Problem: In 0b50eb7294 the usage of the
threshold variables was adjusted. The values had been switched as well
resulting in reversed thresholds after the commit above. Warnings now
have a smaller threshold than critical alerts.

Solution: Adjust thresholds to reflect that warnings should be alerted
on before critical alerts.

Issues: https://github.com/prometheus/node_exporter/pull/2352

Signed-off-by: Jan Fajerski <jfajersk@redhat.com>
pull/2395/head
Jan Fajerski 3 years ago committed by Johannes 'fish' Ziemke
parent
commit
cec414df78
  1. 4
      docs/node-mixin/config.libsonnet

4
docs/node-mixin/config.libsonnet

@ -49,8 +49,8 @@
// Available disk space (%) thresholds on which to trigger the // Available disk space (%) thresholds on which to trigger the
// 'NodeFilesystemAlmostOutOfSpace' alerts. // 'NodeFilesystemAlmostOutOfSpace' alerts.
fsSpaceAvailableCriticalThreshold: 5, fsSpaceAvailableWarningThreshold: 5,
fsSpaceAvailableWarningThreshold: 3, fsSpaceAvailableCriticalThreshold: 3,
rateInterval: '5m', rateInterval: '5m',
// Opt-in for multi-cluster support. // Opt-in for multi-cluster support.

Loading…
Cancel
Save