We are pleased to announce that MySQL Enterprise Monitor 3.0.7 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
January 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-7.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.htmlhttp://www.mysql.com/products/enterprise/query.htmlhttp://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.7
Functionality Added or Changed
* Network file systems, such as NFS, SMB, and CIFS are now supported.
They are displayed in the asset selector and the Advisors
configuration page for filesystem-related advisors. It is also
possible to override their configuration and filter them for
reports, graphs and events. (Bug #18259946)
* It is now possible to edit the Agent CPU Thresholds in the Agent
Health Advisor. The default value for the embedded agent is 40%.
(Bug #18025021)
* The Edit dialog for the following advisors was redesigned for
improved usability:
- Agent Health Advisor
- MySQL Enterprise Backup
- CPU Utilization Advisor
- Filesystem Free Space
The contents of these advisors are now organised using collapsible
sections.
Bugs Fixed
* The Database Availability tooltip for Month displayed the data for
Week instead of Month. The graphs displayed the correct information.
(Bug #18190436)
* Under certain circumstances, NULL was returned if a non-contiguous
list position was encountered, resulting in a NullPointerException.
If this error occurred, the agent stopped monitoring the server.
(Bug #18204794, Bug #18230493)
* It was not possible to display My Oracle Support information in the
Open Support Issues frame on the What's New page due to an issue
with the MOS 6.8 rollout in February 2014. (Bug #18198557)
* Under certain circumstances, for installations with more than 100
agents, the StrategyReplicationManager thread blocked processing of
all agent threads. (Bug #18196843)
* Agents which were active and available were reported as unavailable
if the system was under heavy load. Emergency events were logged as
a result. This issue often occurred after a system restart. (Bug
#18205114)
* Under certain circumstances, a deadlock occurred if a replication
group was renamed. (Bug #18245772)
* Stacked graphs were reset to line graphs if the page was refreshed.
(Bug #18148597)
* Text was displayed incorrectly if the English (Canada) locale was
selected. (Bug #18140344)
* The Support Diagnostics files, generated from the MySQL Instances
dashboard, were very large due to logging of GTID variables which
were constantly changing. This information was also written to the
database, increasing the write load. As of this release, GTID
variables are no longer collected, with the exception of gtid_mode.
(Bug #18180530)
Note: The upgrade process does not delete these entries from
existing logs.
* Under certain circumstances, on Linux systems, the CPU evaluation
results were incorrect. This was caused by a Linux kernel issue,
where the CPU tick counter reset, appearing to go backwards. Based
on this inconsistent data, MySQL Enterprise Monitor inferred a very
high CPU usage and generated false-positive alerts. As of this
release, MySQL Enterprise Monitor does not record such tick resets.
If resets occur, they are represented as gaps in the CPU graph, and
the field and delta values are logged at debug level.
* If an unmonitored master was detected, a group update was repeatedly
performed. As of this release, if an unmonitored master is detected,
the group update is not performed.
* On Mac OS X, the agent reported Mac OS X version 10.9 as "Mac OS X
Unknown".

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.