standard uses of log4j in designing business software

I'm currently doing a research on the standard usage of the 5 levels of Log4j. My question is that is there a standard convention of which level to use when we program? Like should we use DEBUG more often than INFO? I understand that there are certain circumstances which require us to use a specific level. However, how about when we don't have the special cases; which level do we use usually (esp. when we write programs at the production level)? Is there a general concensus/convention/standard?

Also, what is a good approach/standard for logging entry and exit of the method?

I know that this might be a quite specific question. I'm also trying to find out what other programmers/companies are doing...(do they have a standard way of using it?) But It seems really hard to find exact information I'm looking for. If anyone could offer some outlets for finding the solutions to my question, that'd be great. Thank you.

[948 byte] By [log4j_help_neededa] at [2007-10-2 9:48:25]
# 1
> I'm currently doing a research on the standard usage> of the 5 levels of Log4j. Weasel words translation:I am currently cross posting this message in several forums. http://forum.java.sun.com/thread.jspa?threadID=699300&tstart=0
log4j_help_neededa at 2007-7-16 23:53:43 > top of Java-index,Enterprise & Remote Computing,Enterprise Technologies...
# 2
I was going to respond, until I saw all the crossposting.
jverda at 2007-7-16 23:53:43 > top of Java-index,Enterprise & Remote Computing,Enterprise Technologies...
# 3

Hi,

There is a clear definition for using the log4j levels.

For example

Debug has to be used for Debug purpose it is level of 5 (this mainly for programers)

Info has to be used for information to the end user or admin (example property file not able to load using default configuration) level -4

This is the way it is defined for all the level.

softviewa at 2007-7-16 23:53:43 > top of Java-index,Enterprise & Remote Computing,Enterprise Technologies...