Fixed Issues:- 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), SQL DM for MySQL reported false notification alert for GTID counters when notifications for change in server configuration was enabled.
Miscellaneous:- Upgraded libraries that theoretically could be vulnerable to the 'Heartbleed' OpenSSL bug.
New Features:- With only one MySQL server selected, Dashboard page will now display charts in such a way that whitespace and the need of scrolling are reduced. With more than 1 servers selected, the Dashboard charts are drawn using a vertical layout as before.
- Real-Time interface can now show the actual query in addition to replacing literals with the "?" wildcard.
Fixed Issues:- Using TAGS for registered servers in order to manage access for non-admin users did not always work as expected when multiple TAGS were used.
- Yet another fix for a LDAP group authentication issue.
- In Real-Time interface EXPLAIN option was not available if query length was greater than 5000.
- In Real-Time interface database and user@host were not available for aggregating queries. They are now.
Miscellaneous:- MySQL availability and System availability charts in Dashboard are now disabled by default. Users who want them can enable from Dashboard Customize page. We removed them primarily as they consume space in the interface and have little information that is not obvious from other charts.
Fixed Issues:- 5.69 introduced an issue causing LDAP authentication to fail in some cases.
Miscellaneous:- Code cleanups and internal optimizations. Users having a large number of MySQL servers registered will observe a lower system load with this version due to this.
Fixed Issues:- LDAP search for user in group authentication could fail with Active Directory.
- Real-time sessions could fail under rare circumstances when two or more sessions were started at the same time.
- Fixed a crash introduced in version 5.68.
New Features:- Sniffer now shows database name in long running query notification and also in Query Analyzer interface when Processlist based sniffer is selected. Please note that Processlist only exposes this information if a USE statement is associated with the query. If a 'fully qualified tablename' is used in the query this information will be empty.
Fixed Issues:- Monitor's trend charts and history report charts were not displayed. This was introduced in version 5.67 of SQL DM for MySQL.
- Significantly improved the speed of replacing literals for queries with wildcards in Query Analyzer.
- Connection to MySQL via SSL encryption could fail with valid parameters. This bug was introduced in version 5.61 of SQL DM for MySQL.
Fixed Issues:- Fixed a rare crash occurring in CSO's (Custom SQL Objects).
- Fixed a UI issue in Realtime's lower pane. Only Safari browsers were affected.
- SQL DM for MySQL did not retain LDAP group authentication details after restart.
- The SQL DM for MySQL interface for specifying LDAP groups did not allow for more than 64 characters.
- Query Analyzer did not show queries when time range was selected with slow log and general log tables (log files were not a problem) as the source for Query Analyzer.
- CSV-reports exported from Monitors page could show wrong values for a few monitors.
Miscellaneous:- SQL DM for MySQL now loads list of servers interface faster.
New Features:- SQL DM for MySQL can now authenticate users using LDAP user groups without the need to add them in SQL DM for MySQL.
- Explain plan for Insert, Update and Delete queries is now available in SQL DM for MySQL Processlist page for MySQL 5.6+ servers.
Fixed Issues:- The fix for failing alerts for InnoDB deadlocks with MySQL 5.6 servers in 5.65 introduced a new issue where the time for the occurrence of the deadlock reported was wrong.
- When monitoring a Galera cluster and when cluster nodes failed to connect to each others, the error sent by cluster nodes ("unknown command") could cause SQL DM for MySQL to crash.
- When a server was deleted from SQL DM for MySQL in rare cases the corresponding data directory was not removed.
Miscellaneous:- Linux versions of SQL DM for MySQL now include a script that can be used for log rotation of the Monyog.log.
Fixed Issues:- 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 version 5.62 of SQL DM for MySQL.
Fixed issues:- This release includes fixes for a rare crash when deleting servers and when trying to access a SQLite database that could not be accessed for some reason.
Fixed Issue:- If 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 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 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 SQL DM for MySQL 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 from a host name happened multiple times during display of replication page what could slow down rendering of replication page 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 SQL DM for MySQL it would perform a SQLite Schema upgrade even if it was not required. Version 5.61 was affected.
Miscellaneous:- MySQL 3.23 and 4.0 servers are no longer supported and an attempt to register such will be denied.
New Features:- SQL DM for MySQL supports LDAP authentication for login into SQL DM for MySQL interface. This is available only in Ultimate version of SQL DM for MySQL.
- Added a feature in Query Analyzer to include or exclude queries based on the search string / regular expression.
Fixed Issues:- Monitor trend charts were not updating in realtime.
- Tooltips were truncated in DiskInfo's table information.
- In Sniffer, "Queries starting with" option was not working properly if query started with comment.
- Queries starting with a comment did not show EXPLAIN option in the Real Time interface.
- Fixed a crash when viewing replication page if slave details were not properly specified (any detail NULL).
New Features:- Added a feature in realtime to include or exclude queries based on the search string / regular expression.
Fixed Issues:- Purging mechanism was not working properly (this bug was introduced in version 5.57 of SQL DM for MySQL).
- Tag/Group names are in alphabetical order now.
- SQL DM for MySQL can now "Kill query" on Amazon RDS instances.
- The rendering of Dashboard page is further improved.
Fixed Issues:- The rendering of Monitors and Dashboard page was slow with large number of servers both registered and selected and when multiple users were connected simultaneously displaying the page. It could take one minute or more in some cases. It is now a matter of seconds.
- With a large number of servers registered, editing details for one was slow. Also this could take around 1 minute, and the improvement is in the same range as above.
- Event manager's database (Events.data) is now moved from global level to server level in order to prevent locking problems with a large number of servers. SQL DM for MySQL will migrate data first time it starts after the upgrade.
- Fixed a multi-threading issue that in rare cases could crash SQL DM for MySQL while registering more than one server at the same time.
- Fixed a rare crash in SQL DM for MySQL while viewing replication tab.
- Fixed a rare crash in SQL DM for MySQL while resolving CSOs ("Custom SQL Objects").
- SQL DM for MySQL could fail to send mail alerts if a single mail contained alerts for more than one monitor.
- SQL DM for MySQL was showing errors in Query Analyzer, Realtime and Processlist pages when a query contained characters used for specifying HTML tags.
- If a registered server was not a slave but marked as such in Advanced Settings .. Replication, SQL DM for MySQL was leaking connections every time it was collecting data and finally connections (from SQL DM for MySQL as well as other clients) could fail due to 'max_connections' setting being exceeded.
- For MySQL InnoDB-related monitors were showing "(n/a)". The reason was removal of the 'have_innodb' server variable in MySQL 5.6.
Fixed Issues:- Fixed a memory leak when reading MySQL server logs through SFTP.
- Fixed a multi-threading issue that in rare cases could crash SQL DM for MySQL running on Linux while reading the MySQL error log.
- "Apply settings to all the servers with same tags" was not working when data collection was disabled globally.
- The fix in 5.55 for indented display of a slave compared to its master was not complete. Proper indentation could still fail.
Fixed Issues:- In the replication page a slave was not displaying indented compared to its master as it should if slave and master were running on same host.
- Fixed a multi-threading issue that in rare cases could crash SQL DM for MySQL if the Monitors page was viewed simultaneously in multiple browsers.
- Stability fixes for issues found during internal stress-testing and code review. No crash, slowdown ('hang') or similar was reported due to any of those, but it could theoretically happen under specific and rare circumstances.
Fixed Issues:- Sometimes SQL DM for MySQL could hang while editing server's tag.
- Processlist did not show "view query" for prepared statements.
New Features:- Added monitors for monitoring a galera-based cluster. These monitors do not display as default but there is a 'Galera' monitor group that can be unhidden from Tools .. Manage Monitor Groups.
Fixed Issues:- Authentication to SMTP servers could fail with very long passwords. Also authentication with Amazon SES could fail.
- When saving a connection Monyog could apparently 'hang' for a while.
- With a large number of sample points displayed in Dashboard, loading of the page was slow. It could take up to around 1 minute in some cases. Now it is a few seconds.
- SSH keys could be 'forgotten' after a Monyog restart.
- Fixed a rare crash when editing server details.
- In the 'Real Time' interface the option to EXPLAIN queries did not display in Internet Explorer 8.
- For non-admin users, the replication tab was displaying all slave servers instead of showing only those servers which the user has access to.
- Internal optimizations, library upgrades etc.
Fixed Issues:- When upgrading to SQL DM for MySQL 5.51 admin rights for users with such failed to be migrated. This release fixes this for both users that have already upgraded to 5.51 and those that have not.
New Features:- Added a number of monitors and advisors - mostly based on metrics exposed by MySQL 5.5+.
- In the 'Real Time' interface user may now define the threshold for when a query should be considered slow. Lowest possible setting is 1 second.
- In the 'Real Time' interface queries are now truncated after 5000 characters. Before it was 1000.
- 'queries' and 'slow queries' can now be exported to CSV in the 'Real Time' interface.
- Original query formatting is now retained in 'Real-Time'.
- User Manager has added a privilege to allow (or not) to 'view literals' in Query Analyzer page for non-admin users. This can be used for blocking access to read sensitive data for such users and still giving them access to use the Query Analyzer.
- Multiple saved Real-Time sessions can now be viewed at a time.
- Added a 'thread count' showing number of currently running threads on 'Processlist' page.
Fixed Issues:- In the 'Real Time' interface displaying large BULK INSERTS was slow.
- Logging out from SQL DM for MySQL while 'Real Time' was populating could crash SQL DM for MySQL. Linux - and not Windows - was affected.
- In the replication overview page SQL DM for MySQL will now show 'binlog' file name and it's position wherever it applies (where binlogging is enabled). Before it was showing only for master servers.
- In the Monitors page the percentage of SELECTS did not display. This was unlike INSERTS, DELETES and UPDATES .
- A 'Long running query' email alert has added a note clarifying that when the alert was sent the query may still be running. Before it could be understood like the alert was sent after query had completed.
New Features:- Added a new major feature called ‘Real-Time’ to monitor MySQL. This feature details the top 200 queries, slow queries, locked queries, locking queries, tables, databases, users, hosts and query states in real time. Information is retrieved from MySQL every one second. Queries taking more than 10 seconds to execute are considered as slow queries. Note that SQL DM for MySQL depends on the ‘InnoDB Plugin’ (optional with recent MySQL 5.1 versions, standard with higher MySQL versions) to get information on locked and locking queries. Refer
| Newtab2 |
|---|
| alias | MySQL docs |
|---|
| url | http://dev.mysql.com/doc/innodb-plugin/1.0/en/innodb-plugin-introduction-obtaining.html |
|---|
|
for more information on InnoDB plugin. Also note that constants listed here are currently 'hard-coded' but we plan to implement user settings. 'Real-Time' is an Enterprise and Ultimate feature. - Optimized Monitors page to retrieve and display data approximately 10 times faster than before
- Added an option to choose verbosity of email notifications. 'lesser verbosity' is in particular relevant if you receive mails on a mobile phone or another small handheld device.
- Added 'Monitor level' email-address alert setting. If an email address is specified for a specific monitor, notification will be sent to that particular email-address when the monitor is alertable in addition to the email address specified globally for the server.
- In the MySQL query log settings page, the 'file path' field for general query as well as slow query log was disabled for MySQL versions lesser than 5.1.6.
New Features:- Introduced support for 'native' MySQL SSL-encryption with direct MySQL connections.
- SQL DM for MySQL now fully supports IPv6 (Internet Protocol Version 6).
- History-trends have been optimized to retrieve data faster than it was before. With large data sets this results in a speed improvement in the range of a factor ~25.
- Passwords for SQL DM for MySQL users are no longer stored in clear text. A hash is stored (for admin user in MONyog.ini - for other users in the embedded database). Also MySQL passwords as well as SSH/SSL keys, certificates and passphrases are now stored obfuscated. First time SQL DM for MySQL starts after upgrading from a version using clear text storage it will rewrite passwords etc. to the hashed/obfuscated representation.
- Added a Linux counter "Load Average" as exposed by the Linux kernel in /proc/loadavg.
Fixed Issues:- Fixed a memory leak with SSH key based authentication.
- If HTML tags were a part of long running query, the notification email format was getting distorted.
- MySQL connection through SSH tunnel never re-established connection in Sniffer module when the connection failed for the first time
- Filter settings in the sniffer defined on a (MySQL) user with a SPACE character in its name did not work as expected.
- UI fixes.
New Features:- The Monyog API was rewritten and enhanced with more options. Options now include calls to enable/disable data collection, sniffer, notifications etc. for servers by either specifying a server name or a server tag. The old API calls have been blocked.
Fixed Issues:- Notification emails were not being sent when the number of file descriptors used by SQL DM for MySQL exceeded a certain number.
- Fixed a bug with the Custom SQL monitor where no data was being displayed in the Monitors page when all the columns retrieved by the Custom SQL were specified as Key Columns.
- Increased readability by improving SNMP trap format.
- UI fixes and enhancements.
Miscellaneous:- Testing slave connections has been moved to replication monitoring settings. Prior to this release it was in 'MySQL settings' tab making it necessary for users to switch between tabs for testing slave connections.
IMPORTANT note: - This release requires a new registration code. Neither the 5.1x nor the pre-5.1x key will work with this. Registered customers will get the new code from our Customer Portal. Please have the new code available before installing. Until SQL DM for MySQL is registered with new keys, it will not be collecting data from your servers.
New Features:- Added filter for including or excluding specific hosts and(or) users in Slow log analysis.
- Added and modified a few Monitors related to Replication, InnoDB and Security. Most of this utilizes metrics exposed by MySQL from version 5.5 .
- Added a preconfigured Custom SQL Object (CSO) for Percona Servers exposing the most written and most read tables.
- There is now session-wide persistence while sorting columns in Query Analyzer.
- Improved error messages in Query Analyzer and Wayback machine.
- Usability enhancements, GUI fixes and internal optimizations.
Fixed Issues:- SQL DM for MySQL was not working while behind Apache configured as a reverse proxy. This bug was introduced in version 5.0 of SQL DM for MySQL.
Fixed Issues:- Sometimes the default landing page failed to load after a log in. A refresh was necessary. This was introduced in version 5.0 of SQL DM for MySQL.
- Closed alerts could reappear in the Monitors page after an unsuccessful data collection and MySQL restart.
IMPORTANT note: - This release requires a new registration code. Registered customers will get the new code from our Customer Portal. Please have the new code available before installing. Until SQL DM for MySQL is registered with new keys, it will not be collecting data from your servers.
New Features:- Introduced tag level customization in SQL DM for MySQL Monitors. SQL DM for MySQL tags for servers are now available as Monyog Object Model variable (MONyog.Connections.TagName returns an array of tag names defined for a server). Documentation has examples on how to use it in scripting. Also see the note on 'Native JavaScript properties' support in next point below.
- Native JavaScript properties (like length, indexOf, splice etc) are now fully supported in Monitors and Dashboard. Note that 'indexOf' is required to check for individual tags from the array exposed by Monyog.Connections.TagName (see point above) in case there is more than one tag.
- Optimized Dashboard page to retrieve information faster.
- Auto-registered slaves will now have server names as their host names as default.
- Auto registering slaves will now assume the SSH host name of the slaves to be same as that of MySQL host. Before this the slaves' SSH hosts were assumed to be the same as that of the master.
Fixed Issues:- On SQL DM for MySQL restart, server edit, SQLite vacuum and MySQL restart there were 2 consecutive data collections with a short time interval. This could skew charts and MySQL metrics. Now SQL DM for MySQL collects data 2 consecutive times only when required - i.e during the first collection and after an unsuccessful data collection.
- Exporting charts as PNG exported as JPEG instead in Monitors page. This bug was introduced in version 5.0 of SQL DM for MySQL.
- UI fixes.
Miscellaneous:- Increased SQL DM for MySQL session timeout from 30 minutes to 8 hours (the MySQL default).
IMPORTANT note: - This release requires a new registration code. Registered customers will get the new code from our Customer Portal. Please have the new code available before installing. Until SQL DM for MySQL is registered with new keys, it will not be collecting data from your servers.
New Features:- In the 'Disk Info' page, clicking on a donnut chart in the Database level of a server will now drill down to table level.
- Query Analyzer' now has information on Average rows sent & examined while analyzing Slow Query Log. Those options has been hidden in version 5.0 and seen only in "Query details" pop up, now in v5.01 users can view those columns in QA output along with "Query details" pop up.
- Comparison of MySQL server configuration of multiple servers side by side is now faster in the 'Server Config' page.
Fixed Issues:- The 'login' page sometimes did not work in some 'minor' IE 8 builds (if not updated with latest patches from Microsoft). Same could happen with Google Chrome that were not up to date. This happened due to 'Google Gears' (that is no long part of Chrome). It now will work with all IE8 builds and Chrome from version 9.x (current is 17.x) - also with 'Gears'.
- MySQL server configuration could show incorrect values if MariaDB Servers were compared in the 'Server Config' page.
- A MySQL server that was a master and a slave at the same time was not showing the slave status in the 'Replication' tab even if it was marked as a slave in 'Register Server'.
- In the 'Replication' tab of SQL DM for MySQL the display of binlog_do_db and binlog_ignore_db settings were interchanged.
- On a fresh installation the default SQL DM for MySQL port was 8888. This was introduced in 5.0. Its now reverted back to 5555.
- Sometimes queries could fail to display in 'Wayback Machine' interface.
- In 'Monitors' page - History/Trend view charts did not plot if data series contained '(n/a)' value(s).
Miscellaneous:- Internet Explorer 6.x and 7.x are no longer supported. And actually this should have been announced in 5.0 GA release notes, but it was missed (it was announced in 5.0 beta1 release notes however).
UI Enhancements:- Introduced a left panel that contains the list of servers registered in SQL DM for MySQL, 'Tools' & 'Customize'. The 'List of servers' page has been removed. Users can now select/unselect servers from this panel.
- Previously available icons for Edit server/Duplicate server/Diagnostic reports etc now appear as a drop down menu next to each server.
- Previously the 'Customization' page appeared under 'Tools', now it appears as 'Customize' on the left panel.
- 'Manage changed Monitor/Advisors & Dashboard charts' are now available as 'Manage changes' under 'Customize'.
- 'Manage Custom SQL Objects' are now available under 'Manage changes'.
- The Global Notifications come on the top right hand corner before the help button.
- Pagination in Query Analyzer page. This removes the limitation of 200 queries in the result set.
- 'Monitors' is now the default landing page.
New Features:- Added an option to add users to admin group.
- Columns in the replication tab can now be sorted.
- Register/Edit server page now has tabbed interface which eases navigation.
Enhancement: - Improved browser level caching.
Miscellaneous:- The Monyog API responses are now in the following JSON format: {"STATUS": "SUCCESS/FAILURE", "RESPONSE" : ""}
- Query Analyzer will now display query text up to 5000 characters. (before it was 2000)
|