Initializing and Configuring Diagnostic Data Sources
Updated: November 22, 2010
Multiple opportunities exist for you to collect diagnostic data by using Windows Azure Diagnostics.
The following table lists the types of diagnostic data that you can collect.
| Data source | Default configuration | Role types supported |
|---|---|---|
|
Windows Azure logs |
Collected by default (requires a trace listener to be added to the web.config or app.config file) |
Web and worker roles |
|
IIS 7.0 logs |
Collected by default |
Web roles only |
|
Windows Azure Diagnostic infrastructure logs |
Collected by default |
Web and worker roles |
|
Failed Request logs |
Not collected by default |
Web roles only |
|
Windows Event logs |
Not collected by default |
Web and worker roles |
|
Performance counters |
Not collected by default |
Web and worker roles |
|
Crash dumps |
Not collected by default |
Web and worker roles |
|
Custom error logs |
Not collected by default |
Web and worker roles |
 Note |
|---|
| For complete reference information about the APIs provided by Windows Azure Diagnostics, see the Windows Azure Managed Library Reference. |
To start collecting diagnostic data, you must initialize the Windows Azure diagnostic monitor. To do this, complete the procedure listed in How to Initialize the Windows Azure Diagnostic Monitor.
Not all of the data sources are added to the diagnostic monitor by default. Only the Windows Azure logs, Windows Azure Diagnostics infrastructure logs, and IIS 7.0 logs are initially configured in the diagnostic monitor. A data source is represented by a data buffer in the configuration. You must add additional data buffers to the configuration to collect more diagnostic data. To do this, see the following information:
