MySQL Lists are EOL. Please join:

List:Announcements« Previous MessageNext Message »
From:andy bang Date:September 22 2017 8:50pm
Subject:MySQL Enterprise Monitor 3.4.3 has been released
View as plain text  
We are pleased to announce that MySQL Enterprise Monitor 3.4.3 is now
available for download on the My Oracle Support (MOS) web site.  It
will also be available for download via the Oracle Software Delivery
Cloud in a few days.  MySQL Enterprise Monitor is the best-in-class
tool for monitoring and management of your MySQL assets and is
included with your MySQL Enterprise Edition and MySQL Cluster
Carrier Grade Edition subscriptions.

You’ll find information about what’s new here:
   (also included at the end of this note for convenience)

Highlights of MySQL Enterprise Monitor 3.4 include:

* The Replication Dashboard is extended to provide monitoring support
   for Group Replication, which was introduced in MySQL Server 5.7.17.
   The Topology view provides a visual representation of your group
   replication topologies, and the Status drill downs are updated with
   Group Replication-specific information. The status of the entire
   group is reported on, also showing node failure tolerances and
   whether Group Replication has quorum.

* New Group Replication Configuration and Group Replication Status
   Advisors provide continuous analysis of the condition of your group
   replication topologies. The Configuration Advisor checks for
   misconfigurations which could lead to unstable or insecure
   installations; the Status Advisor continuously monitors for servers
   which go offline or fall out of sync with the other members of the

* The new Table Statistics report utilizes sys schema and its
   schema_table_statistics view to show detailed table statistics in
   both table and treemap forms. Available on MySQL 5.6 and above,
   report details include total latencies, total number of rows
   deleted, total I/O write requests.

* In general, the user interface page-loading times and page
   responsiveness are improved in 3.4. In addition, time series graphs
   are much faster in this release, particularly when you specify a
   long time period. This graph performance improvement is gained by
   continuous aggregation of time series data. If you are updating from
   an earlier version, a one-time aggregation of your historic time
   series data is performed when you first start the Service Manager
   (as shown by a progress indicator next to the System Status


You will find binaries for the new release on My Oracle Support:

Choose the "Patches & Updates" tab, and then choose the "Product or
Family (Advanced Search)" side tab in the "Patch Search" portlet.

You will also find the binaries on the Oracle Software Delivery Cloud

Search "All Categories" for "MySQL" and choose from the results
accordingly.  You will find the Enterprise Monitor along with other
MySQL products.

If you are not a MySQL Enterprise customer and want to try the Monitor
and Query Analyzer using our 30-day free customer trial, go to, or contact Sales at

Please open a bug or a ticket on My Oracle Support to report problems,
request features, or give us general feedback about how this release
meets your needs.

Useful URLs

* My Oracle Support -
* What's New in 3.4 -
* Change log -
* Installation documentation -
* Complete documentation -
* Product information -
* Download - (available now) or

Thanks and Happy Monitoring!

- The MySQL Enterprise Tools Development Team


Changes in MySQL Enterprise Monitor 3.4.3

Functionality Added or Changed

* It is now possible to specify an exclusion list of users with
   database-level privileges on all databases in the mysql.user table.
   This is done using a regular expression in the MySQL User Account
   advisor. An event is generated for any user which does not match the
   defined expression.

   For more information, see MySQL User Account 

   Note: This change replaces the Non-root User Has DB, Table, Or Index
   Privileges On All Databases advisor, and moves its functionality to
   the MySQL User Account advisor. If you changed the scheduling or
   thresholds on the Non-root User Has DB, Table, Or Index Privileges
   On All Databases advisor, the changes will be lost after upgrading
   to this version.

   (Bug #26260456, Bug #11748288, Bug #25696565)

   References: See also: Bug #17742263, Bug #26130781.

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

   Important: Changes have been made to the prerequisites of MySQL

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

* --mysql_ssl is no longer required by the MySQL Enterprise Service
   Manager installer and has been removed.

* Data Purge settings have been added for aggregated data. For more
   information, see Data Purge Behavior.

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

   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 
     to 755 for this directory.

   (Bug #26551166)

* Sparkline graphs did not refresh dynamically.

* The Group Replication advisor, when expanded, listed MySQL instances
   which were not involved in Group Replication.

* Under certain circumstances, if the server hosting MySQL Enterprise
   Service Manager was restarted, MySQL Enterprise Service Manager
   failed to restart, logging the following error: Error creating bean
   with name 'groupReplicationMembership'.

* The Add a new graph drop-down menu was not displayed on the Overview

* It was not possible to open a selected range of a timeseries graph
   in the Query Analyzer. The Query Analysis link did not behave as

* An error was displayed when selecting the Table Statistics report:
   Unable to generate SYS Schema report for selected MySQL Server.

   As of this release, the agent's Admin, General, and Limited users
   are granted the EXECUTE privilege.

   Important: If you defined these users manually, you must grant them
   the EXECUTE privilege.

   For more information, see Creating MySQL User Accounts for the
   Monitor Agent.

* The Data Purge Behavior drop-down menus displayed Never if the
   first-time setup was performed using the configuration utility, and
   the purge values set to any value not divisible by 7.

   The values were correctly defined, this was a display issue, only.

* Graphs were not included in the Support Diagnostics report.

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

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

* 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.
MySQL Enterprise Monitor 3.4.3 has been releasedandy bang22 Sep