I've actually used Chainsaw V2. Thought it was a really nice tool too. But I was under the impression that it won't do what I need it to do. When I used it I was sending it log messages in real time which won't work for me in this scenario.
Can Chainsaw go to remote locations (specified as virtual drives so I guess that won't be a problemm) and read the file I specify into chainsaw, filtering out the parts that don't meet it's criteria. My recollection of it was that it acted as a passive receiver of log messages on the fly and filtered them based on specified criteria. This wouldn't work for me because I need to process completed log files. My desire to pretty print the xml could be left unfulfilled as could my wish to merge the log files on multiple machines by chronology, if Chainsaw will process the static files by keywords. Thanks for your help on this. I'd certainly enjoy not having to write the tool myself... alan -----Original Message----- From: Scott Deboy [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 30, 2004 2:17 PM To: Log4J Users List Subject: RE: Static log reading tool... Chainsaw v2 and LogFilePatternReceiver can display log files with arbitrary formats in the UI - with a few restrictions. Here are links: http://logging.apache.org/log4j/docs/chainsaw.html - see 'installation' section for an ant script that can download & build http://cvs.apache.org/viewcvs.cgi/logging-log4j/src/java/org/apache/log4 j/varia/LogFilePatternReceiver.java?rev=1.6&view=auto - read javadocs for information on how to specify the file format (LogFilePatternReceivers are supported directly in the 'receiver' panel of Chainsaw v2 - just hit the 'new' icon in the receiver panel and specify the properties). Let me know if you have questions, Scott -----Original Message----- From: Alan Brown [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 30, 2004 2:13 PM To: [EMAIL PROTECTED] Subject: Static log reading tool... Is there any gui tool out there to statically parse logs, pulling out only the information I specify. It could be done by assuming logging messages are blank line bounded for instance and a search string for the message could be defined with a regular expression. In my case the search string would be the session id so I could see only the logging thread that pertained to the user that generated an error. As a twist I'd like the tool to be able to get information from multiple machines' log files and to make sure the output remains in chronological order. I'm thinking of writing something quick and dirty to do this if there's nothing out there. Alan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
