Versions Compared

Old Version 9

changes.mady.by.user Nicolas Rios

Saved on

compared with

New Version 10

changes.mady.by.user Nicolas Rios

Saved on

Key

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

...

  • EXPLAIN option was not available in Wayback Machine.
  • In some rare cases, Monyog SQL DM for MySQL logged SQLite errors if deadlock details contained double quotes.
  • In Wayback Machine interface, Monyog SQL DM for MySQL showed wrong time in queries tab when a point was selected in the chart.

...

  • In rare cases, Monitors page could show wrong data for Linux counters if the HISTORY timeframe was selected for the page. Other available timeframes were not affected.
  • When monitoring a MariaDB server using a galera-based replication setup we will now execute SHOW ALL SLAVES STATUS rather than just SHOW SLAVE STATUS. Before this Monyog replication page showed an empty result and alerts were not sent. However due to limitations with current Monyog SQL DM for MySQL architecture we are only able to handle the first row of SHOW ALL SLAVES STATUS with this release, if more are returned, and only information from one slave node will be available.

...

  • What is plotted in “Charts” (formerly “Dashboard”) page may now be specified as a time interval and not only as a number of latest sample points. This increases usability of the page.
  • Long running query log now includes action (kill/notify/notify and kill) and the time of action.
  • Locked and locking queries tab in Real-Time interface is optimized and loads faster.
  • Added Wildcard filtering using the “*” character as wildcard for user and host in Query Analyzer for Slow Query Log.

Fixed Issues:

  • Monyog SQL DM for MySQL failed to send notification for an InnoDB deadlock if deadlock details (as recorded by SHOW ENGINE INNODB STATUS) contained double quotes.

...

  • A log of long running queries can now be generated and downloaded as CSV in Sniffer interface (applies only to Processlist mode of sniffer).
  • Real-Time is optimized and loading a session is much faster now. Further it shows only data from top 200 open tables and databases.
  • Wayback Machine now includes user and host information as well.
  • Queries in Wayback Machine can now be exported as CSV.
  • Monyog SQL DM for MySQL can now send long running query notification to specific selected users only.
  • Wildcard filtering using the “*” character as wildcard for user and host is introduced in Sniffer (applies only to Processlist mode of sniffer).
  • Same wildcard filtering implementation is also introduced for Ignore user and host in Long running query options in Sniffer (applies only to Processlist mode of sniffer).
  • Monyog SQL DM for MySQL now logs what user killed a thread in Processlist tab.
  • SQLite library bundled in Monyog SQL DM for MySQL is now upgraded to the latest version. This results in performance improvement for sniffer in particular where it can be up to ~50%.

Fixed Issues:

  • In some cases, Monyog SQL DM for MySQL logged SQLite errors when CSOs (Custom SQL Objects) were enabled even when the CSO worked as expected
  • Small UI fixes.

6.27 SQL DM for MySQL (April 2015)

Fixed Issues:

  • Monyog SQL DM for MySQL no longer prompts the user to re-type the admin password while upgrading on Windows.
  • In Edit Server page it was possible to retrieve the MySQL password by inspecting JSON with browser’s javascript JavaScript debugging module/plugin.
  • Monyog SQL DM for MySQL was not able to authenticate a user from LDAP group consisting of linked users (i.e. users with membership of more than one group).
  • Monitors page failed to load in case an empty group (with no counters) existed.
  • Replication tab failed to load after restart of a server when monitoring a master-master replication setup.

...

  • When monitoring MySQL 5.6.3 and higher, Monyog SQL DM for MySQL reported false notification alert for ‘innodb_thread_sleep_delay’ when notifications for change in server configuration was enabled.
  • Replication page failed to show data if SHOW SLAVE STATUS on one server was hanging.
  • Server Config page was not always showing proper data when “show only changed values” is selected.
  • In some rare cases Monitors page was not displaying data after editing SSH tunnel details.
  • Monyog SQL DM for MySQL 32 bit build was not accepting port beyond 16-bit limit (> 2^16 – 1). This limit has been increased to handle full 32-bit range (up to 2^32 – 1).

Miscellaneous:

  • Email Alerts in Monyog SQL DM for MySQL now contain Tag(s) and MySQL host of the corresponding server.

...