We are pleased to announce that MySQL Enterprise Monitor 3.0.8 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
April 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:
(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.8
Functionality Added or Changed
* The performance of the Data Purge Behavior has been improved.
In previous releases, the data purge executed all DELETE statements
before committing, which could result in a very large, final
transaction. As of this release, each DELETE is committed
individually. (Bug #18482800)
* It is now possible to configure the LDAP connection timeout values.
The following were added to the LDAP Authentication frame of the
Global Settings page:
- Connect timeout: time elapsed without establishing a connection to
the LDAP server. If a connection is not established within the
defined number of seconds, an error is returned.
- Read timeout: time elapsed without a response to a request for
data from the LDAP server. If no response is received within the
defined number of seconds, an error is returned.
Note: If the value is set to 0, the timeout value defaults to the
operating system's default value.
* The Group Overview Configuration toolbar enables you to define the
period for which data is displayed in the timeseries graphs on the
Overview dashboard. It also enables you to specify a default group
of MySQL instances.
* Under certain circumstances, the defined event handlers were not
displayed in the MySQL Enterprise Monitor User Interface. This
occurred if one or more event handlers were used to monitor an
automatically-created replication group which was deleted. If the
instances which made up the replication group could not be detected,
the replication group was deleted in MySQL Enterprise Service
As of this release, if all instances which make up a replication
group are deleted, the replication group monitored by MySQL
Enterprise Service Manager is not deleted, but is displayed with the
following naming convention: Non-existent Replication Group (id=
NNNN), where NNNN is the unique ID of the replication group.
Important: Non-existent replication groups must be removed manually
* The MySQL Enterprise Monitor Agent started as root instead of
starting as the mysql user if the mysql user was defined in
As of this release, the initialization script checks for non-local
users. (Bug #18392067)
* It was not possible for MySQL Enterprise Service Manager 3.0.0 to
use a MySQL Enterprise Monitor Agent of version 3.0.4 or higher. The
agent returned a Null Pointer Exception on start-up.
Important: It is recommended that you upgrade both MySQL Enterprise
Service Manager and MySQL Enterprise Monitor Agent to their most
recent versions to avail of all fixes and enhancements.
* The upgrade process changed the properties of the files backed up in
the backup directory. As a result, if the installation was reverted
to a previous version, the local repository would not start.
As of this release, the properties of these files are not altered
during the upgrade's backup process. (Bug #18341449)
* The full and upgrade installers did not correctly check for
available disk space.
As of this release the installers use the following formula:
- Full installation: Free Space - Installation Size - Extra Space > 0
- Upgrade: Free Space - Backup Space - Installation Size - Extra
Space > 0
- Free Space = the amount of space available on the target disk.
- Installation Size = the amount of space required by the product
- Extra Space = a hardcoded buffer of 500MB.
- Backup Space = the amount of space required to backup the previous
installation. This value can be very large.
* The y-axis labels for the following graphs did not display correctly
for large negative values, more than one hour, or very small
negative values, less than one second:
- Replication Slave Delay
- Agent Latency
(Bug #18312245, Bug #71685)
* The tooltips for several advisors contained broken links, or links
to outdated content. (Bug #18288215)
* If a time difference existed between the MySQL Enterprise Service
Manager and the monitoring agent servers, the agent was reported as
SHUTDOWN or TIMEDOUT, although the agent was still running. As of
this release, if a time difference exists, but the agent is still
collecting and transmitting data to the MySQL Enterprise Service
Manager, the agent is reported as active.
Important: It is recommended that you synchronise the MySQL
Enterprise Service Manager server, and all monitored servers, with
the same time server.
* In previous releases, the upgrade process did not correctly stop the
running Tomcat process. This could result in multiple running Tomcat
processes after the upgrade completed. As of this release, the
upgrade process stops the Tomcat process and the jsvc process which
Note: This issue also affected the upgrade's backup process.
* Under certain circumstances, when monitoring a large number of
servers in the MySQL Enterprise Service Manager browser interface, a
memory management issue occurred. As a result, the browser consumed
a large amount of system resources and performance was reduced. (Bug
* The following enhancements have been made to the MySQL Enterprise
Monitor Agent to improve the MySQL Enterprise Service Manager start-
- Delta Quantizer logging has been moved to the debug log-level.
- The number of default backlog reporting threads has been reduced
to 4. This option can be configured in the data-reporting-threads
parameter of the bootstrap.properties configuration file.
* In previous releases, if the monitored server was under heavy load,
the monitoring agent was unable to collect data at the defined rate.
As a result, gaps were displayed in the Query Response Time Index
As of this release, while it is still possible for such gaps to
occur, their occurrence is greatly reduced by improvements to the
agent's performance. (Bug #17733081)
* A Null Pointer Exception was generated if the Query Analyzer
received EXPLAIN data which was either incomplete or invalid. As of
this release, the incomplete data is logged.
* The units used in the Filesystem Usage Change Rates graph were
* Null values were displayed in the Filesystems section of the MySQL
Instance Details dashboard. This occurred for certain types of
pseudo-filesystem, such as /proc, and for network filesystems. As of
this release, these values are not displayed.
* CPU graph data was not properly stored in the Service Manager
repository after the MySQL Enterprise Service Manager was upgraded.
As a result, some graphs, such as the CPU Utilization graph,
displayed gaps. It was necessary to restart the monitoring agent to
restore the graphs to normal. As of this release, the CPU-related
data is not dropped after an upgrade.
* Under certain circumstances, it was not possible to generate Support
Diagnostics for a remotely monitored instance. A Null Pointer
Exception was returned.
* The URL displayed at the end of the MySQL Enterprise Service Manager
installation was incorrect.
|• MySQL Enterprise Monitor 3.0.8 has been released||andy bang||2 Apr|