{"componentChunkName":"component---src-templates-blog-post-js","path":"/2011/08/08/customizing-log4net-log-entries-on-azure/","result":{"data":{"site":{"siteMetadata":{"title":"Vidar's musings"}},"markdownRemark":{"id":"d48e027d-b3bf-55b9-b8ca-e9b21aee4260","excerpt":"I have earlier blogged about how to use Log4Net on Azure compute. With this solution the log files from the various running instances gets transferred to a…","html":"

I have earlier blogged about how to use Log4Net on Azure compute. With this solution the log files from the various running instances gets transferred to a common container on Azure blob store. When I mine the log data, I usually merge all the log files together an run text utils like grep or sed on them.

\n

One challenge when merging the log files together is that we then lose the information about which instance the different log entries came from. In order to fix this, we can customize the log entries to that we keep this information.

\n

The first we need to do, is to create a new layout class that inherits from PatternLayout:

\n
using log4net.Layout;\nnamespace Demo.Log4Net.Azure\n{\n    public class AzurePatternLayout : PatternLayout\n    {\n        public AzurePatternLayout()\n        {\n             // TODO: add converters\n        }\n    }\n}
\n

Next, we need to register this class in the log4net configuration:

\n
<log4net>\n  <appender ...>\n    <layout type=\"Demo.Log4Net.Azure.AzurePatternLayout, Demo.Log4Net.Azure\">\n      <conversionPattern ... />\n    </layout>\n  </appender>\n  ...\n</log4net>
\n

So now that we have a new PatternLayout class, we can add some logic into it for adding Azure-specific log information into the entries. To do so, we first need a new Converter class:

\n
using System.IO;\nusing log4net.Util;\nusing Microsoft.WindowsAzure.ServiceRuntime;\nnamespace Demo.Log4Net.Azure\n{\n    internal class AzureInstanceIdPatternConverter : PatternConverter\n    {\n        protected override void Convert(TextWriter writer, object state)\n        {\n            writer.Write(RoleEnvironment.CurrentRoleInstance.Id);\n        }\n    }\n}
\n

Now, we register the new AzureInstanceIdPatternConverter in the constructor of AzurePatternLayout:

\n
public class AzurePatternLayout : PatternLayout\n{\n    public AzurePatternLayout()\n    {\n        AddConverter(\"roleinstance\", typeof(AzureInstanceIdPatternConverter));\n    }\n}
\n

Then we can change the conversionPattern element of the Log4Net configuration to use the new Azure environment information:

\n
<layout type=\"Demo.Log4Net.Azure.AzurePatternLayout, Demo.Log4Net.Azure\">\n  <conversionPattern value=\"%date [%roleinstance] [%thread] %-5level %logger [%appdomain] - %message%newline\" />\n</layout>
\n

….which will make the log entries look something like this:

\n

\n \n \n \n \n

\n

(The screenshot shows instance ids generated by DevFabric, not an instance in the cloud).

","frontmatter":{"title":"Customizing Log4net log entries on Azure","date":"August 08, 2011","description":null}},"previous":{"fields":{"slug":"/2011/08/03/using-log4net-in-azure-compute/"},"frontmatter":{"title":"Using Log4Net in Azure Compute"}},"next":{"fields":{"slug":"/2011/08/15/log4net-writing-log-entries-to-azure-table-storage/"},"frontmatter":{"title":"Log4Net: writing log entries to Azure Table Storage"}}},"pageContext":{"id":"d48e027d-b3bf-55b9-b8ca-e9b21aee4260","previousPostId":"a7b51755-30bc-51bb-859a-898509965a36","nextPostId":"f4a540d9-6f60-5670-abea-72ad5e0a53c5"}},"staticQueryHashes":["2841359383","3257411868"]}