1. Pradeep Kumar C Support Escalation Engineer Windows Azure Diagnostics Logging and Monitoring in the Cloud

3. WAD overview & Architecture

5. Reason for Diagnostics in Azure 1. Save diagnostic data that would be lost during a reimaging of the instance (an Azure Cloud Service is stateless) 2. Provide a central repository for diagnostics from multiple role instances Diagnostic Strategy Spend time considering a diagnostic strategy for your Azure application i.e. do want to record, errors, deployment status, monitor performance How will diagnostics setting be changed once deployed? Consider cost of logging, both performance wise and financially How will you access diagnostic information?

6. SDK Component provides distributed monitoring & data Collection Supports standard diagnostic APIs Cloud – Friendly Manage Multiple role instances centrally Scalable Build on Windows Azure Storage & used by scale-out/Scale-in Windows Azure Platform feature Developer in control What to Collect & When to collect

7. How to Enable WAD

8. Enable Programmatically : using DiagnosticMonitor.Start() Enable Diagnostic with : Configuration (diagnostic.wadcfg) Enable Diagnostic with Windows Azure SDK 2.0 via Visual Studio

10. <DiagnosticInfrastructureLogs bufferQuotaInMB="512" scheduledTransferLogLevelFilter="Verbose" scheduledTransferPeriod="PT1S" /> <Logs bufferQuotaInMB="1024" scheduledTransferLogLevelFilter="Verbose" scheduledTransferPeriod="PT1S" /> <WindowsEventLog bufferQuotaInMB="512" scheduledTransferLogLevelFilter="Verbose" scheduledTransferPeriod="PT5M">

13. How Does It Work (in a nutshell)? Role Instance Starts Diagnostic Monitor Starts Monitor is configured Imperatively at Start time Remotely any time via configuration file Configuration is saved in Storage Monitor buffers data locally User can set a quota (FIFO) Initiates transfer to Azure storage from local buffer

15. D E M O

16. Storage Considerations

17. Set up a separate Diagnostic Storage account Choose only required Diagnostic data Use an affinity group Periodically copy and clear the Diagnostic Data from Storage Be aware of cost of logging, both physical and bandwidth

18. Common Diagnostic Tasks

19. Monitoring application performance CPU and memory usage Requests to application Troubleshooting and Debugging issues Errors or exceptions in code Capacity planning Identify need for more compute resource

20. Remote Configuration

23. D E M O

24. Issues & Troubleshooting

25. Scenario Logs no longer or never copied to Azure Storage Could be all logs configured Specific logs All instances of a role or specific ones

26. Troubleshooting steps Check WAD configuration RDP onto instance to check WAD processes Locally check WAD configuration Ensure logs actually exist Raise a support case

30. Questions Visit CIE Blog, Join the Webinar - Windows Azure Diagnostics - Logging and Monitoring in the Cloud on August 6th at 3PM IST (UTC +5:30)Join the Webinar - Windows Azure Diagnostics - Logging and Monitoring in the Cloud on August 6th at 3PM IST (UTC +5:30)

31. © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.