This topic is a source of endless debate where I work.
We have groups that actually separate "event logging" from "tracing", and support about 5 levels of each. So, instead of just 1 trace level, they use 5 different levels of tracing. I doubt the end of this debate will ever be reached with consensus. My opinion - I like to keep things simple, and thus 1 level of debug is fine for me, but I have heard people argue successfully for additional levels. For instance, 1 level of debugging that operations may be able to understand, a lower level that developers understand without source code in front of them, and an even lower level of tracing that requires source code in front of a developer. The debate rages on ... the addition of a single trace level might be a reasonable compromise. This will also incur change in a lot of documentation - these levels are documented in a lot of places. -----Original Message----- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Monday, September 22, 2003 11:42 AM To: Log4J Users List Subject: RE: Plans for supporting a build in level of "trace" Howdy, >"TRACE" or "FINE" is one that many seem to agree is sensible and required. That's the part I'm not convinced of. How do you support the above? >I think the idea is, no matter how many or few default levels there are, >the defaults should cover the range of the "logging space" completely. >FATAL pretty much covers it on one end of the spectrum. >On the other end we need a logging level whose messages would be so >verbose and so often called that we would almost never need a finer level. >DEBUG is too general purpose for that. I disagree, think DEBUG is fine for the other end of the spectrum, and wouldn't use something lower than that. However, if there's really an overwhelming majority of people who disagree, then by definition I'm in the minority and these levels should be added ;) But I'm yet to be convinced this is the case... Yoav Shapira 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] ------------------------------------------------------------------------------- This message and any included attachments are from Siemens Medical Solutions USA, Inc. and are intended only for the addressee(s). The information contained herein may include trade secrets or privileged or otherwise confidential information. Unauthorized review, forwarding, printing, copying, distributing, or using such information is strictly prohibited and may be unlawful. If you received this message in error, or have reason to believe you are not authorized to receive it, please promptly delete this message and notify the sender by e-mail with a copy to [EMAIL PROTECTED] Thank you --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
