Azure offers some very useful out the box tools for pooling diagnostic information into blob and table storage. http://azure.microsoft.com/en-gb/documentation/articles/cloud-services-dotnet-diagnostics/ contains lots of information on this.
In your solution you should end up with a file: diagnostics.wadcfg under the roles folder. One issue we ran into occurred when we changed the name of the counterpart project, the diagnostics file then sat in the wrong place. Ensure the structure is as follows:
|
1 2 3 4 5 6 |
- WebProject -- files for your site - CloudProject -- Roles (default folder name) --- WebProject (folder named the same as your webproject) ---- diagnostics.wadcfg |
You can verify this by checking the Azure project ccproj file. You should see:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 |
<ItemGroup> <ProjectReference Include="..\WebProject\WebProject.csproj"> <Name>CloudProject</Name> ... <RoleName>CloudProject</RoleName> ... </ProjectReference> </ItemGroup> <ItemGroup> <Folder Include="WebProjectContent\" /> </ItemGroup> <ItemGroup> <Content Include="WebProjectContent\diagnostics.wadcfg"> <SubType>Content</SubType> </Content> </ItemGroup> |
When the site fires up you should then see blob storage contain a folder called: wad-control-container. If you have a look in there it should contain a file that mimics the content of your diagnostics.wadcfg file.
I found it was useful to clear out this folder before testing new deployments.