MySQL Forums
Forum List  »  Announcements

MySQL Enterprise Monitor 3.0.25 has been released
Posted by: Andy Bang
Date: November 05, 2015 02:14PM

MySQL Enterprise Monitor 3.0.25 is now available for download on the
My Oracle Support (MOS) web site.

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.0/en/news-3-0-25.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.

Important: MySQL Enterprise Monitor (MEM) 3.1 offers many significant
improvements over MEM 3.0 and we highly recommend that you consider
upgrading. More information on MEM 3.1 is available here:

What's New in MySQL Enterprise Monitor 3.1
http://dev.mysql.com/doc/mysql-monitor/3.1/en/mem-comparison-3-1.html

MySQL Enterprise Monitor
http://www.mysql.com/products/enterprise/monitor.html

MySQL Enterprise Monitor Frequently Asked Questions
http://dev.mysql.com/doc/mysql-monitor/3.1/en/mem-faq.html

MySQL Enterprise Monitor Change History
http://dev.mysql.com/doc/relnotes/mysql-monitor/3.1/en/

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.

Thanks and Happy Monitoring!

- The MySQL Enterprise Tools Development Team

==========

Changes in MySQL Enterprise Monitor 3.0.25

Functionality Added or Changed

* As of this release, SMTP notifications use a default 5 minute
timeout for read and write actions. In previous releases, no such
timeout existed. (Bug #21912643)

* The Reset button on the All Timeseries graphs page is renamed to
Reset To Default. This enables you to revert your changes to the
last saved filter settings.

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

* A replication group display profile is added to the Asset Selector
on the All Timeseries graphs page. The Replication Slave Delay graph
is displayed for replication groups.

Note: The graph is displayed only if the data exists to populate it.
If there is no slave delay, or if a problem exists in the
replication setup, the graph is not displayed.

* FreeBSD 8 and 9 are no longer supported platforms for the MySQL
Enterprise Monitor Agent and MySQL Enterprise Monitor Proxy and
Aggregator. FreeBSD 10 is supported.

* As of this release, SMTP event close notifications are sent
regardless of the status of the event prior to closing.

* The bundled JRE was updated to 1.8.0_66 for both the Agent and
Service Manager.

Bugs Fixed

* The MySQL Enterprise Monitor Proxy was unable to connect to MySQL
instances on port 6446. (Bug #21890025)

* It was possible to save an LDAP configuration even if the values in
the LDAP Server Password and Confirm Password did not match. (Bug
#21818107)

* MySQL Enterprise Monitor did not use SSL when communicating over
port 465. (Bug #21771863)

* It was not possible for MySQL Enterprise Monitor Agent to monitor
MySQL versions 5.7.0 to 5.7.8. As of this release, it is possible to
monitor those versions. (Bug #21746553)

* Under certain circumstances, Event handlers created in a Japanese
locale generated an error. The event handler was created, but was
not visible on the Event Handling page. (Bug #21677510)

* On Windows platforms, the MySQL Enterprise Monitor Agent service
name was not removed from the services list when the MySQL
Enterprise Monitor Agent was uninstalled. As a result, if the MySQL
Enterprise Monitor Agent was reinstalled, the installer prompted for
a new service name, because the default name was still in use.

* Queries which required SUPER were retried with the General and
Limited users if they failed.

As of this release, all configured users are checked to ensure they
have the correct privileges. If they do not have the required
privileges, the connection is regarded as a bad connection and added
to the Bad Connections list on the MySQL Instances dashboard.

* The MySQL Enterprise Firewall status variable
Firewall_access_suspicious was not included.

* Under certain circumstances, for remotely monitored replication
topologies, the agent was unable to detect master/slave
relationships based on the UUIDs of the instances. This occurred if
the hostnames of the instances were not resolvable and the detection
process fell back to the UUIDs.

* A file not found exception was displayed in the
mysqlenterprisetomcat-stderr.log for the logging.properties file.

* When monitoring MySQL 5.7.x, the following Replication advisors did
not generate any events:

- Slave Detection Of Network Outages Too High

- Slave Master Info/Relay Log Info Not Crash Safe

* No values were retrieved for innodb_max_dirty_pages_pct and
innodb_max_dirty_pages_pct_lwm variables on MySQL 5.7.7, or higher.

* Critical events were generated when monitoring MySQL 5.7.x due to
changes in the mysql.user table.

* All SHOW STATUS WHERE and SHOW VARIABLES WHERE queries from MySQL
Enterprise Monitor Agent returned errors on MySQL 5.7.7.

Options: ReplyQuote


Subject
Views
Written By
Posted
MySQL Enterprise Monitor 3.0.25 has been released
3558
November 05, 2015 02:14PM


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.