logging-log4net-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Deboy" <sde...@comotivsystems.com>
Subject RE: Remote listening of server log stream ...
Date Mon, 04 Feb 2008 18:02:00 GMT
Chainsaw provides a LogFilePatternReceiver that can tail log files on a
local file system or available via HTTP.


Chainsaw also includes VFSLogFilePatternReceiver, which will let you
tail log files remotely when if the files are accessible via ssh or any
of the file systems supported by Jakarta commons-vfs


Scott Deboy
Principal Engineer
111 SW Columbia Street Ste. 950
Portland, OR  97201
Office: 503.224.7496
Direct Line: 503.821.6482
Cell: 503.997.1367
Fax: 503.222.0185
sdeboy@comotivsystems.com <mailto:sdeboy@comotivsystems.com> 
www.comotivsystems.com <http://www.comotivsystems.com/> 


From: Parrish, Ken [mailto:KParrish@gomez.com] 
Sent: Monday, February 04, 2008 6:50 AM
To: log4net-user@logging.apache.org
Subject: Remote listening of server log stream ...


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?




Ken Parrish

Gomez, Inc.

View raw message