MySQL Enterprise Monitor 3.3 Release Notes  /  Changes in MySQL Enterprise Monitor 3.3.4 (2017-06-13)

Changes in MySQL Enterprise Monitor 3.3.4 (2017-06-13)

Functionality Added or Changed

  • The Replication Configuration advisor now generates an event if slave_pending_jobs_size_max or slave_max_allowed_packet are less than the source's max_allowed_packet. (Bug #25996472)

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

  • The super_read_only variable is now represented in the Replication dashboard's instance drilldowns. The configured value is displayed in the Replication Configuration section.

  • The backup bar charts, Backup Run Time History and Backup Lock Time History, are replaced by Full Backup Run Time History and Incremental Backup Run Time History timeseries graphs. The run and lock time information is now displayed in the full and incremental backup graphs.

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

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

  • An agent installer is now available for FreeBSD 11.

Bugs Fixed

  • The Statement Type drop-down list on the Query Analyzer page contained incorrectly named entries, formatted as form.label.statementType.option.NAME. (Bug #26132066)

  • A Null Pointer Exception was logged if the Average Statement Execution Time advisor was enabled but all its notice thresholds were disabled. (Bug #25872561)

  • The documentation erroneously stated that SSL certificates which existed in the previous installation must be manually imported after an upgrade.

    The upgrade creates a backup of any existing SSL certificates and imports them into the upgraded version as part of the upgrade process. (Bug #25833748)

  • MySQL Enterprise Service Manager stopped responding if a custom graph was imported, and the graph's definition included a hyphen (-) in the name.

    If a service restart was attempted, an Unexpected token error was logged and Tomcat would not start. (Bug #25761280)

  • MySQL Enterprise Monitor Agent and MySQL Enterprise Service Manager configuration utilities did not clearly state that they must be run while MySQL Enterprise Monitor Agent and MySQL Enterprise Service Manager are stopped.

    The documentation was also updated with this information. (Bug #25697013)

  • Network speeds were incorrectly reported on the Network Interfaces table of the MySQL Instances dashboard. (Bug #25636784)

  • The Query Analyzer's Explain Query tab did not display long queries correctly. As of this release, long keys are wrapped on multiple lines. (Bug #25517867)

  • OS X 10.12 Sierra was not recognized and was listed as Unknown. (Bug #25511036)

  • It MySQL Enterprise Monitor Agent encountered an error, it failed to restart due to a permissions issue. The mysql-monitor-agent.pid ran as root and could not be stopped by the agentrestart.sh which runs under the same user as MySQL Enterprise Monitor Agent.

    As of this release, the mysql-monitor-agent.pid is created with the permissions 644 (-rw-r--r--). (Bug #24667408)

  • On Windows platforms, it was not possible to install to a path which contained spaces on any drive other than the C:\ drive.

    For example, trying to install to D:\Program Files\MySQL\Enterprise\Monitor failed, while C:\Program Files\MySQL\Enterprise\Monitor succeeded. (Bug #24482872)

  • The MySQL Enterprise Monitor Agent was not properly displayed as running and monitoring an instance. This occurred if it was stopped and it's monitored instance removed from the MySQL Instances dashboard, and then the MySQL Enterprise Monitor Agent was restarted.

  • Empty groups were not displayed on the Advisors page.

  • It was not possible to edit a replication group's description. The change was not saved.

  • A number of minor UI issues were corrected in this release. Issues such as double colons (::) in the system uptime frame, duplicated icons on buttons, and so on.

  • If an instance was renamed on the MySQL Instances dashboard, the instance name was not updated immediately elsewhere in the user interface.

  • The backup bar charts, Backup Run Time History and Backup Lock Time History, displayed extra zeroes after an upgrade from MySQL Enterprise Service Manager 3.2 to 3.3 or 3.4.

  • Custom filters which were not edited were displayed as edited on the Query Analyzer and graphs pages.

  • Under certain circumstances, graphs would not load on the Backup dashboard's History tab.

  • After an upgrade from MySQL Enterprise Service Manager 3.1, or 3.2, to 3.3 or higher, the Backup dashboard's Backup Run Time History and Backup Lock Time History displayed zeroes for instances monitored since before the upgrade.

  • Under certain circumstances, if a overrides were defined on MySQL instances in an advisor, both the parent and child schedules were evaluated for the overridden instance, instead of child schedule only. As a result, duplicate collections were performed and incorrect events displayed.

  • The upgrade process prompted you to re-import SSL certificates from the backup of the previous version. This is not necessary unless you are using LDAP and had imported your own SSL certificates into the keystore of the JRE bundled with MySQL Enterprise Monitor.

    The prompt has been updated.

  • Under certain circumstances, a monitored MySQL instance could be reported as having two, different server_uuid values. This could happen if the monitored instance was part of a replication topology, or installed in a docker container, and used Host Plus Data Directory from the MySQL Instance Identity Source menu.

  • Microsoft Windows 2016 Server systems were reported as Unknown.