SL1 PowerFlow PowerPack Release Notes, version 106

The ScienceLogic: PowerFlow PowerPack version 106 includes a new "ScienceLogic: PowerFlow Healthcheck Configuration" Dynamic Application that works with the powerflowcontrol (pfctl) command-line utility to run healthcheck actions on a cluster. Also, an SL1 Event generated by this PowerPack now includes the isapp integration ID for the failed run of an application in SL1 PowerFlow.

  • Minimum Required SL1 Version: 10.2.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 10.2.0 or later of SL1 before installing "ScienceLogic: PowerFlow PowerPack" PowerPack version 106.

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 10.2.0 or later, and upgrade your SL1PowerFlow system to version 2.2.0 or later.
  3. Download the "ScienceLogic: PowerFlow PowerPack" version 106 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 106.
  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 the Actions button and select Add Dynamic Application.
  11. Select the "REST: Performance Metrics Monitor (PowerFlow)" Dynamic Application, select the existing PowerFlow SOAP/XML credential, and then click Save.
  12. Click Save and close the Device Properties modal.

To avoid having gaps for the new "REST: Performance Metrics Monitor (PowerFlow)" report, disable the collection for the old "REST: Performance Metrics Monitor" Dynamic Application. This allows only the new Dynamic Application to collect data.

To disable the collection for the old Dynamic Application:

  1. On the Device Manager page (Devices > Device Manager), locate the PowerFlow Virtual Device, and click the Edit icon (). The Device Properties modal appears.
  2. On the Collections tab, select the old "REST: Performance Metrics Monitor" Dynamic Application and select Disable All Collection Objects from the menu at the bottom.
  3. Click Go.

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.

Features Included in this Release

The following features were included in ScienceLogic: PowerFlow PowerPack version 106:

  • Added the "ScienceLogic: PowerFlow Healthcheck Configuration" Dynamic Application, which works with the powerflowcontrol (pfctl) command-line utility to run healthcheck actions on a cluster. This Dynamic Application runs every six hours by default, and it does not work for a single-node PowerFlow system. Users can disable this Dynamic Application on single-node PowerFlow systems if it was aligned through a template.

    Before you can use this Dynamic Application, you must add credential information to a /tmp/creds.yaml file in the node that is running the Dynamic Application. For more information, see "Configuring the ScienceLogic: PowerFlow Healthcheck Configuration Dynamic Application" topic in the Monitoring SL1 PowerFlow manual.
    manual.

  • The "ScienceLogic: PowerFlow Healthcheck Configuration" Dynamic Application includes three Event Policies that generate a Major, Notice, and Healthy event.
  • Updated Collector Affinity to use the "Assigned Collector" for each PowerFlow Dynamic Application.
  • Added the new "REST: Performance Metrics Monitor (PowerFlow)" Dynamic Application to measure only the REST API metrics between the SL1 collector and the PowerFlowPowerPack. This Dynamic Application does not collect the metrics of PowerFlow itself.

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.

Enhancements and Issues Addressed

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

  • Updated the alert configuration for the "ScienceLogic: PowerFlow Queue Configuration" Dynamic Application so that the log message includes the Application ID (isapp) when an application fails to run in PowerFlow.
  • Enhanced updates to the " ScienceLogic: PowerFlow Application has failed" Event Message for the "PowerFlow Queue Configuration" Dynamic Application to include the exception related to the failure.
  • Renamed all content in the PowerFlow PowerPack to include "ScienceLogic: PowerFlow".
  • Added the "silo_ssh" and "silo_ssh_requests" content libraries and updated the "silo_apps", "silo_core", and "sil_core_rest" content libraries. Removed the "silo_rba_discovery" and "silo_logs" content libraries.
  • Added a new Execution Environment called "ScienceLogic: PowerFlow Environment 1.6" to use with the included Dynamic Applications.
  • Updated the ScienceLogic PowerFlow device template to use the "REST: Performance Metrics Monitor (PowerFlow)" Dynamic Application instead of the "REST: Performance Metrics Monitor" Dynamic Application. In addition, the new "ScienceLogic: PowerFlow Healthcheck Configuration" Dynamic Application and the corresponding ScienceLogic PowerFlow SSH credential example was included in the template for device alignment.
  • Updated the "ScienceLogic: PowerFlow Example" SOAP/XML credential to remove spaces between the HTTP Header name and its value.
  • Content issues and other inconsistencies, including incorrect copyright dates, have been corrected in this PowerPack version.

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 SOAP ScienceLogic: PowerFlow REST Credential Tester displays "Failed" status and cannot collect data even when the credential is able to communicate with the device and is collecting data for some collection objects.
  • 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.