BIND 10 #509: Define required statistics counters

BIND 10 Development do-not-reply at isc.org
Mon May 16 18:13:01 UTC 2011


#509: Define required statistics counters
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  UnAssigned
  stephen                            |                Status:  reviewing
                       Type:  task   |             Milestone:
                   Priority:  major  |  Sprint-20110517
                  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 => UnAssigned


Comment:

 Can you add a key - what does "x" and "o" mean?

 '''Requests'''[[BR]]
 There are a group of items:
 * Authoritative queries rejected
 * Recursive queries rejected
 * Zone transfer requests rejected
 * Update queries rejected

 ... but there don't appear to be corresponding items for the number
 received (or accepted, although I think the total received would be an
 easier statistic to collect.)

 Queries resulting in SERVFAIL, FORMERR etc.  The
 [http://www.iana.org/assignments/dns-parameters IANA registry] records
 RCODEs in the range 0-22 (with values 11-15 unassigned).  Why not
 generalise the statistics and allow the retrieval of "Queries resulting in
 RCODE = n" with 24 bins (0 - 22 plus one for 'other').

 '''Resolver'''[[BR]]
 I'm not clear what "duplicated recursive queries" is.

 "Dropped recursive queries".  Presumably these are queries dropped because
 the server was too busy to handle them.  In this case, should there be a
 similar statistic for the authoritative server ("Dropper authoritative
 queries")?

 "NXDOMAIN/SERVFAILFORMERR/Other responses received" etc.  As above, can
 this be generalised to allow for up to 24 RCODE values?

 Clarification: I assume "Mismatch Responses Received" is when a reply is
 received for which the QNAME/QID does not match that of the question?

 "Qeries aborted due to quota control".  What is this?

 "Failures opening query sockets" - this really belongs in the "Sockets"
 section of the table.

 DNSSEC - it occurs to me that a useful statistic (at least for general
 interest) would be an indication of the algorithms used when decoding a
 key.  At the very least it would give useful information as to the takeup
 of SHA256 over SHA1.

 RTT frequency table.  Question - are the RTT bins passed with the request,
 or are they hard-coded in the server?


 '''Sockets'''[[BR]]
 Number of sockets closed: presumably the idea here is that the difference
 between the number opened and the number closed gives the total still
 open?

 I've put this back to "!UnAssigned" review to encourage others to give
 comments.

-- 
Ticket URL: <http://bind10.isc.org/ticket/509#comment:6>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development


More information about the bind10-tickets mailing list