From 0276fb2cb0506f5ff936d853fb7f58729415e33d Mon Sep 17 00:00:00 2001 From: "Andres J. Diaz" Date: Sun, 13 Jun 2010 12:36:46 +0200 Subject: [PATCH] Complete the collectd.conf man page. Add explanations for some parameters in thresholds configuration, link Hysteresis, Hits or Interesting flags. --- src/collectd.conf.pod | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) diff --git a/src/collectd.conf.pod b/src/collectd.conf.pod index 0fcd6746..98b92981 100644 --- a/src/collectd.conf.pod +++ b/src/collectd.conf.pod @@ -4504,6 +4504,13 @@ information. WarningMin 100000000 + + + DataSource "midterm" + FailureMax 4 + Hits 3 + Hysteresis 3 + @@ -4576,6 +4583,27 @@ percentage value, relative to the other data sources. This is helpful for example for the "df" type, where you may want to issue a warning when less than 5E% of the total space is available. Defaults to B. +=item B I + +Sets the number of occurrences which the threshold must be arised before to +dispatch any notification or, in other words, the number of Bs +than the threshold must be match before dispatch any notification. + +=item B I + +Sets the hysteresis value for threshold. The hysteresis is a method to +prevent flapping between states, until a new received value for +a previously matched threshold down below the threshold condition +(B, B or everthing else) minus the hysteresis value, +the failure (respectively warning) state will be keep. + +=item B B|B + +If set to B (the default), the threshold must be treated as +interesting and, when a number of B values will lost, then +a missing notification will be dispatched. On the other hand, if set to +B, the missing notification will never dispatched for this threshold. + =back =head1 FILTER CONFIGURATION -- 2.30.2