MySQL Enterprise Monitor 3.0.10 has been released

[Andy Bang]

We are pleased to announce that MySQL Enterprise Monitor 3.0.10 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
May update in about 1 week. 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:

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

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
in approximately 1 week:

http://edelivery.oracle.com/

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?
http://dev.mysql.com/doc/mysql-monitor/3.0/en/mem-comparison-2-3.html

MySQL Enterprise Edition: Demos
http://www.mysql.com/products/enterprise/demo.html

MySQL Enterprise Monitor Frequently Asked Questions
http://dev.mysql.com/doc/mysql-monitor/3.0/en/mem-faq.html

MySQL Enterprise Monitor Change History
http://dev.mysql.com/doc/mysql-monitor/3.0/en/mem-news.html

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

http://www.mysql.com/products/enterprise/
http://www.mysql.com/products/enterprise/monitor.html
http://www.mysql.com/products/enterprise/query.html
http://forums.mysql.com/list.php?142

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.

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

Functionality Added or Changed

* The performance of GroupLabel inventory processing has been
improved. This enhancement is particularly useful in implementations
which have many MySQL instances in a small number of groups.

* The bundled Tomcat version was updated to version 7.0.52.

* The bundled Tomcat Native Library was updated to version 1.1.30 from
version 1.1.27.

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

* The output of config.bat has been improved.

Bugs Fixed

* Under certain circumstances, the statement digest data was larger
than the valid data range and generated an exception. As of this
release, a log message is generated but no exception is raised. (Bug
#17857524)