From 421d36537a42d9b397a95d6728b157eb92140d24 Mon Sep 17 00:00:00 2001 From: Florian Forster Date: Mon, 17 Dec 2007 15:48:36 +0100 Subject: [PATCH] collectd.conf(5): Started documenting the threshold thingy. --- src/collectd.conf.pod | 60 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 60 insertions(+) diff --git a/src/collectd.conf.pod b/src/collectd.conf.pod index 49cccdf0..e8f4af78 100644 --- a/src/collectd.conf.pod +++ b/src/collectd.conf.pod @@ -1030,6 +1030,66 @@ the F filesystem that is required by this plugin. The B homepage can be found at L. +=head1 THRESHOLD CONFIGURATION + +Starting with version C<4.3.0> collectd has support for B. By that +we mean that the values are not only stored or sent somewhere, but that they +are judged and, if a problem is recognized, acted upon. + +Since systems and what you expect them to do differ a lot, you can configure +B for your values freely. This gives you a lot of flexibility but +also a lot of responsibility. + + + + Min 0.00 + Max 1000.00 + Invert false + Instance "bar" + + + + Instance "eth0" + + Max 10000000 + + + + + + Instance "idle" + Min 10 + + + + + Instance "cached" + Min 100000000 + + + + + +There are basically two types of configuration statements: The C, +C, and C blocks select the value for which a threshold should be +configured. The C and C blocks may be specified further using the +C option. You can combine the block by nesting the blocks, though +they must be nested in the above order, i.Ee. C may contain either +C and C blocks, C may only contain C blocks and +C may not contain other blocks. If multiple blocks apply to the same +value the most specific block is used. + +The other statements specify the threshold to configure. Currently the +following statements are recognized: + +=over 4 + +=item B I + +... + +=back + =head1 SEE ALSO L, -- 2.11.0