MySQL Lists are EOL. Please join:

List:Announcements« Previous MessageNext Message »
From:andy bang Date:February 24 2016 7:05pm
Subject:MySQL Enterprise Monitor 3.0.26 has been released
View as plain text  
MySQL Enterprise Monitor 3.0.26 is now available for download on the
My Oracle Support (MOS) web site.

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/relnotes/mysql-monitor/3.0/en/news-3-0-26.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.

Important: MySQL Enterprise Monitor (MEM) 3.1 offers many significant
improvements over MEM 3.0 and we highly recommend that you consider
upgrading. More information on MEM 3.1 is available here:

   What's New in MySQL Enterprise Monitor 3.1
   http://dev.mysql.com/doc/mysql-monitor/3.1/en/mem-comparison-3-1.html

   MySQL Enterprise Monitor
   http://www.mysql.com/products/enterprise/monitor.html

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

   MySQL Enterprise Monitor Change History
   http://dev.mysql.com/doc/relnotes/mysql-monitor/3.1/en/

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.

Thanks and Happy Monitoring!

   - The MySQL Enterprise Tools Development Team

==========

Changes in MySQL Enterprise Monitor 3.0.26

Functionality Added or Changed

* The Agent Transport selector on the MySQL Instance Details filter
   was removed in this release. (Bug #22584794)

* Auto-close notifications are now sent only if a previous condition
   triggered a notification. If the auto-close is the first condition,
   no notifications are sent.

   Note: Manually closing an event always triggers a notification.

   (Bug #22500665, Bug #22617829)

* The Connector/J component was upgraded to 5.1.38.

* The OpenSSL library bundled with MySQL Enterprise Monitor has been
   upgraded to OpenSSL 1.0.1q.

* The bundled libcurl library was upgraded to 7.45.

* block_encryption_mode is reported on the Security tab of the
   Instance Configuration section of the instance drilldown.

* The MySQL database, bundled with the MySQL Enterprise Service
   Manager, has been upgraded to MySQL 5.6.29.

Bugs Fixed

* The hostname was not displayed in the Unmonitored Instances list if
   the mysqld process arguments could not be read.

   As of this release, the hostname is displayed even if the process
   arguments cannot be read.

* OS X 10.11 was not reported as Mac OS X El Capitan, but as Unknown.

* Under certain circumstances, the Prepared statements not being used
   effectively advisor returned negative results.

* Notifications were not sent for the event handlers associated with
   the Filesystem Freespace Advisor. This occurred if the Event
   Handler's group was a custom group.

* The MySQL Enterprise Monitor Proxy and Aggregator menu items on the
   Windows Start were incorrectly named.

* Windows 10 Operating Systems were listed as Windows 8.1.

* Graphs of long time ranges were inaccurate if the range was expanded
   and reduced. The individual points on the graph represented larger
   values than were actually present.

* It was not possible to define a custom backup location in the MySQL
   Enterprise Service Manager upgrade installer. The default location
   was used regardless of the path defined.

* Some elements of MySQL Enterprise Monitor User Interface were not
   displayed correctly in Microsoft internet Explorer.

* The graphed value for free space in the InnoDB Buffer Pool was
   incorrectly calculated. It was possible for the free space to be a
   negative number.
Thread
MySQL Enterprise Monitor 3.0.26 has been releasedandy bang24 Feb