Comments on: Logger Level Confession http://stuffthathappens.com/blog/2008/03/25/logger-level-confession/ Technology and Geek Stuff by Eric Burke Sat, 27 Feb 2010 14:52:46 -0500 http://wordpress.org/?v=2.8.6 hourly 1 By: Smitty http://stuffthathappens.com/blog/2008/03/25/logger-level-confession/comment-page-1/#comment-8429 Smitty Mon, 31 Mar 2008 16:05:36 +0000 http://stuffthathappens.com/blog/2008/03/25/logger-level-confession/#comment-8429 @Eric: Maybe it's time for a comic of how Apple, Google, and your company does logging 8^). I'm a bit embarrassed but here goes: DEBUG: Kitchen sink logging level. Everything including variable values, return values, HTTP Response, stack traces, Hi, Mom's, etc. INFO: Program execution trace. Like we don't know how to use a debugger, but meant more for our test servers running our web applications in a QA environment (where yeah, we don't have debuggers). WARNING: An error occurs, we're not sure of the impact, it's probably bad, we better log it. ERROR: A bad error occurs, we're not sure of the impact, we figure prod logs might need it. FATAL: I've never seen one explicitly declared, but that's what we have PROD set to (see the ERROR level where the developers think PROD is set to). We don't see to many production errors logged. Wonder why.... 8^P @Eric: Maybe it’s time for a comic of how Apple, Google, and your company does logging 8^).

I’m a bit embarrassed but here goes:
DEBUG: Kitchen sink logging level. Everything including variable values, return values, HTTP Response, stack traces, Hi, Mom’s, etc.

INFO: Program execution trace. Like we don’t know how to use a debugger, but meant more for our test servers running our web applications in a QA environment (where yeah, we don’t have debuggers).

WARNING: An error occurs, we’re not sure of the impact, it’s probably bad, we better log it.
ERROR: A bad error occurs, we’re not sure of the impact, we figure prod logs might need it.
FATAL: I’ve never seen one explicitly declared, but that’s what we have PROD set to (see the ERROR level where the developers think PROD is set to).

