MySQL Lists are EOL. Please join:

List:Announcements« Previous MessageNext Message »
From:andy bang Date:February 11 2016 4:43pm
Subject:MySQL Enterprise Monitor 3.1.2 has been released
View as plain text  
We are pleased to announce that MySQL Enterprise Monitor 3.1.2 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
February 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-2.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 in a week or so)

Thanks and Happy Monitoring!

   - The MySQL Enterprise Tools Development Team

==========

Changes in MySQL Enterprise Monitor 3.1.2

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 Create Event Handler dialog was redesigned for usability.

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

* As of this release, the agent restarts in the event of an Out Of
   Memory error.

* 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.28.

* Deleting a user also closes the active sessions opened by that user.

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.

* Selecting the Stack display option for some graphs displayed areas
   instead of the stacked data.

* Windows 10 Operating Systems were listed as Windows 8.1.

* The contents of the Security advisor category were not displayed if
   the thresholds of the MySQL Enterprise Audit Plugin advisor were
   edited.

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

* The Timezone and Locale selection drop-down lists were not displayed
   correctly in the Welcome! dialog.

* An error was displayed in the Support Diagnostics report if the
   first instance in the selected group used sys schema.

   This also occurred if the report was run on a single instance if
   that instance used sys schema.

* config.bat did not return a result code. As a result, errors were
   not detected by the calling process.

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

* Under certain circumstances, a Null Pointer Exception was logged
   when the sys schema was installed from the MySQL Enterprise Service
   Manager. This exception blocked the installation of the sys schema.

* Dependent permissions were not displayed correctly in Firefox. For
   example, if Server Group was set to Administer, MySQL Instances
   should also have changed to Administer, automatically, but was not.
Thread
MySQL Enterprise Monitor 3.1.2 has been releasedandy bang11 Feb