Functionality Added or Changed
The new Aggregator component accepts Query Analyzer data from any source.
The “What's New?” page integrates with My Oracle Support service, in addition to the MySQL Enterprise web site.
There is a new advisor and corresponding graph for MySQL Cluster.
There is a new advisor and corresponding graph for network and disk I/O.
There is no longer a requirement to enter a license key.
There is a new advisor and corresponding graph for InnoDB Plugin.
Query Analyzer, Replication monitoring, and all rules and graphs are now available to all licensed users. See http://www.mysql.com/products/ for details.
When MySQL Enterprise Monitor truncated the legacy data
collection tables, such as
dc_ng_long_now, the disk space was not
released back to the operating system, even if the
was enabled. Now, the disk space is released correctly, for all
combinations of MySQL with or without the InnoDB Plugin.
User Search Pattern when defined in
Bind as User method of
authentication overrode the
User Search Attribute
Pattern method, even though it shows as greyed out.
--skip-locking option for the
embedded MySQL server was being used in place of the
The embedded OpenSSL has been updated to version 0.9.8o. (Bug #55949)
The CA certificate files
myKeystore are now backed up during the
upgrade process, and their file locations are stored within
(Bug #55505, Bug #11762859)
If identical JSON-format data was submitted to the Aggregator within the same 60-second window, the counts displayed on the Dashboard could be incorrect. (Bug #54669)
The data reported for the binary log file size (in
erroneously reporting the count of the files, not the sum of the
size of the binary logs.
The list of active support issues on the What's New page has been updated to not show issues that are stale, and to not show issues if you have disabled the support issue checks. (Bug #54600)
Monitoring a database with a large number of tables would lead
to long queries on
could lead to operating system memory graphs not being updated
The MySQL Enterprise Monitor Agent installer would ask for agent credentials, even if you had indicated that the correct user credentials had already been created. (Bug #53943)
config.properties file, which can
contain sensitive information, is world-readable, the server
issues a warning message and does not start.
The timeout for information being supplied through the aggregator was too high, leading to a failure to identify that the aggregator was unavailable. (Bug #52280)
The installer dialog for the text installation for MySQL Enterprise Monitor Agent would show a blank password prompt when asking for confirmation of the root password. (Bug #52129)
With the setting
log-level=debug, the JSON
data in the Aggregator log is now formatted.
If the output from the
SHOW ENGINE INNODB
STATUS command is truncated because it exceeds the
size limit, and MySQL Enterprise Monitor cannot get information
about all InnoDB transactions, now a message is printed to the
agent log. To avoid the possibility of the status information
being truncated, enable the
MySQL Enterprise Monitor gets the status information from this
file if it is available. The status file is not subject to a
maximum size like the
SHOW ENGINE INNODB
The file permissions on the
within the MySQL Enterprise Service Manager installation would not be set
correctly on Mac OS X.
Added regex parsing for the new InnoDB plugin, as features
SHOW INNODB STATUS would output