MySQL Enterprise Monitor 4.0 Release Notes  /  Changes in MySQL Enterprise Monitor 4.0.2 (2017-12-05)

Changes in MySQL Enterprise Monitor 4.0.2 (2017-12-05)

Functionality Added or Changed

  • As of this release, on Solaris platforms, the installer and upgrade installer check for the presence of the Oracle Developer Studio 12.5 Runtime libraries. If these libraries are not installed, the installation stops and displays an error.

    Oracle Developer Studio 12.5 Runtime libraries must be installed before running the MySQL Enterprise Monitor installers on Solaris.

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

  • The OpenSSL libraries used by the MySQL Enterprise Monitor installers and MySQL Enterprise Monitor Aggregator have been upgraded to 1.0.2m.

Bugs Fixed

  • The service_manager privilege descriptions lacked examples. For more information, see MySQL Enterprise Monitor Repository. (Bug #27130180)

  • The documentation incorrectly stated that a Service Manager user required privileges on the mysql.inventory table. The mysql.inventory table is no longer created. (Bug #27130103)

  • It was not possible to edit the sparkline selection on the Overview. The drop-down list was empty. (Bug #27126595)

  • Under certain cirumstances, some group replication topologies, such as InnoDB clusters, did not load in the Topology. (Bug #27126443)

  • Some selections were not properly displayed in the Column drop-down menus on the Query Analyzer's Advanced filter. (Bug #27110602)

  • Long confirmation messages on the What's New page were not correctly formatted and overflowed the boundaries of the tooltip popup. (Bug #26941371)

  • The Advisors drop-down list on the Create Event Handler dialog was not displayed properly. It was not possible to scroll the list. (Bug #26870551)

  • It was not possible to delete or edit a notification group if the subject contained braces, { or }. An error was displayed.

    As of this release, it is possible to edit, and correct, notification group subjects which contain unsupported characters. Also, an error is displayed on saving if the notification group's subject contains an unsupported character. (Bug #25535520)

  • Data purge was not completed if the MySQL Enterprise Service Manager was restarted while the purge was running.

  • Sparkline graphs were not correctly displayed for cluster group selections on the Replication view.

  • Current Emergency & Critical Events displayed no data if All entries was selected. It was necessary to refresh the page manually.

  • The Current Emergency & Critical Events list was filtered by the current, active personal filter.