MySQL Enterprise Monitor 8.0 Release Notes

7 Changes in MySQL Enterprise Monitor 8.0.1 (2018-07-24)

Functionality Added or Changed

  • The usability of the Context and Target selection fields has been improved. As of this release, you can select a group or asset from the list or by searching for the name of a group or asset.

    The view is no longer refreshed after making a selection in the Global Summaries field. As of this release, the filter is not applied until you select an asset from the All Targets field. (Bug #27019694)

  • It is now possible to delete entries from the MySQL Enterprise Monitor inventory. Deleting assets from the MySQL Enterprise Monitor 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, and instances which were monitored, but are no longer in use.

    Ensure the asset or group is either not running, or not installed, before attempting to delete it from the MySQL Enterprise Monitor inventory.

    For more information, see Deleting Assets from the Command Line. (Bug #26981023)

  • The Oracle JavaScript Extension Toolkit (JET) is upgraded to version 4.2.0 in this release.

  • The installers were updated with improved Japanese and Chinese translations.

    Also, to better support Japanese installations, the configuration_report files, generated by the installer, now use the utf8 character set.

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

  • The MySQL server, bundled with MySQL Enterprise Service Manager, has been upgraded to MySQL 5.7.23.

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

Bugs Fixed

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

  • Changes to the Query Analysis Reporting advisor's configuration were ignored by the built-in agent of MySQL Enterprise Service Manager. The changes were created correctly, but the built-in agent continued using the default schedule and configuration.

    Important

    This issue affected the built-in agent of MySQL Enterprise Service Manager only. It did not affect the standalone MySQL Enterprise Monitor Agent.

    For information on this distinction, see MySQL Enterprise Monitor Component Overview.

    (Bug #27986851)

  • MySQL Enterprise Service Manager always used the default data purge values, regardless of what values were specified. (Bug #27869486)

  • MySQL Enterprise Monitor Agent parsed all name=value pairs, even if they were inside comments, or outside legal config sections in a Cluster config.ini.

    As of this release, only configuration values in legally defined sections are parsed. (Bug #27844552)

  • The Query Analyzer's Configure Query Analyzer link did not link to the Query Analyzer advisors. (Bug #27844552)

  • It was not possible to add or remove sparkline graphs from the Global Overview. Also, an error was logged if the Reset to Default button was clicked. (Bug #27733748)

  • If a range was selected on the graph for a single instance, and the Query Analyzer was opened from the selected range, the single instance selected was replaced by All Targets context selection when the view reloaded. (Bug #27268314)

  • The plus character (+) was added to search criteria on the Query Analyzer filter's Value field. These characters were added if a search was performed, the Details page was opened for one of the search results, then the Query Analyzer page was opened again.

    For example, searching for INSERT INTO `mem__quan` resulted in the string INSERT+INTO+`mem__quan`.

  • The agent upgrade option, --ignore-old-proxy-aggr was present in the MySQL Enterprise Monitor Agent and documentation. The upgrade from MySQL Enterprise Agent Proxy Service 2.3 is no longer supported.

  • If the configuration of the Query Analysis Reporting advisor was changed, for example by disabling, then re-enabling, the Example Query or Explain, the Auto-Explain Threshold value was set to zero instead of to the default value of 100 milliseconds. This resulted in an error and no new queries were displayed on the Query Analyzer.

  • The Example Statements configuration message, displayed if EXAMPLE/EXPLAIN query was not enabled, incorrectly referenced performance_schema_events_statements_history_size instead of performance_schema_events_statements_history_long_size.

  • The bottom of the Query Analyzer Details dialog was truncated by the bottom of the screen if the Graphs tab was selected, making it impossible to close the dialog.

  • The graph range controls on the Query Analyzer graphs, Cancel selection, Query Analysis, and Zoom to selection were visible, overlaid on the Statement Details dialog.

  • If the data retention policy was set to zero, or a negative value, and MySQL Enterprise Service Manager was upgraded, the upgraded MySQL Enterprise Service Manager failed to start.