X-Git-Url: https://git.octo.it/?a=blobdiff_plain;f=src%2Fcollectd.conf.pod;h=7a66c8188f8182589da12df69cc04e9dbf21ea1e;hb=218c57128f2e54960133cff3e774b5ef9944068a;hp=7cf5c7505482bd9c7a5d4ecbae3730098f69bf85;hpb=b0743c5554fafc6c96180949a8da3766e481b4bd;p=collectd.git

diff --git a/src/collectd.conf.pod b/src/collectd.conf.pod
index 7cf5c750..7a66c818 100644
--- a/src/collectd.conf.pod
+++ b/src/collectd.conf.pod
@@ -150,24 +150,27 @@ plugins that don't provide any configuration, e.g. the I<Load plugin>.
 When set to B<true>, various statistics about the I<collectd> daemon will be
 collected, with "collectd" as the I<plugin name>. Defaults to B<false>.
 
-The "write_queue" I<plugin instance> reports :
+The following metrics are reported:
 
 =over 4
 
-"queue_length" I<type> : the number of elements currently queued. You may want
-to limit this queue with the B<WriteQueueLimitLow>/B<WriteQueueLimitHigh>
-mechanism.
+=item C<collectd-write_queue/queue_length>
 
-"derive-dropped" I<type>-I<type instance> : the number of elements dropped. If
-this value is nul, either everything is going well or you set 
-B<WriteQueueLimitLow>/B<WriteQueueLimitHigh> too high. If this value is not nul
-too often, either you set B<WriteQueueLimitLow>/B<WriteQueueLimitHigh> too low
-or you have a serious problem.
+The number of metrics currently in the write queue. You can limit the queue
+length with the B<WriteQueueLimitLow> and B<WriteQueueLimitHigh> options.
 
-=back
+=item C<collectd-write_queue/derive-dropped>
+
+The number of metrics dropped due to a queue length limitation.
+If this value is non-zero, your system can't handle all incoming metrics and
+protects itself against overload by dropping metrics.
 
-The "cache" I<plugin instance> reports the number of elements in the value list
-cache (the cache you can interact with using L<collectd-unixsock(5)>).
+=item C<collectd-cache/cache_size>
+
+The number of elements in the metric cache (the cache you can interact with
+using L<collectd-unixsock(5)>).
+
+=back
 
 =item B<Include> I<Path> [I<pattern>]
 
@@ -2510,6 +2513,23 @@ do that: By setting B<IgnoreSelected> to I<true> the effect of
 B<Interface> is inverted: All selected interfaces are ignored and all
 other interfaces are collected.
 
+It is possible to use regular expressions to match interface names, if the
+name is surrounded by I</.../> and collectd was compiled with support for
+regexps. This is useful if there's a need to collect (or ignore) data
+for a group of interfaces that are similarly named, without the need to
+explicitly list all of them (especially useful if the list is dynamic).
+Example:
+
+ Interface "lo"
+ Interface "/^veth/"
+ Interface "/^tun[0-9]+/"
+ IgnoreSelected "true"
+
+This will ignore the loopback interface, all interfaces with names starting
+with I<veth> and all interfaces with names starting with I<tun> followed by
+at least one digit.
+
+
 =back
 
 =head2 Plugin C<ipmi>
@@ -2550,9 +2570,13 @@ a notification is sent.
 
 =item B<Chain> I<Table> I<Chain> [I<Comment|Number> [I<Name>]]
 
-Select the rules to count. If only I<Table> and I<Chain> are given, this plugin
-will collect the counters of all rules which have a comment-match. The comment
-is then used as type-instance.
+=item B<Chain6> I<Table> I<Chain> [I<Comment|Number> [I<Name>]]
+
+Select the iptables/ip6tables filter rules to count packets and bytes from.
+
+If only I<Table> and I<Chain> are given, this plugin will collect the counters
+of all rules which have a comment-match. The comment is then used as
+type-instance.
 
 If I<Comment> or I<Number> is given, only the rule with the matching comment or
 the I<n>th rule will be collected. Again, the comment (or the number) will be