It is not possible to upgrade to MySQL Enterprise Monitor 8.0 from versions preceding MySQL Enterprise Monitor 3.3. To upgrade an older version, it is recommended you first upgrade to MySQL Enterprise Monitor 4.0 before running the MySQL Enterprise Monitor 8.0 upgrade process.
MySQL Enterprise Service Manager 8.0's bundled repository is MySQL Server 5.7.22.
MySQL Enterprise Service Manager supports monitoring of MySQL 8.Important
Due to password plugin changes in the server, only MEM 8.0 and later support monitoring MySQL 8.0.11, or higher.Note
If you intend to use MySQL 8 as an external repository, the installer no longer checks for
innodb_locks_unsafe_for_binlogas they are deprecated in MySQL 8.
For more information, see Prerequisites.
Several system and status variables used by the MySQL Enterprise Service Manager's advisors were deprecated in MySQL 8. As such, some advisors do not evaluate for MySQL 8. Instead of presenting advice, as they do for earlier versions of MySQL, a warning is displayed, advising you that the advisor does not evaluate against MySQL 8, or higher.
The following advisors do not evaluate for MySQL 8:
InnoDB Not Using Newest File Format
Insecure Password Authentication Option is Enabled
Next-Key Locking Disabled For InnoDB But Binary Logging Enabled
Warnings Not Being Logged
Query Cache Has Sub-Optimal Hit Rate
Query Cache Is Excessively Fragmented
Query Cache Potentially Undersized
The InnoDB Undo Logs graph is not displayed for MySQL 8 instances.
For more information on the variables added and removed in this release, see Server and Status Variables and Options Added, Deprecated, or Removed in MySQL 8.0. (Bug #25877130)
System variables introduced in MySQL 8 are available in MySQL Enterprise Monitor views such as the per-instance drilldown on the MySQL instance dashboard. For more information on the variables added and removed in this release, see Server and Status Variables and Options Added, Deprecated, or Removed in MySQL 8.0.
The MySQL server, bundled with MySQL Enterprise Service Manager, has been upgraded to MySQL 5.7.22.
Memory Usage report enables you to view how memory is allocated within the MySQL Instance.
For more information, see Memory Usage Report.
Query Analyzer Statement Details view is updated in this release.
For more information, see Detailed Query Information.
The documentation did not clearly state that the GUI-based advisors could not be copied as the basis for custom advisors. Only expression-based advisors can be copied in this manner. (Bug #27731494)
The Time Span and Graph From: labels did not display multibyte characters correctly. The character codes were displayed instead of the characters themselves. (Bug #27695440)
The Zoom links on the Query Analyzer page did not alter the graph time range. (Bug #27410942)
The columns of the Current Emergency & Critical Events list, on the Overview page, contained chevrons, indicating it was possible to sort the events. It is not possible to sort the events of this list, the emergency events are always listed first, and the list is sorted by Current and Time. (Bug #27011755, Bug #27720503)
Retrieving Query Analyzer data for the Statement details report resulted in resource-intensive index scans on the
As part of the Query Analyzer performance improvements in MySQL Enterprise Monitor 8.0, this index scan is no longer performed. (Bug #17731793)
On Windows platforms, the agent service description contained an incorrect version number.
The emailed links were incorrect for events generated by the SQL Statement Generates Warnings or Errors and Average Statement Execution Time Advisor advisors.
It was not possible to edit any notification groups other than the first 10 displayed. The remaining groups were displayed as inactive.
The link to the Settings page, in the Important Product-Related Announcements section of the What's New page, did not link to the Settings page.