Functionality Added or Changed
The inventory update load has been reduced, thereby reducing the overall load on the system. (Bug #18671895)
The name of the agent is now displayed in the Delete Connection dialog for bad connections. (Bug #18361685)
The agent.sh/agent.bat help output has been improved. (Bug #17592046)
The Problem Description text of the Binary Log Debug Information Disabled advisor was updated.
As of this release, the HTTP connection between agent and
Service Manager has a default timeout of 250 seconds for an
attempted connection and 300 seconds for an established
connection. It is possible to override these values in
bootstrap.properties using the following
http-connect-timeout-ms=N: Where N is the number of milliseconds to wait before timing-out a HTTP connection attempt.
http-socket-timeout-ms=N: Where N is the number of milliseconds to wait before timing-out a HTTP socket read or write.
If set to zero (0), no timeout is defined. Negative values are not supported.
The MySQL Enterprise Monitor Agent installer assumed umask=0022. If a more restrictive permission set was used, such as umask=0077, the agent failed to start. (Bug #18867946)
The y-axis of the Slow Queries graph was incorrectly labelled Queries/Minutes. As of this release, it is correctly labelled Queries/Seconds. (Bug #18748920)
It was not possible to establish socket connections on x86-based Solaris or FreeBSD systems. (Bug #18711927, Bug #18531354)
The agent failed to restart if the backlog was corrupted. As of
this release, the agent checks the status of the backlog on
startup and, if the backlog is corrupted, backs it up to a
backlog.xxx directory. The agent logs the
error and creates a new backlog, replacing the corrupted
Agents could not auto-discover running MySQL instances on Solaris platforms.
For the agent to auto-discover the running MySQL process on Solaris, it must run with the same rights as the user running the MySQL process.
The Service Manager did not automatically reflect Daylight Savings Time. (Bug #18384580)
Agent queries failed if they were run on a MySQL instance with sql_mode="ONLY_FULL_GROUP_BY". An error was returned.
As of this release, the agent sets the sql_mode to STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION automatically. The agent checks to ensure sql_mode is set correctly. If sql_mode is not set, an error is logged. (Bug #18308706)
The agent did not read the master-file-info parameter of a replication slave's configuration. As a result, the slave was not displayed in the MySQL Enterprise Monitor User Interface. (Bug #18198992)