Versions Compared

Old Version 12

changes.mady.by.user Nicolas Rios

Saved on

compared with

New Version 13

changes.mady.by.user Nicolas Rios

Saved on

Key

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

...

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

...

  • Parsing the output of SHOW ENGINE INNODB STATUS for InnoDB deadlocks if server was MySQL 5.6.x. For same reason alerting also failed.
  • Some counters failed to report alert conditions. This bug was introduced in Monyog version 5.62 of SQL DM for MySQL.

5.64 SQL DM for MySQL (October 2013)

...

5.63 SQL DM for MySQL (September 2013)

Fixed Issue:

  • If Monyog SQL DM for MySQL was not able to connect to a MySQL server, replication page would 'hang' and even crash in rare cases. This was introduced in version 5.62.

5.62 SQL DM MySQL (September 2013)

New Features:

  • Removed a hardcoded hard coded limit (of 512) of the number of MySQL servers that could be registered with an 'unlimited server'-license. Now the restriction is solely with the implementation of the license in the license key.
  • Added and updated a few counters in order to provide more specific support for MySQL 5.6 and MariaDB 10.

Fixed Issues:

  • Cleaned up javascript JavaScript execution running in the background that was not needed. With a large number of servers registered (from around 150 on a typical system) this could result in some slugginess in interactive parts of Monyog due to CPU contention.
  • Explain option was not present in processlist page for queries starting with comment.
  • On Windows 'Real_time' monitoring did not work since 5.61.
  • Rendering of replication page failed if GTID (Global Transaction ID) mode was enabled for MySQL Slaves.
  • Resolving the ip IP from a host name happened multiple times during display of replication page what could slow down rendering of replication page noticably noticeably on some environments.
  • Some Dashboard charts could show incorrect data.
  • Dashboard failed to render charts when based on a counter saved without caption, series caption and series values.
  • When restarting Monyog SQL DM for MySQL it would perform a SQLite Schema upgrade even if it was not required. Version 5.61 was affected.

...

5.6 SQL DM for MySQL (August 2013)

New Features:

  • Monyog SQL DM for MySQL supports LDAP authentication for login into Monyog SQL DM for MySQL interface. This is available only in Ultimate version of MonyogSQL DM for MySQL.
  • Added a feature in Query Analyzer to include or exclude queries based on the search string / regular expression.

...

  • Purging mechanism was not working properly (this bug was introduced in Monyog version 5.57 of SQL DM for MySQL).
  • Tag/Group names are in alphabetical order now.
  • Monyog SQL DM for MySQL can now "Kill query" on Amazon RDS instances.
  • The rendering of Dashboard page is further improved.

...