MySQL Enterprise Monitor 3.4.0 GA has been released

We are very happy to announce the general availability of MySQL
Enterprise Monitor, Version 3.4. 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 Enterprise
Carrier Grade subscriptions.

You’ll find information about what’s new here:

   http://dev.mysql.com/doc/relnotes/mysql-monitor/3.4/en/news-3-4-0.html
   (also included at the end of this note for convenience)

Highlights

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

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

Download

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

   https://support.oracle.com

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
soon:

   http://edelivery.oracle.com/

Choose "MySQL Database" as the Product Pack and 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
http://www.mysql.com/trials, or contact Sales at
http://www.mysql.com/about/contact.

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 - http://support.oracle.com/
* What's New in 3.4 - 
https://dev.mysql.com/doc/mysql-monitor/3.4/en/mem-comparison-3-4.html
* Change log - http://dev.mysql.com/doc/relnotes/mysql-monitor/3.4/en/
* Installation documentation - 
http://dev.mysql.com/doc/mysql-monitor/3.4/en/mem-installing.html
* Complete documentation - http://dev.mysql.com/doc/mysql-monitor/3.4/en/
* Product information - 
http://www.mysql.com/products/enterprise/monitor.html
* Download - http://support.oracle.com/ (available now) or 
http://edelivery.oracle.com/

Thanks and Happy Monitoring!

- The MySQL Enterprise Tools Development Team

==========

Changes in MySQL Enterprise Monitor 3.4.0

Important:

   It is not possible to upgrade to MySQL Enterprise Monitor 3.4 from
   versions preceding MySQL Enterprise Monitor 3.1. To upgrade an older
   version, you must first upgrade to MySQL Enterprise Monitor 3.1
   before running the MySQL Enterprise Monitor 3.4.0 upgrade process.

   The upgrade installer generates an error if you attempt to upgrade
   an older version to 3.4.

Important:

   As of this release, only MySQL Server 5.7.9, or higher, is supported
   for the MySQL Enterprise Service Manager repository. If you are
   using an external repository, not the version bundled with the MySQL
   Enterprise Service Manager installer, you must upgrade it to at
   least MySQL Server 5.7.9 before upgrading your MySQL Enterprise
   Service Manager to 3.4.

   The installers generate an error if you attempt to use a MySQL
   Server version older than 5.7.9.

   MySQL Enterprise Service Manager 3.4's bundled repository is MySQL
   Server 5.7.18.

Performance Tuning Enhancements in MySQL Enterprise Monitor 3.4

* Important Change: The page-loading times of the MySQL Enterprise
   Service Manager user interface are improved.

* Important Change: Graph performance for long-period graphs is
   improved. Timeseries data is aggregated, allowing for faster data
   retrieval.

   When you upgrade to MySQL Enterprise Monitor 3.4.0, all existing
   timeseries data is aggregated when the MySQL Enterprise Service
   Manager first starts. A progress bar is displayed on the Overview
   dashboard indicating the completeness of the aggregation process.

   Note: While the timeseries data is being aggregated for the first
   time, no performance enhancements are evident in the graph response
   times. Performance improvement is evident only after the process
   completes and the timeseries data is retrieved from the new,
   aggregated data.

Replication Monitoring Enhancements in MySQL Enterprise Monitor 3.4

* Important Change: The Replication dashboard is extended to provide
   monitoring support for Group Replication, introduced in MySQL Server
   5.7.17.

   The Topology view provides a visual representation of your group
   replication topologies and the Status drilldowns are updated with
   Group Replication-specific information. The status of the entire
   group is reported on, including node-failure tolerances and whether
   the group has quorum.

   In addition, new replication advisors, Group Replication
   Configuration and Group Replication Status, provide continuous
   analysis of the condition of your group replication toplogies. The
   configuration advisor analyses the configuration of the servers,
   checking for misconfigurations which could lead to unstable or
   insecure installations While the status advisor continously monitors
   for servers which go offline, or fall out of sync with the other
   members of the cluster.

   The group replication advisors also populate the following 
group-level graphs:

   - Group Replication - Transactions Rows Validating - Per Member

   - Group Replication - Transactions Checked - Per Member

   - Group Replication - Conflicts Detected - Per Member

   - Group Replication - Transactions In Queue - Per Member

Functionality Added or Changed

* 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 Account Has An Overly Broad Host Specifier advisor is removed in
   this release. Its functionality is included in the new MySQL User
   Account security advisor. This new advisor also enables you to
   exclude users from event generation using regular expressions.

Bugs Fixed

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

* OS X 10.12 Sierra was not recognised 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 graphs displayed extra zeroes after an upgrade from MySQL
   Enterprise Service Manager 3.2 to 3.3 or 3.4.

-- 
MySQL Announce Mailing List
For list archives: http://lists.mysql.com/announce
To unsubscribe:    http://lists.mysql.com/announce