RE: Help understanding Log4j basics
I've previously searched the manual and I understand the hierarchy of:
DEBUG INFO WARN ERROR FATAL
However, I'm interested in in learning if there is a way to print ONLY
one level rather than the target level and all levels above it. Unless
I've missed it, the manual does not explain if this is possible (or
how to do it).
In order to print a particular level only you can use LevelFilters which you
can configure in xml configuration. E.g.
appender name=CONSOLE.OUT class=org.apache.log4j.ConsoleAppender
param name=target value=System.out/
layout class=org.apache.log4j.PatternLayout
param name=ConversionPattern value=%d{HH:mm:ss.SSS} (%6r) %-5p
[%-7t] %F:%L %x - %m%n/
/layout
filter class=org.apache.log4j.varia.LevelRangeFilter
param name=LevelMin value=trace/
param name=LevelMax value=info/
param name=AcceptOnMatch value=false/
/filter
/appender
-
To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-user-h...@logging.apache.org
RE: [SCL-4] Intercepting LoggingEvent
Write your own Renderer derivation which you can specify in xml configuration (assign to your specific class, see below). The Trick is that you pass a custom object to the log calls (the param need not to be a String, it is formally an object): MySpecificLogInfoHolder infos = new MySpecificLogInfoHolder() myLog.info( infos ); When the log4j framework comes to render (after having checked the levels etc.) it calls your custom renderer where you can render the output string as you like. Heri -Original Message- From: Mohan.Radhakrishnan [mailto:moh...@fss.co.in] Sent: Thursday, November 25, 2010 7:46 AM To: log4j-user@logging.apache.org Subject: [SCL-4] Intercepting LoggingEvent I am trying to intercept the LoggingEvent which is an instance of a custom LoggingEvent created by a library. I have a custom appender and also a filter but neither seems to be a clean way of extracting specific custom information for logging. I think there should be a way to log only what I want from the LoggingEvent by extracting it before the log is written. Is this feasible ? -- View this message in context: http://old.nabble.com/Intercepting-LoggingEvent- tp30302884p30302884.html Sent from the Log4j - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org - To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org
Re: [SCL-4] Intercepting LoggingEvent
Look at RewriteAppender. I think you May be able to do what you need with that and a custom RewritePolicy. Scott On Nov 25, 2010, at 6:33 AM, Bender Heri hben...@ergonomics.ch wrote: Write your own Renderer derivation which you can specify in xml configuration (assign to your specific class, see below). The Trick is that you pass a custom object to the log calls (the param need not to be a String, it is formally an object): MySpecificLogInfoHolder infos = new MySpecificLogInfoHolder() myLog.info( infos ); When the log4j framework comes to render (after having checked the levels etc.) it calls your custom renderer where you can render the output string as you like. Heri -Original Message- From: Mohan.Radhakrishnan [mailto:moh...@fss.co.in] Sent: Thursday, November 25, 2010 7:46 AM To: log4j-user@logging.apache.org Subject: [SCL-4] Intercepting LoggingEvent I am trying to intercept the LoggingEvent which is an instance of a custom LoggingEvent created by a library. I have a custom appender and also a filter but neither seems to be a clean way of extracting specific custom information for logging. I think there should be a way to log only what I want from the LoggingEvent by extracting it before the log is written. Is this feasible ? -- View this message in context: http://old.nabble.com/Intercepting-LoggingEvent- tp30302884p30302884.html Sent from the Log4j - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org - To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org - To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org
