Skip to main content

Windows Azure Diagnostics Logging

Although the logging functionality in Windows Azure uses the familiar Trace class, some extra steps are required. As I always forget them, a quick step-by-step guide:

Step 1: Adding DLL references

Remark: If you create a new cloud project and immediately add a web/worker role, the required DLL reference is already added.

Open the project you’ll host on Azure and add a reference to Microsoft.WindowsAzure.Diagnostics.dll. This is the dll that exposes the diagnostics configuration and management APIs.

Step 2: Register the Azure Diagnostics TraceListener

Remark: If you create a new cloud project and immediately add a web/worker role, the required tracelistener is already added to your configuration file.

Open your configuration file and add the following config settings:

<system.diagnostics>
<trace>
<listeners>
<add type="Microsoft.WindowsAzure.Diagnostics.DiagnosticMonitorTraceListener, Microsoft.WindowsAzure.Diagnostics, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
name="AzureDiagnostics">
<filter type="" />
</add>
</listeners>
</trace>
</system.diagnostics>

Step 3: Configure a storage account

The diagnostics will be shipped from time to time to some specific tables inside a Windows Azure Storage account. Therefore you need to specify an Azure Storage connection string that can be used. The default VS template sets up the connection string name as ‘DiagnosticsConnectionString’ and the value as ‘UseDevelopmentStorage=true’. This particular connection string sets up Diagnostics Monitor to use Development Storage account. The connection string can be changed to point to a cloud storage account of your choice. Open up ServiceDefinition.cscfg or use the IDE to change this setting:

<ConfigurationSettings>
<Setting name="Microsoft.WindowsAzure.Plugins.Diagnostics.ConnectionString" value="DefaultEndpointsProtocol=https;AccountName=<accountname>;AccountKey=<key>" />
</ConfigurationSettings>

Step 4: Start the Diagnostics monitor

To enable log shipping you need to start the Diagnostics Monitor. Probably the best place to do this is inside the OnStart() method of your RoleEntryPoint class. In there add the following code:

public override bool OnStart() 
{ 
DiagnosticMonitorConfiguration dmc = DiagnosticMonitor.GetDefaultInitialConfiguration(); 
dmc.Logs.ScheduledTransferPeriod = TimeSpan.FromMinutes(1); 
dmc.Logs.ScheduledTransferLogLevelFilter = LogLevel.Verbose;

DiagnosticMonitor.Start("DiagnosticsConnectionString", dmc); 
} 

This configures the Diagnostic Monitor to ship the log data every minute to the Azure Storage. You can manipulate the Diagnostic Monitor configuration from outside Windows Azure, but this is something for another blog post.

Popular posts from this blog

DevToys–A swiss army knife for developers

As a developer there are a lot of small tasks you need to do as part of your coding, debugging and testing activities.  DevToys is an offline windows app that tries to help you with these tasks. Instead of using different websites you get a fully offline experience offering help for a large list of tasks. Many tools are available. Here is the current list: Converters JSON <> YAML Timestamp Number Base Cron Parser Encoders / Decoders HTML URL Base64 Text & Image GZip JWT Decoder Formatters JSON SQL XML Generators Hash (MD5, SHA1, SHA256, SHA512) UUID 1 and 4 Lorem Ipsum Checksum Text Escape / Unescape Inspector & Case Converter Regex Tester Text Comparer XML Validator Markdown Preview Graphic Color B

Help! I accidently enabled HSTS–on localhost

I ran into an issue after accidently enabling HSTS for a website on localhost. This was not an issue for the original website that was running in IIS and had a certificate configured. But when I tried to run an Angular app a little bit later on http://localhost:4200 the browser redirected me immediately to https://localhost . Whoops! That was not what I wanted in this case. To fix it, you need to go the network settings of your browser, there are available at: chrome://net-internals/#hsts edge://net-internals/#hsts brave://net-internals/#hsts Enter ‘localhost’ in the domain textbox under the Delete domain security policies section and hit Delete . That should do the trick…

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.