MySQL Lists are EOL. Please join:

List:Announcements« Previous MessageNext Message »
From:andy bang Date:September 2 2014 8:35pm
Subject:MySQL Enterprise Monitor 3.0.14 has been released
View as plain text  
We are pleased to announce that MySQL Enterprise Monitor 3.0.14 is now
available for download on the My Oracle Support (MOS) web site.  It
will also be available via the Oracle Software Delivery Cloud with the
September update in a few weeks.  MySQL Enterprise Monitor is a
commercial extension to the MySQL family of products.

This is a maintenance release that includes a few enhancements and
fixes a number of bugs.  You can find more information on the contents
of this release in the change log:
     (also included at the end of this note for convenience)

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
in a few weeks:

Choose "MySQL Database" as the Product Pack and you will find the
Enterprise Monitor along with other MySQL products.

Based on feedback from our customers, MySQL Enterprise Monitor (MEM)
3.0 offers many significant improvements over previous releases.
Highlights include:

o Policy-based automatic scheduling of rules and event handling
   (including email notifications) make administration of scale-out
   easier and automatic

o Enhancements such as automatic discovery of MySQL instances,
   centralized agent configuration and multi-instance monitoring
   further improve ease of configuration and management

o The new cloud and virtualization-friendly, "agent-less" design
   allows remote monitoring of MySQL databases without the need for any
   remote agents

o Trends, projections and forecasting - Graphs and Event handlers
   inform you in advance of impending file system capacity problems

o Zero Configuration Query Analyzer - Works "out of the box" with
   MySQL 5.6 Performance_Schema (supported by 5.6.14 or later)

o False positives from flapping or spikes are avoided using
   exponential moving averages and other statistical techniques

o Advisors can analyze data across an entire group; for example, the
   Replication Advisor can scan an entire topology to find common
   configuration errors like duplicate server UUIDs or a slave whose
   version is less than its master's

More information on the contents of this release is available here:

   What's new in MySQL Enterprise Monitor 3.0?

   MySQL Enterprise Edition: Demos

   MySQL Enterprise Monitor Frequently Asked Questions

   MySQL Enterprise Monitor Change History

More information on MySQL Enterprise and the Enterprise Monitor can be
found here:

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

If you haven't looked at 3.0 recently, please do so now and let us
know what you think.

Thanks and Happy Monitoring!

   - The MySQL Enterprise Tools Development Team


Changes in MySQL Enterprise Monitor 3.0.14

Functionality Added or Changed

* The MySQL Enterprise Monitor Proxy and Aggregator is delivered with
   this release. This package works without the need of an agent to
   communicate with the Service Manager, using a new plugin
   infrastructure that allows the Proxy to send raw query statistics to
   the Aggregator, to then aggregate out of band of client connections,
   saving memory and processing overhead for client statements.

     Important: The MySQL Enterprise Monitor Proxy and Aggregator is
     not yet available on Microsoft Windows platforms. This changelog
     will be updated when the Windows version is available.

   The MySQL Enterprise Monitor Proxy and Aggregator is delivered as a
   separate installation package.

     Important: If you are using the 2.3 Proxy/Aggregator installation
     with a 3.0.x version of MySQL Enterprise Service Manager, you must
	uninstall the 2.3 version of the Proxy/Aggregator before
	installing MySQL Enterprise Monitor Proxy and Aggregator delivered
	with this version.

   Changes were made to many configuration settings. Your existing
   scripts or batch files may not work with the new configurations. It
   is highly recommended you read the updated Proxy and Aggregator
   documentation delivered with this release before installing the new
   MySQL Enterprise Monitor Proxy and Aggregator.

* The MySQL Enterprise Monitor Proxy and Aggregator supports EXPLAIN
   for the INSERT, REPLACE, UPDATE, and DELETE DML statements.

     Important: EXPLAIN on these statement types is supported for MySQL
     5.6.3 and higher.

* The bundled JRE was updated to 1.7.0_67 for both the Agent and
   Service Manager.

* As of this release, an options file is delivered,, which enables you to specify minimum and
   maximum heapsize, and log dump settings when running the agent from

   This file is installed to the bin directory of your Agent
   installation. Any custom settings added to this file are preserved
   during upgrades of the Agent.

* The performance of the File System Free Space advisor has been

Bugs Fixed

* Clicking Reload on the InnoDB Buffer Pool Usage report displayed the
   Generate Report page instead of reloading the report. As of this
   release, clicking Reload reloads the report. (Bug #19286607)

* Under certain circumstances, the asset list did not load correctly.
   This issue only occurred when using the Firefox browser to view the
   MySQL Enterprise Monitor User Interface. (Bug #19217939)

* If monitoring large installations, the Database Availability graph
   on the Overview dashboard could take a long time to load. As of this
   release, the underlying queries used to populate this graph have
   been optimized to enable much faster loading times. (Bug #19064180)

* If a replication group was automatically deleted, it was not
   possible to edit an Event Handler which used that Replication Group.
   It was only possible to delete the Event Handler.

* Under certain circumstances, Select.from queries performed on the
   Inventory table resulted in a large number of temporary disk tables.

* Under certain circumstances, the HTTP timeout values were overridden
   and both connection and socket timeout values could be set to
MySQL Enterprise Monitor 3.0.14 has been releasedandy bang2 Sep