Windows Azure Diagnostics (WAD) has the ability to copy files to Azure blob storage.  The feature is meant for copying custom log files but you can use it to copy any file that WAD has permission to access.  To configure this feature via diagnostics.wadcfg add appropriate <DataSource>...

Azure 1.3 added the ability to control Windows Azure Diagnostics (WAD) via a config file. The MSDN documentation covering diagnostics.wadcfg explains that the capability was added to support the VM role. The documentation also says to continue configuring WAD via code in OnStart for the other role types...

By default Windows Azure Diagnostics (WAD) does not receive ASP.NET Health Monitoring events.  The machine web.config file at %windir%\Microsoft.NET\Framework64\v4.0.30319\Config\web.config shows the default behavior of ASP.NET Health Monitoring.  Basically all unhandled errors and audit failures...

Windows Azure Diagnostics (WAD) is built upon Event Tracing for Windows (ETW) . To get the most out of WAD and future Azure product offerings you need to understand and use ETW. Here is a little ETW primer and how it relates to WAD: 1. ETW is the efficient kernel-level tracing facility built into...

I’ve decided to write a series of blog posts on Windows Azure Diagnostics best practices to share what I’ve learned. MSIT is in the process of reviewing our current Azure monitoring, combining it with some product team insight, to define MSIT’s Azure monitoring and debugging best practices...