MySQL Enterprise Monitor 3.0.12 has been released
Posted by: Andy Bang
Date: June 30, 2014 03:02PM
Date: June 30, 2014 03:02PM
We are pleased to announce that MySQL Enterprise Monitor 3.0.12 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
July update in about 1 week. 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/mysql-monitor/3.0/en/mem-news-3-0-12.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 approximately 1 week:
http://edelivery.oracle.com/
Choose "MySQL Database" as the Product Pack and you will find the
Enterprise Monitor along with other MySQL products.
Based on feedback from our customers, MySQL Enterprise Monitor (MEM)
3.0 offers many significant improvements over previous releases.
Highlights include:
o Policy-based automatic scheduling of rules and event handling
(including email notifications) make administration of scale-out
easier and automatic
o Enhancements such as automatic discovery of MySQL instances,
centralized agent configuration and multi-instance monitoring
further improve ease of configuration and management
o The new cloud and virtualization-friendly, "agent-less" design
allows remote monitoring of MySQL databases without the need for any
remote agents
o Trends, projections and forecasting - Graphs and Event handlers
inform you in advance of impending file system capacity problems
o Zero Configuration Query Analyzer - Works "out of the box" with
MySQL 5.6 Performance_Schema (supported by 5.6.14 or later)
o False positives from flapping or spikes are avoided using
exponential moving averages and other statistical techniques
o Advisors can analyze data across an entire group; for example, the
Replication Advisor can scan an entire topology to find common
configuration errors like duplicate server UUIDs or a slave whose
version is less than its master's
More information on the contents of this release is available here:
What's new in MySQL Enterprise Monitor 3.0?
http://dev.mysql.com/doc/mysql-monitor/3.0/en/mem-comparison-2-3.html
MySQL Enterprise Edition: Demos
http://www.mysql.com/products/enterprise/demo.html
MySQL Enterprise Monitor Frequently Asked Questions
http://dev.mysql.com/doc/mysql-monitor/3.0/en/mem-faq.html
MySQL Enterprise Monitor Change History
http://dev.mysql.com/doc/mysql-monitor/3.0/en/mem-news.html
More information on MySQL Enterprise and the Enterprise Monitor can be
found here:
http://www.mysql.com/products/enterprise/
http://www.mysql.com/products/enterprise/monitor.html
http://www.mysql.com/products/enterprise/query.html
http://forums.mysql.com/list.php?142
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.
If you haven't looked at 3.0 recently, please do so now and let us
know what you think.
Thanks and Happy Monitoring!
- The MySQL Enterprise Tools Development Team
==========
Changes in MySQL Enterprise Monitor 3.0.12
Functionality Added or Changed
* As of this release, the Linux installer containing the 64-bit Agent
with the 32-bit JVM has been discontinued. The following Agent
installers are provided for Linux platforms:
- 32-bit Agent with 32-bit JVM.
- 64-bit Agent with 64-bit JVM.
Important: On 64-bit Linux platforms, where possible, it is
strongly recommended to use the 32-bit Agent and 32-bit JVM. The
32-bit version consumes considerably less resources than its 64-
bit counterpart. Consult your platform documentation for
information on the compatibility libraries required to run 32-bit
applications on a 64-bit platform.
* The behavior of replication groups and associated event handlers has
been improved in this release.
- If all instances which make up a replication group are deleted,
the replication group is deleted automatically.
If a replication group is automatically deleted, an event is
generated and a message is displayed in the MySQL Enterprise
Monitor User Interface.
- If the deleted replication group was associated with an event
handler, the replication group is automatically removed from the
event handler's definition.
An event is generated and a message is displayed in the MySQL
Enterprise Monitor User Interface stating that the group was
removed.
- If the deleted replication group was the only filter defined on
the event handler, the event handler is suspended.
An event is generated and a message is displayed in the MySQL
Enterprise Monitor User Interface stating that the group was
removed and the event handler suspended.
Important: This enhancement replaces the manual workaround
described in issue #18473938, in version 3.0.8.
* Support Diagnostics now includes a SQL dump of the Advisor
Schedules, Inventory and Configuration schemas.
Important: The Configuration schema may contain login credentials.
However, these credentials are encrypted using keys which are not
stored in the repository.
* The OpenSSL library bundled with MySQL Enterprise Monitor has been
upgraded to OpenSSL 1.0.1h.
Important: If you are using IPv6 on Windows, you must remove the
Tomcat Native Library (tcnative-1.dll) from the apache-tomcat\bin
directory of your Tomcat installation.
* The Tomcat server, bundled with the MySQL Enterprise Service
Manager, has been upgraded to Tomcat 7.0.54.
* The MySQL database, bundled with the MySQL Enterprise Service
Manager, has been upgraded to MySQL 5.6.19.
Bugs Fixed
* It was not possible to add, remove or edit an asset in an event
handler which had an asset already defined on it. (Bug #18867946)
* If more than 10 event handlers were defined, it was not possible to
edit any event handler after the first 10. (Bug #18766362)
* The MySQL Ignore Server advisor is no longer used and has been
removed.
available for download on the My Oracle Support (MOS) web site. It
will also be available via the Oracle Software Delivery Cloud with the
July update in about 1 week. 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/mysql-monitor/3.0/en/mem-news-3-0-12.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 approximately 1 week:
http://edelivery.oracle.com/
Choose "MySQL Database" as the Product Pack and you will find the
Enterprise Monitor along with other MySQL products.
Based on feedback from our customers, MySQL Enterprise Monitor (MEM)
3.0 offers many significant improvements over previous releases.
Highlights include:
o Policy-based automatic scheduling of rules and event handling
(including email notifications) make administration of scale-out
easier and automatic
o Enhancements such as automatic discovery of MySQL instances,
centralized agent configuration and multi-instance monitoring
further improve ease of configuration and management
o The new cloud and virtualization-friendly, "agent-less" design
allows remote monitoring of MySQL databases without the need for any
remote agents
o Trends, projections and forecasting - Graphs and Event handlers
inform you in advance of impending file system capacity problems
o Zero Configuration Query Analyzer - Works "out of the box" with
MySQL 5.6 Performance_Schema (supported by 5.6.14 or later)
o False positives from flapping or spikes are avoided using
exponential moving averages and other statistical techniques
o Advisors can analyze data across an entire group; for example, the
Replication Advisor can scan an entire topology to find common
configuration errors like duplicate server UUIDs or a slave whose
version is less than its master's
More information on the contents of this release is available here:
What's new in MySQL Enterprise Monitor 3.0?
http://dev.mysql.com/doc/mysql-monitor/3.0/en/mem-comparison-2-3.html
MySQL Enterprise Edition: Demos
http://www.mysql.com/products/enterprise/demo.html
MySQL Enterprise Monitor Frequently Asked Questions
http://dev.mysql.com/doc/mysql-monitor/3.0/en/mem-faq.html
MySQL Enterprise Monitor Change History
http://dev.mysql.com/doc/mysql-monitor/3.0/en/mem-news.html
More information on MySQL Enterprise and the Enterprise Monitor can be
found here:
http://www.mysql.com/products/enterprise/
http://www.mysql.com/products/enterprise/monitor.html
http://www.mysql.com/products/enterprise/query.html
http://forums.mysql.com/list.php?142
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.
If you haven't looked at 3.0 recently, please do so now and let us
know what you think.
Thanks and Happy Monitoring!
- The MySQL Enterprise Tools Development Team
==========
Changes in MySQL Enterprise Monitor 3.0.12
Functionality Added or Changed
* As of this release, the Linux installer containing the 64-bit Agent
with the 32-bit JVM has been discontinued. The following Agent
installers are provided for Linux platforms:
- 32-bit Agent with 32-bit JVM.
- 64-bit Agent with 64-bit JVM.
Important: On 64-bit Linux platforms, where possible, it is
strongly recommended to use the 32-bit Agent and 32-bit JVM. The
32-bit version consumes considerably less resources than its 64-
bit counterpart. Consult your platform documentation for
information on the compatibility libraries required to run 32-bit
applications on a 64-bit platform.
* The behavior of replication groups and associated event handlers has
been improved in this release.
- If all instances which make up a replication group are deleted,
the replication group is deleted automatically.
If a replication group is automatically deleted, an event is
generated and a message is displayed in the MySQL Enterprise
Monitor User Interface.
- If the deleted replication group was associated with an event
handler, the replication group is automatically removed from the
event handler's definition.
An event is generated and a message is displayed in the MySQL
Enterprise Monitor User Interface stating that the group was
removed.
- If the deleted replication group was the only filter defined on
the event handler, the event handler is suspended.
An event is generated and a message is displayed in the MySQL
Enterprise Monitor User Interface stating that the group was
removed and the event handler suspended.
Important: This enhancement replaces the manual workaround
described in issue #18473938, in version 3.0.8.
* Support Diagnostics now includes a SQL dump of the Advisor
Schedules, Inventory and Configuration schemas.
Important: The Configuration schema may contain login credentials.
However, these credentials are encrypted using keys which are not
stored in the repository.
* The OpenSSL library bundled with MySQL Enterprise Monitor has been
upgraded to OpenSSL 1.0.1h.
Important: If you are using IPv6 on Windows, you must remove the
Tomcat Native Library (tcnative-1.dll) from the apache-tomcat\bin
directory of your Tomcat installation.
* The Tomcat server, bundled with the MySQL Enterprise Service
Manager, has been upgraded to Tomcat 7.0.54.
* The MySQL database, bundled with the MySQL Enterprise Service
Manager, has been upgraded to MySQL 5.6.19.
Bugs Fixed
* It was not possible to add, remove or edit an asset in an event
handler which had an asset already defined on it. (Bug #18867946)
* If more than 10 event handlers were defined, it was not possible to
edit any event handler after the first 10. (Bug #18766362)
* The MySQL Ignore Server advisor is no longer used and has been
removed.
Subject
Views
Written By
Posted
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.