While I agree not having TRACE built in is a significant deficiency in what Log4j provides, Log4j DOES make it trivial to add and is addressed in the FAQ. For your convenience, here's a direct link to the relevant section in the FAQ: http://nagoya.apache.org/wiki/apachewiki.cgi?Log4JProjectPages/TraceLevel
Btw: This has been brought up many times on the log4j-user list (where comments and questions like this should be posted), so a quick search of the list archives would've pointed it out... -----Original Message----- From: Endre Stølsvik [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 29, 2003 10:30 AM To: LOG4J Developers Mailing List Subject: Rationale for TRACE-level/priority. I -need- a trace-level! We've used log4j for about 3 years now, and my company's portal server is totally dependent on it, and all our applications use it. Why isn't THE TRACE LEVEL there? It's so obviously needed.. There is a HUGE difference between "trace" statements, and "debug" statements. What I need is a level where I can log "Adding user to the validation-map.", or "FormField [count] accepted incoming value [5]." or similar -very detailed- statements. -These aren't debug statements-, as they'll give you 2000 lines of log for each "click" (on a web application) a user makes. Debug should give you e.g. 20-80 lines, e.g. "Form validated OK" and possibly "Connection [pooled#8] fetched" Info should give you 0-3, e.g. "user [Endre] added new customer [log4j]". Trace "traces" the opartion of an application - and should be put in everywhere one wonders about a call, or a value of something.. and WHATEVER. E.g. for each method entry and exit: would be wonderful. Warn and error are obvious to me, while "fatal" aren't that obvious: it sounds like a level that only should have one log-line -ever-: the one that makes the application crash! BUT TRACE IS MISSING! IT IS BLATANTLY *MISSING*!! What I end up doing now, is to add debug-lines, and then remove them again, as they give to much information for the "day-to-day" development of the platform, where I'd like to have the debug-logging on, all the time. I would then like to turn it down to info when it has been in "staging" for a while, and goes into raw "production" mode. Then I'd like, runtime (click "reload logconfig"), to increase the logging output to DEBUG, and possibly TRACE again if things starts to crash in some part of the application. What are the rationale for not having the TRACE level? All other logging packages have it..!!! - It should be -clearly- stated on the FRONT webpage why it's not there.. I -could- make a wrapper. Ok. But that -sucks-. I'd rather switch the entire system. Thanks, Endre --------------------------------------------------------------------- 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]
