MySQL Enterprise Monitor 3.3 Release Notes

11 Changes in MySQL Enterprise Monitor 3.3.0 (2016-09-15)

Functionality Added or Changed

  • Important Change: As of this release, it is not possible to use MySQL Server 5.1 or 5.5 as the MySQL Enterprise Monitor repository. The installer displays an error and the installation process stops.

  • Important Change: The Enterprise Backup dashboard is introduced in this release. This dashboard enables monitoring of Full, Incremental, TTS, and Partial backups performed by MySQL Enterprise Backup on the monitored instances.

    For more information, see Enterprise Backup Dashboard

  • The event status is now included in the body of the notification mail. (Bug #24311586)

  • The Warnings Not Being Logged advisor text was updated.

  • The Tomcat server, bundled with the MySQL Enterprise Service Manager, has been upgraded to 8.0.33.

  • Named filters are introduced in this release. Named filters make it possible to create and save filters on the following pages:

    • MySQL Instances

    • Events

    • Query Analyzer

    • All Timeseries Graphs

    • Advisors

    A number of default named filters have been added in this release. See System and User-defined Filters for more information.


    Existing default filters are migrated by the upgrade process and are renamed to User Default.

  • The MySQL server, bundled with the MySQL Enterprise Service Manager, has been upgraded to MySQL 5.7.15.


    If you are upgrading from a previous version, the upgrade installer will handle the upgrade of your existing repository to the new version. All previous versions of MySQL Enterprise Service Manager used MySQL 5.6.x, which must be upgraded to 5.7.15, the version delivered with this release. This only applies to installations using the bundled MySQL Server. If you are using an external MySQL Server as the repository, you must upgrade it manually to at least 5.6.15 before running the MySQL Enterprise Service Manager upgrade installer. MySQL 5.7.15 is the recommended version.

    As of this release, the MySQL Enterprise Service Manager installer and upgrade installer raise an error if an attempt is made to configure MySQL Enterprise Service Manager to use an unsupported MySQL version for the repository.

Bugs Fixed

  • The documentation did not specify the correct format for the ssl-ca-keystore-path parameter. It was listed as a file path, but is a URL. For example:

    ssl-ca-keystore-path=file:///mysql/enterprise/agent/etc/mykeystore (Bug #24386496)

  • Attempting to monitor a group replication topology caused all replication topology discovery to fail. (Bug #24376827)

  • The InnoDB Redo Log Pending Writes graph was not displayed for MySQL 5.7 instances. (Bug #23563358)

  • LDAP configuration was not validated when saved. As a result, if the LDAP connection information was incorrectly configured, NullPointerExceptions were logged, and it was not possible to connect to the LDAP server. (Bug #23299288)

  • The certificate to keystore upgrade process attempted to use the system's openSSL installation instead of that delivered with the installer. As a result, if openSSL was not installed on the system, the upgrade failed. As of this release, the upgrade only uses the openSSL libraries delivered with the installer. (Bug #22522309)

  • The MySQL Enterprise Service Manager utility returned a stack trace for unsupported commands, instead of redirecting the user to the help.

  • Custom agent service names were not maintained by the agent upgrade process. The custom name was overwritten by the default agent service name, MySQLEnterpriseMonitorAgent.

  • A NullPointerException was logged for replication monitoring. This exception did not affect the performance of replication monitoring.

  • The advice page generated by the MySQL Enterprise Backup Health advisor contained broken links to the InnoDB chapters of the MySQL Reference Manual. It also incorrectly referred to the --start-lsn option as the --lsn option.

  • The Overview page elements did not resize properly if the browser window was resized.

  • On certain browser versions, the symbol << was transformed to Â<<.

  • Replication filter information was not collected. As a result, the replica's Filter/Delay Status frame of the Source Replication Status was not correctly populated.