BIND 10 #170: document how stats are collected (via spec files)
BIND 10 Development
do-not-reply at isc.org
Mon Sep 20 14:57:18 UTC 2010
#170: document how stats are collected (via spec files)
-----------------------------+----------------------------------------------
Reporter: larissas | Owner: naokikambe
Type: task | Status: reviewing
Priority: major | Milestone: 06. 4th Incremental Release
Component: statistics | Resolution:
Keywords: | Sensitive: 0
Estimatedhours: 0.0 | Hours: 0
Billable: 0 | Totalhours: 0.62
Internal: 0 |
-----------------------------+----------------------------------------------
Comment(by jinmei):
Replying to [comment:24 jinmei]:
> > In such case, I think the ''increase'' method is useful.
> >
> I don't get this part. How exactly does the ''increase'' method help
this scneario? Could you be more specific, maybe with an example case?
I think I understand it. You probably wanted to let the receiver (stats
collector) be unaware of different senders.
If so, I see the advantage. But it comes with its own cost. Basically
it's a tradeoff about which one should maintain states, the sender or the
receiver.
I personally still think it's better to have the receiver keep the state
(e.g. a list of senders) because the sender (which is most typically some
DNS server module) would tend to be pretty complicated without this and it
would make sense to keep it as simple as possible. But I understand this
may be a matter of opinion.
In any case, I'd suggest a minimalist approach: begin with "total" only,
and when we see the real need where ''increase'' can be a choice we should
discuss whether that's the best approach.
For the design documentation, I'd suggest we leave it open, describing
these discussion points.
--
Ticket URL: <https://bind10.isc.org/ticket/170#comment:25>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list