MySQL Enterprise Monitor 3.3 Release Notes

2 Changes in MySQL Enterprise Monitor 3.3.9 (2018-04-26)


It is not possible to monitor MySQL 8 with this version of MySQL Enterprise Monitor, nor is it possible to configure this version of MySQL Enterprise Monitor to use MySQL 8 as its repository. To monitor MySQL 8, you must use MySQL Enterprise Monitor 8.0.

Functionality Added or Changed

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

  • The bundled JRE was updated to 1.8.0_172 for both the Agent and Service Manager.

Bugs Fixed

  • The MySQL Enterprise Service Manager always used the default data purge values, regardless of what values were specified. (Bug #27869486)

  • MySQL Enterprise Monitor Agent parsed all name=value pairs, even if they were inside comments, or outside legal config sections in a Cluster config.ini.

    As of this release, only configuration values in legally defined sections are parsed. (Bug #27844552)

  • The Query Analyzer's Configure Query Analyzer link did not link to the Query Analyzer advisors. (Bug #27844552)

  • 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 Last Seen column of the Unreachable Agents did not sort by date.

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