logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ognjen Kavazovic <okavazo...@slb.com>
Subject RE: patterns and levels
Date Mon, 26 Apr 2004 16:00:20 GMT
>You could pass a parameter to the extended localisation parameter. You
>can for example write:

>log4j.appender.stdoutAppender.layout.ConversionPattern=[%c] - \
>(%Fx{DEBUG}:%Lx{DEBUG}) %p [%t]: %m%n

>I hope you find the above convincing.

Yes, this is convincing. Didn't know you can pass parameters...good enough
for me. :)

>By the way, the original problem of extracting localisation
>information for DEBUG, but not INFO, for performance reasons, does
>not seem to be worth the effort. Usually, one has 10 times more DEBUG
>statements than INFO and higher.

Right, you are going be slow at DEBUG level whether you have localization
parameters in your pattern or not, due to the sheer volume of DEBUG
messages. However, one wants to be as efficient as possible when logging in
"production mode", presumably at INFO level.

Thanks again.

>Cheers,
>-Ogi.

--
Ceki Gülcü

      For log4j documentation consider "The complete log4j manual"
      ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp



---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message