MySQL Lists are EOL. Please join:

List:Announcements« Previous MessageNext Message »
From:andy bang Date:November 30 2015 8:22pm
Subject:MySQL Enterprise Monitor 3.1.1 has been released
View as plain text  
We are pleased to announce that MySQL Enterprise Monitor 3.1.1 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
December 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.1/en/news-3-1-1.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.

Version 3.1 adds significant enhancements in the areas of security and
performance tuning.  Highlights include:

* New MySQL 5.7 metrics and collections.

* Performance tuning tools to identify I/O hot spots and lock wait
   contention. The Database File I/O and Lock Waits reports utilize the
   sys schema, which can be installed on the selected instance from
   within MySQL Enterprise Monitor.

* Access Control Lists - MySQL Enterprise Monitor 3.1 introduces
   Access Control Lists (ACLs) that enable the following functionality
   within the monitoring tool:

   - Define visibilty: strictly limit access to specific groups of
     assets or grant access to all assets.

   - Define Roles: rather than define permissions per user, as in
     previous releases, permission sets are defined in roles and roles
     can be assigned to users.

   - Restrict access to sensitive data: grant or deny rights to view
     specific types of potentially sensitive data, such as Query
     Analyzer data.

   - Authenticate using external services: map your users to roles
     defined in LDAP or Active Directory.

* Monitoring of MySQL Enterprise Firewall to protect your MySQL
   servers from database-specific attacks and receive alerts when a
   potential security threat has been identified.

* Monitoring of MySQL Enterprise Audit to enforce your own security
   policies and satisfy regulatory compliance with HIPAA, Sarbanes-
   Oxley, and the PCI Data Security Standard.

* Bug fixes, enhancement requests and usability improvements were made
   throughout the product, including a new Group Editor on the Settings
   menu, new User and Roles editors, and customizable graphs on the
   Overview dashboard.

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/ (available now) or 
http://edelivery.oracle.com/ (refreshed by mid-November)

Thanks and Happy Monitoring!

   - The MySQL Enterprise Tools Development Team

==========

Changes in MySQL Enterprise Monitor 3.1.1

Functionality Added or Changed

* As of this release, on OS X platforms, the upgrade process preserves
   any existing, custom certificates and keystores. If no keystore
   exists, one is created.

   Important: If a keystore exists, but does not use the default name
   keystore, the upgrade process renames it to keystore.

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

* In previous versions, if the agent was unable to retrieve sys-
   schema-based collection, no message was displayed in the user
   interface. The failure was written to the log files.

   As of this release, any such failure is treated as an event and
   displayed on the Events page.

* As of this release, the 32-bit MySQL Enterprise Service Manager is
   discontinued.

   For more information, see MySQL Enterprise Service Manager Supported
   Platforms.

Bugs Fixed

* It was not possible to connect to MySQL 5.7.9 using the MySQL
   Enterprise Agent Proxy Service. (Bug #22256273)

* Replication groups were renamed during the upgrade process. (Bug
   #22226374)

* The documentation did not describe which privileges were required to
   install sys schema from within MySQL Enterprise Monitor.

   For more information, see Creating MySQL User Accounts for the
   Monitor Agent. (Bug #22188730)

* An error was generated by the installer if it was run on a non-
   English language platform. (Bug #22174999)

* It was not possible to upgrade to MySQL Enterprise Monitor 3.1 from
   MySQL Enterprise Monitor 2.3 without upgrading to 3.0 first. As of
   this release, it is possible to upgrade directly from 2.3 to 3.1.1.
   (Bug #22144486)

* Under certain circumstances, a deadlock occurred in the MySQL
   Enterprise Service Manager repository and event updates could be
   lost. As of this release, further checks for such deadlocks are
   included. (Bug #22079805)

* The Service Manager's Small installation type generated out of
   memory errors.

   As of this release, the heap size parameter of the small
   installation type is 512MB.

* The Roles page was not reset if another area of the product was
   selected and the Roles page selected again. Unsaved data was
   displayed.

* It was possible for the current user to delete themselves on the
   Users page.

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

* Locally monitored instances were displayed as remotely monitored if
   their connections used SSL.

* The Password Digest Mechanism drop-down menu, on the Settings page,
   was disabled.

* Instances with unknown status, because they were no longer
   monitored, were reported as running and available.

* A system error occurred if the default Admin user was assigned to a
   new Role.

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

* Under certain circumstances, if the received data was incomplete,
   the Asset Selector could not render some nodes in the tree. For
   example, if the Server Name could not be resolved, the Asset
   Selector was unable to display the instances nested beneath the
   server name in the asset tree.

* Under certain circumstances, groups did not display their contents.

* Under certain circumstances, it was possible for the Exponential
   Moving Average calculations to generate invalid values (Double.NaN).
   A MySQLException error was logged as a result.

* Under certain circumstances, Roles did not display their default
   selections. Some or all of the permissions were not selected.

* Errors were displayed twice on the Users and Roles pages.
Thread
MySQL Enterprise Monitor 3.1.1 has been releasedandy bang1 Dec