It is not possible to upgrade to MySQL Enterprise Monitor 3.4 from versions preceding MySQL Enterprise Monitor 3.1. To upgrade an older version, you must first upgrade to MySQL Enterprise Monitor 3.1 before running the MySQL Enterprise Monitor 3.4.0 upgrade process.
The upgrade installer generates an error if you attempt to upgrade an older version to 3.4.
As of this release, only MySQL Server 5.7.9, or higher, is supported for the MySQL Enterprise Service Manager repository. If you are using an external repository, not the version bundled with the MySQL Enterprise Service Manager installer, you must upgrade it to at least MySQL Server 5.7.9 before upgrading your MySQL Enterprise Service Manager to 3.4.
The installers generate an error if you attempt to use a MySQL Server version older than 5.7.9.
MySQL Enterprise Service Manager 3.4's bundled repository is MySQL Server 5.7.18.
Important Change: Graph performance for long-period graphs is improved. Timeseries data is aggregated, allowing for faster data retrieval.
If you upgrade to MySQL Enterprise Monitor 3.4.0, all existing timeseries data is aggregated when the MySQL Enterprise Service Manager first starts. A progress bar is displayed on the Overview dashboard indicating the completeness of the aggregation process.Note
While the timeseries data is being aggregated for the first time, no performance enhancements are evident in the graph response times. Performance improvement is evident only after the process completes and the timeseries data is retrieved from the new, aggregated data.
Important Change: The page-loading times of the MySQL Enterprise Service Manager user interface are improved.
Important Change: The Replication dashboard is extended to provide monitoring support for Group Replication, introduced in MySQL Server 5.7.17.
The Topology view provides a visual representation of your group replication topologies and the Status drilldowns are updated with Group Replication-specific information. The status of the entire group is reported on, including node-failure tolerances and whether the group has quorum.
In addition, new replication advisors, Group Replication Configuration and Group Replication Status, provide continuous analysis of the condition of your group replication topologies. The configuration advisor analyzes the configuration of the servers, checking for misconfigurations which could lead to unstable or insecure installations, and the status advisor continuously monitors for servers which go offline, or fall out of sync with the other members of the cluster.
The group replication advisors also populate the following group-level graphs:
Group Replication - Transactions Rows Validating - Per Member
Group Replication - Transactions Checked - Per Member
Group Replication - Conflicts Detected - Per Member
Group Replication - Transactions In Queue - Per Member
It is now possible to define filter intervals of three, six, and nine months, and one, or two years in the Timeseries and Query Analyzer graph filters. (Bug #11746539)
super_read_onlyvariable is now represented in the Replication dashboard's instance drilldowns. The configured value is displayed in the Replication Configuration section.
The backup bar charts, Backup Run Time History and Backup Lock Time History, are replaced by Full Backup Run Time History and Incremental Backup Run Time History timeseries graphs. The run and lock time information is now displayed in the full and incremental backup graphs.
The Account Has An Overly Broad Host Specifier advisor is removed in this release. Its functionality is included in the new MySQL User Account security advisor. This new advisor also enables you to exclude users from event generation using regular expressions.
The documentation erroneously stated that SSL certificates which existed in the previous installation must be manually imported after an upgrade.
The upgrade creates a backup of any existing SSL certificates and imports them into the upgraded version as part of the upgrade process. (Bug #25833748)
MySQL Enterprise Service Manager stopped responding if a custom graph was imported, and the graph's definition included a hyphen (-) in the name.
If a service restart was attempted, an
Unexpected tokenerror was logged and Tomcat would not start. (Bug #25761280)
MySQL Enterprise Monitor Agent and MySQL Enterprise Service Manager configuration utilities did not clearly state that they must be run while MySQL Enterprise Monitor Agent and MySQL Enterprise Service Manager are stopped.
The documentation was also updated with this information. (Bug #25697013)
Network speeds were incorrectly reported on the Network Interfaces table of the MySQL Instances dashboard. (Bug #25636784)
OS X 10.12 Sierra was not recognized and was listed as Unknown. (Bug #25511036)
It MySQL Enterprise Monitor Agent encountered an error, it failed to restart due to a permissions issue. The
mysql-monitor-agent.pidran as root and could not be stopped by the
agentrestart.shwhich runs under the same user as MySQL Enterprise Monitor Agent.
As of this release, the
mysql-monitor-agent.pidis created with the permissions 644 (-rw-r--r--). (Bug #24667408)
On Windows platforms, it was not possible to install to a path which contained spaces on any drive other than the C:\ drive.
For example, trying to install to
D:\Program Files\MySQL\Enterprise\Monitorfailed, while
C:\Program Files\MySQL\Enterprise\Monitorsucceeded. (Bug #24482872)
The MySQL Enterprise Monitor Agent was not properly displayed as running and monitoring an instance. This occurred if it was stopped and it's monitored instance removed from the MySQL Instances dashboard, and then the MySQL Enterprise Monitor Agent was restarted.
Empty groups were not displayed on the Advisors page.
It was not possible to edit a replication group's description. The change was not saved.
A number of minor UI issues were corrected in this release. Issues such as double colons (::) in the system uptime frame, duplicated icons on buttons, and so on.
If an instance was renamed on the MySQL Instances dashboard, the instance name was not updated immediately elsewhere in the user interface.
The backup bar charts, Backup Run Time History and Backup Lock Time History, displayed extra zeroes after an upgrade from MySQL Enterprise Service Manager 3.2 to 3.3 or 3.4.