Now that I had a functional application in Azure, my next step was to get the Azure management pack added into Operations Manager 2012 and start monitoring my sample application. Please note that for this test I had an existing functional Operations Manger 2012 environment. The steps below were what was required to get my Azure application monitored in OpsMgr:
1) Download and install the Azure management pack (downloaded from here).
2) Read the attached OM2007_MP_Azure.docx file which provides excellent guidance to get this MP integrated.
4) Create and upload a valid X509 certificate in .CER format to the Windows Azure developer portal to enable use of the Windows Azure Management API. Note it needs to be a .CER file not a .PFX file on Azure, but in OpsMgr the documentation it says it needs to be a pfx file. I ended up creating both by creating a certificate request in IIS (shown below) and exporting it to a PFX. The following writeup provided an excellent explanation for the accounts required and the certificates required: http://blogs.msdn.com/b/walterm/archive/2011/02/14/adding-azure-application-monitoring-to-scom-2007-r2.aspx.
After this I browsed to my certificate store for the local computer, found the certificate and exported it as a CER file as well.
5) The next step was to configure the management pack run as accounts which is documented well at: http://technet.microsoft.com/en-us/library/gg276377.aspx. I created two accounts, one with the Basic Authentication which had the password that I specified when exporting the certificate and one with the certificate file that I exported (which was the PFX file).
6) Add the Azure application to monitoring by Operations Manager: (see http://technet.microsoft.com/en-us/library/gg276377.aspx for additional details). This is done in the authoring pane by using the Windows Azure Application management pack template. For my environment this was eventually changed to monitor the staging environment as that is where I deployed my application in Azure.
The subscription ID information is available on the Azure site in Azure portal, account, subscriptions properties as shown below:
The following shows the results of this monitoring after my Azure application was successfully monitored by Operations Manager.
The deployment state view was extremely useful as it included the URL which could also be used to perform synthetic web transactions against which will be discussed later in this blog series.
Note: The performance views are not currently providing any data on my application even after adding synthetic web transactions to access the application I have uploaded to Azure. This will be investigated later in this blog series.
The next part of this blog series will discuss monitoring Azure with Global Service Monitoring.