Functionality Added or Changed
Graphs that are produced on the Dashboard pages can now be saved
.csv format (the raw data for the
.png format (an image file showing
the rendered graph). Where graphs are displayed on the
Monitor, Graphs, and
Query Analyzer pages, 2 icons to the right
of the graph title let you export in these formats. Hover over
the icon to confirm which one corresponds to which format. Since
.png files typically display in the browser
rather than bringing up a Save dialog, either click the icon and
save the image file on the resulting page, or bring up the
context menu for the icon and choose Save linked
file or the equivalent for your browser. (You might
need to change the extension to
.png in the
(Bug #11754772, Bug #46431)
The method of evaluating functions and expressions now uses the Java Expression Parser. The available choices are different. If you use custom rules with functions that are not implemented under the Java Expression Parser, file a service request with the requirement. For details, see Section 4.1.3, “Overview of Rule Creation”.
A new option,
, within the
agent-instance.ini configuration file, lets
you specify a schema other than
which to create the inventory table that records the UUID for a
Oracle has discontinued support for the Intel Itanium platform. We plan to discontinue building MySQL Enterprise Monitor service manager and agent binaries for this hardware platform.
Per the Oracle/MySQL Support Lifecycle policy regarding ending support for OS versions that are obsolete, have reached end of life, or have little usage pattern, we plan to discontinue building MySQL Enterprise Monitor agent binaries for certain operating systems.
See http://www.mysql.com/support/eol-notice.html for details of these EOL announcements. (Bug #12565806)
Query Cache Has Sub-Optimal Hit Rate rule
was updated to avoid false positives on systems with little
query activity. The rule only triggers an alert when a
significant amount of data is held in the query cache memory.
(Bug #12543416, Bug #61111)
When using variable substitution for Alerts, now you can
substitute in all fields using the GUI. Formerly, substitution
was only allowed in the
Recommended Action fields.
The “Excessive Number of Long Running Processes”
rule was updated to also ignore the
Waiting for master
to send event and
Has read all relay log;
waiting for the slave I/O thread to update it
replication thread states, as these are also classed as idle
(Bug #12531640, Bug #61081)
messages could be logged if the current “active”
alarm was already closed, especially if the alarm was scheduled
to be automatically closed.
The Update installer for the Service Manager did not back up all original directories. The following files and directories were missing from the backup:
./version.txt ./mysql/docs/* ./mysql/man/* ./mysql/README ./mysql/sql-bench ./mysql/ssl
If you made any changes to the file
those changes are now preserved during an upgrade install of the
When uninstalling the Agent from an OS X system, some files and directories could be left behind if the installation directory was an external (that is, mounted) disk. The following items remained behind:
Info.plist MacOS Resources
The “MyISAM Indexes Found with No Statistics” rule
gave incorrect warnings for the
performance_schema tables in MySQL 5.5.
Rather than writing the user name and password into the
configuration_report.txt file, the
installer now writes a placeholder value using asterisks. Make
sure to record these credentials yourself at the time of the
install. If you remove that report file, the upgrade installer
now handles that situation gracefully rather than reporting an
(Bug #12407359, Bug #60984)
Key Buffer Size Greater Than 4 GB and
Key Buffer Size May Not Be Optimal For System
RAM rules were updated to take in to account that the
key_buffer_size variable can now be set to
greater than 4GB on 64-bit Windows systems.
(Bug #12407351, Bug #60991)
The “Prepared Statements Not Being Used
Effectively” rule was updated to look at the status
variables relating to SQL-based prepared statements
EXECUTE, and so
on) rather than API-based (for example,
mysql_stmt_prepare()) status counters.
(Bug #12402871, Bug #60919)
Workaround to improve the performance of data collection queries on systems with partitioned tables. For the Schema advisors, the following rules cannot be run against any instances that contain partitioned tables:
Tables Found with No Primary or Unique Keys MyISAM Indexes Found with No Statistics AUTO_INCREMENT Field Limit Nearly Reached
The rule “Root Account Can Login Remotely” could
give an incorrect warning on MySQL 5.5, if the root account
logged in using the local specification
(for the IPv6 loopback interface).
(Bug #12325490, Bug #60697)
The “Tables Found with No Primary or Unique Keys”
rule gave incorrect warnings for the
performance_schema tables in MySQL 5.5.
(Bug #12325487, Bug #60695)
On Solaris, the Agent could crash with signal 11 while accessing
a mounted file system, then get a
DuplicateAgentUuidException upon immediate
Upgraded the bundled MySQL instance to 5.1.56. (Bug #11897189)
For several alerts, the titles mentioning “Security
Alterations” were clarified to reflect that they are
related to MySQL privileges The advice now points to a view of
Query Analyzer that filters for
(Bug #11766681, Bug #59846)
The new properties
were added to the Connector/J plugin. The
property is no longer needed.
(Bug #11766637, Bug #59786)
If the value for
missing or incorrect in
mysql-monitor-agent.ini, the Agent could
crash, and crash repeatedly as it was restarted.
(Bug #11766371, Bug #59471)
Performing the action
Delete Servers, when no
servers were selected, would return a popup box with the text
(Bug #11766054, Bug #59087)
Agent Memory Usage Excessive advisor
reported a value for memory used that was too low. Now the
reported value includes the memory used by the Lua scripting
language within the Agent.
(Bug #11765326, Bug #58284)
Disk IO Usage and
Usage graphs are now available on Solaris systems.
(Bug #11764734, Bug #57598)
The types for the
collection items were changed to the string/varchar type to
reflect changes within MySQL 5.5.
(Bug #11764502, Bug #57340)
Removed references to the discontinued MySQL 6.0 release from
Row-based Replication Broken For UTF8 CHAR
Columns Longer Than 85 Characters.
(Bug #11761878, Bug #54410)