Functionality Added or Changed
MySQL Enterprise Monitor 2.3.7 includes partial support for the authentication plugins introduced in MySQL 5.5.16. MEM supports using the PAM Authentication plugin in certain configurations:
The MySQL Enterprise Agent can connect to the monitored server using the PAM Authentication plugin for authorization.
MySQL Proxy supports the PAM authentication plugin.
Although none of the Connectors distributed with MEM
currently support MySQL 5.5.16's
applications linked with the
libmysqlclient library can send data
through the Proxy to the Query Analyzer when the PAM plugin
is in use.
MySQL Enterprise Monitor currently does not support the Windows Native Authentication plugin for connections from the Agent or the Proxy.
MySQL Enterprise Monitor now includes a new Connector plugin, MySQL Enterprise Plugin for Connector/PHP. This new feature lets you use the Query Analyzer with PHP-based applications. See Section 3.1.2, “Using the MySQL Enterprise Plugin for Connector/PHP” for details.
Attempts to check the MyOracle Support web site could fail with the message:
There is a problem checking Advisor Bundle updates and My Oracle Support issues. If the machine running the Enterprise Monitor can directly connect to the internet, make sure your My Oracle Support credentials are correct. If there is no direct internet access, you may need to configure an HTTP proxy.
The open/closed state for some nodes in the Server Tree was not remembered correctly when the Server Tree grew to a large number of entries. (Bug #12976291)
Doing an upgrade of the MySQL Enterprise Monitor server overwrites any contents in the library directory of the bundled Tomcat server. Previously, certain files in that directory were preserved during an upgrade. MySQL Enterprise Monitor now bundles the Apache Tomcat Native Library, removing the need for users to add or manage their own files in that directory. (Bug #12972364)
Using non-printable escaped characters in the
agent-mgmt-password field of the Agent
configuration file could cause a crash when starting the Agent.
After installation of the MySQL Enterprise Monitor server, an
attempt to access the dashboard could result in a 404 error,
with error messages in the monitor and Tomcat logs referring to
a bean named
The Agent was upgraded to the MySQL 5.5.16
libmysqlclient library on the Solaris 10 x86
After deleting a large number of servers and associated
schedules, rules, and so on from the Server Tree, the Dashboard
report show an error (
when returning to the main page.
(Bug #11762672, Bug #55294)