8. Statistics¶
The Loop nameserver maintains many statistics counters and provides an interface for administrators to access them in an XML format.
Warning
The counter symbol names may change in future major releases. Please check the release notes before upgrading.
The statistics information is categorized into the following sections.
Incoming Requests |
The number of incoming DNS requests for each OPCODE. |
Incoming Queries |
The number of incoming queries for each RR type. |
Outgoing Queries |
The number of outgoing queries for each RR type sent from the internal resolver. Maintained per view. |
Name Server Statistics |
Statistics counters about incoming request processing. |
Zone Maintenance Statistics |
Statistics counters regarding zone maintenance operations such as zone transfers. |
Resolver Statistics |
Statistics counters about name resolution performed in the internal resolver. Maintained per view. |
Cache DB RRsets |
The number of RRsets per RR type and nonexistent names stored in the cache database. If the exclamation mark (!) is printed for a RR type, it means that particular type of RRset is known to be nonexistent (this is also known as "NXRRSET"). If a hash mark (#) is present then the RRset is marked for garbage collection. Maintained per view. |
Socket I/O Statistics |
Statistics counters about network related events. |
A subset of statistics is collected and shown per-zone for which the
server has the authority when zone-statistics
is set to full
(or
yes
for backward compatibility. See the description of
zone-statistics
in section_title for further details.
These statistics counters are shown with their zone and view names. The view name is omitted when the server is not configured with explicit views.
Statistics counters are dumped in an XML format to the file specified by
the statistics-file
configuration option.
8.1. XML Format¶
Error
TODO: Add examples of parsing the XML statistics.
8.2. Counters¶
The following tables summarize statistics counters that Loop provides. For each row of the tables, the leftmost column is the abbreviated symbol name of that counter. These symbols are shown in the statistics information accessed via an HTTP statistics channel. The rightmost column gives the description of the counter, which is also shown in the statistics file (but, in this document, possibly with slight modification for better readability). Additional notes may also be provided in this column.
8.3. Nameserver Counters¶
Symbol |
Description |
---|---|
|
IPv4 requests received. Note: this also counts non query requests. |
|
IPv6 requests received. Note: this also counts non query requests. |
|
Requests with EDNS(0) received. |
|
Requests with unsupported EDNS version received. |
|
Requests with TSIG received. |
|
Requests with SIG(0) received. |
|
Requests with invalid (TSIG or SIG(0)) signature. |
|
TCP requests received. |
|
Authoritative (non recursive) queries rejected. |
|
Recursive queries rejected. |
|
Zone transfer requests rejected. |
|
Dynamic update requests rejected. |
|
Responses sent. |
|
Truncated responses sent. |
|
Responses with EDNS(0) sent. |
|
Responses with TSIG sent. |
|
Responses with SIG(0) sent. |
|
Queries resulted in a successful answer. This means the query which returns a NOERROR response with at least one answer RR. |
|
Queries resulted in authoritative answer. |
|
Queries resulted in non authoritative answer. |
|
Queries resulted in referral answer. |
|
Queries resulted in NOERROR responses with no data. |
|
Queries resulted in SERVFAIL. |
|
Queries resulted in FORMERR. |
|
Queries resulted in NXDOMAIN. |
|
Queries which caused the server to perform recursion in order to find the final answer. |
|
Queries which the server attempted to recurse but discovered an existing query with the same IP address, port, query ID, name, type and class already being processed. |
|
Recursive queries for which the server
discovered an excessive number of
existing recursive queries for the same
name, type and class and were
subsequently dropped. This is the
number of dropped queries due to the
reason explained with the
|
|
Other query failures. This corresponds Note: this counter
is provided mainly for backward
compatibility with the previous
versions. Normally a more fine-grained
counters such as |
|
Requested zone transfers completed. |
|
Update requests forwarded. |
|
Update responses forwarded. |
|
Dynamic update forward failed. |
|
Dynamic updates completed. |
|
Dynamic updates failed. |
|
Dynamic updates rejected due to prerequisite failure. |
|
Responses dropped by rate limits. |
|
Responses truncated by rate limits. |
|
Response policy zone rewrites. |
8.4. Zone Maintenance Counters¶
The following are statistics counters related to zone maintenance operations such as zone transfers.
Symbol |
Description |
|
IPv4 notifies sent. |
|
IPv6 notifies sent. |
|
IPv4 notifies received. |
|
IPv6 notifies received. |
|
Incoming notifies rejected. |
|
IPv4 SOA queries sent. |
|
IPv6 SOA queries sent. |
|
IPv4 AXFR requested. |
|
IPv6 AXFR requested. |
|
IPv4 IXFR requested. |
|
IPv6 IXFR requested. |
|
Zone transfer requests succeeded. |
|
Zone transfer requests failed. |
8.5. Resolver Counters¶
The following are statistics counters related to query resolution performed in the internal resolver. They are maintained per-view.
Symbol |
Description |
|
IPv4 queries sent. |
|
IPv6 queries sent. |
|
IPv4 responses received. |
|
IPv6 responses received. |
|
NXDOMAIN received. |
|
SERVFAIL received. |
|
FORMERR received. |
|
Other errors received. |
|
EDNS(0) query failures. |
|
Mismatch responses received. The DNS
ID, response's source address, and/or
the response's source port does not
match what was expected. (The port must
be 53 or as defined by the |
|
Truncated responses received. |
|
Lame delegations received. |
|
Query retries performed. |
|
Queries aborted due to quota control. |
|
Failures in opening query sockets. One common reason for such failures is a failure of opening a new socket due to a limitation on file descriptors. |
|
Query timeouts. |
|
IPv4 NS address fetches invoked. |
|
IPv6 NS address fetches invoked. |
|
IPv4 NS address fetch failed. |
|
IPv6 NS address fetch failed. |
|
DNSSEC validation attempted. |
|
DNSSEC validation succeeded. |
|
DNSSEC validation on negative information succeeded. |
|
DNSSEC validation failed. |
|
Frequency table on round trip times
(RTTs) of queries. Each |
8.6. Socket I/O Counters¶
The following are statistics counters related to network events.
Symbol |
Description |
---|---|
UDP4Open |
IPv4 UDP sockets opened successfully |
UDP6Open |
IPv6 UDP sockets opened successfully |
TCP4Open |
IPv4 TCP sockets opened successfully |
TCP6Open |
IPv6 TCP sockets opened successfully |
RawOpen |
Raw sockets opened successfully |
UDP4OpenFail |
Failures in opening IPv4 UDP sockets |
UDP6OpenFail |
Failures in opening IPv6 UDP sockets |
TCP4OpenFail |
Failures in opening IPv4 TCP sockets |
TCP6OpenFail |
Failures in opening IPv6 TCP sockets |
RawOpenFail |
Failures in opening raw sockets |
UDP4Close |
IPv4 UDP sockets closed |
UDP6Close |
IPv6 UDP sockets closed |
TCP4Close |
IPv4 TCP sockets closed |
TCP6Close |
IPv6 TCP sockets closed |
RawClose |
Raw sockets closed |
UDP4BindFail |
Failures in binding IPv4 UDP sockets |
UDP6BindFail |
Failures in binding IPv6 UDP sockets |
TCP4BindFail |
Failures in binding IPv4 TCP sockets |
TCP6BindFail |
Failures in binding IPv6 TCP sockets |
UDP4ConnFail |
Failures in connecting IPv4 UDP sockets |
UDP6ConnFail |
Failures in connecting IPv6 UDP sockets |
TCP4ConnFail |
Failures in connecting IPv4 TCP sockets |
TCP6ConnFail |
Failures in connecting IPv6 TCP sockets |
UDP4Conn |
IPv4 UDP connections established successfully |
UDP6Conn |
IPv6 UDP connections established successfully |
TCP4Conn |
IPv4 TCP connections established successfully |
TCP6Conn |
IPv6 TCP connections established successfully |
TCP4AcceptFail |
Failures in accepting incoming IPv4 TCP connection requests |
TCP6AcceptFail |
Failures in accepting incoming IPv6 TCP connection requests |
TCP4Accept |
Incoming IPv4 TCP connections successfully accepted |
TCP6Accept |
Incoming IPv6 TCP connections successfully accepted |
UDP4SendErr |
Errors in IPv4 UDP socket send operations |
UDP6SendErr |
Errors in IPv6 UDP socket send operations |
TCP4SendErr |
Errors in IPv4 TCP socket send operations |
TCP6SendErr |
Errors in IPv6 TCP socket send operations |
UDP4RecvErr |
Errors in IPv4 UDP socket receive operations. It includes errors of send operations on a connected UDP socket notified by an ICMP error message. |
UDP6RecvErr |
Errors in IPv6 UDP socket receive operations. It includes errors of send operations on a connected UDP socket notified by an ICMP error message. |
TCP4RecvErr |
Errors in IPv4 TCP socket receive operations |
TCP6RecvErr |
Errors in IPv6 TCP socket receive operations |
RawRecvErr |
Errors in raw socket receive operations |
UDP4Active |
IPv4 UDP sockets currently active |
UDP6Active |
IPv6 UDP sockets currently active |
TCP4Active |
IPv4 TCP sockets currently active |
TCP6Active |
IPv6 TCP sockets currently active |
RawActive |
Raw sockets currently active |