Metrics and Statistics
======================
The PowerDNS Recursor collects many statistics about itself.
Regular Statistics Log
----------------------
Every half hour or so (configurable with :ref:`setting-statistics-interval`, the recursor outputs a line with statistics.
To force the output of statistics, send the process a SIGUSR1. A line of statistics looks like this::
stats: 346362 questions, 7388 cache entries, 1773 negative entries, 18% cache hits
stats: cache contended/acquired 1583/56041728 = 0.00282468%
stats: throttle map: 3, ns speeds: 1487, failed ns: 15, ednsmap: 1363
stats: outpacket/query ratio 54%, 0% throttled, 0 no-delegation drops
stats: 217 outgoing tcp connections, 0 queries running, 9155 outgoing timeouts
stats: 4536 packet cache entries, 82% packet cache hits
stats: thread 0 has been distributed 175728 queries
stats: thread 1 has been distributed 169484 queries
stats: 1 qps (average over 1800 seconds)
This means that in total 346362 queries were received and there are 7388 different name/type combinations in the record cache, each entry may have multiple records attached to it.
There are 1773 items in the negative cache, items of which it is known that don't exist and won't do so for the near future.
18% of incoming questions not handled by the packets cache could be answered without any additional queries going out to the net.
The record cache was consulted or modified 56041728 times, and 1583 of those accesses caused lock contention.
Next a line with the sizes of maps that can be consulted by :program:`rec_control` is printed.
The outpacket/query ratio means that on average, 0.54 packets were needed to answer a question.
This ratio can be greater than 100% since additional queries could be needed to actually recurse the DNS and figure out the addresses of nameservers.
0% of queries were not performed because identical queries had gone out previously and failed, saving load on servers worldwide.
217 outgoing tcp connections were done, there were 0 queries running at the moment and 9155 queries to authoritative servers saw timeouts.
The packets cache had 4536 entries and 82% of queries were served from it.
The workload of the the worker queries was 175728 and 169484 respectively.
Finally, measured in the last half hour, an average of 1 qps was performed.
Multi-threading and metrics
---------------------------
Some metrics are collected in thread-local variables, and an aggregate values is computed to report.
Other statistics are recorded in global memory and each thread updates the one instance, taking proper precautions to make sure consistency is maintained.
The only exception are the `cpu-msec-thread-N`_ metrics, which report per-thread data.
.. _metricscarbon:
Sending metrics to Graphite/Metronome over Carbon
-------------------------------------------------
For carbon/graphite/metronome, we use the following namespace.
Everything starts with 'pdns.', which is then followed by the local hostname.
Thirdly, we add 'recursor' to signify the daemon generating the metrics.
This is then rounded off with the actual name of the metric. As an example: 'pdns.ns1.recursor.questions'.
Care has been taken to make the sending of statistics as unobtrusive as possible, the daemons will not be hindered by an unreachable carbon server, timeouts or connection refused situations.
To benefit from our carbon/graphite support, either install Graphite, or use our own lightweight statistics daemon, Metronome, currently available on `GitHub `_.
To enable sending metrics, set :ref:`setting-carbon-server`, possibly :ref:`setting-carbon-interval` and possibly :ref:`setting-carbon-ourname` in the configuration.
.. warning::
If your hostname includes dots, they will be replaced by underscores so as not to confuse the namespace.
If you include dots in :ref:`setting-carbon-ourname`, they will **not** be replaced by underscores.
As PowerDNS assumes you know what you are doing if you override your hostname.
Getting Metrics from the Recursor
---------------------------------
Should Carbon not be the preferred way of receiving metrics, several other techniques can be employed to retrieve them.
Using the Webserver
^^^^^^^^^^^^^^^^^^^
The :doc:`API ` exposes a statistics endpoint at
.. http:get:: /api/v1/servers/:server_id/statistics
This endpoint exports all statistics in a single JSON document.
Using ``rec_control``
^^^^^^^^^^^^^^^^^^^^^
Metrics can also be gathered on the system itself by invoking :doc:`rec_control `::
rec_control get-all
Single statistics can also be retrieved with the ``get`` command, e.g.::
rec_control get all-outqueries
External programs can use this technique to scrape metrics, though it is preferred to use a Prometheus export.
Using Prometheus export
^^^^^^^^^^^^^^^^^^^^^^^
The internal web server exposes Prometheus formatted metrics at
.. http:get:: /metrics
The Prometheus name are the names listed in `metricnames`_, prefixed with ``pdns_recursor_`` and with hyphens substituted by underscores.
For example::
# HELP pdns_recursor_all_outqueries Number of outgoing UDP queries since starting
# TYPE pdns_recursor_all_outqueries counter
pdns_recursor_all_outqueries 7
Sending metrics over SNMP
-------------------------
The recursor can export statistics over SNMP and send traps from :doc:`Lua `, provided support is compiled into the Recursor and :ref:`setting-snmp-agent` set.
MIB
^^^
.. literalinclude:: ../RECURSOR-MIB.txt
.. _metricnames:
Gathered Information
--------------------
These statistics are gathered.
It should be noted that answers0-1 + answers1-10 + answers10-100 + answers100-1000 + answers-slow + packetcache-hits + over-capacity-drops + policy-drops = questions.
Also note that unauthorized-tcp and unauthorized-udp packets do not end up in the 'questions' count.
almost-expired-pushed
^^^^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.6
number of almost-expired tasks pushed
almost-expired-run
^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.6
number of almost-expired tasks run
almost-expired-exceptions
^^^^^^^^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.6
number of almost-expired tasks that caused an exception
aggressive-nsec-cache-entries
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.5
number of entries in the aggressive NSEC cache
aggressive-nsec-cache-nsec-hits
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.5
number of negative answers generated from NSEC entries by the aggressive NSEC cache
aggressive-nsec-cache-nsec3-wc-hits
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.5
number of answers synthesized from NSEC entries and wildcards by the NSEC aggressive cache
aggressive-nsec-cache-nsec3-wc-hits
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.5
number of answers synthesized from NSEC entries and wildcards by the NSEC3 aggressive cache
all-outqueries
^^^^^^^^^^^^^^
counts the number of outgoing UDP queries since starting
answers-slow
^^^^^^^^^^^^
counts the number of queries answered after 1 second
answers0-1
^^^^^^^^^^
counts the number of queries answered within 1 millisecond
answers1-10
^^^^^^^^^^^
counts the number of queries answered within 10 milliseconds
answers10-100
^^^^^^^^^^^^^
counts the number of queries answered within 100 milliseconds
answers100-1000
^^^^^^^^^^^^^^^
counts the number of queries answered within 1 second
auth4-answers-slow
^^^^^^^^^^^^^^^^^^
counts the number of queries answered by auth4s after 1 second (4.0)
auth4-answers0-1
^^^^^^^^^^^^^^^^
counts the number of queries answered by auth4s within 1 millisecond (4.0)
auth4-answers1-10
^^^^^^^^^^^^^^^^^
counts the number of queries answered by auth4s within 10 milliseconds (4.0)
auth4-answers10-100
^^^^^^^^^^^^^^^^^^^
counts the number of queries answered by auth4s within 100 milliseconds (4.0)
auth4-answers100-1000
^^^^^^^^^^^^^^^^^^^^^
counts the number of queries answered by auth4s within 1 second (4.0)
auth6-answers-slow
^^^^^^^^^^^^^^^^^^
counts the number of queries answered by auth6s after 1 second (4.0)
auth6-answers0-1
^^^^^^^^^^^^^^^^
counts the number of queries answered by auth6s within 1 millisecond (4.0)
auth6-answers1-10
^^^^^^^^^^^^^^^^^
counts the number of queries answered by auth6s within 10 milliseconds (4.0)
auth6-answers10-100
^^^^^^^^^^^^^^^^^^^
counts the number of queries answered by auth6s within 100 milliseconds (4.0)
auth6-answers100-1000
^^^^^^^^^^^^^^^^^^^^^
counts the number of queries answered by auth6s within 1 second (4.0)
auth-zone-queries
^^^^^^^^^^^^^^^^^
counts the number of queries to locally hosted authoritative zones (:ref:`setting-auth-zones`) since starting
cache-bytes
^^^^^^^^^^^
size of the cache in bytes (disabled by default, see :ref:`setting-stats-rec-control-disabled-list`)
This metric is a rough estimate and takes a long time to compute, and is therefore not enabled in default outputs.
cache-entries
^^^^^^^^^^^^^
shows the number of entries in the cache
cache-hits
^^^^^^^^^^
counts the number of cache hits since starting, this does **not** include hits that got answered from the packet-cache
cache-misses
^^^^^^^^^^^^
counts the number of cache misses since starting
case-mismatches
^^^^^^^^^^^^^^^
counts the number of mismatches in character case since starting
chain-resends
^^^^^^^^^^^^^
number of queries chained to existing outstanding query
client-parse-errors
^^^^^^^^^^^^^^^^^^^
counts number of client packets that could not be parsed
.. _stat-concurrent-queries:
concurrent-queries
^^^^^^^^^^^^^^^^^^
shows the number of MThreads currently running
cpu-msec-thread-n
^^^^^^^^^^^^^^^^^
shows the number of milliseconds spent in thread n. Available since 4.1.12.
cpu-iowait
^^^^^^^^^^
.. versionadded:: 4.4
Time spent waiting for I/O to complete by the whole system, in units of USER_HZ.
cpu-steal
^^^^^^^^^
.. versionadded:: 4.4
Stolen time, which is the time spent by the whole system in other operating systems when running in a virtualized environment, in units of USER_HZ.
cumul-authanswers-x
^^^^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.6
Cumulative counts of answer times of authoritative servers in buckets less than x microseconds.
(disabled by default, see :ref:`setting-stats-rec-control-disabled-list`)
These metrics are useful for Prometheus and not listed in other outputs by default.
cumul-clientanswers-x
^^^^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.6
Cumulative counts of our answer times to clients in buckets less or equal than x microseconds.
These metrics include packet cache hits.
These metrics are useful for Prometheus and not listed in other outputs by default.
dns64-prefix-answers
^^^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.6
number of ``AAAA`` and ``PTR`` answers generated by :ref:`setting-dns64-prefix` matching.
dnssec-authentic-data-queries
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.2
number of queries received with the AD bit set
dnssec-check-disabled-queries
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.2
number of queries received with the CD bit set
dnssec-queries
^^^^^^^^^^^^^^
number of queries received with the DO bit set
.. _stat-dnssec-result-bogus:
dnssec-result-bogus
^^^^^^^^^^^^^^^^^^^
number of responses sent, packet-cache hits excluded, that were in the DNSSEC Bogus state. Since 4.4.2 detailed counters are available, see below.
Since 4.5.0, if :ref:`setting-x-dnssec-names` is set, a separate set of ``x-dnssec-result-...`` metrics become available, counting
the DNSSEC validation results for names suffix-matching a name in ``x-dnssec-names``.
dnssec-result-bogus-no-valid-dnskey
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.4.2
number of responses sent, packet-cache hits excluded, that were in the Bogus state because a valid DNSKEY could not be found.
dnssec-result-bogus-invalid-denial
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.4.2
number of responses sent, packet-cache hits excluded, that were in the Bogus state because a valid denial of existence proof could not be found.
dnssec-result-bogus-unable-to-get-dss
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.4.2
number of responses sent, packet-cache hits excluded, that were in the Bogus state because a valid DS could not be retrieved.
dnssec-result-bogus-unable-to-get-dnskeys
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.4.2
number of responses sent, packet-cache hits excluded, that were in the Bogus state because a valid DNSKEY could not be retrieved.
dnssec-result-bogus-self-signed-ds
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.4.2
number of responses sent, packet-cache hits excluded, that were in the Bogus state because a DS record was signed by itself.
dnssec-result-bogus-no-rrsig
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.4.2
number of responses sent, packet-cache hits excluded, that were in the Bogus state because required RRSIG records were not present in an answer.
dnssec-result-bogus-no-valid-rrsig
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.4.2
number of responses sent, packet-cache hits excluded, that were in the Bogus state because only invalid RRSIG records were present in an answer.
dnssec-result-bogus-missing-negative-indication
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.4.2
number of responses sent, packet-cache hits excluded, that were in the Bogus state because a NODATA or NXDOMAIN answer lacked the required SOA and/or NSEC(3) records.
dnssec-result-bogus-signature-no-yet-valid
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.4.2
number of responses sent, packet-cache hits excluded, that were in the Bogus state because the signature inception time in the RRSIG was not yet valid.
dnssec-result-bogus-signature-expired
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.4.2
number of responses sent, packet-cache hits excluded, that were in the Bogus state because the signature expired time in the RRSIG was in the past.
dnssec-result-bogus-unsupported-dnskey-algo
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.4.2
number of responses sent, packet-cache hits excluded, that were in the Bogus state because a DNSKEY RRset contained only unsupported DNSSEC algorithms.
dnssec-result-bogus-unsupported-ds-digest-type
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.4.2
number of responses sent, packet-cache hits excluded, that were in the Bogus state because a DS RRset contained only unsupported digest types.
dnssec-result-bogus-no-zone-key-bit-set
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.4.2
number of responses sent, packet-cache hits excluded, that were in the Bogus state because no DNSKEY with the Zone Key bit set was found.
dnssec-result-bogus-revoked-dnskey
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.4.2
number of responses sent, packet-cache hits excluded, that were in the Bogus state because all DNSKEYs were revoked.
dnssec-result-bogus-invalid-dnskey-protocol
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.4.2
number of responses sent, packet-cache hits excluded, that were in the Bogus state because all DNSKEYs had invalid protocols.
dnssec-result-indeterminate
^^^^^^^^^^^^^^^^^^^^^^^^^^^
number of DNSSEC validations that had the Indeterminate state
dnssec-result-insecure
^^^^^^^^^^^^^^^^^^^^^^
number of responses sent, packet-cache hits excluded, that were in the Insecure state
dnssec-result-nta
^^^^^^^^^^^^^^^^^
number of responses sent, packet-cache hits excluded, that were in the NTA (negative trust anchor) state
dnssec-result-secure
^^^^^^^^^^^^^^^^^^^^
number of responses sent, packet-cache hits excluded, that were in the Secure state
dnssec-validations
^^^^^^^^^^^^^^^^^^
number of responses sent, packet-cache hits excluded, for which a DNSSEC validation was requested by either the client or the configuration
dont-outqueries
^^^^^^^^^^^^^^^
number of outgoing queries dropped because of :ref:`setting-dont-query` setting (since 3.3)
dot-outqueries
^^^^^^^^^^^^^^
counts the number of outgoing DoT queries since starting
qname-min-fallback-success
^^^^^^^^^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.3.0
number of successful queries due to fallback mechanism within :ref:`setting-qname-minimization` setting.
ecs-queries
^^^^^^^^^^^
number of outgoing queries adorned with an EDNS Client Subnet option (since 4.1)
ecs-responses
^^^^^^^^^^^^^
number of responses received from authoritative servers with an EDNS Client Subnet option we used (since 4.1)
ecs-v4-response-bits-*
^^^^^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.2.0
number of responses received from authoritative servers with an IPv4 EDNS Client Subnet option we used, of this subnet size (1 to 32).
(disabled by default, see :ref:`setting-stats-rec-control-disabled-list`)
ecs-v6-response-bits-*
^^^^^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.2.0
number of responses received from authoritative servers with an IPv6 EDNS Client Subnet option we used, of this subnet size (1 to 128).
(disabled by default, see :ref:`setting-stats-rec-control-disabled-list`)
edns-ping-matches
^^^^^^^^^^^^^^^^^
number of servers that sent a valid EDNS PING response
edns-ping-mismatches
^^^^^^^^^^^^^^^^^^^^
number of servers that sent an invalid EDNS PING response
failed-host-entries
^^^^^^^^^^^^^^^^^^^
number of addresses in the failed NS cache.
.. _stat-fd-usage:
fd-usage
^^^^^^^^
Number of currently used file descriptors.
Currently, this metric is available on Linux and OpenBSD only.
ignored-packets
^^^^^^^^^^^^^^^
counts the number of non-query packets received on server sockets that should only get query packets
ipv6-outqueries
^^^^^^^^^^^^^^^
number of outgoing queries over IPv6
ipv6-questions
^^^^^^^^^^^^^^
counts all end-user initiated queries with the RD bit set, received over IPv6 UDP
malloc-bytes
^^^^^^^^^^^^
returns the number of bytes allocated by the process (broken, always returns 0)
max-cache-entries
^^^^^^^^^^^^^^^^^
currently configured maximum number of cache entries
max-packetcache-entries
^^^^^^^^^^^^^^^^^^^^^^^
currently configured maximum number of packet cache entries
max-mthread-stack
^^^^^^^^^^^^^^^^^
maximum amount of thread stack ever used
negcache-entries
^^^^^^^^^^^^^^^^
shows the number of entries in the negative answer cache
no-packet-error
^^^^^^^^^^^^^^^
number of erroneous received packets
nod-lookups-dropped-oversize
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Number of NOD lookups dropped because they would exceed the maximum name length
noedns-outqueries
^^^^^^^^^^^^^^^^^
number of queries sent out without EDNS
noerror-answers
^^^^^^^^^^^^^^^
counts the number of times it answered NOERROR since starting
non-resolving-nameserver-entries
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
number of entries in the non-resolving NS name cache
noping-outqueries
^^^^^^^^^^^^^^^^^
number of queries sent out without ENDS PING
nsset-invalidations
^^^^^^^^^^^^^^^^^^^
number of times an nsset was dropped because it no longer worked
nsspeeds-entries
^^^^^^^^^^^^^^^^
shows the number of entries in the NS speeds map
nxdomain-answers
^^^^^^^^^^^^^^^^
counts the number of times it answered NXDOMAIN since starting
outgoing-timeouts
^^^^^^^^^^^^^^^^^
counts the number of timeouts on outgoing UDP queries since starting
outgoing4-timeouts
^^^^^^^^^^^^^^^^^^
counts the number of timeouts on outgoing UDP IPv4 queries since starting (since 4.0)
outgoing6-timeouts
^^^^^^^^^^^^^^^^^^
counts the number of timeouts on outgoing UDP IPv6 queries since starting (since 4.0)
.. _stat-over-capacity-drops:
over-capacity-drops
^^^^^^^^^^^^^^^^^^^
questions dropped because over maximum concurrent query limit (since 3.2)
packetcache-bytes
^^^^^^^^^^^^^^^^^
size of the packet cache in bytes (since 3.3.1) (disabled by default, see :ref:`setting-stats-rec-control-disabled-list`)
This metric is a rough estimate and takes a long time to compute, and is therefore not enabled in default outputs.
packetcache-entries
^^^^^^^^^^^^^^^^^^^
size of packet cache (since 3.2)
packetcache-hits
^^^^^^^^^^^^^^^^
packet cache hits (since 3.2)
packetcache-misses
^^^^^^^^^^^^^^^^^^
packet cache misses (since 3.2)
policy-drops
^^^^^^^^^^^^
packets dropped because of (Lua) policy decision
policy-hits
^^^^^^^^^^^
Number of policy decisions based on Lua (``type = "filter"``), or RPZ (``type = "rpz"``). RPZ hits include the :ref:`rpz-policyName`.
These metrics are useful for Prometheus and not listed in other outputs by default.
policy-result-noaction
^^^^^^^^^^^^^^^^^^^^^^
packets that were not acted upon by the RPZ/filter engine
policy-result-drop
^^^^^^^^^^^^^^^^^^
packets that were dropped by the RPZ/filter engine
policy-result-nxdomain
^^^^^^^^^^^^^^^^^^^^^^
packets that were replied to with NXDOMAIN by the RPZ/filter engine
policy-result-nodata
^^^^^^^^^^^^^^^^^^^^
packets that were replied to with no data by the RPZ/filter engine
policy-result-truncate
^^^^^^^^^^^^^^^^^^^^^^
packets that were forced to TCP by the RPZ/filter engine
policy-result-custom
^^^^^^^^^^^^^^^^^^^^
packets that were sent a custom answer by the RPZ/filter engine
proxy-protocol-invalid
^^^^^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.4
Invalid proxy-protocol headers received.
qa-latency
^^^^^^^^^^
shows the current latency average, in microseconds, exponentially weighted over past 'latency-statistic-size' packets
query-pipe-full-drops
^^^^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.2
questions dropped because the query distribution pipe was full
questions
^^^^^^^^^
counts all end-user initiated queries with the RD bit set
rebalanced-queries
^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.1.12
number of queries balanced to a different worker thread because the first selected one was above the target load configured with 'distribution-load-factor'
record-cache-acquired
^^^^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.4.0
number of record cache lock acquisitions
record-cache-contended
^^^^^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.4.0
number of contended record cache lock acquisitions
resource-limits
^^^^^^^^^^^^^^^
Counts the number of queries that could not be performed because of resource limits.
This counter is increased when Recursor encounters a network issue that does not seem to be caused by the remote end.
For example when it runs out of file descriptors (monitor :ref:`stat-fd-usage`) or when there is no route to a
given IP address.
security-status
^^^^^^^^^^^^^^^
security status based on :ref:`securitypolling`
server-parse-errors
^^^^^^^^^^^^^^^^^^^
counts number of server replied packets that could not be parsed
servfail-answers
^^^^^^^^^^^^^^^^
counts the number of times it answered SERVFAIL since starting
spoof-prevents
^^^^^^^^^^^^^^
number of times PowerDNS considered itself spoofed, and dropped the data
sys-msec
^^^^^^^^
number of CPU milliseconds spent in 'system' mode
taskqueue-pushed
^^^^^^^^^^^^^^^^
.. versionadded:: 4.5.0
number of tasks pushed to the taskqueue
taskqueue-expired
^^^^^^^^^^^^^^^^^
.. versionadded:: 4.5.0
number of tasks expired before they could be run
taskqueue-size
^^^^^^^^^^^^^^
.. versionadded:: 4.5.0
number of tasks currently in the taskqueues
.. _stat-tcp-client-overflow:
tcp-client-overflow
^^^^^^^^^^^^^^^^^^^
number of times an IP address was denied TCP access because it already had too many connections
.. _stat-tcp-clients:
tcp-clients
^^^^^^^^^^^
counts the number of currently active TCP/IP clients
tcp-outqueries
^^^^^^^^^^^^^^
counts the number of outgoing TCP queries since starting
tcp-questions
^^^^^^^^^^^^^
counts all incoming TCP queries (since starting)
throttle-entries
^^^^^^^^^^^^^^^^
shows the number of entries in the throttle map
throttled-out
^^^^^^^^^^^^^
counts the number of throttled outgoing UDP queries since starting
throttled-outqueries
^^^^^^^^^^^^^^^^^^^^
idem to throttled-out
too-old-drops
^^^^^^^^^^^^^
questions dropped that were too old
truncated-drops
^^^^^^^^^^^^^^^
.. versionadded:: 4.2
questions dropped because they were larger than 512 bytes
empty-queries
^^^^^^^^^^^^^
.. versionadded:: 4.2
questions dropped because they had a QD count of 0
unauthorized-tcp
^^^^^^^^^^^^^^^^
number of TCP questions denied because of allow-from restrictions
unauthorized-udp
^^^^^^^^^^^^^^^^
number of UDP questions denied because of allow-from restrictions
source-disallowed-notify
^^^^^^^^^^^^^^^^^^^^^^^^
number of NOTIFY operations denied because of allow-notify-from restrictions
zone-disallowed-notify
^^^^^^^^^^^^^^^^^^^^^^
number of NOTIFY operations denied because of allow-notify-for restrictions
unexpected-packets
^^^^^^^^^^^^^^^^^^
number of answers from remote servers that were unexpected (might point to spoofing)
unreachables
^^^^^^^^^^^^
number of times nameservers were unreachable since starting
uptime
^^^^^^
number of seconds process has been running (since 3.1.5)
user-msec
^^^^^^^^^
number of CPU milliseconds spent in 'user' mode
variable-responses
^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.2
Responses that were marked as 'variable'. This could be because of EDNS
Client Subnet or Lua rules that indicate this variable status (dependent on
time or who is asking, for example).
.. _stat-x-our-latency:
x-our-latency
^^^^^^^^^^^^^
.. versionadded:: 4.1
Not yet proven to be reliable
PowerDNS measures per query how much time has been spent waiting on authoritative servers.
In addition, the Recursor measures the total amount of time needed to answer a question.
The difference between these two durations is a measure of how much time was spent within PowerDNS.
This metric is the average of that difference, in microseconds.
x-ourtime0-1
^^^^^^^^^^^^
.. versionadded:: 4.1
Not yet proven to be reliable
Counts responses where between 0 and 1 milliseconds was spent within the Recursor.
See :ref:`stat-x-our-latency` for further details.
x-ourtime1-2
^^^^^^^^^^^^
.. versionadded:: 4.1
Not yet proven to be reliable
Counts responses where between 1 and 2 milliseconds was spent within the Recursor.
See :ref:`stat-x-our-latency` for further details.
x-ourtime2-4
^^^^^^^^^^^^
.. versionadded:: 4.1
Not yet proven to be reliable
Counts responses where between 2 and 4 milliseconds was spent within the Recursor. Since 4.1.
See :ref:`stat-x-our-latency` for further details.
x-ourtime4-8
^^^^^^^^^^^^
.. versionadded:: 4.1
Not yet proven to be reliable
Counts responses where between 4 and 8 milliseconds was spent within the Recursor.
See :ref:`stat-x-our-latency` for further details.
x-ourtime8-16
^^^^^^^^^^^^^
.. versionadded:: 4.1
Not yet proven to be reliable
Counts responses where between 8 and 16 milliseconds was spent within the Recursor.
See :ref:`stat-x-our-latency` for further details.
x-ourtime16-32
^^^^^^^^^^^^^^
.. versionadded:: 4.1
Not yet proven to be reliable
Counts responses where between 16 and 32 milliseconds was spent within the Recursor.
See :ref:`stat-x-our-latency` for further details.
x-ourtime-slow
^^^^^^^^^^^^^^
.. versionadded:: 4.1
Not yet proven to be reliable
Counts responses where more than 32 milliseconds was spent within the Recursor.
See :ref:`stat-x-our-latency` for further details.
x-dnssec-result-...
^^^^^^^^^^^^^^^^^^^
.. versionadded:: 4.5.0
See :ref:`stat-dnssec-result-bogus`.