Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

How to Make NLog Create Separate Log per Service Thread

DZone's Guide to

How to Make NLog Create Separate Log per Service Thread

· DevOps Zone
Free Resource

In response to accelerated release cycles, a new set of testing capabilities is now required to deliver quality at speed. This is why there is a shake-up in the testing tools landscape—and a new leader has emerged in the just released Gartner Magic Quadrant for Software Test Automation.

NLog on is popular logging component for .NET applications. I am using it in one project where I built multi-threaded server that is running similar threads with different configuration. As those thread are independent services I needed way how to configure NLog to create different log file for each thread. Here is my solution.

Server instances structure in file systemWhen new service starts in its thread I will configure NLog in code to create log file to correct folder with correct name and layout. Image on right shows how server is keeping instances data on disk. Each instance has its own folder and for logs there is subfolder because for every date there will be new log file.

var target = new FileTarget();
target.Name = InstanceName;
target.FileName = LogsFolder + "/${shortdate}.log";
target.Layout = "${date:format=HH\\:MM\\:ss} ${logger} ${message}";
 
var config = new LoggingConfiguration();
config.AddTarget(this.Name, target);
 
var rule = new LoggingRule("*", LogLevel.Info, target);
config.LoggingRules.Add(rule);
 
LogManager.Configuration = config;
 
_logger = LogManager.GetLogger(InstanceName);
_logger.Info("Logger is initialized");

This way I got all logging done on code level and as there is arbitrarily small probability that logging ever changes I am very sure that this seemingly temporary solution will live with project for long time.


Recently published 5th annual Software Fail Watch Report identified 606 recorded software fails impacting half of the world’s population (3.7 billion people), $1.7 trillion in assets, and 314 companies. Our advice: Rethink your testing strategies and approach to quality so they’re not finding it in your next release.

Topics:

Published at DZone with permission of Gunnar Peipman, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}