BIND 10 #1448: document basic design of stats snmp interface

BIND 10 Development do-not-reply at isc.org
Mon Jan 30 18:51:04 UTC 2012


#1448: document basic design of stats snmp interface
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  UnAssigned
  naokikambe                         |                Status:  reviewing
                       Type:  task   |             Milestone:
                   Priority:  major  |  Sprint-20120207
                  Component:         |            Resolution:
  statistics                         |             Sensitive:  0
                   Keywords:         |           Sub-Project:  DNS
            Defect Severity:  N/A    |  Estimated Difficulty:  5
Feature Depending on Ticket:  SNMP   |           Total Hours:  0
  stats                              |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:8 naokikambe]:

 > BTW as another approach: each non-stats module stores its statistics
 somewhere in the SQLite database, and then stats module reads there
 periodically. Such statistics saved in the sqlite might be permanent even
 if the bind 10 reboots. But after the bind10 starts, each module may have
 to take care about consistency of statistics data between in database and
 in itself.

 I've been thinking about the same idea, especially in the context of
 handling a huge amount of statistics information (e.g., for an auth
 server managing millions of zones and collecting statistics per
 zone).  Whether it's push or pull, it would be just unrealistic to
 exchange the counters via a msgq (or its successor).  Using a
 permanent database storage as a shared placeholder of statistics would
 be one possible solution in that scenario.

 Anyway...

 > Anyway I don't think we should discuss here about these protocols.

 ...that's right.  This should go to a separate ticket (and/or
 perhaps a biweekly call topic)

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


More information about the bind10-tickets mailing list