Svante Seleborg
Sep 2, 2010
(3 votes)

log4net Remote Logging Service released

If you ever had to look at more than one log4net log file from EPiServer, or you have had more than one site log to the same log file, this is for you.

I have released the log4net Remote Logging Server Service project to codeplex. It's not much actual code, but I could not find it ready-made for use anywhere else, so I made this for myself and also for you!

It’s been a huge life- and time-saver for myself in any situation where there is more than one log4net log file to inspect – which is pretty much every project I’ve been involved in…

It’s also solved all my issues with having EPiServer log different sites to the same file (issues such as no logging, overwritten logs at rollover etc).

You can:

  1. Consolidate all your log4net logs from your sites and servers to a single log via the built-in log4net .NET Remoting Appender.
  2. Solve all issues with simultaneous writes to the log file, lost logs during roll-over etc.
  3. Browse all logs from all systems in a single log file.

Get it at, either a ready-made Windows Installer MSI package or the full source code in C# for Visual Studio 2008.

Sep 02, 2010


Sep 21, 2010 10:33 AM


Sep 21, 2010 10:33 AM

Is it an idea to log errors locally too? Just in case there is a network error... or... hm... - if we're unable to log over remoting due to network errors, the site will be in a much worse shape I guess.

I have considered logging to the database (using a custom database appender), but have put it off, as important database problems would not be logged.

The remote logging is a really good idea, I'll check it out.

Svante Seleborg
Svante Seleborg Sep 21, 2010 10:33 AM

It's certainly useful to have several appenders active at the same time. I regularily have UDP-logging on in order to be able to 'listen in' easily, and also an e-mail appender filtering Fatal-level logs so I'll get an e-mail if something really bad happens. Provided the network is up of course ;-)

The beauty of log4net (and similar frameworks) is the capability to instrument your code in one place independent of the number and location of actual logging targets. Also note that you can log differently to different appenders, it's more flexible than just being able to redirect the output.

So, sure, log it to a local RollingFileAppender as well as a 'backup'.

In actual practice my experience with it for the last couple of months have actually been 100% uptime. I lost many more logs before, due to EPiServer simultaneous access to the logfile in enterprise-mode.

Please login to comment.
Latest blogs
Plug-in manager is back in CMS 12

Plug-in manager is back in the UI, what is it and how can i use it?

Luc Gosso (MVP) | Oct 6, 2022 | Syndicated blog

Display Child Pages in Content Delivery API Response

The below example will implement an instance of IContentConverterProvider to customise the serialisation of PageData and output child pages in the...

Minesh Shah (Netcel) | Oct 4, 2022

Bring the Report Center back in Optimizely CMS 12

The Report Center has been a part of Optimizely CMS since its first debut in version 5R2 in 2008, but in CMS 12, it's removed! Don't despair! Make...

Tomas Hensrud Gulla | Oct 4, 2022 | Syndicated blog

Customizing Property Lists in Optimizely CMS

Generic property lists is a cool editorial feature that has gained a lot of popularity - in spite of still being unsupported (officially). But if y...

Allan Thraen | Oct 2, 2022 | Syndicated blog

Optimizely names Luminary Senior Developer, Ynze Nunnink, OMVP

Luminary Senior Developer and Optimizely Lead, Ynze Nunnink has secured the coveted position of Optimizely MVP. Earning a Platinum badge for his...

Ynze | Oct 2, 2022 | Syndicated blog

Content Delivery API – The Case of the Duplicate API Refresh Token

Creating a custom refresh provider to resolve the issues with duplicate tokens in the DXC The post Content Delivery API – The Case of the Duplicate...

David Lewis | Sep 29, 2022 | Syndicated blog