Version 118 of the Microsoft: Azure PowerPack includes new Dynamic Applications and Device Classes for monitoring four additional Azure services.
- Minimum Required SL1 Version: 11.1.2
Before You Install or Upgrade
Ensure that you are running version 11.1.2 or later of SL1 before installing "Microsoft: Azure" PowerPack version 118.
For details on upgrading SL1, see the relevant SL1 Platform Release Notes.
NOTE: As of Microsoft Azure ClassicPowerPack version 106, Data Collectors running CentOS can no longer discover and monitor Microsoft Azure.
Prior to using the multiple subscription functionality introduced in version 104, ScienceLogic recommends that you review your device capacity and load limits to determine the best method for implementation.
Installation Process
To install this PowerPack:
- Search for and download the PowerPack from the PowerPacks page (Product Downloads > PowerPacks & SyncPacks) at the ScienceLogic Support Site.
- In SL1, go to the PowerPacks page (System > Manage > PowerPacks).
- Click the Actions menu and choose Import PowerPack. The Import PowerPack modal appears.
- Click and navigate to the PowerPack file from step 1.
- Select the PowerPack file and click . The PowerPack Installer modal displays a list of the PowerPack contents.
- Click . The PowerPack is added to the PowerPack Manager page.
See the manual Monitoring Microsoft Azure for instructions on using the new PowerPack.
Upgrading the Microsoft: Azure PowerPack from Version 104 and Later
By default, installing a new version of a PowerPack will overwrite all content in that PowerPack that has already been installed on the target system. You can use the Enable Selective PowerPack Field Protection setting in the Behavior Settings page (System > Settings > Behavior) to prevent the new version of the PowerPack from overwriting local changes for some commonly customized fields.
To upgrade the Microsoft: Azure PowerPack from version 104 and later:
- Familiarize yourself with the Known Issues for this release.
- See the Before You Upgrade section. If you have not done so already, upgrade your system to the minimum required platform version or later release.
- Download this version of the PowerPack from the Support Site to a local computer.
- Before importing and installing this version of the PowerPack, you must disable the existing tree of Azure parent and component devices, recursively. To do so:
- Go to the Device Components page (Registry > Devices > Device Components)
- Collapse the root Azure component device.
- Select the root Azure device's checkbox.
- Click the Select Action drop-down menu. Under Change Collection State, select Disabled (recursive), and then click [Go].
- Go to the PowerPack Manager page (System > Manage > PowerPacks). Click the menu and choose Import PowerPack. Import the Version 118 of the Microsoft: Azure PowerPack. For details on importing PowerPacks, see the chapter on Installing a PowerPack in the PowerPacks manual.
- Click the button. For details on installing PowerPacks, see the chapter on Installing a PowerPack in the PowerPacks manual.
- If you are implementing the multiple subscription feature, go to the Credential Management page (System > Manage > Credentials) and create a new credential or edit an existing one as needed for use with the multiple subscription configuration. (For more information, see the manual Monitoring Microsoft Azure.)
- You must now enable the existing tree of Azure parent and component devices, recursively. To do so:
- Go to the Device Components page (Registry > Devices > Device Components)
- Collapse the root Azure component device.
- Select the root Azure component device's checkbox.
- Click the Select Action drop-down menu. Under Change Collection State, select Active (recursive), and then click [Go].
Upgrading from a Microsoft: Azure PowerPack Version Prior to v104
To upgrade the Microsoft: Azure PowerPack from a version earlier than v104:
- Familiarize yourself with the Known Issues for this release.
- See the Before You Upgrade section. If you have not done so already, upgrade your system to the minimum required platform version or later release.
- Download this version of the PowerPack from the Support Site to a local computer.
- Before importing and installing this version of the PowerPack, you must disable the existing tree of Azure parent and component devices, recursively. To do so:
- Go to the Device Components page (Registry > Devices > Device Components).
- Collapse the root Azure component device.
- Select the root Azure component device's checkbox.
- Click the Select Action drop-down menu. Under Change Collection State, select Disabled (recursive), and then click [Go].
- Because the following Dynamic Applications were force-removed from v103 and v104, when you upgrade to version 111, you must manually remove the device components discovered by these Dynamic Applications.
- Microsoft: Azure Backup Jobs Discovery
- Microsoft: Azure Backup Policies Service Discovery
- Microsoft: Azure Backup Policy Discovery
- Microsoft: Azure Recovery Jobs Service Discovery
- Microsoft: Azure Storage Blob Configuration
- Microsoft: Azure Storage Blob Discovery
- Microsoft: Azure Storage Container Discovery
- Microsoft: Azure Storage Table Discovery
- Microsoft: Azure Storage Queue Discovery
- Go to the Device Manager page (Registry > Devices > Device Manager).
- Filter the list of devices by Device Class | Sub-Class. Type the following in the filter:
Azure Storage Container, Azure Storage Blob, Azure Storage Queue, Azure Storage Table, Backup Policies Service, Backup Policy, Jobs Service, Backup Job
- The Device Manager page now displays only devices with the specified Device Classes. Click the Select All checkbox in the upper right to select all these devices.
- Click on the field, and choose DELETE Selected Devices. Click the button. Confirm that you want to delete the device.
- Next, you must delete the Device Classes associated with the Dynamic Applications that were force-removed. Go to the Device Class Editor page (System > Customize > Device Classes).
- Filter the list of Device Classes. To do so, enter the following:
- Device Class. In this field, type Microsoft.
- Description. In this field, type Backup Policies Service, Backup Policy, Jobs Service, Backup Job, Azure Storage Container, Azure Storage Blob, Azure Storage Queue, Azure Storage Table.
- The Device Class Editor page should now display only the following Device Classes:
- Azure Backup Job
- Azure Backup Policies Service
- Azure Backup Policy
- Azure Jobs Service
- Microsoft Azure Storage Container
- Microsoft Azure Storage Blob
- Microsoft Azure Storage Table
- Microsoft Azure Storage Queue
- Click the field, choose DELETE Device Classes, and click the button. Confirm that you want to delete the device.
- Go to the PowerPack Manager page (System > Manage > PowerPacks). Click the menu and choose Import PowerPack. Import this version of the PowerPack. For details on importing PowerPacks, see the chapter on Installing a PowerPack in the PowerPacks manual.
- Click the button. For details on installing PowerPacks, see the chapter on Installing a PowerPack in the PowerPacks manual.
- Enable the existing tree of Azure parent and component devices, recursively. To do so:
- Go to the Device Components page (Registry > Devices > Device Components).
- Collapse the root Azure component device.
- Select the root Azure component device's checkbox.
- Click the Select Action drop-down menu. Under Change Collection State, select Enabled (recursive), and then click [Go].
- See the manual Monitoring Microsoft Azure for instructions on using the new PowerPack.
Features
This release includes the following features:
- Dynamic Applications that enable SL1 to discover, model, and monitor performance metrics and collect configuration data for Azure resources
- Event Policies that are triggered when Azure resources meet certain status criteria
- Device Classes for each Azure data center location and all of the Azure resources that SL1 monitors
- Example credentials for discovering Azure resources
- A Credential Test to ensure that your Azure credential works as expected
- Run Book Action and Automation policies that can automate certain Azure monitoring processes
Enhancements and Issues Addressed
The following enhancements and addressed issues are included in version 118 of the "Microsoft: Azure" PowerPack:
- The following Dynamic Applications were added to the PowerPack:
- Microsoft: Azure API Apps Discovery
- Microsoft: Azure Container Instances Configuration
- Microsoft: Azure Container Instances Discovery
- Microsoft: Azure Container Instances Performance
- Microsoft: Azure Container Instances Service Discovery
- Microsoft: Azure Container Registry Configuration
- Microsoft: Azure Container Registry Discovery
- Microsoft: Azure Container Registry Performance
- Microsoft: Azure Event Grid Domain Configuration
- Microsoft: Azure Event Grid Domain Discovery
- Microsoft: Azure Event Grid Domain Performance
- Microsoft: Azure Event Grid Domain Service Discovery
- Microsoft: Azure Event Grid Domain Subscription Configuration
- Microsoft: Azure Event Grid Domain Subscription Discovery
- Microsoft: Azure Event Grid Domain Topic Subscription Config.
- Microsoft: Azure Event Grid Domain Topic Subscription Disc.
- Microsoft: Azure Event Grid Domain Topics Configuration
- Microsoft: Azure Event Grid Domain Topics Discovery
- Microsoft: Azure Event Grid Event Subscription Performance
- Microsoft: Azure Event Grid System Topics Configuration
- Microsoft: Azure Event Grid System Topics Discovery
- Microsoft: Azure Event Grid System Topics Performance
- Microsoft: Azure Event Grid System Topics Service Discovery
- Microsoft: Azure Event Grid Sys Topic Subscription Discovery
- Microsoft: Azure Event Grid Topic Configuration
- Microsoft: Azure Event Grid Topic Discovery
- Microsoft: Azure Event Grid Topic Performance
- Microsoft: Azure Event Grid Topic Service Discovery
- The following Dynamic Applications were updated to align to components discovered by the Microsoft: Azure API Apps Discovery Dynamic Application:
- Microsoft: Azure App Configuration
- Microsoft: Azure App Performance
- Microsoft: Azure App Service Plan Discovery
- The following device classes and icons were added to the PowerPack:
- Azure API Apps
- Microsoft: Azure Container Instances
- Microsoft: Azure Container Instances Service
- Microsoft: Azure Container Registry
- Microsoft: Azure Container Registry Service
- Microsoft: Azure Event Grid Domain
- Microsoft: Azure Event Grid Domain Service
- Microsoft: Azure Event Grid Domain Subscription
- Microsoft: Azure Event Grid Domain Topic
- Microsoft: Azure Event Grid Domain Topic Subscription
- Microsoft: Azure Event Grid System Topic
- Microsoft: Azure Event Grid System Topic Service
- Added unified alerts for the following services:
- Microsoft Container Instances Service
- Microsoft Container Registry Service
- Microsoft Event Grid Domain Service
- Microsoft Event Grid System Topic Service
- Updated the snippet in the "Microsoft: Azure Virtual Network Gateway Performance" Dynamic Application to apply metrics to different types of gateways.
- Corrected typos in alert/event names in the "Microsoft: Azure HDInsight Cluster Configuration" Dynamic Application.
- Moved the list of supported services and health resources from the content library to the snippet code in the "Microsoft: Azure Location Discovery" Dynamic Application.
- Added the "Cloud.EventGrid" device category.
The following known issues affect version 118 of the Microsoft: Azure PowerPack:
- If there is a device under any Azure service that contains special characters, the device will display as an empty service container as devices with special characters will not be discovered. This will be addressed in an upcoming release.
- After upgrading to version 117, you may notice critical events for SQL database resources at the Azure root component level. This is expected and should disappear after a few polling cycles. If this does not resolve, contact ScienceLogic Support.
- If you encounter a 529 error, this is usually a temporary issue with the Microsoft API service.
- Some environments could experience an issue when installing the PowerPack in which the installation window will show that the PowerPack is still installing when the PowerPack has finished being installed. If this occurs, users can close the window and check the PowerPack version number in the PowerPack Manager page (System > Manage > PowerPacks) to confirm that installation has completed.
- The default metric System Availability requires an availability report every five minutes by default. However, the "Microsoft Azure: Virtual Machine Discovery" Dynamic Application runs every 15 minutes by default, which causes gaps in the data. To avoid seeing gaps in System Availability, reduce the default poll time for the Discovery Dynamic Application to five minutes.
- When discovering a large number of component devices, the discovery process can cause the appearance of numerous critical events with the message, "
Large backlog of asynchronous jobs detected". - The Dynamic Application "Microsoft: Azure Backup Policy Configuration" retrieves an additional parameter (HourlyLogBackup) that is not displayed in the Azure portal. The parameter does not contain a value. This issue is caused by a parameter being available in the Azure API but not in the Azure portal.
NOTE: This issue does not occur for Microsoft Azure Government subscribers.
- In Microsoft Azure, no count appears for Recovery Service Vault > Backup items > Azure Backup Server. This is a bug in the Azure API.
- The API for Microsoft Azure Government does not currently provide performance data for Azure Application Gateways. This is a bug in the Azure API.
- The API for Microsoft Azure Government does not currently support the following performance data for Azure SQL Databases: deadlock, dtu_consumption_percent, dtu_limit, dtu_used, log_write_percent, sessions_percent, storage, storage_percent, workers_percent, and xtp_storage_percent. This is a bug in the Azure API.
Workarounds
Version 103 fixed an issue where the Dynamic Application "Microsoft: Azure Virtual Machine Discovery" was not automatically assigning a device class to each discovered device.
As a result, if you are upgrading from a version of the PowerPack prior to version 103, after the upgrade you must either re-discover the Azure Virtual Machine devices that previously had no device class, or you must manually assign the device class "Microsoft | Azure Virtual Machine Service" to each of those devices.
To manually re-discover the Azure Virtual Machine devices that previously had no device class:
- Go to the Dynamic Applications Manager page (System > Manage > Applications).
- Find the Dynamic Application "Microsoft: Azure Virtual Machine Discovery" and select its checkbox.
- Click the field and choose DISCOVER Applications. Click the button.
To manually assign a device class to the Azure Virtual Machine devices, perform these steps on each device:
- Go to the Device Manager page (Registry > Devices > Device Manager).
- Find the device you want to edit and select its wrench icon (
). - In the Device Properties page, find the Device Class field and select the toolbox icon (
). - In the Select New Device Class modal page, select the device class that matches the Azure Virtual Machine in both size and type.
- The newly selected device class is now associated with the device.