MySQL Lists are EOL. Please join:

List:Announcements« Previous MessageNext Message »
From:andy bang Date:September 15 2016 9:04pm
Subject:MySQL Enterprise Monitor 3.3 GA has been released
View as plain text  
We are very happy to announce the general availability of MySQL
Enterprise Monitor, Version 3.3. 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 Enterprise
Carrier Grade subscriptions.

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

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

Highlights

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

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

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

Functionality Added or Changed

* Important Change: The Enterprise Backup dashboard is introduced in
   this release. This dashboard enables monitoring of Full,
   Incremental, TTS, and Partial backups performed by MySQL Enterprise
   Backup on the monitored instances.

   For more information, see:
 
http://dev.mysql.com/doc/mysql-monitor/3.3/en/mem-ui-backup-dashboard.html

* Named filters are introduced in this release. Named filters make it
   possible to create and save filters on the following pages:

   - MySQL Instances

   - Events

   - Query Analyzer

   - All Timeseries Graphs

   - Advisors

   A number of default named filters have been added in this release.
   See System and User-defined Filters for more information.

   Important: Existing default filters are migrated by the upgrade
   process and are renamed to User Default.

* The event status is now included in the body of the notification
   mail. (Bug #24311586)

* The Warnings Not Being Logged advisor text was updated.

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

* The MySQL server, bundled with the MySQL Enterprise Service Manager,
   has been upgraded to MySQL 5.7.15.

   Important: If you are upgrading from a previous version, the upgrade
   installer will handle the upgrade of your existing repository to the
   new version. All previous versions of MySQL Enterprise Service
   Manager used MySQL 5.6.x, which must be upgraded to 5.7.14, the
   version delivered with this release. This only applies to
   installations using the bundled MySQL Server. If you are using an
   external MySQL Server as the repository, you must upgrade it
   manually to at least 5.6.14 before running the MySQL Enterprise
   Service Manager upgrade installer. MySQL 5.7.14 is the recommended
   version.

   As of this release, the MySQL Enterprise Service Manager installer
   and upgrade installer raise an error if an attempt is made to
   configure MySQL Enterprise Service Manager to use an unsupported
   MySQL version for the repository.

* Important Change: As of this release, it is not possible to use
   MySQL Server 5.1 or 5.5 as the MySQL Enterprise Monitor repository.
   The installer displays an error and the installation process stops.

Bugs Fixed

* The documentation did not specify the correct format for the ssl-ca-
   keystore-path parameter. It was listed as a file path, but is a URL.
   For example:

   ssl-ca-keystore-path=file:///mysql/enterprise/agent/etc/mykeystore
   (Bug #24386496)

* Attempting to monitor a group replication topology caused all
   replication topology discovery to fail. (Bug #24376827)

* The InnoDB Redo Log Pending Writes graph was not displayed for MySQL
   5.7 instances. (Bug #23563358)

* LDAP configuration was not validated when saved. As a result, if the
   LDAP connection information was incorrectly configured,
   NullPointerExceptions were logged, and it was not possible to
   connect to the LDAP server. (Bug #23299288)

* The certificate to keystore upgrade process attempted to use the
   system's openSSL installation instead of that delivered with the
   installer. As a result, if openSSL was not installed on the system,
   the upgrade failed. As of this release, the upgrade only uses the
   openSSL libraries delivered with the installer. (Bug #22522309)

* The MySQL Enterprise Service Manager utility config.sh returned a
   stack trace for unsupported commands, instead of redirecting the
   user to the help.

* Custom agent service names were not maintained by the agent upgrade
   process. The custom name was overwritten by the default agent
   service name, MySQLEnterpriseMonitorAgent.

* A NullPointerException was logged for replication monitoring. This
   exception did not affect the performance of replication monitoring.

* The advice page generated by the MySQL Enterprise Backup Health
   advisor contained broken links to the InnoDB chapters of the MySQL
   Reference Manual. It also incorrectly referred to the --start-lsn
   option as the --lsn option.

* The Overview page elements did not resize properly if the browser
   window was resized.

* On certain browser versions, the symbol << was transformed to Â<<.

* Replication filter information was not collected. As a result, the
   replica's Filter/Delay Status frame of the Source Replication Status
   was not correctly populated.
Thread
MySQL Enterprise Monitor 3.3 GA has been releasedandy bang15 Sep