We don’t see to many production errors logged. Wonder why…. 8^P

]]> By: superfoo http://stuffthathappens.com/blog/2008/03/25/logger-level-confession/comment-page-1/#comment-8098 superfoo Fri, 28 Mar 2008 13:45:32 +0000 http://stuffthathappens.com/blog/2008/03/25/logger-level-confession/#comment-8098 I stick to Debug, Info, Warning and Severe. I add debug to help with program flow when troubleshooting bugs and slowdowns. I stick to Debug, Info, Warning and Severe. I add debug to help with program flow when troubleshooting bugs and slowdowns.

]]> By: Dave Aronson http://stuffthathappens.com/blog/2008/03/25/logger-level-confession/comment-page-1/#comment-7987 Dave Aronson Wed, 26 Mar 2008 13:47:11 +0000 http://stuffthathappens.com/blog/2008/03/25/logger-level-confession/#comment-7987 My usual set is NFEWID: None (don't even bother opening the log file), Fatal (log fatal errors only), Error (only log if there was something actually wrong with the data or ops), Warning (odd but usable), Info (normal operations), and Debug (excruciating detail, sometimes with specific flags for what chunks of code I want to spew like that, everything else being in Info mode). My usual set is NFEWID: None (don’t even bother opening the log file), Fatal (log fatal errors only), Error (only log if there was something actually wrong with the data or ops), Warning (odd but usable), Info (normal operations), and Debug (excruciating detail, sometimes with specific flags for what chunks of code I want to spew like that, everything else being in Info mode).

]]> By: Neil Weber http://stuffthathappens.com/blog/2008/03/25/logger-level-confession/comment-page-1/#comment-7970 Neil Weber Wed, 26 Mar 2008 05:11:25 +0000 http://stuffthathappens.com/blog/2008/03/25/logger-level-confession/#comment-7970 So, on a production system, you'll set the threshold to WARN? But then if there is a problem, the logs are pretty much empty. I prefer to set the threshold to INFO and log user actions at the INFO (e.g. " deleted Contract" or " listed Documents matching "A%"). That way when there is a problem there is some context. Then I log information useful for debugging problems at FINE (or DEBUG if using log4j). So, on a production system, you’ll set the threshold to WARN? But then if there is a problem, the logs are pretty much empty. I prefer to set the threshold to INFO and log user actions at the INFO (e.g. ” deleted Contract” or ” listed Documents matching “A%”). That way when there is a problem there is some context. Then I log information useful for debugging problems at FINE (or DEBUG if using log4j).

]]> By: Charlie http://stuffthathappens.com/blog/2008/03/25/logger-level-confession/comment-page-1/#comment-7969 Charlie Wed, 26 Mar 2008 04:47:52 +0000 http://stuffthathappens.com/blog/2008/03/25/logger-level-confession/#comment-7969 The others are only useful to programmers when they're building or debugging it. We do this because we're not supposed to use print statements. The others are only useful to programmers when they’re building or debugging it. We do this because we’re not supposed to use print statements.

]]> By: Jesse http://stuffthathappens.com/blog/2008/03/25/logger-level-confession/comment-page-1/#comment-7965 Jesse Wed, 26 Mar 2008 02:25:40 +0000 http://stuffthathappens.com/blog/2008/03/25/logger-level-confession/#comment-7965 Fine choice. Fine choice.

]]> By: Mark Volkmann http://stuffthathappens.com/blog/2008/03/25/logger-level-confession/comment-page-1/#comment-7964 Mark Volkmann Wed, 26 Mar 2008 01:46:56 +0000 http://stuffthathappens.com/blog/2008/03/25/logger-level-confession/#comment-7964 I agree with your three choices, but you might also use CONFIG. I'm guessing that's for logging of application configuration settings that were in effect, if any. I agree with your three choices, but you might also use CONFIG. I’m guessing that’s for logging of application configuration settings that were in effect, if any.

]]> By: Adrian Smith http://stuffthathappens.com/blog/2008/03/25/logger-level-confession/comment-page-1/#comment-7962 Adrian Smith Wed, 26 Mar 2008 01:41:39 +0000 http://stuffthathappens.com/blog/2008/03/25/logger-level-confession/#comment-7962 I agree. There should be a standard policy and everyone should stick to it. But because that's not the case, recently I thought long and hard about which log levels to use when and this was what I came up with: http://www.databasesandlife.com/which-log-levels-to-use-when/ I agree. There should be a standard policy and everyone should stick to it.

But because that’s not the case, recently I thought long and hard about which log levels to use when and this was what I came up with:

http://www.databasesandlife.com/which-log-levels-to-use-when/

]]> By: Mario Aquino http://stuffthathappens.com/blog/2008/03/25/logger-level-confession/comment-page-1/#comment-7958 Mario Aquino Wed, 26 Mar 2008 00:20:29 +0000 http://stuffthathappens.com/blog/2008/03/25/logger-level-confession/#comment-7958 I use the fine level when I want to communicate something that is interesting but not necessarily important, like finding out that there was water on Mars a million years ago. Finer is useful when the code is entering a state of mild interest, like gossip you might read regarding the French president and his mistress or Britney's latest court date; I guess it's news but my day would be the same without knowing it. Finest logging level is reserved for things that are the least amount of useful knowledge but might be interesting to someone out there, like how much of the national anthem would fit if written on a grain of rice or the number of balls that the world-record holder of juggling can keep in the air at the same time. This strategy has helped me make the most out of all the logger API levels. I use the fine level when I want to communicate something that is interesting but not necessarily important, like finding out that there was water on Mars a million years ago. Finer is useful when the code is entering a state of mild interest, like gossip you might read regarding the French president and his mistress or Britney’s latest court date; I guess it’s news but my day would be the same without knowing it. Finest logging level is reserved for things that are the least amount of useful knowledge but might be interesting to someone out there, like how much of the national anthem would fit if written on a grain of rice or the number of balls that the world-record holder of juggling can keep in the air at the same time. This strategy has helped me make the most out of all the logger API levels.

]]> By: Rusty Wright http://stuffthathappens.com/blog/2008/03/25/logger-level-confession/comment-page-1/#comment-7956 Rusty Wright Tue, 25 Mar 2008 23:29:53 +0000 http://stuffthathappens.com/blog/2008/03/25/logger-level-confession/#comment-7956 You can create your own log level; in your case I suggest making one called WHATEVER. You can create your own log level; in your case I suggest making one called WHATEVER.

]]>