MySQL Enterprise Monitor 3.1.3 has been released

[Andy Bang]

We are pleased to announce that MySQL Enterprise Monitor 3.1.3 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-3.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.3

Functionality Added or Changed

* The sys-related information presented on the Database File I/O and
Lock Waits reports now includes a link to the sys schema GitHub
repository. (Bug #22540573)

* It is now possible to pause the page refresh using the pause button
adjacent to the Refresh drop-down list.

Note: The pause is temporary. If the page is manually refreshed, the
pause is cancelled and the defined refresh behavior resumes.

To resume the defined page refresh, click the button again.

Also in this release, 5, 10, and 30 second refresh options were
added to the Refresh drop-down list.

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

* The openSSL libraries, delivered with the MySQL Enterprise Monitor
Proxy and Aggregator have been upgraded to 1.0.1r.

Bugs Fixed

* If MySQL Enterprise Service Manager installed sys schema to a
replication master, the sys installation was propaagated to the
replica instances. If the replica instance already used sys,
replication stopped with an error.

As of this release, if sys is installed on a master instance, it is
not propagated to the replicas. (Bug #22807490)

* It was not possible to upgrade MySQL Enterprise Service Manager from
2.3.x to 3.1.x if the 2.3 installation of Tomcat was not configured
to use SSL. (Bug #22759744)

* The data in the sys schema-related reports did not refresh. (Bug
#22750089)

* Monitoring a slow filesystem could result in gaps in other OS
collections, such as CPU usage, affecting the OS-related graphs.

As of this release, filesystem collections are performed
independently of CPU and RAM usage collections.

Note: Filesystem-related collection can still be affected by slow
filesystem performance.

(Bug #21459378)

* It was not possible for MySQL Enterprise Monitor Agent 2.3.x to
communicate with a MySQL Enterprise Service Manager 3.1.x.