RE: logging in a remoting scenario

[Nicko Cadell <ni...@neoworks.com>]

Joben,

There are a number of different ways of transmitting log events from a
remote machine, some may be more suited to your situation than others.

The simplest is to use the RemotingAppender. It is implemented and
leverages the existing remoting infrastructure.

You could use the UdpAppender to log from the remote machine to some
form of listener on the local machine.

If you can setup a shared network drive between the local and remote
machines you could use the FileAppender with the MinimalLock model to
write to the same file. This could have severe performance issues.

Depending on the networking, reliability and throughput required you may
want to consider using MSMQ channels to deliver the log events, although
this is more work as an MSMQ appender is not included in the
distribution.

Nicko

> -----Original Message-----
> From: velocity [mailto:velocity.lists@gmail.com] 
> Sent: 26 April 2005 08:07
> To: log4net-user@logging.apache.org
> Subject: logging in a remoting scenario
> 
> Hi. I'm quite new to log4net and just using it for simple situations.
> My question is on the possibility of capturing logging events 
> across processes (remoting in .NET)
> 
> I would want to be able to log messages from AppA running on 
> my local machine and also log messages from RemoteAppB 
> running on a different machine where the log events for both 
> are recorded in one log file on my local machine.
> 
> I've seen the remoting appenders and went though the samples. 
> Is this the only way? that is have my local machine act as a 
> remoting server and the remote machine as the remoting client?
> 
> Is there a better alternative?
> 
> thanks,
> 
> Joben
> 
>