BIND 10 #719: configurable stats do nothing
BIND 10 Development
do-not-reply at isc.org
Mon May 9 13:07:42 UTC 2011
#719: configurable stats do nothing
-------------------------------------+-------------------------------------
Reporter: jreed | Owner: UnAssigned
Type: | Status: reviewing
defect | Milestone: New Tasks
Priority: minor | Resolution:
Component: | Sensitive: 0
statistics | Sub-Project: DNS
Keywords: | Estimated Difficulty: 0.0
Defect Severity: N/A | Total Hours: 0
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by jelte):
Hmm, I think this approach is slightly off. It's a step in the right
direction, but I would suggest we *do* put the definition of statistics
items in the same spec files, but under a different sublevel, e.g.:
{{{
{ "module_spec": {
"module_name": "my_own_module",
"module_description": "foo",
"config_data": [ <list of configurable options> ],
"commands": [ <list of commands> ],
"statistics": [ <list of collected statistics> ]
}
}
This requires us to change the specfile parser, but it would be far less
complicated for modules to collect statistics (and I suspect that we want
more than one module to do so).
I think we should also put the definitions of module-specific statistics
in that module, and not in the specification for the stats-daemon;
b10-stats should be agnostic about what specific data is collected, so
that modules can define their own, so if we do decide to do the above, I'd
suggest we move the specification for things like boot time to the boss
spec file, and auth query counters to the auth spec file.
--
Ticket URL: <http://bind10.isc.org/ticket/719#comment:3>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list