Versions Compared

Old Version 5

changes.mady.by.user Nicolas Rios

Saved on

compared with

New Version 6

changes.mady.by.user Nicolas Rios

Saved on

Key

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

...

  • A Galera cluster can now be automatically registered specifying any single node in the cluster.
  • Optimized counter migration logic. This will reduce migration conflicts on upgrading SQL DM for MySQL tremendously. Post SQL DM for MySQL-8.6.0, a conflict will be raised on upgrade only if any counter definition is modified in the latest release and the user has also customized the same counter.
  • Added more columns for Slow Query log (for MariaDB and Percona Server) like full_scan, full_join etc. These values are written to Slow query log when ‘log_slow_verbosity’ is set to “Query_plan”.
  • Connection timeout (MySQL, SSH and SSH Tunnel) can now be set for servers individually. The default value is 30 second

...

  • SQL DM for MySQL logged an SQLite error “Udo.def: not an error” on fresh installation.
  • “Create User..” and “Create role..” queries were shown as a schema change in audit log.
  • Queries containing ‘<’ or ‘>’ were displayed with their HTML-entities ‘&lt’, ‘&gt’ in “Threads” page.
  • SQL DM for MySQL failed to read the MySQL log files when ‘log_output’ variable was set as both File and Table.
  • SQL DM for MySQL failed to connect and displayed “Operations error” when using Active Directory External Authentication.
  • In rare cases SQL DM failed to raise alerts for the monitor “Recent entries of type [Error]”.

...

8.5.0 SQL DM for MySQL (March 2018)

New Features:

  • Monyog SQL DM for MySQL can now analyze MariaDB and MySQL enterprise Audit log.
  • Added support for LDAP with StarTLS and SSL.
  • The default path for MONyog.log can be changed using the parameter “MONyogLogPath” from the MONyog.ini file.

Fixed Issues:

  • Monyog SQL DM for MySQL logged bogus SQLite errors on fresh installation.
  • Monyog SQL DM for MySQL displayed console error if LDAP group name contained inverted comma.
  • Changed alert condition for “Seconds behind master” monitor to consider “NULL” as an alertable condition. It considered the value “NULL” stable condition earlier.
  • On upgrading, Monyog SQL DM for MySQL filled the mail alert field for sniffer with the bogus email id “admin@mydomain.com”.
  • On selecting a tag in server selector GUI and then returning back to the main list, the default list of tags disappeared.

...

  • The Linux command ‘ps’ failed to identify Monyog SQL DM for MySQL process status. This was due to a packaging issue introduced in 8.4.0. Versions before that were not affected.
  • The option “Notify when server config change detected” compared in a case-sensitive manner and thus raised false alerts when the value for the MySQL variables changed from lower to upper case and vice versa. This could happen when a MySQL server was upgraded.

...

  • Added more notification channels (Slack and Pagerduty) for SQL DM for Monyog MySQL alerts.
  • Option to write Monyog SQL DM for MySQL alerts in the Syslog (of the machine where Monyog SQL DM for MySQL is installed). This option is only available for Linux.
  • Option to edit the subject line for SQL DM for Monyog MySQL alerts.
  • Added MONyog API to disable notification for a monitor based on a server/tag.
  • Complete re-design of the Settings page.

...

  • Export as CSV was downloading sorted based on “Average latency” column, even if sorted based on another column in Query Analyzer.
  • Fixed a case where Monyog SQL DM for MySQL sent bogus alerts.
  • Fixed a bug in reading RDS log files.
  • The Query filter “Custom” did not work in “Threads” page.
  • In rare cases, Monyog SQL DM for MySQL Disk space Monitoring alert gave false alerts.
  • The “Table” column returned empty values under “Tables” filter in Real-time.
  • SNMPv2 traps were having the same OID for two different objects what caused SNMP alerts failure with SNMPv2 services.

...

  • Option to set a distinct email distribution list for warning and critical alerts: Now you can define a proper demarcation between the users who will receive a particular alert based on the alert status. For instance, if you want only your on-call DBAs to receive critical alerts 24/7, this feature handles that easily.

  • Graph Analysis: You can group one single metric (which you find most important) from different servers into one unified chart. This allows You can group one single metric (which you find most important) from different servers into one unified chart. This allows you to visually analyse a metric across servers at various points in time.

  • Disk monitoring of the system where Monyog SQL DM for MySQL is installed: In case the free space on the system where Monyog SQL DM for MySQL is installed goes below the threshold value, Monyog SQL DM for MySQL will raise an alert.

  • Filter to exclude unwanted long running queries in Sniffer:

  • You can tell Monyog SQL DM for MySQL to ignore a particular type of query by specifying a regular expression. Monyog SQL DM for MySQL neither would kill nor send an alert for such long-running queries.

  • Option to filter queries based on poor indexes, missing indexes, errors and warnings. This feature is available for PERFORMANCE SCHEMA based sniffer in Query Analyzer and "Show details" page in Dashboard. When you choose a filter, Monyog SQL DM for MySQL will show queries based on the criterias set.

  • Redesigned Server selector

  • Redesigned Query Analyzer: a more intuitive view of the top 5 queries based on total time.

  • Added proper Y-axis unit for charts, along with the option to define the units and unit-factors.

Fixed Issues:

  • Monyog SQL DM for MySQL was logging “UNIQUE constraint failed..” errors in MONyog.log

  • System charts failed to show data for many data collections, when the system metrics was enabled from the Dashboard page.

  • In some rare cases, real-time page hanged on switching between real-time sessions.

  • Option to plot values based on data collection in History/Trend analysis (For uptime counters). Only Group by option was available for those counters.

  • Monyog SQL DM for MySQL failed to recognise recognize Aurora instances for OS monitoring. The four required fields for OS monitoring were not displayed.

  • Email addresses with + in monitor level notification settings was not accepted.

  • Added ‘DB’ as a column under ‘Manage Columns’ in Dashboard’s ‘show details’ page in ‘Processlist’ mode

  • Monyog SQL DM for MySQL showed the total time and average latency as 0 when the execution time of the query was less than a second for table based slow query log.

  • Fixed an issue with Custom SQL Object (CSO) - Monyog SQL DM for MySQL logged entries like “not an error” in MONyog.log.

...

  • Query count could return negative value in Overview page due to integer overflow.
  • The History/Trend analysis chart for the counter “Free disk space” was not rendering properly.
  • The Monyog SQL DM for MySQL API for enabling System metrics for RDS instances was not working as expected.
  • After zooming into the real-time chart, the Query column was not getting sorted.
  • History/Trend could show wrong value for some counters – mainly string based counters.
  • In case of RDS servers, rebuild of a server’s database, restarting Monyog SQL DM for MySQL or using “editserver” API could stop the collection for OS metrics.
  • When using cname for RDS servers, Monyog SQL DM for MySQL failed to enable system metrics.

...

  • Regression bug introduced in MonyogSQL DM for MySQL-8.1.0: Monyog SQL DM for MySQL failed to install on Linux machines with no “kernel headers” installed

...