MySQL PowerPack Release Notes version 101

Version 101 of the MySQL PowerPack includes security updates and a discovery enhancement to a Dynamic Application.

  • Minimum Required SL1 Version: 8.14.0

Before You Install or Upgrade

Ensure that you are running version 8.14.0 or later of SL1 before installing "MySQL" PowerPack version 101.

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

Installation and Upgrade Process

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 local changes for some commonly customized fields from being overwritten.

If you are currently using the Dynamic Applications in the 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.

Features

This release includes the following features:

  • Dynamic Applications to discover, model, and monitor performance metrics and collect configuration data for MySQL servers and instances.
  • Execution environments to process data and commands for MySQL.

Enhancements and Issues Addressed

The following enhancements are included in the PowerPack:

  • Addressed an issue in which the MySQL: Discovery Dynamic Application did not return results. To discover a MySQL instance with one port, users must specify the "Range" header as "Range:<port_begin>-<port_end>". Meaning, "port_begin" and "port_end" must be the same port. For example, "Range:7706-7706".
  • Added a new execution environment, "My SQL EE", to work with all Dynamic Applications and Run Book Actions in the PowerPack.
  • Snippet logging was updated in the PowerPack to improve security.

  • Addressed an issue in which non-MySQL devices logged the following error: "Credential does not have header: Service: MySQL". Errors will no longer be logged for non-MySQL devices.

Known Issues

The following known issues affect version 101 of the MySQL PowerPack:

  • Version 101 of the MySQL PowerPack does not support error logs from MySQL on a Docker container.
  • The MySQL PowerPack only parses errors (and not warnings) from the files set by the variable log_error. If it is set, it does not parse from stderr
  • Users need to have permission to read the MySQL error log file on Linux servers. To enable this, execute the following command:

sudo usermod -a -G mysql <ssh user>

  • The MySQL PowerPack is not supported on Military Unique Deployment (MUD) systems.
  • The caching_sha2_password plugin is not supported in MySQL 8. Users should use mysql_native_password.