|Oct 2014||Fix for an issue in version 18.104.22.168, where Azure VMs do not persist on the “Virtual machines” tab when you click OK and reopen the template UI. This happens when you configure Azure monitoring using the template.|
The Management Pack for Microsoft Azure enables you to monitor the availability and performance of Azure fabric resources that are running on Microsoft Azure. The management pack runs on a specified server pool and then uses various Microsoft Azure APIs to remotely discover and collect instrumentation information about a specified Microsoft Azure resource, such as a Cloud Service, Storage, or Virtual Machines. The Management Pack for Microsoft Azure provides no functionality on import. For each Microsoft Azure subscription that contains Azure resources you want to monitor, you must configure discovery and monitoring by first using the Microsoft Azure wizard in the administration section of the Operations Console, then the Microsoft Azure Monitoring template in the authoring section of the Operations Console. For more information, see Configuring the Management Pack for Microsoft Azure Fabric.
After configuration, the Management Pack for Microsoft Azure Fabric offers the following functionality:
• Discovers Microsoft Azure Cloud services.
• Provides status of each role instance.
• Collects and monitors performance information per role instance.
• Collects and monitors Windows events per role instance
• Collects and monitors the .NET Framework trace messages from each role instance.
• Grooms performance, event, and the .NET Framework trace data from Microsoft Azure storage.
• Changes the number of role instances.
• Discovers Microsoft Azure Virtual Machines
• Provides status of each role instance of the Virtual Machine
• Discovers Microsoft Azure Storage
• Monitors availability and size of each Storage and optionally alerts
• Discover relationships between discovered Azure resources, to see which other resources a particular Azure resource uses. This information is then displayed in a topology dashboard
• Monitors management and cloud service certificates and alerts if the certificates are about to expire
• Includes a new Distributed Application template that lets you create distributed applications that span Azure as well as on-premise resources, for Hybrid monitoring scenarios.
• Includes a set of dashboards for the Hybrid monitoring scenarios
Monitoring a Large Number of Azure Instances
The Operations Manager Management Pack monitors memory usage of the proxy agent. If you are monitoring more than 500 Microsoft Azure instances from a particular agent, you should increase the threshold for the Monitoring Host Private Bytes Threshold monitor to 350 MB or higher.
The following requirements must be met to run this Management Pack:
• You must have an Operations Manager 2012 SP1 or later environment, this Management Pack will not import on Operations Manager 2007 R2 or Operations Manager 2012 RTM.
• At least one machine in your server pool must have internet connectivity in order to be able to communicate with Microsoft Azure
• Microsoft Azure Diagnostics must be enabled. For more information about Microsoft Azure Diagnostics, see Collect Logging Data by Using Microsoft Azure Diagnostics
• Microsoft Azure Diagnostics must be configured to forward diagnostic data to a Microsoft Azure storage. For more information about configuring Microsoft Azure Diagnostics, see Transferring Diagnostic Data to Microsoft Azure Storage
• If you create an Azure subscription on a console computer that is not connected to the Internet – even when all management servers in the group are connected to the Internet, you will receive the following exception:
Message: Could not get subscription details
System.Exception: Azure Management REST request is failed. Method:GET URI:https://management.core.windows.net/a906c760-2c06-4af1-9ef0-0fc7309476b7 StatusCode:0, ErrorCode: ErrorMessage: Exception:The remote name could not be resolved: ‘management.core.windows.net’
The connection string for Microsoft Azure Diagnostics must be specified in the service configuration file (.cscfg) and should not be hardcoded in the application. By default, the Management Pack for Microsoft Azure Applications references the DiagnosticsConnectionString setting name in the service configuration file. If a different name is used in the service configuration file, you must override the Diagnostics Storage Account Setting Name parameter for Microsoft Azure Hosted Service Total Discovery.
You must manually ensure that the prerequisites are met. The management pack does not validate that prerequisites are met.