- Application Monitoring
- Setting Up Windows Azure Diagnostics
- Accessing Windows Azure Diagnostic Data
- Windows Azure Diagnostics Configuration Demo
- On-Demand Transfer for the Windows Azure Diagnostics Configuration?
- Modifying the Windows Azure Diagnostics Configuration
- Tradeoffs with Windows Azure Diagnostics Configuration
- Windows Azure Service Dashboard
- Scenarios
- Summary
Accessing Windows Azure Diagnostic Data
Figure 2 illustrates how you access the saved Windows Azure diagnostic data.
Figure 2 Diagnostic data access.
You can access the data in one of two ways: You can schedule periodic transfers of data, as illustrated in the previous code fragment, or you can download data on demand. Downloading data on demand, combined with the ability to alter the Diagnostic Monitor configuration without a service refresh, allows you to diagnose scenarios that are difficult to debug. You can add diagnostic information to the configuration, download data as needed, and then remove the additional information when you no longer need it.
Certain information is collected by default, as shown in the following table. If you want to collect data that isn't collected by default, you have to modify the default configuration. The table also shows what data is collected in Azure tables and which information is collected in Azure blob storage.
Default Diagnostic Monitor Configuration with Data Formats
Data Source |
Collected by Default? |
Data Format |
Windows Azure logs |
Yes, with Trace Listener |
Table |
IIS 7 logs |
Yes |
Blob |
Infrastructure logs |
Yes |
Table |
Failed request logs |
No |
Blob |
Event logs |
No |
Table |
Performance counters |
No |
Table |
Crash dumps |
No |
Blob |
Custom logs |
No |
Blob |