Version 102 of the MySQL PowerPack includes a new sample credential and updates to Dynamic Applications and Device Categories.
-
Minimum Required SL1 Version: 10.1.0
Before You Install or Upgrade
Ensure that you are running version 10.1.0 or later of SL1 before installing "MySQL" PowerPack version 102.
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.
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:
- Search for and download the PowerPack from the PowerPacks page (Product Downloads > PowerPacks & SyncPacks) at the ScienceLogic Support Site.
- In SL1, go to the PowerPacks page (System > Manage > PowerPacks).
- Click the Actions menu and choose Import PowerPack. The Import PowerPack modal appears.
- Click PowerPack file from step 1. and navigate to the
- Select the PowerPack file and click . The PowerPack Installer modal displays a list of the PowerPack contents.
- Click PowerPack is added to the PowerPack Manager page. . The
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 and addressed issues are included this release of the "MySQL":
- The "silo_apps" content library was updated to version 3.1.4.
- The "MySQL EE v1.0" execution environment was added to the PowerPack.
- The "MySQL Example Credential SSL" example credential was added to the PowerPack to support loading SSL certificates on the database connection. (Support Case: 00203146; JIRA ID: SOL-15582)
- The "Database.Application" Device Category has been applied to the "MySQL Server" Device Class.
- The "Database.Instance" Device Category has been applied to the "MySQL Instance" Device Class.
- The "Slow Queries Rate" presentation object was added to the "MySQL: Instance Overall Performance" Dynamic Application.
- The "Slow Queries" collection object was added to the "MySQL: Instance Overall Performance" Dynamic Application.
- The following collection objects were added to the "MySQL: Instance Configuration" Dynamic Application:
- Long Query Time
- Query Not Using Indexes
- Slow Admin Statements
To collect these metrics, your MySQL slow query log needs to be turned on.
- The following collection objects were added to the "MySQL: Instance InnoDB Buffer Pool Performance" Dynamic Application:
- Log Waits
- Log Wait Rate
- Log Write Requests
- The "Table Locks Immediate Rate" collection object was added to the "MySQL: Instance Table Locking Performance" Dynamic Application.
- The following Dynamic Applications were updated to have Collector Affinity set to Root device collector by default:
- MySQL: Discovery
- MySQL: Instance Configuration
- MySQL: Instance Discovery
- MySQL: Linux Instance Error Log Configuration
- MySQL: Windows Instance Error Log Configuration
- The following Dynamic Applications were updated to have Collector Affinity set to Assigned collector by default:
- MySQL: Events Errors Summary Configuration
- MySQL: Instance Commands Performance
- 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 Performance Schema Statements Configuration
- MySQL: Performance Schema Summary Statement Configuration
- MySQL: Process List Configuration
- MySQL: Statements With Error/Warning Configuration
- The SQL Log Reader for PowerShell systems was updated to validate query results before checking for errors.
- An issue was addressed in the "MySQL: Discovery" Dynamic Application in which it was not discovering MySQL instances on slow Windows systems. Support was added to use the Timeout field in the SOAP/XML credential to address this issue. (Support Case: 00239606; JIRA ID: SOL-18318)
Known Issues
The following known issues affect version 102 of the MySQL PowerPack:
- When the server log level variable (log_error verbosity on MySQL, log_warnings on MariaDB) is set to information on a monitored device, a "Got Packets out of order" message may appear in some entries every 15 minutes.
- Version 102 of the MySQL PowerPack does not support error logs from MySQL on a Docker container.
- The MySQLPowerPack only parses errors (and not warnings) from the files set by the variable
log_error
. If it is set, it does not parse fromstderr
- 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 MySQLPowerPack is not supported on Military Unique Deployment (MUD) systems.
- The
caching_sha2_password
plugin is not supported in MySQL 8. Users should usemysql_native_password
.