Versions Compared

Old Version 7

changes.mady.by.user Nicolas Rios

Saved on

compared with

New Version 8

changes.mady.by.user Nicolas Rios

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Miscellaneous:

  • When stopping Monyog SQL DM for MySQL service, all running Real-time sessions will now be saved automatically.
  • Upgraded LibSSH and LibCurl to the latest versions (0.7.5 and 7.54.0 respectively).
  • Monyog SQL DM for MySQL will now only support Linux’es with kernel version equal to or higher than 2.6.32 . This is a consequence of an upgrade of our build environment necessary in order to support recent kernel versions and distributions.
  • Upgraded the MariaDB Connector/C to 2.3.3. Due to this the MariaDB auth_gssapi (Kerberos) plugin is now supported.

...

  • In monitors page, history chart did not plot for some counters.
  • In Firefox browser, Servers page hanged with a large number of servers.
  • Monyog SQL DM for MySQL failed to connect over SSH tunnel for Ubuntu-16.04.
  • If ‘show_compatibility_56’ is off for MySQL-5.7 servers “Slave_running” counter gave a false alert. It will display “(n/a)” now.

...

  • Added Dashboard charts and monitors for the Aria storage engine.
  • Performance schema can now be used with RDS Aurora (version 5.6.10).

Fixed Issues:

  • Monyog SQL DM for MySQL failed to recognize replication topology in cases when “SHOW SLAVE STATUS” returned master host as an alias name while the master server was registered with an ip IP address in MonyogSQL DM for MySQL.
  • Also Monyog SQL DM for MySQL could fail to recognize replication topology if SSH-tunnel was used to master.
  • The replication monitors stopped updating values, when slaves stopped running as slaves.
  • When logging in with LDAP group users, the onboarding tool-tips continued to display when no longer needed.
  • Threads page stopped updating data once the custom query filter returned empty list.
  • Monyog SQL DM for MySQL did not show queries starting with “SHOW..” in slow query log in Query Analyzer.
  • “Lock time” column was not getting sorted properly for PS based real-time.
  • Monyog SQL DM for MySQL returned console error for server name containing single quote(s).
  • Deleting server registrations in Monyog SQL DM for MySQL could result in high CPU-load and IO. This is now reduced.
  • Monyog SQL DM for MySQL RPM installer script failed to start Monyog SQL DM for MySQL in SUSE Linux Enterprise servers.

...

  • The Galera counter “Total number of bytes replicated to other nodes” now uses “wsrep_replicated_bytes” and not “wsrep_replicated” variable as before.
  • The Logrotate script shipped with Monyog SQL DM for MySQL failed to rotate the Monyog SQL DM for MySQL log in some cases.
  • In some cases Top-5 tables in Disk Info page were not showing tables sorted based on total size.

...

  • Overview will now show top 10 queries only for the selected servers and not for all the registered servers in MonyogSQL DM for MySQL.
  • Overview, Dashboard, Monitors, Threads and Server Config (Compare Config) pages will have their own separate server selector.
  • Now the maximum no of servers that can be selected in each page is limited. Default is 10, but the number can be configured in Monyog.ini. On most systems we don’t advise raising the value as it may increase the time for loading pages.

...

  • Fixed a crash occurring when upgrading Monyog SQL DM for MySQL from Ultimate/Trial to Enterprise/Professional.
  • In rare cases dashboard failed to load charts.
  • In some cases Monyog SQL DM for MySQL could fail to analyse the sniffer and returned error “Integer overflow” instead.
  • Additional InnoDB deadlock information from SHOW ENGINE INNODB STATUS available in MySQL 5.6+ was not displayed in Monitors page.
  • Fixed an issue where log analysis wasn’t working with Aurora instances.
  • RDS servers were not being detected as RDS instances because of change in ‘basedir’ variable for RDS.
  • In Monitors page, it could happen sometimes that some charts were not displayed in ‘history’ timeframe.
  • The ‘Minimum time taken’ -setting for Processlist-based sniffer also affected Performance_Schema-based sniffer. This is wrong and has been corrected.
  • In some cases the Overview page loaded slowly if the request for checking any unresolved counters, functions or UDOs responded late.
  • Login to Monyog failed if the password had any of the characters “%”, “&”, “+” and “?”.
  • A few UI/display fixes.

