MySQL Lists are EOL. Please join:

List:Announcements« Previous MessageNext Message »
From:andy bang Date:May 26 2016 5:02pm
Subject:MySQL Enterprise Monitor 3.1.4 has been released
View as plain text  
We are pleased to announce that MySQL Enterprise Monitor 3.1.4 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.1/en/news-3-1-4.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.2 offers many significant
improvements over MEM 3.1 and we highly recommend that you consider
upgrading. More information on MEM 3.2 is available here:

   What's New in MySQL Enterprise Monitor 3.2
   http://dev.mysql.com/doc/mysql-monitor/3.2/en/mem-comparison-3-2.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.2/en/mem-faq.html

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

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.

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.

Useful URLs

* My Oracle Support - http://support.oracle.com/
* What's New in 3.1 - 
https://dev.mysql.com/doc/mysql-monitor/3.1/en/mem-comparison-3-1.html
* Change log - http://dev.mysql.com/doc/relnotes/mysql-monitor/3.1/en/
* Installation documentation - 
http://dev.mysql.com/doc/mysql-monitor/3.1/en/mem-installing.html
* Complete documentation - http://dev.mysql.com/doc/mysql-monitor/3.1/en/
* Product information - 
http://www.mysql.com/products/enterprise/monitor.html
* FAQs - http://dev.mysql.com/doc/mysql-monitor/3.1/en/mem-faq.html
* Download - http://support.oracle.com/

Thanks and Happy Monitoring!

   - The MySQL Enterprise Tools Development Team

==========

Changes in MySQL Enterprise Monitor 3.1.4

Functionality Added or Changed

* Important Change: It is now possible to configure the MySQL
   Enterprise Service Manager from the command line, or from a script,
   using the MySQL Enterprise Service Manager Configuration Utilities
   defined in config.sh, or config.bat on Windows platforms. This tool
   is located in the bin directory of your MySQL Enterprise Service
   Manager installation.

* The Agent backlog is no longer written to the filesystem, but to
   active RAM only.

* The default font used in MySQL Enterprise Service Manager is now
   Open Sans Fontface 1.4.2.

* The OpenSSL libraries bundled with MySQL Enterprise Monitor and the
   MySQL Enterprise Monitor Proxy and Aggregator have been upgraded to
   OpenSSL 1.0.1s.

* The Memory Usage - OS Resident graph now also displays filesystem
   buffer and cache data for Linux systems.

* Duplicate MySQL Server UUID events are generated with Critical
   status.

* A new advisor, HTTP Server KeyStore's Certificate About to Expire,
   is added in this release. This advisor checks the expiry date of the
   TLS certificate and raises events as the expiration date approaches.

   The events are raised against configurable thresholds, defined in
   number of days.

Bugs Fixed

* The default instance name was not applied to a instance which had
   been renamed, deleted, then added again. The custom name was cached
   and reapplied to the newly detected instance. (Bug #23063022)

* The default replication group name was not applied to a replication
   group which had been renamed, deleted, then added again. The custom
   name was cached and reapplied to the newly detected group. (Bug
   #23062844)

* Events were not displayed if the monitored instance was installed on
   a host whose system time was set to a future time. (Bug #23049015)

* Replication groups were removed from event handlers during the
   ugprade process for upgrades from 3.0.x to 3.2. (Bug #23012687)

* Exporting graphs as PNG did not export the graph correctly. Some of
   the graph data, such as y-axis detail, was not exported. (Bug
   #23004372)

* The agent troubleshooting documentation incorrectly stated that the
   agent failed to start if the supplied credentials were incorrect.
   (Bug #22989144)

* Under certain circumstances, time-unit drop-down menus on Advisor
   configuration dialogs disappeared when selected. (Bug #22977419)

* The Event label Worst Alarm Time is renamed Time of Worst Status
   (Bug #22849129)

* The documentation on installing SSL certificates was not included.
   (Bug #22724280)

* If the network was misconfigured, SSL certificate generation failed
   because the CN could not be defined. As of this release, if the
   fully-qualified domain name cannot be retrieved, the system falls
   back to the contents of hostname, or, if hostname does not return a
   usable value, uses localhost.localdomain as the CN value. (Bug
   #22583338)

* The help text of the Binary Log Space Exceeds Specified Limit
   advisor was updated. (Bug #2078129)

* The self-signed certificate expiration date was 10 years. It is now
   changed to 365 days.

* The advice text in the Events table overlapped the adjacent text.

* The help output of the agent configuration utility contained
   spelling errors and a duplicated entry.
Thread
MySQL Enterprise Monitor 3.1.4 has been releasedandy bang26 May