[bind10-dev] auth statistics

[JINMEI Tatuya / 神明達哉]

As we discussed in the biweekly call yesterday, I think we need some
more design-level discussions on how to manage statistics counters for
b10-auth before proceeding with tickets #2154, #2155, and #2157.  I'd
like to have a project-wide discussion about

- how to represent these counters (it may be different for different
  types of statistics, e.g., generic counters like total # of incoming
  requests vs per-RR type queries).
- how to update these counters with minimizing performance impact on
  query processing, maybe with prototyping and benchmarking
- how to exchange these counters with external modules (which will
  mainly be b10-stats, but can be in general).  This is probably
  mostly trivial, but I guess we need to consider how to *cleanly*
  convert things like per RR counters into JSON representation.

Then, on top of these, implement the concept in the above tickets.
The end result may be the same, but I want to do it after fully
discussing the design and performance impacts.

As for the schedule, I've revised the most recent proposal:

"must be done" (scheduled to end until Aug21):
    #2135 design a new statistics model
    #2136 update the stats daemon according to the new statistics model
    #2137 update the boss module according to the new statistics model
    #2138 update the Auth module according to the new statistics model
    #2179 Update Stats to support differential statistics updates

"optional" (scheduled to end until Sep18):
    #2154 Create a set of counters to hold auth statistics items
    #2155 Collect query/response statistics items in Auth module
    #2157 Create an interface to pass statistics counters in Auth module
    #2156 Collect socket statistics items in Auth module
    #2158 Implement counters into Xfrout (1/3)

"hopeful" (scheduled to end until Oct09):
    #tbd8  Implement counters into Xfrout (2/3)
    #tbd14 Implement per-zone counters into Auth (1/3)
    #tbd15 Implement per-zone counters into Auth (2/3)
    #tbd16 Implement per-zone counters into Auth (3/3)
    #tbd18 Update Auth to support differential statistics updates
    #tbd9  Implement counters into Xfrout (3/3)

According to this, the tickets in question are actually "optional".
If I interpret it literally, I'd assume it's okay we first discuss
more details about the design and then implement/review it (and, as a
result, it may appear in the release later than September).  Is this
correct?

If so, my specific suggestion is:

- extract #2154, #2155, #2157 from the review queue for now
- start the above discussion
- shift our short-term focus to remaining things that are not affected
  by the above three tickets.  I guess xfrout-related ones can be done
  independently.

---
JINMEI, Tatuya