BIND 10 #2199: Add a configuration item to specify zones to collect statistics in Auth module
BIND 10 Development
do-not-reply at isc.org
Wed Aug 22 14:27:10 UTC 2012
#2199: Add a configuration item to specify zones to collect statistics in Auth
module
-------------------------------------+-------------------------------------
Reporter: | Owner: y-aharen
y-aharen | Status: new
Type: | Milestone: New Tasks
enhancement | Resolution:
Priority: | Sensitive: 0
medium | Sub-Project: DNS
Component: | Estimated Difficulty: 3
b10-auth | Total Hours: 0
Keywords: |
Defect Severity: N/A |
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by vorner):
Sorry, but if I imagine being an admin, it seems extremely cumbersome to
me. If I had 10k zones and wanted to know which of them are most active,
would I really need to list them all there, one by one? And if I added a
zone to the sqlite3, would I need to change the list too?
I think a more sane approach would be to:
* Keep statistics of anything that got at least one query (zones without
queries are not listed)
* Have a configuration to enable or disable zones somehow ‒ let's say a
statistics ACL, with actions „Collect“, „Detailed“, „No statistics“ (and
the default would be Collect).
Admin that wanted just the usual amount would be happy without
configuration, it could be very flexible, the admin would need to learn
ACLs anyway and we already have them (we would need to instantiate them
with the different actions and provide some "origin" match, but we will
need that for DDNS ACLs anyway I think).
--
Ticket URL: <http://bind10.isc.org/ticket/2199#comment:3>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list