Return-Path: Delivered-To: apmail-logging-log4net-user-archive@www.apache.org Received: (qmail 50220 invoked from network); 4 Feb 2008 14:48:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Feb 2008 14:48:35 -0000 Received: (qmail 72360 invoked by uid 500); 4 Feb 2008 14:48:26 -0000 Delivered-To: apmail-logging-log4net-user-archive@logging.apache.org Received: (qmail 72333 invoked by uid 500); 4 Feb 2008 14:48:26 -0000 Mailing-List: contact log4net-user-help@logging.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: "Log4NET User" List-Id: Delivered-To: mailing list log4net-user@logging.apache.org Received: (qmail 72322 invoked by uid 99); 4 Feb 2008 14:48:26 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Feb 2008 06:48:26 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,WHOIS_NETSOLPR X-Spam-Check-By: apache.org Received-SPF: unknown mxa:mailrelay.webperform.comip4:65.221.100.0/24ip4:65.214.60.137ip4:63.251.134.0/24ip4:63.150.46.16ip4:63.150.46.10ip4:193.120.123.44ip4:204.14.234.14ip4:64.18.4.10?all (nike.apache.org: encountered unrecognized mechanism during SPF processing of domain of KParrish@gomez.com) Received: from [65.221.100.25] (HELO entdc1ms02.corp.gomez.com) (65.221.100.25) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Feb 2008 14:48:09 +0000 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C8673D.DF0491C6" Subject: Remote listening of server log stream ... X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Mon, 4 Feb 2008 09:50:27 -0500 Message-ID: <6D3CA9B0BEA31640B4E6338360C84740016FA0F7@entdc1ms02.corp.gomez.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Remote listening of server log stream ... thread-index: AchnPUfpOwRKh+arQ/eyJJXUyqh1qg== From: "Parrish, Ken" To: X-Virus-Checked: Checked by ClamAV on apache.org This is a multi-part message in MIME format. ------_=_NextPart_001_01C8673D.DF0491C6 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I have a scenario where I have a server with several ADO.NET and Windows services running. Under normal operation, the applications write log messages of various severities to a rolling file(s), Windows event viewer, and e-mail via the SmtpAppender. =20 I would like to set up a logger/appender that would allow remote listening in on the stream of logging messages. In this case, the server runs continuously and is constantly generating a stream of logging events to a RollingFileAppender. From time to time, I'd like to 'attach' to the logging output, remotely from a separate host and 'listen in' on the steam of messages being generated. =20 I looked into the UdpAppender in combination with log4netview or logview4net. But it seems that the UdpAppender requires specification of a specific Host and TCP port. I didn't see a way that I could connect in to listen to the UDP stream remotely. =20 I also considered writing a separate Windows Service that supported .NET remoting to which log messages were routed. I could then 'subscribe' via .NET remoting and remote message sinks listen in on the log stream. Seems like a lot of work for a simple task. =20 I noticed the .NET RemotingAppender in the example appender source code, but am not sure if that will work. =20 Has anyone needed this type of remote 'log listening' capability and have a suggestion for a solution or approach? =20 Thanks, =20 Ken Parrish Gomez, Inc. ------_=_NextPart_001_01C8673D.DF0491C6 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I have a scenario where I have a server with several = ADO.NET and Windows services running.  Under normal operation, the = applications write log messages of various severities to a rolling file(s), Windows event = viewer, and e-mail via the SmtpAppender.

 

I would like to set up a logger/appender that would = allow remote listening in on the stream of logging messages.  In this = case, the server runs continuously and is constantly generating a stream of = logging events to a RollingFileAppender.  From time to time, I’d like to = ‘attach’ to the logging output, remotely from a separate host and ‘listen = in’ on the steam of messages being generated.

 

I looked into the UdpAppender in combination with log4netview or logview4net.  But it seems that the UdpAppender = requires specification of a specific Host and TCP port.  I didn’t see a way that I = could connect in to listen to the UDP stream remotely.

 

I also considered writing a separate Windows Service = that supported .NET remoting to which log messages were routed.  I could = then ‘subscribe’ via .NET remoting and remote message sinks listen in on the log = stream.  Seems like a lot of work for a simple task.

 

I noticed the .NET RemotingAppender in the example = appender source code, but am not sure if that will = work.

 

Has anyone needed this type of remote ‘log = listening’ capability and have a suggestion for a solution or = approach?

 

Thanks,

 

Ken Parrish

Gomez, Inc.

------_=_NextPart_001_01C8673D.DF0491C6--