Chainsaw uses a cyclic buffer by default, which means as new events are received, old ones are removed from the table. That cyclic buffer size is global, but you can toggle between cyclic and non-cyclic and that is a tab-specific persistnet setting. Once you hit the cyclic buffer limit, more CPU will be used to drop old events.
Chainsaw holds all events in memory, so modify the -Xmx and -Xms VM args to support bigger files if you want cyclic buffering disabled. Chainsaw can store events received from a file - use the file, load chainsaw configuration menu option and then either choose to have it read your log4j.xml/log4j.properties fileappender configuration, or use the 'process a log file' option to build the LogFilePatternReceiver configuration yourself. Scott On Thu, Sep 15, 2011 at 12:24 PM, Konduru, Geetha <[email protected]>wrote: > 1.How many events will it store? > > 2..Using chain saw can we store all events received in a file. > > > > > > Thank U, > > Vgss > > ********************************************************************** > This e-mail message and any attachments contain confidential information > from Medco. If you are not the intended recipient, you are hereby notified > that disclosure, printing, copying, distribution, or the taking of any > action in reliance on the contents of this electronic information is > strictly prohibited. If you have received this e-mail message in error, > please immediately notify the sender by reply message and then delete the > electronic message and any attachments. >
