You found a bug! The log4jid property is just used internally by chainsaw to ensure that if you save events from Chainsaw, that they can be re-added with the same 'id' field they had when they were first seen by Chainsaw.
I've just committed a fix that should fix your problem. Please feel free to post any comments/problems you find. Thanks, Scott -----Original Message----- From: Rob Oxspring [mailto:[EMAIL PROTECTED] Sent: Wed 1/7/2004 8:48 AM To: Log4J Users List Cc: Subject: Generating logs to view in Chainsaw Hi, We're currently trying to evaluate chainsaw to let us analyse customer's log files and we're struggling to write log files in a format that chainsaw can cope with. I figured that it should be enough to use the XmlLayout but chainsaw simply displayed the first couple of events with an id of 1. After a little hacking around with the log file we discovered that chainsaw could be fooled into showing more events if we added the following to each event with an ever increasing value: <log4j:properties><log4j:data name="log4jid" value="1"/></log4j:properties> But what's the trick to getting this information added to the logs as they go? Do we need to be using an appender / layout specific to chainsaw? - I hope not as I see no real reason to add the chainsaw jar to our dependancy list. To be honest I'd have thought that chainsaw could add an ever increasing value on load if its not there but maybe I'm taking too simplistic a view. Thanks in advance, Rob --------------------------------------------------------------------- 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]
