In the previous blog posts we used an existing MSDN subscription to activate an Azure subscription, created and deployed a sample Azure application, and added the Azure management pack to Operations Manager 2012. That should be sufficient to provide monitoring for the application but hey – what’s the fun in stopping there! We need some synthetic transactions to access this application to actually use the application and why not try using Azure to generate synthetic transactions to monitor an application in Azure! So, here we go. Steps required:
1) Start with an existing functional Operations Manager 2012 environment and upgrade it to System Center 2012 Beta.
2) Join in the beta, download and configure GSM by following this excellent writeup (great job Walter!) which provides steps required to install and configure GSM for OpsMgr 2012 SP1 beta.
3) The Windows Azure / Deployment State view provides an external URL which can be used to for synthetic web transactions. The screenshot below shows the Web Application Availability monitoring available in OpsMgr 2012 RTM (without GSM) showing the results of synthetic web transactions performed to this website from an OpsMgr agent.
4) Using GSM we can now see the Azure application monitored from across the globe as shown in the two figures below:
[You have GOT to admit, those two screenshots are extremely cool!]
In the next part of this blog series we will look into how to extend beyond what is available by default in the Azure management pack.