During the course of debugging Windows Azure applications on a daily basis I have accumulated several tips, tricks, and debugging techniques that are specific to the Azure platform. I plan to create a series of blog posts to share a lot of the information that my team uses internally to troubleshoot Windows Azure. The first one will start off with some of the resources that you can find once you RDP into an Azure VM.
Debugging Windows Azure Series
One of the keys to troubleshooting an issue is understanding the overall environment and what resources and log files are available. The C: drive contains config info and local storage, the D: drive contains Windows and WaAppAgent logs, and the E: drive contains the customer’s role code.
C: - log files, LocalResource folders, etc
D: - Windows (%SystemDrive%, %SystemRoot%, etc), agent logs
E: - Virtual drive containing service package
This drive is created when the guest agent deploys the service package. Note that this is dynamically created and may end up being the F: drive, G: drive, etc.