SL1 PowerFlow PowerPack Release Notes, version 107

The ScienceLogic: PowerFlow PowerPack version 107 adds new icons for device classes, migrates multiple Dynamic Applications to the Snippet Framework, and removes multiple items from the PowerPack.

  • Minimum Required SL1 Version: 11.3.0

Versions 105 and earlier of this PowerPack were named the ScienceLogic: Integration Service PowerPack.

Before You Install or Upgrade

Ensure that you are running version 11.3.0 or later of SL1 before installing "ScienceLogic: PowerFlow PowerPack" PowerPack version 107.

For details on upgrading SL1, see the relevant SL1 Platform Release Notes.

This PowerPack requires SL1 PowerFlow version 2.2.0 or later.

Installing or Upgrading the PowerPack

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.

If you are currently using the Dynamic Applications in this PowerPack to monitor devices, collection errors might occur for one or two polling cycles during the installation of a new version. To prevent collection errors during an upgrade, you can optionally disable collection for monitored devices before performing the following steps and re-enable collection after the upgrade.

If you are currently using the Dynamic Applications in this PowerPack to monitor devices, collection errors might occur for one or two polling cycles during the installation of a new version. To prevent collection errors during an upgrade, you can optionally disable collection for monitored devices before performing the following steps and re-enable collection after the upgrade.

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.

To upgrade to this version of the PowerPack:

  1. Familiarize yourself with the Known Issues for this release.
  2. See the Before You Install or Upgrade section. If you have not done so already, upgrade your SL1 system to version 11.3.0 or later, and upgrade your SL1PowerFlow system to version 2.2.0 or later.
  3. Download the "ScienceLogic: PowerFlow PowerPack" version 107 PowerPack from the Support Site to a local computer.
  4. Go to the PowerPack Manager page (System > Manage > PowerPacks). Click the Actions menu and choose Import PowerPack. When prompted, import "ScienceLogic: PowerFlow PowerPack" version 107.
  5. Click the Install button. For details on installing PowerPacks, see the chapter on Installing a PowerPack in the PowerPacks manual.
  6. Go to the Credential Management page (Manage > Credentials) and locate the "ScienceLogic: PowerFlow SSH" credential example. Duplicate the credential and then edit it to define the Name, Hostname/IP, Username, Password, and Private Key, if needed.
  7. On the Device Manager page (Devices > Device Manager), locate the PowerFlow Virtual Device, and click the Edit icon (). The Device Properties modal appears.
  8. On the Collections tab, click the Actions button and select Add Dynamic Application. The Dynamic Application modal appears.
  9. Select the "ScienceLogic: PowerFlow Healthcheck Configuration" Dynamic Application, select the previously saved PowerFlow SSH credential, and then click Save. The Dynamic Application is now aligned to the device.
  10. Click Save and close the Device Properties modal.

To disable collection for the old "REST: Performance Metrics Monitor", you can also choose Stop Collecting and Remove Data to cease the collection of historical data.

See the Monitoring SL1 PowerFlow manual for instructions on using the PowerPack.

Enhancements and Issues Addressed

The following enhancements and addressed issues are included in this release:

  • Added new device class icons.

  • Migrated the "ScienceLogic: PowerFlow Workers Configuration" Dynamic Application to the Snippet Framework.

  • Migrated the "ScienceLogic: PowerFlow Queue Configuration" Dynamic Application to the Snippet Framework.

  • Migrated the "ScienceLogic: PowerFlow Healthcheck Configuration" Dynamic Application to the Snippet Framework. As part of this migration, the following changes were made:

    • A new execution environment was created for this Dynamic Application, called "ScienceLogic: PowerFlow Environment SSH 107 (python3)".

    • The "Health" collection object was removed.

    • The pfctl command was added to all collection objects in the Dynamic Application.

Since all of the collection objects contain the call to the pfctl command, if for some reason you need to adjust the command, you must update it in all of them.

  • Removed the following items from the PowerPack:

    • Dashboards:

      • REST Discovery Initiation

    • Dashboard widgets:

      • REST Discovery Initiation

      • REST Discovery Log Widget

    • Run book action policies:

      • REST Discovery: Phase 0 - Device Creation

      • REST Discovery: Phase I - Collection Test Lookup

      • REST Discovery: Phase II Credential Check

      • REST Discovery: Phase III - Apply template

    • Run book automation policies:

      • REST Discovery - Application Alignment

      • REST Discovery - Device Creation

    • Execution environments:

      • silo_rba_discovery

      • silo_logs

    • Event policies:

      • REST Device Discovery

    • Dynamic Applications:

      • REST: Performance Metrics Monitor

      • REST: Performance Metrics Monitor (PowerFlow)

ScienceLogic recommends disabling or deleting both of these Dynamic Applications. They no longer function now that the PowerPack has been upgraded to use the Snippet Framework.

To view the latest manuals for the SL1 PowerFlow Platform, see the SL1 PowerFlow page. To view the latest release notes for PowerFlow, see SL1 PowerFlow Release Notes.

Known Issues

This PowerPack has the following known issues:

  • This pfctl command with --json might take a long time to return an output when collecting data with the "ScienceLogic: PowerFlow Healthcheck Configuration" Dynamic Application. If you do not see data collected, change the timeout settings in the SSH credentials to more than 30 seconds.
  • The "ScienceLogic: PowerFlow Healthcheck Configuration" Dynamic Application will not be able to collect data if the "Data Collection: SSH Collector" process has the "Operating State" set to "Enabled" instead of "Disabled".
  • The Active Queues Group of the "ScienceLogic: PowerFlow Workers Configuration" Report displays records that appear to be duplicates because the records do not have unique identifiers.
  • The Error message that indicates the reason for failure on the "ScienceLogic: PowerFlow Healthcheck Configuration" Dynamic Application gets truncated if the message is more than 128 characters. The same happens for Information messages if the text cannot fit on a single row.
  • In the "ScienceLogic: PowerFlow Healthcheck Configuration" Dynamic Application, the Information message of the get cb cluster status Healthcheck lacks proper formatting for extra characters.
  • The "ScienceLogic: PowerFlow Workers Configuration" Report shows "message" as Workers name and "Unauthorized" as Workers status in Workers Group when 401 status is displayed as status code for Application endpoint.
  • The "ScienceLogic: PowerFlow Healthcheck OK" Event Policy displays a message that includes an "\n" character because the "ScienceLogic: PowerFlow Healthcheck Configuration" report is not applying the proper format before triggering the event.