The Microsoft Hybrid cloud, as it stands currently, is a mixture of a Hyper-V private cloud with an Azure public cloud, managed by System Center App Controller (formerly Concero). One of the key pieces of the Microsoft solution is monitoring the health of the application (that the business really cares about) using System Center Operations Manager (OpsMgr).
Management packs make monitoring of Hyper-V, Windows, SQL, Exchange, CRM, hardware, storage, etc, easy. You can put together end user perspective monitoring from the basic ping test to the advanced synthetic transaction, build service-centric distributed application models, and provide SLA monitoring of the LOB applications. That’s got the private cloud covered.
There is also a management pack for Azure. This allows you to monitor the availability, health, and performance of your public cloud services. Let’s face it – even if Microsoft does/did provide a monitoring solution within Azure – can you really use a monitoring solution that is a part of the thing you are monitoring, i.e. the Microsoft public cloud? I say no – and that’s the first reason why you should use OpsMgr and this management pack. The second reason is that it allows you to integrate your monitoring of public and private clouds, giving you that mythical single pane of glass for monitoring.
- The features of this management pack are:
- Discovers Windows Azure applications.
- Provides status of each role instance.
- Collects and monitors performance information.
- Collects and monitors Windows events.
- Collects and monitors the .NET Framework trace messages from each role instance.
- Grooms performance, event, and the .NET Framework trace data from Windows Azure storage account.
- Changes the number of role instances via a task.
The prerequisites of it are:
- The management group must be running Operations Manager 2007 R2 Cumulative Update 3.
- The Windows Azure role must be published with full trust level. For more information about Windows Azure trust levels, see Windows Azure Partial Trust Policy Reference.
- Windows Azure Diagnostics must be enabled. For more information about Windows Azure Diagnostics, see Implementing Windows Azure Diagnostics.
- Windows Azure Diagnostics must be configured to forward diagnostic data to a Windows Azure storage account. For more information about configuring Windows Azure Diagnostics, see Transferring Diagnostic Data to Windows Azure Storage.
- Microsoft .NET Framework version 2.0 or newer must be installed on the computer that you designate as the proxy agent when you configure the Monitoring Pack for Windows Azure Applications.
This blog post is the property of Aidan Finn (@joe_elway / http://www.aidanfinn.com) and may not be reused in any manner without prior consent of Aidan Finn. You may quote one paragraph from this blog post if you link to the original blog post.
No related posts.