In the first part of this article (http://blogs.technet.com/b/dcaro/archive/2012/05/02/how-to-monitor-your-windows-azure-application-with-system-center-2012.aspx), I have explained how to enable monitoring for a Windows Azure application. We have seen that you can enable it from the code of the application or you can enable performance monitoring as well as event log monitoring by leveraging Windows Azure Powershell cmdlets or third party application.
Once that configuration part has been done, we can work on the configuration of System Center 2012, more specifically the Operation Manager component (SCOM). This requires to have installed the “System Center Monitoring Pack for Windows Azure Applications” that you can download here : http://www.microsoft.com/download/en/details.aspx?id=11324 (At the time this post is written, the management pack is targeting SCOM 2007 but it works with the 2012 release).
Once you have installed the Azure Management pack on your SCOM server, you will have to follow those steps :
Let’s walk through these steps.
You will need three “run as” account in System Center Operation Manager 2012 :
You will find the detailed step by step procedure on this blog : http://oakleafblog.blogspot.fr/2011/09/installing-systems-center-monitoring.html (Although it was made for SCOM 2007, the steps to create the accounts are still valid with SC 2012).
Because we have installed the monitoring pack for Azure, under the Authoring you can see the “Windows Azure Application” management pack template.
From there we select the “Add Monitoring Wizard” to create the monitoring for our Azure application. Select “Windows Azure Application” as the monitoring type.
Type a name and select a management pack for your application.
Make sure you have the following information from your Azure Application :
All what you need to do is now fill in the wizard.
For the Azure Certificate Run As Account and the Azure Certificate Password Run As Account, use the accounts we have created in step 1.
Then specify the Proxy Agent which is the server you want to use to actually do the monitoring. In my lab, I’ve used the VMM Server but you can choose any server in your environment.
Review the summary and validate.
Go to the Monitoring tab and look for the "Windows Azure” node in the top left list.
After a while you will be able to see your azure application under the Windows Azure node. Be patient, it takes some time ! In my case, it took about 8 minutes.
Initially the application will appear as not monitored and then the empty green circle will change to a green circle with a green check mark.
Now we are ready to look at the performance counters themselves. You have to go to the "Performance” node still under the Monitoring tab.
Once the application has been discovered, Operation Manager will pull the data every 300 seconds. Again, be patient and the counters will appear in the bottom of the performance graph as you can see bellow.
From here you can create you own dashboard and / or publish it on Sharepoint if you want to give access to those graph to some people who do not have the SCOM console installed.
Enjoy the power and elasticity of Azure to deploy your applications with the control and insights brought to you by System Center Operation Manager 2012.
List of useful additional resources and blogs to read more about this topic :