Comments on: Loggerheadache http://stuartsierra.com/2006/09/07/loggerheadache From programming to everything else Sun, 12 Oct 2008 12:58:31 +0000 http://wordpress.org/?v=2.6 By: sidereal http://stuartsierra.com/2006/09/07/loggerheadache#comment-16717 sidereal Wed, 29 Aug 2007 20:57:18 +0000 http://stuartsierra.com/2006/09/07/loggerheadache#comment-16717 Ugh. Thanks for this. Had to google to figure out why the hell my log entries weren't coming out, despite a hundred lines of debugging output. Fine-grained control over per-handler error levels is fine, but at the very least they should default them to ALL. In other words, don't turn the extra filtering on unless I tell you to. Defaulting to INFO in the absence of any other information is just irritating. Ugh. Thanks for this. Had to google to figure out why the hell my log entries weren’t coming out, despite a hundred lines of debugging output.

Fine-grained control over per-handler error levels is fine, but at the very least they should default them to ALL. In other words, don’t turn the extra filtering on unless I tell you to. Defaulting to INFO in the absence of any other information is just irritating.

]]> By: anonymous http://stuartsierra.com/2006/09/07/loggerheadache#comment-649 anonymous Sat, 09 Sep 2006 11:59:30 +0000 http://stuartsierra.com/2006/09/07/loggerheadache#comment-649 I don't think this is a mess, since you may even use different Loggers with the same handler (e.g. printing to Console) and therefore it is often usefull to set the log level for the Loggers and the Handlers... so you can disable one Logger at runtime but others are still able to send messages to the handlers... I don’t think this is a mess, since you may even use different Loggers with the same handler (e.g. printing to Console) and therefore it is often usefull
to set the log level for the Loggers and the Handlers… so you can disable one Logger at runtime but others are still able to send messages to the handlers…

]]>