Log4j doesn't have an NT event log receiver, but it does have LogFilePatternReceiver, which can be used to read syslog messages, IIS logs, etc.
You could use Chainsaw V2 configured with these various receivers to see the events. The events may end up in separate tabs, depending on what you have set as your 'tab identifier'. Even if you have Chainsaw configured to use the default tab identifier (events for each file are displaying in their own tab), use the 'view-create custom expression log panel' to combine events from these separate tabs into a single tab. Hope this helps Scott -----Original Message----- From: Lutz Michael [mailto:[EMAIL PROTECTED] Sent: Wed 5/25/2005 7:14 AM To: 'Log4J Users List' Cc: Subject: RE: **SPAM** RE: Log4J - log aggregation my apologies, you are absolutely correct. Also ... Log4j comes with many appenders already capable of doing this (socket, JMS) so you might not even have to write your own. In an enterprise setting we might run into applications where we can't control their logging, e.g. code out of our control may log to an IIS log, NT Event Log, Unix Syslog, etc. In such situations a viewer such as XpoLog can bring disparate data together into a single view. The only requirement is that a datetime-stamp be in each record. But you're absolutely right - if you have control over the code then Log4j provides a solution out of the box. -----Original Message----- From: Jan Pernica [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 25, 2005 9:11 AM To: Log4J Users List Subject: Re: **SPAM** RE: Log4J - log aggregation Write your own appender, which will do the job Lutz Michael wrote: >http://www.xplg.com/ > >-----Original Message----- >From: James P Barber [mailto:[EMAIL PROTECTED] >Sent: Wednesday, May 25, 2005 8:04 AM >To: Log4J Users List >Subject: Log4J - log aggregation > > > > > > >I am looking for ideas on practical techniques for aggregating logs from >multiple source applications to a central log >repository. Any suggestions would be appreciated. I am new to Log4J. >Thanks... Jim Barber > >--------------------------------------------------------------------------- ---- >This message and any included attachments are from Siemens Medical Solutions >USA, Inc. and are intended only for the addressee(s). >The information contained herein may include trade secrets or privileged or >otherwise confidential information. Unauthorized review, forwarding, printing, >copying, distributing, or using such information is strictly prohibited and may >be unlawful. If you received this message in error, or have reason to believe >you are not authorized to receive it, please promptly delete this message and >notify the sender by e-mail with a copy to [EMAIL PROTECTED] > >Thank you > >--------------------------------------------------------------------- >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] ------------------------------------------------------------------------------- This message and any included attachments are from Siemens Medical Solutions USA, Inc. and are intended only for the addressee(s). The information contained herein may include trade secrets or privileged or otherwise confidential information. Unauthorized review, forwarding, printing, copying, distributing, or using such information is strictly prohibited and may be unlawful. If you received this message in error, or have reason to believe you are not authorized to receive it, please promptly delete this message and notify the sender by e-mail with a copy to [EMAIL PROTECTED] Thank you --------------------------------------------------------------------- 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]
