NLog: How to exclude specific loggers from a specific rule?

nlog
Nathan Ridley picture Nathan Ridley · Nov 3, 2011 · Viewed 16.9k times · Source

In my NLog configuration, I have a catch-all logger but a specific logger I have created is very spammy and I want its output to go to its own file. That part is easy, but the catch-all logger receives the spammy log messages as well. How do I tell the main logger to log everything but to exclude the spammy logger?

I'm using NLog 2.0.

Answer

wageoghe picture wageoghe · Nov 3, 2011

I think something like this is what you want:

<logger name="SpammyLogger" minlevel="Off" maxlevel="Trace" final="true" />  
<logger name="SpammyLogger" minlevel="Debug" maxlevel="Fatal" writeTo="SpammyFileTarget" final="true" />  
<logger name="*" levels="Trace" writeTo="RegularFileTarget/" />

Adding final="true" means that no more rules will be executed for the events produced by "SpammyLogger", but it applies only to the specified levels.(see https://github.com/nlog/nlog/wiki/Configuration-file#rules)

See this link for more NLog info that you might find helpful:

Most useful NLog configurations

Related questions

Most useful NLog configurations

What are the best or most useful configurations for logging with NLog? (These can be simple or complex, as long as they're useful.) I'm thinking of examples like automatically rolling over log files at a certain size, changing the layout (…

Read More
log4net vs. Nlog

Anyone have experience for both? How do they stack up against each other? We are planning on using one of them for logging in an enterprise application. References: log4net nlog EDIT: We have no existing dependencies to either nlog …

Read More
NLog does not create a log file

I am trying to add logging to an application running on mobile device with Windows Mobile 6.1. � .NET Compact framework 3.5. using NLog. I have the appropriate version of the NLog distribution installed. However no log files are being created. Here is …

Read More