We are pleased to announce that MySQL Enterprise Monitor 3.0.6 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 fixes a number of bugs. You can
find more information on the contents of this release in the change
(also included at the end of this note for convenience)
You will find binaries for the new release on My Oracle Support:
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:
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.
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
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?
MySQL Enterprise Edition: Demos
MySQL Enterprise Monitor Frequently Asked Questions
MySQL Enterprise Monitor Change History
More information on MySQL Enterprise and the Enterprise Monitor can be
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
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.6
Functionality Added or Changed
* An MySQL Instance Identity Source option was added to the MySQL
Process Discovery Advisor. This sets the mysql-identity-source
option which determines how the UUID is defined for a discovered
MySQL instance. (Bug #17986420)
* A search filter was added to the Advisors page. Advisors may now be
filtered by Advisor, Group, and/or Asset name. (Bug #17656494)
* The Agent now watches for changes in log4j.properties every 60
seconds, and applies the changes if found.
* The Duplicate Server UUID Advisor was added. It attempts to find
MySQL instances with the same UUID, and generates an Event if one is
found. An example scenario is when a MySQL instance is cloned to a
different host, but without the cloned MySQL instance's UUID being
updated. MySQL instances with the same UUID are monitored and
reported as a single MySQL instance in MySQL Enterprise Monitor.
* A large Asset Selector would not load in Internet Explorer. (Bug
* Attempting to view a statement history graph in the drill-in details
pop-up for a particular query analyzer statement would return a 404
error, as the corresponding page was renamed. (Bug #18075985)
* Calling mysqlmonitorctl.sh would report an error similar to "su:
illegal option – c" on FreeBSD, Mac OS X, and Solaris. (Bug
* The bundled config.sh / config.bat utility now manually executes
"umask 066", as opposed to executing setenv.sh. This affects the
initial creation of log files. (Bug #18037827)
* On RDS systems, the "super" user lacks privileges to execute SET
SESSION sql_log_bin=0, which causes monitoring to fail. Disabling
the binary log is no longer required when monitoring MySQL server
5.6+, as the server_uuid variable is used instead. (Bug #17995425)
* On Mac OS X, the MySQL Enterprise Service Manager Installer would
install a 32-bit MySQL server on a 64-bit system. (Bug #17936588)
* Deleted Agents would sometimes remain visible in the Events tab's
Asset Selector. (Bug #17985573)
* The Slow Query Log Not Enabled Advisor text was updated, to adhere
to the preference towards and MySQL Server 5.6.1 deprecation of --
log-slow-queries in favor of the --slow_query_log and --
slow_query_log_file options. (Bug #17911633)
* Closing an event from the Events removes the Event entry from the
screen. Before the closed Events would remain visible until the
"Refresh" action was executed. (Bug #17851337, Bug #71003)
* The configuration report for the MySQL Enterprise Service Manager
upgrade installer would incorrectly detect differences between the
MySQL Enterprise Monitor repository and recommended configuration
values, when the configuration setting did not require a value. (Bug
* Caching and resource restraints were added to the LDAP authenticator
for negative responses, which helps reduce the number of service
requests to the respective LDAP servers when clients are failing
authentication. (Bug #17709023)
* The Query Analyzer configuration documentation was improved in the
MySQL Enterprise Monitor User Interface. (Bug #17645857)
* Installing MySQL Enterprise Service Manager no longer creates
separate Service Manager accounts (for the SM repository) with hosts
defined as '::1' and 'Fully Qualified Domain Name', but continues to
use '127.0.0.1' and 'localhost'. (Bug #17559057, Bug #70504)
* The libsigar library was updated so the Agent can build on SLES 10.
* On Mac OS X, general improvements were made to the Agent and Service
Manager Installer for both the upgrade and installation processes,
and the services now automatically start. (Bug #17550529)
* General improvements were made to the impact of gaps in graphs. (Bug
* MySQL Instance Identity Source information was added to the
Diagnostic Report, in query.instanceOverview.html.
* Documentation improvements were made to the Service Manager
configuration step of the Agent Installation wizard.
* Due to performance reasons, MySQL Enterprise Monitor no longer
includes Query Analyzer data in MySQL instance support diagnostic
* The host_plus_datadir value for the mysql-identity-source
configuration option was not preserved in the MySQL Enterprise
Monitor User Interface. Editing a connection would show the default
UUID source option.
* The CPU related graphs and advisors were simplified and improved,
and new statistics (nice, irq, soft irq, and stolen) were added.
* Hovering over a series on a graph now shows the time range for the
point (where appropriate) instead of always showing a specific
* The CPU Advisor did not gracefully handle an operating system
changing the number of CPUs.
|• MySQL Enterprise Monitor 3.0.6 has been released||andy bang||3 Feb|