That is probably what Dennis was looking for. But I feel it exactly shows my point; all but the debug level are well defined, with the debug level being the big-ol'-bucket-of... ahhh. Yes. Because it includes "critical method" info, but also "contents of resultsets...parameters...performance...".
Suppose you need to find out why an application is taking a left turn instead of the expected right turn. It's not a program error, or warning, nor does it inform you each time it takes a left. So all you have, is turning on debug and get overloaded with resultsets, and variables and stuff, when you have no idea what class to look in at that time.
Hence my suggestion for splitting up debug in two levels: trace (follow the program logic) and debug (explain the program logic). It's all about not mixing different scopes of information. But definitions like "fine", "finer", "finest" is totally BS: what goes where?
In that line of reasoning, combined with your text, I have one more thought: you also include performance information in the debug level, and that made me think.
Usually when I'm all done with an application, and it works ok, AND I have some time left or spare time, I'm wondering if I can improve stuff somewhere. Now having performance info is great, but do I want it to be cluttered with debug info? So: would having a totally separate (not hierachically) category "performance" be interesting? Or is performancing something that is done between info and trace? IMHO, it does not hurt having performance info while tracing, so hierachically would be ok.
So my current favorite ;-) FATAL ERROR WARN INFO PERFORMANCE TRACE DEBUG
Sorry for addressing a subject that is so difficult to agree upon... On the other hand, a talk about levels or contexts of logging information might be educational. Love to hear reactions.
Tom
Shapira, Yoav wrote:
Howdy, Did you mean this thread? http://marc.theaimsgroup.com/?l=log4j-user&m=105189448809301&w=2
Yoav Shapira Millennium ChemInformatics
-----Original Message----- From: Dennis Cook [mailto:[EMAIL PROTECTED] Sent: Sunday, October 19, 2003 4:05 PM To: [EMAIL PROTECTED] Subject: Log level definitions
A little while back someone posted some definitions of the type of information, for which the various logging levels should be used. I thought it quite good and would like to share it with some coworkers, but I cannot locate it. I am asking for a repost of that information.
thanks
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
