log4net is used in many .NET projects to provide logging facilities. log4net supports logging to different targets, including the Windows Event log, a database, as e-mail and as plain text files.

Most use the plain text file options via either the FileAppender or the RollingFileAppender, the latter having options to automatically roll-over the log to a new file when a certain size is reached, or once a day etc.

This is all nice, until you have either several concurrent but related applications in the same server logging, sometimes to the same file, or several related applications, such as web servers and back ends.

Two major issues appear in these scenarios:

  1. log4net does not really support logging to the same file, there’s a workaround with something called ‘minimal locking’, but there are issues with this. Sometimes logging does not work, and sometimes logs are lost when the files roll over at midnight for example.
  2. It’s really inconvenient to follow log events for example in a web farm where you never know just which server will be handling (and logging) which request, or when two different servers communicate and do their logging to different files in different systems.

There are specifically large issues with Web platforms such as EPiServer which by definition will use the same logging configuration for different sites, since they share the same virtual directory.

This software addresses all these issues.

The log4net Remote Logging Service is a small piece of software that quickly and easily installs itself using a Windows Installer MSI setup file to any server, and provides an end-point for any logs provided via the RemotingAppender .

There is no need to install anything on any servers doing the actual logging, only on the consolidating server on the receiving end. You do need to configure log4net on the logging servers to log to the RemotingAppender .

Last edited Sep 2, 2010 at 7:04 PM by svante, version 5


No comments yet.