BIND 10 #1074: Use debug levels consistently
BIND 10 Development
do-not-reply at isc.org
Wed Jun 29 09:16:53 UTC 2011
#1074: Use debug levels consistently
-------------------------------------+-------------------------------------
Reporter: stephen | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: logging | Sprint-20110712
Sensitive: 0 | Keywords:
Sub-Project: DNS | Defect Severity: N/A
Estimated Difficulty: 0 | Feature Depending on Ticket:
Total Hours: 0 | Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
(Summarised from bind10-dev, 29 June 2011)
>> missing debug number ("A debug message" or "only appear if debug is
enabled" is too vague -- when will it be logged at what debug level?)
>> I think there should be separate "DEBUG" severity for developers
too.... now we have debug message useful for admins to debug and then
other debug message clearly only useful for admins (even referring to
specific code "the RecursiveQuery::resolve method...").
> Agreed. Although 100 debug levels are available, for consistency we
need to define how they are used. We have discussed the idea of debug
levels of 20 or below being used for messages that might be useful to
!SysAdmins and levels above 20 being reserved for "programmer-level"
messages. Perhaps now is the time to formalise that?"
This ticket should be done after all other tickets relating to the
addition of logging messages have been completed. The categories of debug
messages should be reviewed and debug levels assigned such that the
correspondence between category and level is consistent across all
modules.
--
Ticket URL: <http://bind10.isc.org/ticket/1074>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list