MySQL PowerPack Release Notes version 100

Version 100 of the MySQL PowerPack monitors MySQL configuration and performance metrics.

  • Minimum Required SL1 Version: 8.8.0

NOTE: Version 100 of the PowerPack does not monitor MySQL clusters.

NOTE: Version 100 of the PowerPack is not supported on Military Unique Deployment (MUD) systems.

Before You Install or Upgrade

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

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, including:
  • MySQL: Discovery
  • MySQL: Events Errors Summary Configuration
  • MySQL: Instance Commands Performance
  • MySQL: Instance Configuration
  • MySQL: Instance Discovery
  • MySQL: Instance Handler Performance
  • MySQL: Instance InnoDB Buffer Pool Performance
  • MySQL: Instance InnoDB Configuration
  • MySQL: Instance InnoDB Data Performance
  • MySQL: Instance InnoDB Row Performance
  • MySQL: Instance Overall Performance
  • MySQL: Instance Sort and Select Performance
  • MySQL: Instance Table Locking Performance
  • MySQL: Instance Threads and Connections Performance
  • MySQL: Linux Instance Error Log Configuration
  • MySQL: Performance Schema Statements Configuration
  • MySQL: Performance Schema Summary Statement Configuration
  • MySQL: Process List Configuration
  • MySQL: Statements With Error/Warning Configuration
  • MySQL: Windows Interface Error Log Configuration
  • Device Classes for MySQL Servers and MySQL instances
  • A sample credential for discovering MySQL servers
  • Event Policies and corresponding alerts that are triggered when MySQL servers and instances meet certain status criteria
  • A Device Dashboard for viewing data about MySQL instances

Known Issues

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

  • Version 100 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.