Changes in MySQL Enterprise Monitor 8.0.14 (2019-01-21)

Important

It is not possible to upgrade to MySQL Enterprise Monitor 8.0.14 from versions preceding MySQL Enterprise Monitor 3.4. To upgrade an older version, it is recommended you first upgrade to MySQL Enterprise Monitor 4.0 before running the MySQL Enterprise Monitor 8.0.14 upgrade process.

MySQL Enterprise Service Manager 8.0.14 bundled repository is MySQL Server 8.0.14.

• MySQL Product Versioning

• Functionality Added or Changed

• Bugs Fixed

MySQL Product Versioning

• Important Change: Beginning with version 8.0.14, MySQL Enterprise Monitor is now aligned with the version number of the MySQL product line. Version numbers 8.0.4 to 8.0.13 are skipped.

Functionality Added or Changed

• Important Change: It is now possible to delete obsolete or unused assets from the MySQL Enterprise Monitor inventory using the user interface.

  Important

  Deleting assets from the inventory does not delete or uninstall assets from their installed locations. The delete process removes all record of an asset or group of assets from the internal record of MySQL Enterprise Service Manager, only. This enables you to remove entries for clusters, topologies, agents, hosts, and instances which were monitored, but are no longer in use.

  For more information, see Deleting Assets (Bug #26805727)

• Important Change: The MySQL server, bundled with MySQL Enterprise Service Manager, has been upgraded to MySQL 8.0.14.

  Important

  It is strongly recommended you backup your existing MySQL Enterprise Monitor repository, and test the backup, before upgrading to MySQL Enterprise Monitor 8.0.14.

  The following MySQL 5.7-specific configuration parameters have been removed from the MySQL configuration file included with the bundled repository. These parameters were removed because they are either obsolete and no longer used by MySQL 8, or because the values defined by them are now defaults in MySQL 8.

  • default_storage_engine=INNODB

  • default_tmp_storage_engine=INNODB

  • event_scheduler=ON

  • explicit_defaults_for_timestamp=1

  • sql_mode=STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION

  • innodb_file_format=Barracuda

  • innodb_file_per_table

  • innodb_support_xa=0

  • innodb_adaptive_flushing=1

  • innodb_locks_unsafe_for_binlog=1

  • skip_external_locking

  • local_infile=0

  • --skip-symbolic-links

  • performance_schema

  For more information on parameters added, changed, deprecated, or removed in MySQL 8, see What Is New in MySQL 8.0.

  The MySQL X plugin is disabled by default. If enabled in an existing configuration, the upgrade process disables it.

  log-bin is disabled, by default, by setting --skip-log-bin. If you enabled log_bin, your setting is preserved by the upgrade process.

  It is recommended you backup your configuration before upgrading.

• Important Change: New asset views are added in this release. These asset views enable you to examine, in detail, the configuration and status of Agents, Hosts, and NDB Clusters.

  For more information, see Asset Management

• Important Change: As of this release, to install MySQL Enterprise Monitor on Solaris platforms, you must install the Oracle Developer Studio 12.6 Runtime libraries first. If the installer does not detect those libraries, the installation displays an error and cannot proceed until the prerequisite libraries are present.

• A new configuration view filter form is added in this release. It is used by the Query Analyzer, and the Agent, Hosts, and NDB Cluster asset views.

  These views enable you to define default viewing options such as graphs, filtering, and sorting.

  For more information, see Configuration Views. (Bug #18203424)

• The user interface of the Query Analyzer has been completely redesigned. Building upon Oracle's JavaScript Extension Toolkit (JET) framework, this new design improves navigation in the Query Analyzer and introduces advanced configuration options which enable you to customize, sort, and filter the data displayed.

  For more information, see Query Analyzer User Interface. (Bug #18203339)

• The bundled JRE was updated to 1.8.0_202 for both the Agent and Service Manager.

• As of this release, performance-schema-consumer-events-statements-history-long is enabled on the bundled repository. If you are using an external repository, you must enable this consumer by adding the following to your MySQL configuration file:

          performance_schema_consumer_events_statements_history_long=ON

• The OpenSSL libraries used by the MySQL Enterprise Monitor installers and have been upgraded to 1.0.2q.

Bugs Fixed

• The documentation describing the Active Directory configuration incorrectly stated that a port was required in addition to the hostname. The port is 389 and cannot be altered. (Bug #29173152)

• In certain circumstances, MySQL Enterprise Service Manager did not start after upgrading from version 3.4 to version 8.0. The error cannot determine singular foreign key name for normalized_statements_by_server_by_schema was logged. (Bug #28938022)

• The documentation describing the logic of replica promotion to source was incorrect. (Bug #28905972)

• It was not possible to remove the CPU Utilization - Mysql Server - CPU graph from the Overview if only a single instance was selected. (Bug #28794385)

• Several Advisor tooltips contained broken links and links pointing to outdated content. (Bug #28171028)

• The graph range selection controls (Cancel selection and Query Analysis) were visible through any menu or dialog which overlaid the selection. (Bug #17555151)

• It was not possible to use the percentage character (%) in filter names. The filter was saved and was displayed in the list of available filters, but did not display the configured data when selected.

• Automatic page refresh did not pause if an asset was selected.

• Null Pointer Exceptions were logged relating to Query Analysis and Explain Plan when monitoring MySQL 8. These exceptions were caused by the removal of EXPLAIN EXTENDED in MySQL 8.

  As of this release, MySQL Enterprise Monitor checks which MySQL version is being monitored and only attempts to use EXPLAIN EXTENDED on versions which support it.

• The vertical scroll bar did not behave as expected in Microsoft Internet Explorer 11. No other browser was affected by this issue.