Question

Is there any .NET logging framework that have ability to switch appender if something is wrong with current one. Actually what I want is following:

If I’m using database appender and when something goes wrong with database (e.g. server goes down, lose power…) I want to switch to second appender (e.g. which log into file).

Does this ability have one of following: log4net, NLog, Enterprise Library? I was looking for this but no luck.

Answer 1

Because log4netContribute FallbackAppender is not working as expected I’ve made deep research and found that this ability has nLog. I tested it and it is working like a charm 😉 Here is an example:

[app.config]

<?xml version="1.0"?>
<configuration>
<configSections>
<section name="nlog" type="NLog.Config.ConfigSectionHandler, NLog"/>
</configSections>
<nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<variable name="appTitle" value="My Application"/>
<targets>
<target name="file" xsi:type="FallbackGroup" returnToFirstOnSuccess="true">
<target xsi:type="File" fileName="x:\vladimir.txt" />
<target xsi:type="File" fileName="w:\pavlovic.txt" />
<target xsi:type="File" fileName="w:\zvjerka24.txt" />
</target>
</targets>
<rules>
<logger name="*" minlevel="Debug" writeTo="file" />
</rules>
</nlog>
</configuration>

[code]

Logger _logger = LogManager.GetCurrentClassLogger();
_logger.Info("Neki Info");
_logger.Debug("Neki debug");
_logger.Error("Neki  ERROR");
_logger.Error("Pa jos neki");