X-Git-Url: https://git.verplant.org/?a=blobdiff_plain;f=src%2Fcollectd.conf.pod;h=781e273823730d9265dfeea6dc15f0f3729c5ad9;hb=d07f285d446bdb5abbb6294ef592c890f7515200;hp=40c31581a330ed8a4421690574bde8840bbc567a;hpb=173f0b2aa8b0ce5b5d43d9e719e3585f5f9786c7;p=collectd.git

diff --git a/src/collectd.conf.pod b/src/collectd.conf.pod
index 40c31581..781e2738 100644
--- a/src/collectd.conf.pod
+++ b/src/collectd.conf.pod
@@ -1361,6 +1361,7 @@ information.
      Instance "eth0"
      <Type "if_octets">
        FailureMax 10000000
+       DataSource "rx"
      </Type>
    </Plugin>
 
@@ -1411,6 +1412,19 @@ infinity. If a value is less than B<FailureMin> a B<FAILURE> notification will
 be created. If the value is less than B<WarningMin> but greater than (or equal
 to) B<FailureMin> a B<WARNING> notification will be created.
 
+=item B<DataSource> I<DSName>
+
+Some data sets have more than one "data source". Interesting examples are the
+C<if_octets> data set, which has received (C<rx>) and sent (C<tx>) bytes and
+the C<disk_ops> data set, which holds C<read> and C<write> operations. The
+system load data set, C<load>, even has three data sources: C<shortterm>,
+C<midterm>, and C<longterm>.
+
+Normally, all data sources are checked against a configured threshold. If this
+is undesirable, or if you want to specify different limits for each data
+source, you can use the B<DataSource> option to have a threshold apply only to
+one data source.
+
 =item B<Invert> B<true>|B<false>
 
 If set to B<true> the range of acceptable values is inverted, i.E<nbsp>e.