Page History
...
- 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 Monyog SQL DM tremendously. Post MonyogSQL 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
Fixed Issues:
- Monyog 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 ‘<’, ‘>’ in “Threads” page.
- Monyog SQL DM failed to read the MySQL log files when ‘log_output’ variable was set as both File and Table.
- Monyog SQL DM failed to connect and displayed “Operations error” when using Active Directory External Authentication.
- In rare cases Monyog SQL DM failed to raise alerts for the monitor “Recent entries of type [Error]”.
...
- If the server’s log query path variable returns a relative path, then Monyog SQL DM for MySQL will generate the absolute path – required by MONyog – automatically.
- Added the monitor “Most Advanced Node” in the Galera group.
...