DevOps Zone is brought to you in partnership with:

I am developer and technology maniac who is working on Microsoft and PHP technologies. I have ASP.NET MVP title and I hold MCAD, MCSD and MCTS certificates. When I have free time I usually play with new technologies, hack something, read books, participate in communities and speak in events. I am also active blogger and my ASP.NET blog is the place you can find some interesting reading about my discoveries and personal thoughts. Gunnar is a DZone MVB and is not an employee of DZone and has posted 142 posts at DZone. You can read more from them at their website. View Full User Profile

How to Make NLog Create Separate Log per Service Thread

  • submit to reddit

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);
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.

Published at DZone with permission of Gunnar Peipman, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)