MySQL Enterprise Monitor 3.3.3 has been released

[Andy Bang]

We are pleased to announce that MySQL Enterprise Monitor 3.3.3 is now
available for download on the My Oracle Support (MOS) web site. It
will also be available for download via the Oracle Software Delivery
Cloud in a few days. MySQL Enterprise Monitor is the best-in-class
tool for monitoring and management of your MySQL assets and is
included with your MySQL Enterprise Edition and MySQL Cluster
Carrier Grade Edition subscriptions.

You’ll find information about what’s new here:

http://dev.mysql.com/doc/relnotes/mysql-monitor/3.3/en/news-3-3-3.html
(also included at the end of this note for convenience)

Highlights of MySQL Enterprise Monitor 3.3 include:

* 3.3 introduces a new Enterprise Backup Dashboard that brings deeper
integration with MySQL Enterprise Backup. View current backup
status, history and archive details by group or instance using MySQL
Enterprise Backup Advisor collections from existing
mysql.backup_history and mysql.backup_progress table data.

* Backup Group view shows a summary of backup events, details on the
last successful full and Incremental backup types, any failed
backups and an indication of whether the group has full backup
coverage. Coverage calculations include appropriate checks on
replication filters across your replication topologies.

* Backup view of a single MySQL Instance shows a summary of backup
events, details on the last successful full and Incremental backup
types and any failed backups. Sparkline histories graph the total
backup time per backup and the total time the MySQL Instance had a
global read-lock during the backup process.

* Select the Backup History tab to see all known backups in the event
you need to perform a restore operation. Each row in the backup
history table shows the backup type, status, completion timestamp
and the log coordinates when the consistent snapshot was taken.

* Drill down to an individual Backup archive to view all its metadata
and associated progress logs.

* The 3.3 User Interface now makes zooming in on common problems a
single click on a named filter. Use these shortcuts to quickly
select the search criteria of most interest on the MySQL Instances,
Events, Query Analyzer and All Timeseries Graphs pages. Examples of
pre-defined filters include all MySQL Instances using an EOL
version, old MySQL Enterprise Monitor Agent installations, currently
open Emergency events, and all statements that cause a full table
scan, temporary tables on disk or SQL Errors. In addition to pre-
defined filters, you can assign a name to your own favorite search
conditions for reuse across sessions.

Download

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:

http://edelivery.oracle.com/

Type "MySQL Enterprise Monitor 3.3.3" in the search box, or enter a
license name to find Enterprise Monitor along with other MySQL
products: "MySQL Enterprise Edition" or "MySQL Cluster Carrier
Edition". Then select your platform.

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.

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.

Useful URLs

* My Oracle Support - http://support.oracle.com/
* What's New in 3.3 - https://dev.mysql.com/doc/mysql-monitor/3.3/en/mem-comparison-3-2.html
* Change log - http://dev.mysql.com/doc/relnotes/mysql-monitor/3.3/en/
* Installation documentation - http://dev.mysql.com/doc/mysql-monitor/3.3/en/mem-installing.html
* Complete documentation - http://dev.mysql.com/doc/mysql-monitor/3.3/en/
* Product information - http://www.mysql.com/products/enterprise/monitor.html
* Download - http://support.oracle.com/ (available now) or http://edelivery.oracle.com/

Thanks and Happy Monitoring!

- The MySQL Enterprise Tools Development Team

==========

Changes in MySQL Enterprise Monitor 3.3.3

Functionality Added or Changed

* As of this release, MySQL Enterprise Monitor Agent no longer creates
the mysql.inventory table on MySQL Server 5.6, or higher. The value
of server_uuid is used to uniquely identify the server.

For MySQL Server 5.5, the functionality is unchanged and the agent
creates the mysql.inventory table. (Bug #24699549)

* It is now possible to change the number of rows displayed in the
Backups section on the History tab of the Enterprise Backup
dashboard.

* The OpenSSL libraries used by the MySQL Enterprise Monitor
installers and MySQL Enterprise Monitor Aggregator have been
upgraded to 1.0.2k.

* The Tomcat server,undled with the MySQL Enterprise Service Manager,
has been upgraded to 8.5.9.

Bugs Fixed

* Security Fix: MySQL Enterprise Service Manager has been updated to
use Apache Struts 2.3.32, which has been publicly reported as not
vulnerable to CVE-2017-5638. (Bug #25698531, CVE-2017-5638)

* MySQL Enterprise Service Manager failed to start if the operating
system's locale was set to FR_FR. (Bug #25615156)

* MySQL Enterprise Monitor Agent installer stopped unexpectedly on
Solaris platforms. This occurred for both unattended and text
installation modes during the agent user credential step. (Bug
#25427615)

* No message was displayed on the Roles and Users pages if an attempt
was made to save an incorectly defined user or role. Such as a role
without a name, or mismatched passwords. The role was not saved, but
no reason was given for the failure to save. (Bug #25268334)

* Input fields were available on the Roles and Users pages before a
role or user was selected. (Bug #25268248)

* No error was generated if the General and Limited user passwords
violated a server-side password validation rule. This error occurred
if the MySQL server used the password validation plugin.

As of this release, if a monitoring connection request fails because
the General or Limited user's passwords do not meet the requirements
on the server, an error is displayed with the server error message
and the username which caused the error. (Bug #25153652)

* Query detail graphs were not displayed on the Graphs tab of the
query details dialog on the Query Analyzer page if the locale was
set to Japanese. (Bug #24830763)

* The Group Settings tab on the Edit Instance dialog was too small to
properly display its contents. (Bug #24481474)

* If agent.sh was run as root, incorrect permissions were applied to
some log and keystore files, making them inaccessible to the agent,
which runs as mysql.

As of this release, it is not possible to run agent.sh from the
command line as root, but only as mysql. (Bug #24338452)

* The agent failed to start on Solaris platforms due to incorrectly
defined permissions. (Bug #24327644)

* MySQL Enterprise Monitor Agent upgrades overwrote custom, log4j
configuration files with a new, default configuration file. As of
this release, the custom log4j configuration files are preserved,
and the new, default configuration is written to the same directory
with the filename log4j.properties.default. (Bug #18501221)

* MySQL Enterprise Service Manager upgrade, installed as root,
reported errors on OS X. Services did not start after the upgrade
completed, but could be started manually.