We now log less-verbosely in user-facing logs
mysql-monitor-agent.log), but include stack
traces in logs with file names like
mysql-monitor-log-full.log (note the string
"-full"). The full log files are useful for customer support and
(Bug #17636944, Bug #17561327)
The Agent now creates new
table entries using the string "hostid" instead of "hostId", as
it was written in MySQL Enterprise Monitor 2.3.x.
The MySQL Enterprise Backup Succeeded Advisor did not function, as it would not report that a backup had succeeded. (Bug #17626850)
Binary logging of the CREATE/GRANT statements issued by the Agent are now disabled when auto-managing users, as binary logging would potentially cause replication failures. (Bug #17656497)
The LDAP login form was not available in the MySQL Enterprise Monitor User Interface unless the LDAP Server Allows Anonymous Binds option was selected. (Bug #17607700)
isServerDown system check could generate
Disabling LDAP authentication did not function. (Bug #17607791)
Extra newlines were removed from Replication Advisor email subject lines, which caused rendering problems for some email clients. (Bug #17536761)
The Replication Status Advisor would not
always generate an event when the
command was issued. The
Slave Has Stopped
Replicating event is now generated.
A log entry was added that logs when the MySQL Enterprise Monitor application started. The log entry reads similar to "2013-10-27 12:12:49,395 INFO [...] Oracle MySQL Enterprise Monitor version 3.0.3.xxxx started". (Bug #17595743)
The replication topology discovery process would fail when two or more unmonitored masters were found. An exception would be generated that caused the MySQL Enterprise Service Manager to not start. (Bug #17588575)
The Query Analyzer link did not function for some OS related graphs, such as CPU Usage graph. (Bug #17544163)
While attempting to monitor a new MySQL instance with the built-in Agent, the Monitor From field would be blank and not show the built-in Agent when MySQL Enterprise Service Manager did not recognize the host. (Bug #17469739)
When installing MySQL Enterprise Service Manager as root, the "Configuration Report" would wrongly declare that a startup script could not be created because it requires the root user, when in fact the startup script was installed. (Bug #17470643)
Corrected the default From/To time filter for the Query Analyzer and All Timeseries Graphs pages. (Bug #17474880)
Double-clicking on an Advisor is now ignored, as to avoid unexpected behaviors, like generating duplicate details. (Bug #17471416)
After renaming a MySQL Server hostname on a box, and then restarting MySQL, the changed name did not show up on the MySQL Enterprise Monitor User Interface.
The Display Name will remain as is, but the Monitor From drop-down value will update to the new hostname. (Bug #11751801)
On Mac OS X, an "Unknown memory pool Tenured Gen" message could be logged every minute, thus cluttering the log file.
Additional MySQL Enterprise Monitor User Interface elements were translated to Japanese.
The down arrow button now correctly activates additional selection lists, such as the Refresh dialog.
Uninstalling an upgraded (2.3.x to 3.0.x) Agent did not remove the old (2.3.x) log and installation directories, as the upgrade process does not delete them. Running the installer now removes these directories.
The bundled MySQL Server was upgraded to 5.6.14. The previous version, in MySQL Enterprise Monitor 3.0.2, was a patched 5.6.13.
When a monitored MySQL instance went down, the monitor log was
exceptions. These error messages are now grouped.
On POSIX-based systems, the Agent Installer now checks and
ensures that the
custom.xml file is only
writable by the Agent user.
On Microsoft Windows, only Administrators can edit
On POSIX-based systems, an Agent now only reads the
custom.xml file if this file is owned and
only writable by the user that is running the Agent.
Column re-sizing was enabled in the MySQL Instances Details view from the MySQL Instances page.
glibc2.3- was removed from the
Agent Installer file names.