From: Remi Gacogne Date: Fri, 24 Nov 2023 08:52:03 +0000 (+0100) Subject: dnsdist: Document that the `responses` metric changed in 1.8 X-Git-Tag: dnsdist-1.9.0-alpha4~24^2 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=refs%2Fpull%2F13533%2Fhead;p=thirdparty%2Fpdns.git dnsdist: Document that the `responses` metric changed in 1.8 --- diff --git a/pdns/dnsdistdist/docs/statistics.rst b/pdns/dnsdistdist/docs/statistics.rst index 1d1c73fc6e..00477693ec 100644 --- a/pdns/dnsdistdist/docs/statistics.rst +++ b/pdns/dnsdistdist/docs/statistics.rst @@ -14,8 +14,11 @@ To make sense of the statistics, the following relation should hold: queries - noncompliant-queries = - responses - noncompliant-responses + cache-hits + downstream-timeouts + self-answered + no-policy - + rule-drop + responses - noncompliant-responses + downstream-timeouts + no-policy + rule-drop + +Before 1.8.0, cache hits and self-answered responses were not accounted in the responses counters, so the relation was: + + responses - noncompliant-responses + cache-hits + downstream-timeouts + self-answered + no-policy + rule-drop Note that packets dropped by eBPF (see :doc:`../advanced/ebpf`) are accounted for in the eBPF statistics, and do not show up in the metrics @@ -261,9 +264,9 @@ Current memory usage. responses --------- -Number of responses received from backends. Note! This is not the number of -responses sent to clients. To get that number, add 'cache-hits' and -'responses'. +Number of response sent to clients. + +Before 1.8.0, it was the number of responses received from backends, not accounting for cache hits or self-answered responses. rule-drop ---------