SL1: Concurrent PowerShell Monitoring PowerPack Release Notes version 102

Version 102 of the SL1: Concurrent PowerShell Monitoring PowerPack includes updates to event policies and Dynamic Applications.

  • Minimum Required SL1 Version: 10.1.4

Before You Install or Upgrade

Ensure that you are running version 10.1.4 or later of SL1 before installing "SL1: Concurrent PowerShell Monitoring" PowerPack version 102.

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

Installation or Upgrade Process

To install version 102 of the SL1: Concurrent PowerShell Monitoring PowerPack, perform the following steps:

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 install this 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 system to the 10.1.4 or later release.
  3. Download the "SL1: Concurrent PowerShell Monitoring" version 102PowerPack 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 "SL1: Concurrent PowerShell Monitoring" version 102.
  5. Click the Install button. For details on installing PowerPacks, see the chapter on Installing a PowerPack in the PowerPacks manual.

See the manual Monitoring Windows Systems with PowerShellfor instructions on using the PowerPack.

Features

This release includes the following features:

  • Two Dynamic Applications for monitoring the concurrent PowerShell service:
  • ScienceLogic: PowerShell Collector Performance. Collects Prometheus performance metrics from the service container
  • ScienceLogic: PowerShell Service Log Parser. Monitors the service log and raises major events on devices when errors are found containing device IDs

  • A device template to automatically align the "ScienceLogic: PowerShell Service Log Parser" Dynamic Application to multiple Data Collectors
  • Event policies and corresponding alerts that are triggered when devices meet certain status criteria

Enhancements and Issues Addressed

The following enhancements and addressed issues are included this release of the "SL1: Concurrent PowerShell Monitoring":

  • The "ScienceLogic: PowerShell Service No Route To Host" event policy has been disabled by default.
  • The "ScienceLogic: PowerShell Collector Performance" Dynamic Application was updated to support data collection using a PEM key.
  • The "ScienceLogic: PowerShell Service Log Parser" Dynamic Application was updated to address an issue in which unhandled exceptions were appearing when the credential type used was different from the required credential.

Known Issues

The following known issues affect version 102 of the SL1: Concurrent PowerShell Monitoring PowerPack:

  • The "ScienceLogic: PowerShell Collector Performance" and "ScienceLogic: PowerShell Service Log Parser" Dynamic Applications do not support data collection using PEM keys when a passphrase is used to encrypt the key.
  • The Dynamic Application "ScienceLogic: PowerShell Collector Performance" cannot connect over SSH to SL1 version 11.1.0 or later. If you are on SL1 version 11.1.0 or later, you will need to enable the Prometheus client on the Data Collector on which you want to enable multi-process mode. To do this, add the property ENABLE_PROMETHEUS_CLIENT=True to the /opt/em7/services/powershell_collector/powershell_collector.env file.
  • Once the Prometheus client is enabled, the URL HTTP[S}://localhost:8084/metrics is enabled (HTTP or HTTPS depending on the USE_HTTPS setting in the config file). Once the Prometheus client is enabled, restart the PowerShell collector using the sudo systemctl restart powershell_collector