...

Fixed Issues:

  • In rare cases Monyog SQL DM for MySQL would hang while editing a server.
  • Enabling “Monitor locked queries” switched back to off state after editing settings for the actual MySQL server.
  • Regression fix: Monyog-v7.x releases had a higher load average than 6.x predecessors.

...

  • Overview page giving the top-level picture of all the servers running, down, critical alerts, warnings and the top 10 queries across all the servers registered with MonyogSQL DM for MySQL.
  • Option to create customized dashboard with specific charts with the ability to explode a chart
  • Search option for servers registered with MonyogSQL DM for MySQL.
  • Query Analyzer will now show the top 5 queries based on execution time in a separate window.
  • Replication overview page showing the replication hierarchy in a clean graphical way.
  • Servers page providing an overview of all the servers registered and their status in one place.

...

Fixed Issues:

  • In rare cases Monyog SQL DM for MySQL failed to connect to SSH and returned the error “failed to connect to SFTP: SshConnect: Error while connecting to ssh server –kex error”.
  • Monyog SQL DM for MySQL failed to authenticate as required when using the authentication mode “Comparison” for LDAP users and groups.
  • Some galera charts were not loading due to the syntax error in the chart definition.
  • Monyog SQL DM for MySQL was allowing users to add/edit the server using the API even if the user did not have privilege to add/edit the server.

...

  • Support for the ‘clear-text plugin’ (used by Oracle/MySQL LDAP authentication) and the ‘dialog plugin’ (used for MariaDB PAM authentication) was broken.
  • With RDS servers Monyog SQL DM for MySQL could fail to detect log file content and size and would display the error “No queries found” and “Unable to fetch file size”. It happened because of recent changes in the XML-response of Amazon’s REST API.
  • Slow query log/General query log paths were not always setting properly when adding/editing a server using the Monyog SQL DM for MySQL API.
  • MySQL InnoDB-related charts displayed empty with MySQL 5.6+. The reason was removal of the ‘have_innodb’ server variable in MySQL 5.6. Now these charts don’t depend on this variable.

...

Fixed Issues:

  • When user logged in to Monyog SQL DM for MySQL with an account other than the built-in admin account, tabs were hidden.

6.6 SQL DM for MySQL (September 2016)

New Features:

  • Monyog SQL DM for MySQL user management was enhanced with a ‘roles’ feature.
  • LDAP role based access: users can now map External LDAP roles to Monyog SQL DM for MySQL roles.
  • Added option to restrict access to specific tabs for specific users.
  • SNMP traps will now have “Tag” and the “MySQL hostname” in the message.
  • Now Monyog SQL DM for MySQL will show the number of servers selected in the tag along with the total servers in that tag.
  • Added a message in the charts page if system charts are enabled and SSH settings are not enabled.

...

  • When adding a server through Monyog SQL DM for MySQL API, sniffer was not enabled by default.
  • The setting for “Override send notification when alert-able?” was ignored if the value specified was greater than the setting for “Send notification when alertable”.
  • In rare cases Real-Time failed to start a new session and showed a random number.

...

  • The “Explain Query” dialog box in Real Time and Query Analyzer returned the message “Extended is deprecated” for MySQL 5.7.3+ servers. Now (plain) “EXPLAIN” is used to fetch the value.
  • In rare cases some monitor groups were not getting Enabled/Disabled at “Manage Monitor groups” page when using Internet Explorer.
  • The fields “SeriesCaption” and “SeriesValues” in “Edit chart” page did not give any error on saving when having different number of arguments, but a console error showed up while loading the charts.
  • Monyog SQL DM for MySQL was not able to connect to RDS instances using SSL encryption. Attempting to do so returned the error “Failed to connect to MySQL: SSL connection error: certificate verify failed”.

...