We are pleased to announce that MySQL Enterprise Monitor 3.0.13 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
August 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.
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
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
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
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.13
Functionality Added or Changed
* As of this release, a warning is displayed when an instance is
selected for the InnoDB Buffer Pool Usage report. The warning
advises on the resources utilized and the possible load imposed on
the selected instance. (Bug #18344437)
* As of this release, the graph is displayed on the Query Analyzer
page by default. (Bug #18203339)
Important: It is recommended to clean your browser's cookies. The
open, or closed, status of the graph is stored in a cookie.
* It is now possible to delete unused or obsolete assets from the
Inventory. For more information, see Inventory Pages .
* Orphaned events are now closed automatically. If a custom advisor is
deleted, or one of the default advisors is removed after an upgrade,
and leaves orphaned events on the Events page, those events are
automatically closed. A system-generated comment is added to the
* It is now possible to add a note when suspending an event handler.
The content of the note is displayed if you hover the cursor over
the event handler's state icon.
If an event handler is automatically suspended, due to the removal
of the advisor, or change in replication topology, a note is
automatically generated by the system.
* A data-connection pool configuration issue resulted in reduced
performance and application scalability where large installations
were monitored. (Bug #19209049)
* The SNMP trap configuration field, Target 2 was cleared when the
SNMP settings were saved. The value defined in Target 2 was saved,
but not displayed. (Bug #19002285)
* It was not possible to purge events if autocommit=0 and
enforce_gtid_consistency=1. An error was displayed. (Bug #18960568)
* MySQL Enterprise Monitor User Interface behaved unpredictably if a
custom graph or advisor was imported with the same title as an
existing graph or advisor, but a different UUID.
As of this release, checks are introduced to ensure normal behaviour
of the MySQL Enterprise Monitor User Interface if such duplication
- If the graph or advisor has the same name and UUID, but the
version number was not incremented, the import fails and MySQL
Enterprise Service Manager raises an error.
- If the graph or advisor has the same name but a different UUID,
the import fails and MySQL Enterprise Service Manager raises an
error containing the name of the advisor.
In both scenarios, the import process fails. (Bug #18306986)
* The rangeLabel element was not processed if it was used in a custom
graph. Unknown was displayed instead. (Bug #17556299, Bug #18311827)
* The tcnative-1.dll is restored on Windows hosts in this release.
* 32-bit Java installations were not properly removed on Linux
platforms if they were upgraded with the 64-bit MySQL Enterprise
Monitor package delivered with version 3.0.12.
As of this release, if you upgrade an 32-bit Java installation with
the 64-bit version, the 32-bit version's files are completely
|• MySQL Enterprise Monitor 3.0.13 has been released||andy bang||18 Jul|