Interested in how a service level agreement can help you keep track of your overall health in the cloud? My session at Dev Connections reviewed the things you need to care about, even as developers, to help produce metrics that support a robust 24x7 operation. Building an SLA can help even if only used internally. For supporting code on diagnostics and performance counters you should look for my forthcoming post for my tutorial.
VWA03: The Cloud, the SLA and the Code
Here’s the thing...you need visibility into any cloud application. Rest assured someone at the top has their job on the line if things go wrong and you can’t foresee the issue or recover quickly. One of the best ways to gain visibility is to write your own Service Level Agreement (SLA) that captures the necessary performance and diagnostic statistics; process and escalation procedures; backup and recovery procedures; and much more. Of course you also want to leverage the capabilities of your provider since they also provide many aspects of these services. This session focuses on what developers can do to help produce information useful to the SLA to support the end goal. You’ll learn the must-do list for rigging your Windows Azure cloud applications with diagnostics, learn how to monitor that information, and see how it relates to the SLA.