On Thu, 30 Oct 2003, Shapira, Yoav wrote: | | Howdy, | >That said, I'd be hard pressed to give a coherant reason why I | >shouldn't used DEBUG. But I don't. | | Which of course is exactly the point. The decision on which logging | level to use for what is subjective. For example, I use INFO and DEBUG | that way Senor Stolsvik uses DEBUG and TRACE. So I don't need TRACE at | all.
Info is a level where -informational- messages are given, and I'd guess most installations leave the INFO level "on" for production servers. The best point I've made, in my own opinion, is the one about "production levels" (4: info, warn, error, fatal) and "development levels" (1: debug). Do you feel that a info-statement is a "development" statement? You obviously turn off information-level logging in production servers then, don't you? Then you're left with -three- production levels, ALL of which represent some kind of anomaly (warn, error, fatal) - where do you "inform" your log about "customer [log4j] added to database" - which in MY opinion is a statement that I'd ALWAYS like to have in my logs, but isn't no warning, no error, nor a fatal happening. E. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
