Hi, On Thu, May 28, 2009 at 6:17 PM, Ceki Gulcu <c...@qos.ch> wrote: > Are you saying in the majority of SLF4J deployments the thread name is > not available?
No, just that in most cases some essential piece of the puzzle (source code, stack traces, or in this specific example thread names) is not readily available for a variety of different reasons. For example, I've seen lots of log4j configurations without thread names included in the log output. Sure you can ask the configuration to be changed, but that's not very optimal if you're trying to identify a problem that occurs perhaps only once a month in a production environment. In summary, you generally can't trust on having all the potential data available to support the task of deciphering the meaning of a log entry, which makes meaningful log messages all the more important. BR, Jukka Zitting _______________________________________________ dev mailing list dev@slf4j.org http://www.slf4j.org/mailman/listinfo/dev