NLog: writing log entries to Azure Table Storage

In August last year, I blogged about how to get Log4Net log entries written to Azure Table Storage. In this article, I will show how the same thing can be easily achieved using NLog.

The concepts in NLog is very similar to Log4Net. More or less, replace the word “appender” in Log4Net lingo with “target”, and you’re game.

First, let’s create a class for log entries:

public class LogEntry : TableServiceEntity
    public LogEntry()
        var now = DateTime.UtcNow;
        PartitionKey = string.Format("{0:yyyy-MM}", now);
        RowKey = string.Format("{0:dd HH:mm:ss.fff}-{1}", now, Guid.NewGuid());
    #region Table columns
    public string Message { get; set; }
    public string Level { get; set; }
    public string LoggerName { get; set; }
    public string RoleInstance { get; set; }
    public string DeploymentId { get; set; }
    public string StackTrace { get; set; }

Next, we need to do is to create a class that represents the table storage service. It needs to inherit from TableServiceContext:

public class LogServiceContext : TableServiceContext
    public LogServiceContext(string baseAddress, StorageCredentials credentials) : base(baseAddress, credentials) { }
    internal void Log(LogEntry logEntry)
        AddObject("LogEntries", logEntry);
    public IQueryable<LogEntry> LogEntries
            return CreateQuery<LogEntry>("LogEntries");

Finally, as far as code is concerned, a class that is a custom NLog target that gets called when the NLog framework needs to log something:

public class AzureStorageTarget : Target
    private LogServiceContext _ctx;
    private string _tableEndpoint;
    public string TableStorageConnectionStringName { get; set; }
    protected override void InitializeTarget()
        var cloudStorageAccount =
        _tableEndpoint = cloudStorageAccount.TableEndpoint.AbsoluteUri;
        CloudTableClient.CreateTablesFromModel(typeof(LogServiceContext), _tableEndpoint, cloudStorageAccount.Credentials);
        _ctx = new LogServiceContext(cloudStorageAccount.TableEndpoint.AbsoluteUri, cloudStorageAccount.Credentials);
    protected override void Write(LogEventInfo loggingEvent)
        Action doWriteToLog = () =>
                _ctx.Log(new LogEntry
                    RoleInstance = RoleEnvironment.CurrentRoleInstance.Id,
                    DeploymentId = RoleEnvironment.DeploymentId,
                    Timestamp = loggingEvent.TimeStamp,
                    Message = loggingEvent.FormattedMessage,
                    Level = loggingEvent.Level.Name,
                    LoggerName = loggingEvent.LoggerName,
                    StackTrace = loggingEvent.StackTrace != null ? loggingEvent.StackTrace.ToString() : null
            catch (DataServiceRequestException e)
                InternalLogger.Error(string.Format("{0}: Could not write log entry to {1}: {2}",
                    GetType().AssemblyQualifiedName, _tableEndpoint, e.Message), e);
        doWriteToLog.BeginInvoke(null, null);

So, to make it work, we need to register the target with the NLog framework. This is done in the NLog.config file:

<?xml version="1.0"?>
<nlog xmlns="" xmlns:xsi="">
    <add assembly="Demo.NLog.Azure" />
    <target name="azure" type="AzureStorage" tableStorageConnectionStringName="Log4Net.ConenctionString" />
    <logger name="*" minlevel="Info" writeTo="azure" />

For information about how to set your ServiceDefinition.csdef and ServiceConfiguration.cscfg files, see my previous post.You can find the code for this example on GitHub. Suggestions for improvement are very welcome.

  • Peter Seewald

    Good stuff I think you should made it a nuget package. 🙂

  • Mark Phillips

    Can I ask what the benefit of the Action delegate is inside the Write Method – is this personal preference or required for some reason? Other than that – this was exactly what I was looking for – i might do some additional refactoring once I progress – but a good starting point.

    • The idea was to make the actually writing to the storage asynchronously. Basically, the calling thread does not sit and wait around for the writing to finish. There might be better ways to do this, suggestions are welcome. There might be that the Azure storage client library has some way of handling this as well…

  • Stefan

    Thanks, what’s …tableStorageConnectionStringName=”Log4Net.ConenctionString” in the NLog.config file?

  • I noticed the BeginInvoke here and the BeginSaveChanges in the GitHub code, for some reason I found that this prevented the log from writing more than the first entry. When I replaced BeginSaveChanges(SaveChangesOptions.Batch, null, null) with just SaveChanges() the log started writing all the incoming entries. In the nlog.config I added the “async wrapper” to achieve roughly the same idea and letting NLog worry about how to implement the threading.

    Thanks so much for working through all the difficult bits, as I can’t seem to get Azure diagnostics working I really am pleased to be able to fall back on a library I already use for that.

    Thanks again,


  • Neil

    Hi, I am new to Azure and Nlog.

    I am able to sae nlogg logs into txt files on my local root folder.
    Now, I want to store it on either Aure table storage or blob storage.
    As per this code demo I have created classes in my NLog utility class and treid but nothis is happening.
    Can you please guide me where to crete those classes ?

  • Ashsi

    can you give me an example on how to use this library.

  • nesbo

    Thanks for the tip!