Page History

...

• In Monitors page, the small trend charts in current and delta timeframes were not displayed for some monitors.
• Charts were not displayed in Monitors page- History/Trend if data series contained "N/A" values.
• Monyog SQL DM for MySQL was not able to connect to MySQL server if password contained a leading or a trailing empty space.
• In rare cases, some server(s) could stop showing in the UI after Monyog restartSQL DM for MySQL restarts.
• Fixed a rare irresponsiveness ("hang") occurring when starting data collection after editing server details.
• The option to stop the current running saved session was not available in Real-Time in some cases.
• A number of minor GUI fixes.

...

• The Real-Time interface in Monyog SQL DM for MySQL has been completey completely rewritten. In addition to a more consistent/intuitive GUI it is now able to collect data from multiple MySQL servers simultaneously ( one collection of Real-Time data per server). Once data collection for a server has been started it will continue until stopped by user, also if browser connection is closed in between. The sole exception is that Real-Time data collection for a server will stop after 3 days if no activity has happened inside the particular Real-Time session.
• Added an option to set line terminator for csv reports.

...

• Renaming a registered server to a new name already in use would not raise any error. Instead data for the affected server would not display anymore.
• In rare cases clicking 'test SSH settings'-button would not display any response.
• When registering a 'Postmaster Enterprise SMTP server' in MonyogSQL DM for MySQL, mail notifications failed to be sent.
• 'Diagnostics report' failed to download when Monyog SQL DM for MySQL was running behind a HTTP ('reverse') proxy server.
• Clicking on editing SMTP settings from server registration page did not redirect to tools page and thus editing was not possible from here. The problem was alone a problem with the particular hyperlink. From the tools page everyting everything worked as expected.
• The following gtid-related variables in MariaDB 10 could trigger false notifications: gtid_binlog_pos, gtid_binlog_state, gtid_current_pos, gtid_slave_pos and last_gtid.
• Monyog SQL DM for MySQL failed to establish SSH connection to Linux servers using the "OpenSSH-HPN" SSH implementation..
• When an identifier contained digits (such as 'abc12', 'ab12ab' etc.), the Query Analyzer, the WayBack Machine and Real-TIme interface would consider these digits literals, and they would be replaced with '?'.
• If Monyog SQL DM for MySQL did not have sufficient privileges to the MONyog/Data folder, adding a new server could crash MonyogSQL DM for MySQL.

Miscellaneous:

• Dashboard page was renamed to 'Charts'.
• The tab-order of Monyog's SQL DM for MySQL interface has been rearranged.
• Also note that 'WayBack machine' interface is still available (unlike what was the case with the 6.2 beta, where we experimentally removed it.

...

• Fixed a rare SQLite database corruption under very heavy load and with Custom SQL Objects enabled.
• Changing refresh interval setting for Processlist page was not possible for non-admin users.

Miscellaneous:

• Monyog SQL DM for MySQL installed on the Amazon Cloud from the Amazon Machine Image ("AMI") we provide as an option, will now start first time with the Amazon instance ID as the admin password and not an empty password as before. This change could take some days to propagate across the Amazon Cloud.

...

• The Monyog API is enhanced with more options to manage servers registered in MonyogSQL DM for MySQL. Options now include calls to add/edit/remove servers. Refer documentation for full details.
• Monyog SQL DM for MySQL now supports Query analysis using Performance Schema tables (events_statements_summary_by_digest and events_statements_history_long tables). This feature is supported only for MySQL 5.6.14 and MariaDB 10.0 and above.
• Explain plan is available in Query analyzer for Slow_log table based logging and Processlist sniffer.
• An example query is now shown in detailed query view in Query analyzer if queries replaced with literals is selected.
• Monyog SQL DM for MySQL now has a configurable option to define the max. query length displayed. Beyond this Monyog SQL DM for MySQL will truncate. The setting has effect for Query Analyzer, Real-time and Way Back Machine interfaces. Default is now 10000 characters and maximum setting is 64000 characters). However please note that this does not apply when Performance_Schema is used with the Query Analyzer as P_S itself truncates.

...

• Explain option was not available in locked and locking queries for Real-Time sessions.
• In some rare case Monyog SQL DM for MySQL logged SQLite errors while running Real-Time sessions.
• Monyog SQL DM for MySQL could crash when connecting using a 'Named Pipe' on Windows.
• When monitoring MySQL v5.6 with replication using GTIDs (global transaction IDs), Monyog SQL DM for MySQL reported false notification alert for the 'gtid_purged' variable, when notifications for change in server configuration was enabled. This particular variable was overlooked in 5.72 where there was a similar fix.
• Query literals with hex values were not replaced with '?' in Query analyzer.
• When using SSH-tunnel, connections created by the CSO (Custom SQL Object) feature were not always closed properly, and the MySQL error log as well as 'aborted_clients' status variable would record aborted connections.

...

• When GTID's (Global Transaction ID's) were used with replication, Monyog's SQL DM for MySQL replication page would display a lot of information about changing GTIDs. This is now hidden in the primary interface, but can still be displayed in detailed view.
• Monyog SQL DM for MySQL now displays the binary version on commandline when the command switch -version (or -v) is used.

...

Fixed Issues:

• In rare cases, Monyog SQL DM for MySQL could not close alerts from Monitors page.
• When monitoring MySQL v5.6 with replication using GTIDs (global transaction IDs), Monyog reported false notification alert for GTID counters when notifications for change in server configuration was enabled.

...

• Monitor's trend charts and history report charts were not displayed. This was introduced in Monyog version 5.67 of SQL DM for MySQL.
• Significantly improved the speed of replacing literals for queries with wildcards in Query Analyzer.
• Connection to MySQL via SSL encryption could fail with valid parameters. This bug was introduced in Monyog version 5.61 of SQL DM for MySQL.

5.67 SQL DM for MySQL (February 2014)

...

• Fixed a rare crash occurring in CSO's (Custom SQL Objects).
• Fixed a UI issue in Realtime's lower pane. Only Safari browsers were affected.
• Monyog SQL DM for MySQL did not retain LDAP group authentication details after restart.
• Monyog's The SQL DM for MySQL interface for specifying LDAP groups did not allow for more than 64 characters.
• Query Analyzer did not show queries when time range was selected with slow log and general log tables (log files were not a problem) as the source for Query Analyzer.
• CSV-reports exported from Monitors page could show wrong values for a few monitors.

Miscellaneous:

• Monyog SQL DM for MySQL now loads list of servers interface faster.

5.66 SQL DM for MySQL (November 2013)

New Features:

• Monyog SQL DM for MySQL can now authenticate users using LDAP user groups without the need to add them in MonyogSQL DM for MySQL.
• Explain plan for Insert, Update and Delete queries is now available in Monyog's SQL DM for MySQL Processlist page for MySQL 5.6+ servers.

...

• The fix for failing alerts for InnoDB deadlocks with MySQL 5.6 servers in 5.65 introduced a new issue where the time for the occurence occurrence of the deadlock reported was wrong.
• When monitoring a Galera cluster and when cluster nodes failed to connect to each others, the error sent by cluster nodes ("unknown command") could cause Monyog SQL DM for MySQL to crash.
• When a server was deleted from Monyog SQL DM for MySQL in rare cases the corresponding data directory was not removed.

Miscellaneous:

• Linux versions of Monyog SQL DM for MySQL now include a script that can be used for log rotation of the Monyog.log.

...