Docker PowerPack Release Notes, version 105

Version 105 of the Docker PowerPack includes updates to several Dynamic Applications and Run Book Actions, as well a more robust discovery process.

  • Minimum Required SL1 Version: 8.7.1.2

Before You Install or Upgrade

Ensure that you are running version 8.7.1.2 or later of SL1 before installing "Docker" PowerPack version 105.

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

You must also enable the Docker API. For instructions, see the Monitoring Docker manual.

Installation or Upgrade Process

To install version 105 of the Docker 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 8.7.1.2 or later release.
  3. Download the "Docker" version 105PowerPack 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 "Docker" version 105.
  5. Click the Install button. For details on installing PowerPacks, see the chapter on Installing a PowerPack in the PowerPacks manual.

Features

This release includes the following features:

  • Dynamic Applications that discover and collect data from Docker component devices

  • Device Classes for each type of Docker component device monitored
  • Event policies that are triggered when Docker devices meet certain status criteria
  • Run Book Actions and Policies that automate some aspects of the device discovery and creation process
  • An example Basic/Snippet Credential and an example SSH/Key Credential for discovering Docker devices
  • Device Dashboards that display information about Docker component devices

Enhancements and Issues Addressed

The following enhancements and addressed issues are included this release of the "Docker":

  • The discovery process was updated so that if the Run Book Action that triggers device creation fails to run for any reason, the system will attempt to run it again up to five additional times. This increases the likelihood of the system automatically discovering the device and aligning it with the proper Device Class.
  • The Run Book Action policies included in the PowerPack were updated to work with any database credential, rather than with only the EM7 DB credential.
  • The "Docker: Swarm Performance" Dynamic Application was updated to generate a critical alert when the number of running containers is 0 and the number of Replicas is greater than 0, and to generate a minor alert when the number of running containers is less than the number of Replicas but greater than 1.
  • The "Docker: Container Configuration" Dynamic Application was updated to collect and display the labels associated with a Docker container.
  • The "Docker: Container Performance" Dynamic Application was updated to change the "Memory Usage" collection object from a counter type object to a gauge type.
  • The "Docker: Image Performance" Dynamic Application was updated to use RepoTags to determine the image name if the RepoDigest value is Null.
  • The "Docker Host" Device Class Weight setting was updated to "4" to ensure that the Run Book Action that triggers device class realignment runs successfully.

Users can create a new Device Class, but should be aware that any value under or equal to "4" will not be classified as a Docker Host. Only values above "4" will be classified as Docker Hosts.

  • The silo_docker ScienceLogic library was repackaged as a Python package.
  • An issue was addressed that was causing Dynamic Applications to log passwords in plain text when run in debug mode. (Support ID: 178727)
  • An issue was addressed that was causing some alerts to not be processed properly due to a label in the event message not being collected.
  • An issue was addressed that was causing errors relating to objects not having an _api attribute to appear in the device and system logs.

Known Issues

This release has no known issues.