BIND 10 #2200: Collect per-zone query/response statistics items in Auth module

[BIND 10 Development]

#2200: Collect per-zone query/response statistics items in Auth module
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  y-aharen
  y-aharen                           |                Status:  new
                       Type:         |             Milestone:  New Tasks
  enhancement                        |            Resolution:
                   Priority:         |             Sensitive:  0
  medium                             |           Sub-Project:  DNS
                  Component:         |  Estimated Difficulty:  0
  b10-auth                           |           Total Hours:  0
                   Keywords:         |
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:2 y-aharen]:
 > I haven't considered the less efficiency of ZoneFinder::getOrigin() as
 it is called while processing queries in addAuthAdditional() and addSOA().

 For these (IMO) we should eventually introduce in-memory specific
 optimizations by extending `FinderContext`.

 > Is there another approach to get which zone is the nearest ancestor to
 qname? If there is an efficient method to get zone identifier of
 ZoneFinder other than zone name, I'll use it.

 One possibility is to extend the finder so it can return the origin
 information in the form of `LabelSequence`.  But that's a bit ad hoc
 and I'm not sure if it's a really good idea.

 In my gut feeling we should consider this problem at one or a few
 levels higher, i.e., how we manage the per zone statistics and
 integrate it to the data source API in general, rather than trying to
 solve it locally within the b10-auth implementation.  It will require
 some architecture/design level considerations and discussions.

-- 
Ticket URL: <https://bind10.isc.org/ticket/2200#comment:3>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development