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

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

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.

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...