Microsoft: Azure PowerPack Release Notes, version 119

Version 119 of the Microsoft: Azure PowerPack updated the PowerPackto be compatible with Python 3.

• Minimum Required SL1 Version: 11.3.0

Before You Install or Upgrade

Ensure that you are running version 11.3.0 or later of SL1 before installing "Microsoft: Azure" PowerPack version 119.

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:

1. Search for and download the PowerPack from the PowerPacks page (Product Downloads > PowerPacks & SyncPacks) at the ScienceLogic Support Site.
2. In SL1, go to the PowerPacks page (System > Manage > PowerPacks).
3. Click the Actions menu and choose Import PowerPack. The Import PowerPack modal appears.
4. Click Browse and navigate to the PowerPack file from step 1.
5. Select the PowerPack file and click Import. The PowerPack Installer modal displays a list of the PowerPack contents.
6. Click Install. 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:

1. Familiarize yourself with the Known Issues for this release.
2. 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.
3. Download this version of the PowerPack from the Support Site to a local computer.

4. 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].

5. Go to the PowerPack Manager page (System > Manage > PowerPacks). Click the Actions menu and choose Import PowerPack. Import the Version 119 of the Microsoft: Azure PowerPack. For details on importing PowerPacks, see the chapter on Installing a PowerPack in the PowerPacks manual.
6. Click the Install button. For details on installing PowerPacks, see the chapter on Installing a PowerPack in the PowerPacks manual.
7. 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.)
8. 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].

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 this release of the "Microsoft: Azure" PowerPack:

• Updated the PowerPack to be Python 3 compatible.
• Removed the metrics from collection objects and presentation objects and added them to meta.force_remove from the "Microsoft: Azure App Performance" Dynamic Application: 
  • App Connections
  • io Other Bytes Per Second
  • io Other Operations Per Second
  • Threads
  • Current Assemblies
  • Gen 0 Collections
  • Gen 1 Collections
  • Gen 2 Collections
  • Requests In Application Queue
  • Total App Domains
  • Total App Domains Unloaded
  • Handles
  • Private Bytes
• Removed the metrics from collection objects and presentation objects and added them to meta.force_remove from the "Microsoft: Azure Function App Performance" Dynamic Application: 
  • Threads
  • Current Assemblies
  • Gen 0 Collections
  • Gen 1 Collections
  • Gen 2 Collections
• Updated the maximum device limit from 10 to 30 on the "Microsoft: Azure Virtual Machine Configuration" Dynamic Application.
• The "Microsoft: Azure Virtual Network Gateway Discovery" Dynamic Application was updated to address a discovery issue.

Known Issues

The following known issues affect version 119 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, 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.