BIND 10 #2156: Collect socket statistics items in Auth module

BIND 10 Development do-not-reply at isc.org
Wed Aug 22 06:44:50 UTC 2012


#2156: Collect socket statistics items in Auth module
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  fujiwara
  y-aharen                           |                Status:  assigned
                       Type:         |             Milestone:
  enhancement                        |  StatsRedesign
                   Priority:         |            Resolution:
  medium                             |             Sensitive:  0
                  Component:         |           Sub-Project:  DNS
  b10-auth                           |  Estimated Difficulty:  5
                   Keywords:         |           Total Hours:  0
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:5 fujiwara]:
 > It is impossible to get socket counters listed at StatisticsItems
 because they are hidden by Boost asio.
 > Changing Boost asio is out of scope of BIND 10 project.
 >
 > Errors caught by asiodns are countable.
 > ASIODNS_READ_TIMEOUT, ASIODNS_FETCH_COMPLETED, ASIODNS_FETCH_STOPPED,
 ASIODNS_\
 > UNKNOWN_RESULT, ASIODNS_FD_ADD_UDP, ASIODNS_FD_ADD_TCP
 > Is it OK to change socket counters into ASIODNS error counters ?

 I guess the real question is what we (operators) want to collect at
 this level, rather than what we can collect based on the given tool
 we're using.

 If the operators actually don't care about seeing such lower level
 information, we might just skip implementing it.  If we know a
 specific set of event at this level operators would usually like to
 know, we should try providing that.  Only at this point we can discuss
 whether it's easy (or possible in the first place) based on what we're
 using.

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


More information about the bind10-tickets mailing list