MySQL Enterprise Monitor 3.3 Release Notes

6 Changes in MySQL Enterprise Monitor 3.3.5 (2017-09-22)

Functionality Added or Changed

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

  • As of this release, if you are using a MySQL Server repository other than the installation bundled with the MySQL Enterprise Service Manager installation, the installer checks the MySQL Server for the following, minimum requirements:

    • MySQL Server version: versions older then MySQL 5.7.9 are not supported.

    • SSL: SSL must be enabled on the MySQL Server.

    • innodb_file_format: innodb_file_format must be barracuda.

    • innodb_file_per_table: innodb_file_per_table must be enabled.

    If any of those checks fail, the installer displays an error and cannot proceed until the configuration is corrected.

    The upgrade process performs the same checks.

    To check your repository is correctly configured, the MySQL Enterprise Service Manager's configuration utility is extended with the parameter --mysql-check-requirements.

    For more information, see Service Manager Configuration Utilities.

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


    Changes have been made to the prerequisites of MySQL 5.7.19.

    • must be present on Linux platforms. The MySQL Enterprise Service Manager full and upgrade installers check for the existence of this library.

    • During a MySQL Enterprise Service Manager upgrade, the upgrade installer runs the mysql_upgrade utility.

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

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

Bugs Fixed

  • On the Advisors page, filtering for specific advisors did not return all the advisors filtered for. (Bug #26668301)

  • On Linux, Unix, and Mac OS X platforms, the agent installer did not check the installation directory to ensure it had the required permissions to install MySQL Enterprise Monitor Agent in that location.

    As of this release, the installer checks the directory for the appropriate permissions. If it does not have the rights to install to that location, it returns the following error message:

    There has been an error.
    The current installation directory could not be accessed by non-root users.
    Please select a different installation directory or change the permissions
    to 755 for this directory.

    (Bug #26551166)

  • Under certain circumstances, such as filtering on many graphs on the All Timeseries page, the resulting graphs were not correctly populated with data. This was caused by the default value for the maxHttpHeaderSize in the Tomcat configuration file, server.xml, which is set too low for large quantities of data. The value is set to 32K by default.

    As of this release, the value of maxHttpHeaderSize is doubled, to 64K, and applied to both the SSL and non-SSL connector configurations in server.xml.

    If you are upgrading to this version from a previous version, you must edit server.xml and add maxHttpHeaderSize="65536" to each of the default connectors.

    If you are performing a clean installation of MySQL Enterprise Service Manager, you do not need to edit any files, the new values are included by default. (Bug #26391094)

  • It was not possible to install the MySQL Enterprise Service Manager on Solaris due to a missing file, (Bug #26336679)

  • Validation messages were not displayed on the Settings page after a successful change was made.

  • Sparkline graphs did not refresh dynamically.

  • It was not possible to edit multiple advisors using the Edit Selected button.

  • Agent host names were not displayed in the list of agents on the Advisors page, only the alphanumeric agent ID was displayed in truncated form. This made it difficult to identify the agent.

    As of this release, the agent is listed with the name of the host on which it is installed, instead of the alphanumeric ID.

  • Clicking on the Database Availability graph, on the Overview dashboard, opened a blank page instead of the Events page.

  • On Mac OS X platforms, the java_home_dir variable was not set properly by the installer. As a result, the configuration report contained the following error: ***unknown variable java_home_dir.

  • On Linux, Unix, and Mac OS X platforms, the MySQL Enterprise Service Manager upgrade installer could not upgrade the installation if the installation directory contained files or directories created by a different user, or a user with permissions which differed from those of the user running the upgrade.

    As of this release, the installers check the installation directory to ensure all files and directories have the correct permissions. If they do not, it exits with an informative error message.

  • Under certain circumstances, it was not possible to monitor an instance which had previously been monitored and then deleted by MySQL Enterprise Service Manager.