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