BIND 10 #509: Define required statistics counters
BIND 10 Development
do-not-reply at isc.org
Wed Sep 28 11:37:16 UTC 2011
#509: Define required statistics counters
-------------------------------------+-------------------------------------
Reporter: | Owner: y-aharen
stephen | Status: reviewing
Type: task | Milestone:
Priority: major | Sprint-20111011
Component: | Resolution:
statistics | Sensitive: 0
Keywords: | Sub-Project: DNS
Defect Severity: N/A | Estimated Difficulty: 5.0
Feature Depending on Ticket: | Total Hours: 0
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Changes (by stephen):
* owner: stephen => y-aharen
Comment:
At the moment, there are three counters for incoming requests:
* auth.[zonename].request.v{4|6}: Total number of requests over IPv4/6
* auth.[zonename].request.tcp: Total number of TCP requests.
(The total number of UPD requests can be inferred from these counters.)
Would it be better to alter the counters (and add another one) to:
* auth.[zonename].request.udp{4|6}: Total number of UDP requests over
IPv4/6
* auth.[zonename].request.tcp{4|6}: Total number of TCP requests over
IPv4/6.
The totals of requests for V4 and V6, as well as the total number of UDP
and TCP requests can be found, but in addition the counters give a more
detailed breakdown.
For the resolver, the counters resolver.rdtype.xxx (where xxx is a, ns, mx
etc.) are described as the number of responses received. Is that
responses received from upstream servers, or should the description read
"queries received"?
In the resolver, the counters resolver.requestv4, resolver.requestv6 and
resolver.reqtcp give the number of IPv4, IPv6 and TCP requests received.
For the same reasons as above, would it be better to create four counters:
resolver.reqtcp{4|6} and resolver.requdp{4|6}.
resolver.qryrecursion. Is this needed in BIND 10, given that the resolver
and the authoritative server are now separate and so will have separate
counters?
--
Ticket URL: <http://bind10.isc.org/ticket/509#comment:20>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list