summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 8cc1b61)
raw | patch | inline | side by side (parent: 8cc1b61)
author | Florian Forster <octo@collectd.org> | |
Tue, 29 Nov 2016 07:56:42 +0000 (08:56 +0100) | ||
committer | Florian Forster <octo@collectd.org> | |
Tue, 29 Nov 2016 07:56:42 +0000 (08:56 +0100) |
src/collectd.conf.pod | patch | blob | history |
diff --git a/src/collectd.conf.pod b/src/collectd.conf.pod
index b043a89f64afd3fe790455b7bab79b88a14d9a41..489b7e0b0397be5ef52b91d12d6ffe6885dddeb7 100644 (file)
--- a/src/collectd.conf.pod
+++ b/src/collectd.conf.pod
=item B<ResolveJitter> I<seconds>
-When I<collectd> connects to a TSDB node, it will request the DNS. This can
-become a problem if the TSDN node is unavailable or badly configured because
-collectd will request DNS in order to reconnect for every metric, which can
-flood your DNS. So you can cache the last value for I<ResolveInterval> seconds
-(default: B<600>, i.e. 10 minutes).
+When I<collectd> connects to a TSDB node, it will request the hostname from
+DNS. This can become a problem if the TSDB node is unavailable or badly
+configured because collectd will request DNS in order to reconnect for every
+metric, which can flood your DNS. So you can cache the last value for
+I<ResolveInterval> seconds (default: B<600>, i.e. 10 minutes).
You can also define a jitter, a random interval to wait in addition to
I<ResolveInterval>. This prevents all your collectd servers to resolve the