MySQL Lists are EOL. Please join:

List:Announcements« Previous MessageNext Message »
From:andy bang Date:July 2 2015 1:15am
Subject:MySQL Enterprise Monitor 3.0.22 has been released
View as plain text  
We are pleased to announce that MySQL Enterprise Monitor 3.0.22 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
July 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:

     http://dev.mysql.com/doc/relnotes/mysql-monitor/3.0/en/news-3-0-22.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 a few weeks:

     http://edelivery.oracle.com/

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

More information on MySQL Enterprise Monitor 3.0 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/relnotes/mysql-monitor/3.0/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.

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

Functionality Added or Changed

* The Data Purge process now removes the historical data in order,
   from oldest to newest. (Bug #18251338)

   References: See also Bug #20554946.

* The monitored instance disconnected the Agent if the Agent's
   connection was idle between data collections. This forced repeated
   reconnections between the Agent and the monitored instance.

   As of this release, the Agent provides the wait_timeout value for
   connections to the monitored server. The new timeout value is 1800
   seconds, which is sufficiently long to prevent such reconnections.

* The bundled JRE was updated to 1.8.0_45 for both the Agent and
   Service Manager.

* The bundled libcurl library was upgraded to 7.42.1.

* The following MySQL Enterprise Firewall system and variables are
   available for use in custom graphs and advisors:

   - System Variables:

     mysql_firewall_max_query_size

     mysql_firewall_mode

     mysql_firewall_trace

   - Status Variables:

     Firewall_access_denied

     Firewall_access_granted

     Firewall_cached_entries

   For more information on these variables, see MySQL Enterprise
   Firewall Reference

* As of this release, the Agent sets sql_mode=NO_AUTO_CREATE_USER in
   addition to STRICT_TRANS_TABLES and NO_ENGINE_SUBSTITUTION. This is
   set to prevent repeated occurrences of the following error from
   MySQL 5.7.x:

   Warning | 3129 | Unsetting sql mode 'NO_AUTO_CREATE_USER' is
   deprecated. It will be made read-only in a future release.

* The Rickshaw graph library bundled with MySQL Enterprise Monitor is
   upgraded to version 1.5.1.

* As of this release, TLSv1 support is removed. Only TLSv1.1 and
   TLSv1.2 are supported. TLSv1.2 is preferred. For a full list of the
   supported ciphers, see OpenSSL Ciphers.

   Important: The change in TLS support makes it impossible for MySQL
   Enterprise Service Manager 3.0.22 to communicate with earlier
   versions of MySQL Enterprise Monitor Agent

   MySQL Enterprise Service Manager 3.0.22 can communicate with MySQL
   Enterprise Monitor Agent 3.0.22, only.

   Important: As a result of this change, Microsoft Internet Explorer 9
   is no longer supported by MySQL Enterprise Monitor.

Bugs Fixed

* Default sorting was incorrect for the following:

   - Events: now sorted by Current and Time.

   - Query Analyzer: now sorted by Latency:Total.

   Also, the column names were standardized in the Query Analyzer's
   Show/hide columns selector drop-down list. As of this release, the
   column names listed in the selector now match those used in the
   Query Analyzer. (Bug #21216799)

* If MySQL Enterprise Service Manager was upgraded to 3.0.21, and
   there were active Event Handlers, a NullPointerException was logged
   for each SMTP Notification Action. This error did not interrupt the
   notifications, but could quickly fill the logs. (Bug #21196480)

* A UNIX/Linux script, setenv.sh, was called during the update process
   on Windows platforms. The installation process was unaffected, but
   an error was logged in the installation log file. (Bug #21073969)

* The event text for MySQl Availability and Agent Not Reachable events
   contained a reference to non-existant documentation. These events
   have been updated with links to relevant documentation. (Bug
   #21066744)

* Query Analyzer EXPLAINs failed for views. A connection error was
   displayed. The SHOW VIEWS privilege was not automatically granted to
   the Limited and General users. As of this release, the SHOW VIEWS is
   automatically granted to the auto-created users, General and
   Limited.

   If you are manually managing your users, and want to run EXPLAINs on
   views, you must grant this privilege to your users. (Bug #20974495)

* The tooltip was empty for the MySQL Instance is Down icon on the
   Replication dashboard. (Bug #20916529)

* Text was displayed incorrectly if the English (Canada) locale was
   selected. (Bug #20896159)

* The time displayed on the X-axis of some graphs was incorrect. A
   period of 0 to 45 seconds was repeated instead of displaying the
   time of day. (Bug #20744237)

* If an event handler had more than one group associated with it, and
   one of those groups was removed automatically, by a replication
   topology change for example, MySQL Enterprise Service Manager failed
   to start. A ConcurrentModificationException error was listed in the
   logs. (Bug #20603989)

* If MySQL Enterprise Service Manager was configured to use a reverse
   proxy, Inventory links were not correctly resolved. As of this
   release, all links are server-relative. (Bug #20519137)

* MySQL Enterprise Backup events were not auto-closed even if the
   associated Event Handler was set to auto-close. If the issue was
   corrected, and the backup was successful, no events were generated.

   As of this release, an event is generated for each backup run. Each
   event is identified by the MySQL Enterprise Backup backup ID.
   Successful backup events are auto-closed.

   If a backup fails, generating a failure event, but a subsequent
   backup using the same commandline is successful, both the success
   and failure event are auto-closed. (Bug #19776693)

* In previous releases, many of the graphs, and some expression-based
   Advisors, used a hardcoded frequency of 60 seconds instead of the
   defined schedule.

   As of this release, the variable %defaultFreq% is added to the
   expressions of all affected graphs and Advisors. This variable
   ensures the graphs and Advisors use the defined schedule.

   Note: This new variable can also be used in custom graphs and
   Advisors.

   (Bug #11747974)

* On older, slower systems, the agent startup process reported that
   the agent had not started, even though the agent was running. This
   was caused by the agent taking longer to start than the defined
   timeout on the agent start process.

   As of this release, the agent startup timeout is changed from 60 to
   90 seconds, thereby allowing for old or under-resourced systems.

* The install.log was not removed from the MySQL Enterprise Service
   Manager root directory after a complete uninstallation was
   performed. This occurred if the install.log was created by a product
   update.

* Under certain circumstances, it was not possible to retrieve
   filesystem details for some types of NFS disk. As a result, the
   Filesystem Advisor could not generate Free Space warnings.

* The event text for Binary Log Space Exceeds Specified Limit events
   reported the disk space used in bytes. As of this release, the disk
   space used is reported in the more readable gigabytes (GB) and
   megabytes (MB).
Thread
MySQL Enterprise Monitor 3.0.22 has been releasedandy bang2 Jul