[bind10-dev] List of the statistics tasks which JPRS plans to work for in year 5

[Shane Kerr]

Kambe-san,

Overall I think it seems quite reasonable.

On Tue, 19 Mar 2013 17:50:12 +0900 (JST)
Naoki Kambe <kambe at jprs.co.jp> wrote:
> 
> Statistics tasks which JPRS is going to work for in year 5 are here:
> 
>  - for Auth module
>    #2156 Collect socket statistics items in Auth module

Makes sense.

>    #2196 Update Auth to support differential statistics updates

We need this. :)

>    #2796 Add a counter for queries with RD=1

Straightforward.

>    #2797 Expand EDNS statistics counters for all versions

Important.

>    #2200 Collect per-zone query/response statistics items in Auth
>          module 

We definitely need per-zone statistics, although this is a non-trivial
item as mention in the ticket.

> #2199 Add a configuration item to specify zones to collect
>       statistics in Auth module

It's unclear if we need to be able to configure the per-zone statistics
or not. It might be more useful simply to enable them all the time but
then to ignore them if you don't need them.

>  - for Xfrin module
>    #2274 Implement counters into Xfrin (2/3)
>    #2300 Implement counters into Xfrin (3/3)

Agreed - much of the work here is done, correct?

>  Note: some tickets should be broken into small tickets.
> 
> So JPRS would like to ask you:
> 
>  - Are these enough for statistics work of year 5?
> 
>  - If not enough, what are any other statistics tasks which we should
>    complete in year 5?
> 
> What do you think about this? Could you give your opinion?

We can always use more statistics, so the real question is about
priorities and resources.

I think that making progress on authoritative statistics makes complete
sense, and I also like the xfrin statistics. Having the xfrout work
would seem like a logical next step.

> BTW, JPRS has currently the following technical problems about these
> statistics tasks.
> 
> Regarding #2156, we should resolve how to implement the socket
> counters into the asiolink or asiodns library. There doesn't seem to
> be any elegant way to do it.  Can this library be revised to implement
> such counters easily?

I put a suggestion in the ticket, which is basically to try to collect
the errors that ASIO does report.
 
> Regarding #2200, auth needs to know a zone name for the query from the
> data source. But such a method doesn't seem to be implemented in the
> current zone manager.

We'll need to implement such a query then.

> These technical issues may be separately discussed in other threads.

--
Shane