Functionality Added or Changed
Using IPv6 with the Connector/J plugin would fail, and report an invalid URL.
A "Bad Connection" could not be edited or deleted for MySQL instances that shared the same port on a host. (Bug #17451053)
Several Advisors and graphs from 2.3.x were missing from 3.0.0. (Bug #17436378)
Under rare circumstances, a "form.label.graphFromMsec field value "NaN" could not be parsed as type Long" error would be displayed. (Bug #17435024)
The Agent installation attempted to create auto-managed users without first checking for their existence. (Bug #17403800)
If an Agent was started against a 5.6.14+ instance that did not
setting enabled, enabling it later would not enable example
queries to be sent.
On Microsoft Windows, when running MySQL Enterprise Service Manager with a 'Local System' account, a new installation would show three monitored MySQL instances, instead of one. (Bug #17390005)
Installing MySQL Enterprise Service Manager as a privileged user would start the Tomcat server as the same user. (Bug #17369747)
There were performance issues due to thrashing while doing Advisor scheduling with 2.3 and/or 3.0 Agents that were actively communicating with the Service Manager during a new installation or upgrade. (Bug #17342355)
When a MySQL instance's socket was fixed for a bad connection, the MySQL instance remained unmonitored.
A workaround was to restart the Agent. (Bug #17341466)
Graphs without bytes or time-based formatting, such as the Database Activity graph. did not properly round every value. (Bug #17330131)
Filesystem trending would sometimes change directions well into the future, by switching from going up to suddenly going down. (Bug #17328037)
The Asset Selector did not update dynamically, even with page refresh enabled. (Bug #17292486)
log_slow_queries variable was deprecated
in MySQL 5.1. This affected the behavior of the Slow
Query Log Not Enabled advisor which used that
variable in its expression.
bootstrap.properties option was added. It
is defined as a comma-separated path for custom types XML files.
For external Agents, this value is also viewable via the
MySQL Enterprise Monitor User Interface via Advisors, Create
Rule. For the embedded Agent, this is viewable under
the Import/Export Advisor configuration page.
For new Agent installations,
is created. For upgrades from 2.3, the Installer copies
now referenced in
items-mysql-monitor.xml are no longer used,
and were removed.
The order of unmonitored servers on the MySQL instances page would sometimes change when the page was reloaded.
The MySQL Enterprise Monitor Agent installing in unattended mode would fail to install if it discovered and used Java 6 on FreeBSD 9. The Installer will now filter out unsupported versions of Java for both attended and unattended installation modes.
Pressing tab "onto" a menu, such as Settings or Help, would open the menu. Pressing Enter is now required to open a menu.
An Event's details Action Log was potentially confusing regarding SMTP actions, as it could have shown the same target as both successful and failed.
There was a memory leak when shutting down the MySQL configuration thread pool. This disallowed MySQL Enterprise Monitor to be shutdown from within the Eclipse IDE.
Pressing Enter + Tab will now close a tooltip menu window.
On some pages, the Disable links would gain focus when pressing tab.
The main menu items and sub-menus (such as Dashboards and Configuration), tables, behavior controls, and pop-up windows were not tab-focusable, so neither were their sub-menu items.
The calculation of the InnoDB Buffer Pool Usage graph now has a timeout of 2 minutes. If the server can not respond during that time, a message will appear on the screen with the indication to retry the calculation. This can happened because the calculation of the report is asynchronous.
Also, MySQL server versions less then 5.5.28 can not be calculated, and an informational error will appear on the screen to indicate this.
The MySQL Enterprise Monitor Agent installer default changed from "127.0.0.1" to "localhost", as to allow negotiation of IPv6 or IPv4 at the OS layer.
You could not shut down an Agent and then install a new Agent to monitor an existing and previously monitored MySQL instance.
Renaming a username (under User Preferences) to an existing username was not handled gracefully, and would generate an error with a stack trace.