Are you saying you write a parser for log file entries? Hmm. Why not taking
log4j sources and find the point where you can catch the message events, the
real objects and massage this objects. I say that because you say: Everything
is displayed under Message column. Getting access to the Message
I see. Thank you very much.
QD
-Original Message-
From: Scott Deboy [mailto:scott.de...@gmail.com]
Sent: Monday, July 25, 2011 11:34 AM
To: Log4J Users List
Subject: Re: Help Log4j Chainsaw - VFSLogFilePatternReceiver Usage
You can only specify one format, but you can get the non-matchi
You can only specify one format, but you can get the non-matching rows to
still be included in the table in Chainsaw by setting AppendNonMatches to
'true' in the configuration file. The non-matching rows will be added to
the 'unknown' logger, with the entire line set as the message.
Scott
On Mon
I am out of the office until 02.08.2011.
I will respond to your message when I return.
Note: This is an automated response to your message "RE: Help Log4j
Chainsaw - VFSLogFilePatternReceiver Usage" sent on 25.07.2011 17:27:31.
This is the only notification you will receive while this person
Thank you Scott. It works for the local log file. Everything is displayed
under Message column. I guess I need to try the different format to see how to
parse the log file correctly. One reason it does not parse correctly is that
the log entries are not always consistent. Once in a while ther
