Softpedia >Windows >Internet >Servers >Database Utils >MONyog >  Changelog

MONyog Changelog

What's new in MONyog 8.6.0

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

New in MONyog 8.5.0 (Mar 7, 2018)

  • Features:
  • Monyog can now analyze MariaDB and MySQL enterprise Audit log.
  • Added support for LDAP with StartTLS and SSL.
  • The default path for MONyog.log can be changed using the parameter “MONyogLogPath” from the MONyog.ini file.
  • Bug Fixes:
  • Monyog logged bogus SQLite errors on fresh installation.
  • Monyog 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 filled the mail alert field for sniffer with the bogus email id “[email protected]”.
  • On selecting a tag in server selector GUI and then returning back to the main list, the default list of tags disappeared.
  • Miscellaneous:
  • “MySQL server restarted” alert will now be shown in table format.
  • Added option to view locked and locking queries when hovering over the queries in the Real Time interface.
  • Upgraded SQLite library to v3.21.0.

New in MONyog 8.3.2 (Nov 10, 2017)

  • This maintenance release resolves an issue with access to log files on RDS. The issue occurred because the XML response from the RDS REST API has changed in some cases.
  • Bug Fix:
  • Resolved an issue regarding access to log files on RDS. The issue occurred because the XML response from the RDS REST API has recently changed in some cases. Our XML parsing was improved to handle this.

New in MONyog 8.3.0 (Oct 30, 2017)

  • Features:
  • Added option to set a distinct email distribution list for warning alerts and critical alerts.
  • Graph Analysis: Added option to group a single metric (which one 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.
  • Added option for disk monitoring of the system where Monyog is installed. In case the free space on the system where Monyog is installed goes below a defined threshold value, Monyog will raise an alert.
  • Added a REGEX-based filter to exclude unwanted long_running queries in Sniffer. Monyog will ignore queries satisfying the expression and neither kill nor send an alert for such.
  • Added 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 will show queries based on the criteria set.
  • Redesigned Query Analyzer GUI: a more intuitive view of the top 5 queries based on total time has been added.
  • A more intuitive view of the top 5 queries based on total time has been added
  • Added Y-axis unit for charts, along with the option to define the units and unit-factors.
  • Bug Fixes:
  • Fixed bogus “UNIQUE constraint failed..” -errors in MONyog.log.
  • In rare cases real-time page hanged on switching between real-time sessions.
  • In 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 failed to recognise Aurora instances for OS monitoring. The four required fields for OS monitoring were not displaying.
  • 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 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 logged entries like “not an error” in MONyog.log.
  • Server name with ‘&’ in it was not getting deleted.
  • In some rare cases, Monyog failed to generate alert if the network connection on the machine where MySQL is running goes down.
  • Some monitors in the linux monitor group gave NaN while doing History/Trend Analysis.

New in MONyog 8.2.0 (Sep 21, 2017)

  • This release includes some GUI improvements and also fixes a few (also mostly GUI-related) bugs. Additionally, we have upgraded most libraries used internally to the current version. This – most significantly -includes OpenSSL.
  • Features:
  • Added option to have same Y-axis scaling for Dashboard charts across all servers.
  • Bug Fixes:
  • 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 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 or using “editserver” API could stop the collection for OS metrics.
  • When using cname for RDS servers, Monyog failed to enable system metrics.
  • Miscellaneous:
  • Redesigned Time-selector for all the features.
  • Upgraded OpenSSL to current v1.0.2l. The version used before had a few non-critical security issues. Also quite a lot of libraries used internally were updated.

New in MONyog 6.6.3 (Oct 4, 2016)

  • Features:
  • MONyog API now supports LDAP users and groups.
  • Bug Fixes:
  • In rare cases MONyog failed to connect to SSH and returned the error “failed to connect to SFTP: SshConnect: Error while connecting to ssh server –kex error”.
  • MONyog failed to authenticate as required when using the authentication mode “Comparison” for LDAP users and groups.
  • Some galera charts were not loading due to the syntax error in the chart definition.
  • MONyog was allowing users to add/edit the server using the API even if the user did not have privilege to add/edit the server.

New in MONyog 6.6.2 (Sep 21, 2016)

  • Features:
  • Charts are now loading faster with large time range.
  • Added more pre-configured Galera charts and Performance_Schema Custom SQL Objects.
  • Improved the performance of SQL-query in CSO ‘Tables_Without_Constraints’.
  • Added a new API “_disabledmonitorgroups” for enabling and disabling Monitor Groups at server-level.
  • Bug Fixes:
  • Support for the ‘clear-text plugin’ (used by Oracle/MySQL LDAP authentication) and the ‘dialog plugin’ (used for MariaDB PAM authentication) was broken.
  • With RDS servers MONyog could fail to detect log file content and size and would display the error “No queries found” and “Unable to fetch file size”. It happened because of recent changes in the XML-response of Amazon’s REST API.
  • Slow query log/General query log paths were not always setting properly when adding/editing a server using the MONyog API.
  • MySQL InnoDB-related charts displayed empty with MySQL 5.6+. The reason was removal of the ‘have_innodb’ server variable in MySQL 5.6. Now these charts don’t depend on this variable.

New in MONyog 6.6.1 (Sep 13, 2016)

  • Bug fixes:
  • When user logged in to MONyog with an account other than the built-in admin account, tabs were hidden.

New in MONyog 6.6.0 (Sep 13, 2016)

  • Features:
  • MONyog user management was enhanced with a ‘roles’ feature.
  • LDAP role based access: users can now map External LDAP roles to MONyog roles.
  • Added option to restrict access to specific tabs for specific users.
  • SNMP traps will now have “Tag” and the “MySQL hostname” in the message.
  • Now MONyog will show the number of servers selected in the tag along with the total servers in that tag.
  • Added a message in the charts page if system charts are enabled and SSH settings are not enabled.
  • Bug fixes:
  • When adding a server through MONyog API, sniffer was not enabled by default.
  • The setting for “Override send notification when alert-able?” was ignored if the value specified was greater than the setting for “Send notification when alertable”.
  • In rare cases Real-Time failed to start a new session and showed a random number.

New in MONyog 6.5.5 (Aug 29, 2016)

  • Bug Fixes:
  • The “Explain Query” dialog box in Real Time and Query Analyzer returned the message “Extended is deprecated” for MySQL 5.7.3+ servers. Now (plain) “EXPLAIN” is used to fetch the value.
  • In rare cases some monitor groups were not getting Enabled/Disabled at “Manage Monitor groups” page when using Internet Explorer.
  • The fields “SeriesCaption” and “SeriesValues” in “Edit chart” page did not give any error on saving when having different number of arguments, but a console error showed up while loading the charts.
  • MONyog was not able to connect to RDS instances using SSL encryption. Attempting to do so returned the error “Failed to connect to MySQL: SSL connection error: certificate verify failed”.
  • Miscellaneous:
  • The option “Notify when server configuration changes” will be enabled by default when notification is enabled.
  • Now counters may be customized from “Events” tab as well.

New in MONyog 6.5.4 (Jul 27, 2016)

  • Bug Fixes:
  • MONyog.log file logged bogus SQLite errors like “not an error” if UDOs were enabled in MONyog in some cases.
  • The definition for the counter “Free disk space” in the “Linux” group was misleading as we were giving the free disk space of the volume where mysql binary resided given by “basedir”, instead of giving the free disk space on the volume where data directory resides given by “datadir”.
  • The column “Rows examined” in Performance_Schema based sniffer printed negative values, if the number of “Rows examined” exceeded the value 2G.
  • In Real-Time, charts for Tables tab were not displayed in some rare cases.
  • We are now discarding GTID-related system variables that are changed by MySQL server itself from the “Track Config” tab. These system variables (gtid_executed, gtid_owned, gtid_purged etc.) change if a new transaction occurs in Master and considering them would raise bogus alerts that configuration was changed.
  • Miscellaneous:
  • MONyog will now have sniffer enabled by default for newly registered MySQL servers. If Performance_Schema is enabled for the MySQL server then Performance_Schema mode will be used, else Processlist mode will.
  • Improved the load time of Monitors page. It is noticable in particular when “History” timeframe is used with a large range (several hours or more).

New in MONyog 6.5.3 (May 6, 2016)

  • Bug Fixes:
  • “Count” column did show empty value in Processlist based Real-time.
  • Performance_Schema based Real Time failed if global sql_mode included “ONLY_FULL_GROUP_BY”.
  • Clicking on locked queries were not showing its corresponding locking query and vice versa for Performance_Schema based Real Time.
  • The counter “General Log Enabled?” was showing incorrect value for MySQL 5.6.1+ versions.
  • In rare cases, MONyog would show only time with no date in x-axis if the chart was plotted for multiple days.
  • Editing LDAP group was not always working as expected.
  • With RDS servers MONyog could fail to detect log files and would display the error “log file not present”. It happened because of changes in the XML-response of Amazon’s REST API introduced since we started supporting logs with RDS.
  • Miscellaneous:
  • The default filter for “show queries only” in processlist now includes ‘Command=Execute’. Also ‘Command=Execute’ is now included in processlist-based Real Time and Query Analyzer interfaces.

New in MONyog 6.5.2 (Mar 3, 2016)

  • Features:
  • Added an option to choose data collection mode for Real-Time, Users can now choose between ‘Performance schema’ or ‘Processlist’. Old versions used ‘Processlist’ what we replaced with ‘Performance schema’ recently for servers running with needed P_S instruments enabled. However due to the aggregation and truncation of queries recorded in P_S we had several requests that both options should be there.
  • Information whether a query is performing a full table scan available in Query Analyzer, Wayback Machine and Real-time. This information will help to identify queries which are not using Indexes. Note: this is available only for Performance Schema mode.
  • Added a new monitor group ‘sys schema’. It contains various CSOs (Custom SQL Objects) utilizing the “sys schema” database introduced in MySQL 5.7.7.
  • Added an option to either have a fixed length height or dynamic (full screen) height for Processlist in MONyog GUI. We have been using each in earlier versions, but it seems impossible to make everyone happy with a single solution. Now user can choose what display/design that fits him best.
  • Bug Fixes:
  • The MONyog API failed to set the error log path.
  • With MySQL 5.7+ Query Analyzer was displaying seemingly random values for the column “first seen” and “last seen” when using server logs (slow query log, general query log) as data source. This happened because of change of Timestamp format in the logs in MySQL 5.7.
  • The filter “doesn’t contain” was not working properly in Real-time.
  • Fixed an issue where UDOs were displaying incorrect values after running for some time.
  • While editing the server using MONyog API, SSH settings were automatically set to disabled (even if it was enabled earlier).
  • For RDS/Aurora servers, “Apply the above settings to all the servers with same tags” (Edit server -> Advanced settings) was not working.
  • MONyog was giving the error “Log file not present” if either one of the slow query log or general query log was disabled for RDS servers.
  • Fixed Javascript errors and optimized the charts for Real-time page for IE8 browser.
  • Miscellaneous:
  • The Y-axis in Charts had just “values” written, now it shows relevant units like percentage, seconds etc. and option is provided to customize the Y-axis value.

New in MONyog 6.5.1 (Mar 3, 2016)

  • Features:
  • RDS log monitoring feature can now be configured using the MONyog API.
  • Bug Fixes:
  • The query SHOW ENGINE INNODB STATUS fails for MySQL version less than 4.1.2. and resulted in a MONyog crash. Even though we don’t recommend MySQL 4.1 (and not at all such early beta of it), we should not crash.
  • Fixed JavaScript errors for Query Analyzer and Real Time tab in Internet Explorer 8 (WinXP, Win2003).
  • With MariaDB 10.1.x MONyog erroneously listed all user accounts as having no password.
  • The curl library used could crash, and thus crash MONyog, when resolving too many hostnames at the same time.
  • Monyog failed to send ‘stable alert’ when both “notify till stable” and “notify when stable” options were enabled and if different values were set for the “send notification when alertable” and “remind me after every ..”.
  • Fixed the height of the Processlist display for each server. Each server’s processlist window is now displayed as scrollable window of fixed height. This is a regression fix and a revert of the page design to that of older versions. With recent versions it was necessary to scroll the browser window.
  • Miscellaneous:
  • Upgraded SQLite library to v3.9.1. This results in ~25% performance improvement on most environments.
  • Renamed the “Row Access Statistics” counter to “Queries Executed” as it actually uses the ‘queries’ status variable. The old term confused some users.

New in MONyog 6.5.0 (Mar 3, 2016)

  • Features:
  • On Amazon RDS and Aurora, MySQL log files (Slow Query Log, General Query Log and Error Log) can now be read by MONyog. So Error Log monitoring is now possible here, and the Query Analyzer does not require logging to tables anymore. For this the Amazon “REST” API (and not SFTP) is used. Client functionalities for this API have been integrated into MONyog.
  • Added monitors for Galera: “Presence of non-InnoDB tables” and “Tables without a primary/unique key”.
  • Bug Fixes:
  • Monitors and Real-time page failed to load on Internet Explorer 8 (highest IE option on WinXP) due to javascript errors.
  • Fixed a rare crash when connected to MySQL 5.7.6+.
  • Accessing Realtime interface could cause a crash if connection to the server was not available.

New in MONyog 6.4.0 (Mar 3, 2016)

  • Performance Schema is now available in Realtime:
  • MONyog can now capture all queries and display it in realtime which was not possible earlier with SHOW FULL PROCESSLIST output. To view all queries in realtime, make sure Performance_schema and ‘statements_digest’ table is enabled. If not, MONyog will display the output of SHOW FULL PROCESSLIST in realtime.
  • Bug fixes:
  • Users with MySQL v5.6.3+ will now see explain plan for Insert, Update and Delete queries in Wayback Machine and Query analyzer.

New in MONyog 6.3.4 (Mar 3, 2016)

  • Features:
  • Added more monitors and charts for monitoring a galera cluster. By default, these monitors are hidden. To display these monitors in Monitors page you can enable “Galera” monitor group from Customize -> Manage Monitor Groups. Charts for these new monitors can be enabled from Customize – > Manage charts.
  • Optimized system charts for faster loading.
  • Bug Fixes:
  • EXPLAIN option was not available in Wayback Machine.
  • In some rare cases, MONyog logged SQLite errors if deadlock details contained double quotes.
  • In Wayback Machine interface, MONyog showed wrong time in queries tab when a point was selected in the chart.

New in MONyog 6.3.3 (Mar 3, 2016)

  • Features:
  • Added monitoring of the MySQL –tmpdir volume with the “Free Disk Space” Monitor for Linux (introduced in 6.32).
  • Added an option to view X-Axis labels for large time based charts.
  • The Performance_Schema -based “query sniffer” has been optimized.
  • Bug Fixes:
  • Fixed a rare case, where “Charts” page was not loading properly.

New in MONyog 6.3.2 (Mar 3, 2016)

  • Features:
  • Added a “Free Disk Space” Monitor for Linux. This new feature will collect information directly from the file system (unlike the existing ‘Disk Info’ that uses MySQL “SHOW TABLE STATUS”). Information is collected from volumes storing both MySQL data directory and InnoDB data directory (if different), and user will be alerted if either crosses a specified threshold.
  • In Charts page added an option to select a time interval for display by zooming a chart using mouse and similar input devices (touchpad etc.). Note that zooming one chart will change the timeframe of all the charts displayed.
  • Added an option to view queries for a selected time range in time range based charts in Charts page.
  • Bug Fixes:
  • 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 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.

New in MONyog 6.3.1 (Mar 3, 2016)

  • Features:
  • 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 w ildcard filtering using the “*” character as wildcard for user and host in Query Analyzer for Slow Query Log.
  • Bug Fixes:
  • MONyog failed to send notification for an InnoDB deadlock if deadlock details (as recorded by SHOW ENGINE INNODB STATUS) contained double quotes.

New in MONyog 6.3.0-0 (May 20, 2015)

  • Features:
  • 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 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 option in Sniffer (applies only to Processlist mode of sniffer).
  • MONyog now logs which user killed a thread in Processlist tab.
  • SQLite library bundled in MONyog is now upgraded to the latest version. This results in performance improvement for sniffer in particular where it can be up to ~50%.
  • Bug Fixes:
  • In some cases, MONyog logged SQLite errors when CSOs (Custom SQL Objects) were enabled even when the CSO worked as expected
  • Small UI fixes.

New in MONyog 6.2.7-0 (May 20, 2015)

  • Bug fixes:
  • MONyog 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 debugging module/plugin.
  • MONyog 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.

New in MONyog 6.2.6-0 (May 20, 2015)

  • Bug fixes:
  • When monitoring MySQL 5.6.3 and higher, MONyog 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 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 now contain Tag(s) and MySQL host of the corresponding server.

New in MONyog 6.2.5-0 (May 20, 2015)

  • Features:
  • Optimized Monitors page to populate faster. In particular in history/trends timeframe this is a dramatic performance improvement, as it will now populate 50 or more times faster than before with large data series.
  • Bug fixes:
  • An incorrect (javascript) monitor definition could cause a yellow bar-shaped area to appear instead of a proper error in Monitors page for the affected counter.
  • Setting ‘Notify Till Stable’ using the MONyog API was not working as expected.
  • Fixed a rare crash with a large number servers monitored. It would require more than 300 servers registered for this crash to occur on an average system.
  • Minor UI fixes.

New in MONyog 6.2.4-0 (May 20, 2015)

  • Bug Fixes:
  • MONyog was resetting “Monitor long running queries” to NO after editing a server.
  • MONyog failed to show servers in the UI after upgrading from a pre-5.57 version.
  • “Critical”, “Warning” and “Stable” icons were not showing in Events tab when MONyog was running behind a proxy.
  • MONyog sometimes logged an SQLite locking protocol error while opening internal database(s). But as this is handled it should not be logged as an error.
  • MONyog allowed for saving of server registration details when “Long running query time” was specified smaller than “Minimum time taken” in sniffer settings. This makes no sense and will not save now.
  • MONyog was not considering buffers and cached values from meminfo while calculating RAM usage. The formula for the same is updated now.
  • Miscellaneous:
  • Charts are now enabled by default for all monitors which include MySQL status variables. For example: “Seconds behind master” in replication group.

New in MONyog 6.2.3-0 (May 20, 2015)

  • Features:
  • Added support for the ‘clear-text plugin’ (used by Oracle/MySQL LDAP authentication) and the ‘dialog plugin’ (used for MariaDB PAM authentication). There is no user setting for either. MONyog will transparently for user detect how to communicate with the server during authentication.
  • Bug Fixes:
  • When data collection was stopped for a server then, in some cases, user was not able to delete that server.
  • In ‘Wayback Machine’ interface, the plotted values were sometimes not visible due to how axes were scaled in the chart displayed.
  • If data collection for a server was stopped, then after restarting MONyog. and enabling data collection for that server, the values displayed in the Monitors tab were not getting updated in some cases.
  • Miscellaneous:
  • UI changes for ‘long running queries’ and counters with CSO disabled to make it more intuitive how to fully enable those features.
  • SMTP and SNMP alerts will now as default be sent first time an alertable counter has exceeded the ‘critical’ setting.
  • Formula of a monitor will now be displayed in event detail dialog in Events tab.

New in MONyog 6.2.2-0 (May 20, 2015)

  • Features:
  • MONyog can now resend alert notifications till a counter becomes stable based on a reminder interval setting.
  • Bug Fixes:
  • ‘Upgrade check’ link in 6.21 informed that an “undefined” upgrade was available even though it was not the case.
  • Performance-schema -based sniffer failed if global sql_mode included “ONLY_FULL_GROUP_BY”.

New in MONyog 6.2.1-0 (May 20, 2015)

  • Bug Fixes:
  • In Monitors page, the small trend charts (in current and delta timeframes) were not displayed for some monitors.
  • Charts were not displayed in Monitors page .. history/trend if data series contained “N/A” values.
  • MONyog was not able to connect to MySQL server if password contained a leading or a trailing empty space.
  • In rare cases, some server(s) could stop showing in the UI after MONyog restart.
  • Fixed a rare irresponsiveness (“hang”) occuring when starting data collection after editing server details.
  • The option to stop the current running saved session was not available in Real-Time in some cases.
  • A number of minor GUI fixes.

New in MONyog 6.2.0-0 (May 20, 2015)

  • Features:
  • The Real-Time interface in MONyog has been completey rewritten. In addition to a more consistent/intuitive GUI it is now able to collect data from multiple MySQL servers simultaneously (one collection of Real-Time data per server). Once data collection for a server has been started it will continue untill stopped by user, also if browser connection is closed in between. The sole exception is that Real-Time data collection for a server will stop after 3 days if no activity has happened inside the particular Real-Time session.
  • Added an option to set line terminator for csv reports.
  • Bug Fixes:
  • Renaming a registered server to a new name already in use would not raise any error. Instead data for the affected server would not display anymore.
  • In rare cases clicking ‘test SSH settings’ -button would not display any response.
  • When registering a “Postmaster Enterprise SMTP server” in MONyog, mail notifications failed to be sent.
  • ‘diagnostics report’ failed to download when MONyog was running behind a HTTP (‘reverse’) proxy server.
  • Clicking on editing SMTP settings from server registration page did not redirect to tools page and thus editing was not possible from here. The problem was alone a problem with the particular hyperlink. From the tools page everyting worked as expected.
  • The following gtid-related variables in MariaDB 10 could trigger false notifications: gtid_binlog_pos, gtid_binlog_state, gtid_current_pos, gtid_slave_pos and last_gtid.
  • MONyog failed to establish SSH connection to Linux servers using the “OpenSSH-HPN” SSH implementation.
  • When an identifier contained digits (such as ‘abc12', ‘ab12ab’ etc.), the Query Analyzer, the WayBack Machine and Real-TIme interface would consider these digits literals, and they would be replaced with ‘?’.
  • If MONyog did not have sufficient privileges to the MONyog /Data folder, adding a new server could crash MONyog.
  • In rare cases replication page could fail to render properly.
  • Miscellaneous:
  • Dashboard page was renamed to ‘Charts’.
  • The tab-order of MONyog’s interface has been rearranged.
  • Also note that ‘WayBack machine’ interface is still available (unlike what was the case with the 6.2 beta, where we experimentally removed it)

New in MONyog 6.1.0-0 (Jun 30, 2014)

  • Features:
  • Added more counters and advisors for MySQL 5.6 configuration.
  • Added an extensive set of counters for monitoring the TokuDB storage engine. The monitor groups for this are not visible as default, but can be enabled from the ´Customize’ interface.
  • Bug Fixes:
  • Fixed a rare SQLite database corruption under very heavy load and with Custom SQL Objects enabled.
  • Changing refresh interval setting for Processlist page was not possible for non-admin users.
  • Miscellaneous:
  • MONyog installed on the Amazon Cloud from the Amazon Machine Image (“AMI”) we provide as an option, will now start first time with the Amazon instance ID as the admin password and not an empty password as before. This change could take some days to propagate across the Amazon Cloud.

New in MONyog 6.0.1-0 (Jun 11, 2014)

  • Cleaned up the User Interface in Real-Time page. This includes removing the option to restore saved sessions for ‘all selected servers’. Saved sessions for individual servers can still be restored.
  • OpenSSL is updated to version 1.0.1h in all packages distributed.

New in MONyog 6.0.0-1 (Jun 4, 2014)

  • Features:
  • The MONyog API is enhanced with more options to manage servers registered in MONyog. Options now include calls to add/edit/remove servers. Refer documentation for full details.
  • MONyog now supports Query analysis using Performance Schema tables (events_statements_summary_by_digest and events_statements_history_long tables). This feature is supported only for MySQL 5.6.14 and MariaDB 10.0 and above.
  • Explain plan is available in Query analyzer for Slow_log table based logging and Processlist sniffer.
  • An example query is now shown in detailed query view in Query analyzer if queries replaced with literals is selected.
  • MONyog now has a configurable option to define the max. query length displayed. Beyond this MONyog will truncate the query. The setting has effect for Query Analyzer, Real-time and Way Back Machine interfaces. Default is now 10000 characters and maximum setting is 64000 characters. However please note that this does not apply when Performance_Schema is used with the Query Analyzer as P_S itself truncates. For details please see the note at the bottom.
  • Bug Fixes:
  • Explain option was not available in locked and locking queries for Real-Time sessions.
  • In some rare case MONyog logged SQLite errors while running Real-Time sessions.
  • MONyog could crash when connecting using a ‘Named Pipe’ on Windows. Actually we never promised support for Named Pipes. But we should not crash, of course, and it works with Named Pipes now.
  • When monitoring MySQL v5.6 with replication using GTIDs (global transaction IDs), MONyog reported false notification alert for the ‘gtid_purged’ variable, when notifications for change in server configuration was enabled. This particular variable was overlooked in 5.72 where there was a similar fix.
  • Yet another fix for a LDAP group authentication issue.
  • Query literals with hex values were not replaced with ‘?’ in Query analyzer.
  • When using SSH-tunnel, connections created by the CSO (Custom SQL Object) feature were not always closed properly, and the MySQL error log as well as ‘aborted_clients’ status variable would record aborted connectons.
  • Miscellaneous:
  • When GTID’s (Global Transaction ID’s) were used with replication, MONyog’s replication page would display a lot of information about changing GTIDs. This is now hidden in the primary interface, but can still be displayed in detailed view.
  • MONyog now displays the binary version on commandline when the command switch –version (or -v) is used.

New in MONyog 6.0.0-0 Beta 1 (May 10, 2014)

  • Features:
  • The MONyog API is enhanced with more options to manage servers registered in MONyog. Options now include calls to add/edit/remove servers. Refer documentation for full details.
  • MONyog now supports Query analysis using Performance Schema tables (events_statements_summary_by_digest and events_statements_history_long tables). This feature is supported only for MySQL 5.6.14 and MariaDB 10.0 and above.
  • Bug Fixes:
  • Explain option was not available in locked and locking queries for Real-Time sessions.
  • In some rare case MONyog logged SQLite errors while running Real-Time sessions.
  • MONyog could crash when connecting using a ‘Named Pipe’ on Windows. Actually we never promised support for Named Pipes. But we should not crash, of course, and it works with Named Pipes now.
  • When monitoring MySQL v5.6 with replication using GTIDs (global transaction IDs), MONyog reported false notification alert for the ‘gtid_purged’ variable, when notifications for change in server configuration was enabled. This particular variable was overlooked in 5.72 where there was a similar fix.
  • Miscellaneous:
  • Documentaion for the new features is in progress, but not completed with this beta release.

New in MONyog 5.7.2-0 (Apr 12, 2014)

  • Bug fixes:
  • In rare cases, MONyog could not close alerts from Monitors page.
  • When monitoring MySQL v5.6 with replication using GTIDs (global transaction IDs), MONyog reported false notification alert for GTID counters when notifications for change in server configuration was enabled.
  • Miscellanous:
  • Upgraded libraries that theoretically could be vulnerable to the ‘Heartbleed’ OpenSSL bug. All users are urged to upgrade as soon as possible.

New in MONyog 5.7.1-0 (Mar 28, 2014)

  • 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 intrerface can now show the actual query in addition to replacing literals with the “?” wildcard.
  • Bug fixes:
  • 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.
  • Miscellanous:
  • 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.

New in MONyog 5.6.5-0 (Nov 7, 2013)

  • Bug fixes:
  • 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 5.62.

New in MONyog 5.6.4-0 (Oct 21, 2013)

  • This release is a stability-fix release. Fixes 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.

New in MONyog 5.6.3-0 (Sep 30, 2013)

  • Bug fixes:
  • If MONyog was not able to connect to a MySQL server, replication page would ‘hang’ and even crash in rare cases. This was introduced in 5.62.

New in MONyog 5.6.2-0 (Sep 25, 2013)

  • Features:
  • Removed a hardcoded 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. Customers of ‘MONyog unlimited’ requiring more than 512 MySQL servers registered in one MONyog instance can request a special license key.
  • Added and updated a few counters in order to provide more specific support for MySQL 5.6 and MariaDB 10.
  • Bug fixes:
  • 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 MONyog due to CPU contention.
  • Explain option was not present in processlist page for queries starting with comment.
  • Rendering of replication page failed if GTID (Global Transaction ID) mode was enabled for MySQL Slaves.
  • Resolving the ip from a hostname happened multiple times during display of replication page what could slow down rendering of replication page noticably 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.
  • On Windows ‘Real_time’ monitoring did not work since 5.61.
  • When restarting MONyog it would perform a SQLite Schema upgrade even if it was not required. Version 3.61 was affected.

New in MONyog 5.6.0-4 (Aug 3, 2013)

  • Features:
  • MONyog supports LDAP authentication (including Microsoft ‘Active Directory’) for login into MONyog interface (Note: This is available only in Ultimate version of MONyog).
  • Added a feature in Query Analyzer to include or exclude queries based on a search string / regular expression.
  • Bug fixes:
  • 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 a 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). We now check for this condition and don’t crash.

New in MONyog 5.6.0-2 Beta (Jul 4, 2013)

  • Features:
  • MONyog now supports LDAP with Encryption, which was not supported in beta 1. Also, the Microsoft/Windows LDAP ‘dialect’ known as ‘Active Directory’ is now supported.
  • Bug fixes:
  • Queries starting with a comment did not show EXPLAIN option in the Real Time interface.

New in MONyog 5.6.0-0 Beta (Jun 12, 2013)

  • Features:
  • MONyog supports LDAP authentication for login into MONyog interface (Note: This is available only in Ultimate version of MONyog).
  • Added a feature in Query Analyzer to include or exclude queries based on the search string / regular expression.
  • Bug fixes:
  • 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 a comment.

New in MONyog 5.5.8-0 (Apr 30, 2013)

  • Features:
  • Added a feature in realtime to include or exclude queries based on the search string / regular expression.
  • Bug fixes:
  • Purging mechanism was not working properly (this bug was introduced in MONyog 5.57).
  • Tag/Group names are in alphabetical order now..
  • MONyog can now “Kill query” on Amazon RDS instances.
  • The rendering of Dashboard page is further improved.

New in MONyog 5.5.6-0 (Dec 28, 2012)

  • Fixed a memory leak when reading MySQL server logs through SFTP.
  • Fixed a multi-threading issue that in rare cases could crash MONyog 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.

New in MONyog 5.5.5-0 (Dec 18, 2012)

  • Bug fixes:
  • 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 MONyog 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.

New in MONyog 5.5.4-0 (Nov 28, 2012)

  • Bug fixes:
  • Sometimes MONyog could hang while editing server’s tag.
  • Processlist did not show “view query” for prepared statements.

New in MONyog 5.5.3-0 (Nov 22, 2012)

  • 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.
  • Bug fixes:
  • 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.

New in MONyog 5.5.2-0 (Oct 19, 2012)

  • Bug fixes:
  • When upgrading to MONyog 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 in MONyog 5.5.1-0 (Oct 17, 2012)

  • 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.
  • Added an option in ‘Real-Time’ to view all saved sessions for all selected servers.
  • Added a ‘thread count’ showing number of currently running threads on ‘Processlist’ page.
  • Bug fixes:
  • In the ‘Real Time’ interface displaying large BULK INSERTS was slow.
  • Logging out from MONyog while ‘Real Time’ was populating could crash MONyog. Linux – and not Windows – was affected.
  • In the replication overview page MONyog 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 in MONyog 5.5.0-0 Beta 1 (Aug 30, 2012)

  • 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 MONyog 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 MySQL docs for more information on InnoDB plugin. Also note that constants listed here are currently ‘hard-coded’ but we plan to implement user settings.
  • 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.

New in MONyog 5.3.0-1 Beta 2 (Jul 24, 2012)

  • Features:
  • Introduced support for 'native' MySQL SSL-encryption with direct MySQL connections.
  • 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.
  • MONyog now fully supports Internet protocol version 6.
  • Bug fixes:
  • 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.
  • UI fixes.

New in MONyog 5.1.1-1 (Apr 9, 2012)

  • Features:
  • Introduced tag level customization in MONyog Monitors. MONyog 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.
  • Bug fixes:
  • On MONyog 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 MONyog 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 MONyog 5.0.
  • UI fixes.
  • Miscellaneous:
  • Increased MONyog session timeout from 30 minutes to 8 hours (the MySQL default).

New in MONyog 4.8.1-4 (Jan 11, 2012)

  • Bug fixes:
  • Custom SQL Objects (CSO) with a large result set could fail to display content in Monitors/Advisors page.
  • Specifying the “Key Column” field has now been made mandatory while adding a new CSO. If not specified the CSO will not save.
  • Small UI fixes.

New in MONyog 4.8.0-3 (Dec 19, 2011)

  • Features
  • This release adds a new major feature to MONyog: Custom SQL Counters and Custom SQL Objects. A Custom SQL Object is an object populated from a user-defined SQL-query returning a result set. It is exposed as a javascript array for defining counters (Custom SQL Counters) in MONyog
  • Bug fixes
  • If a query contained the literal substring 'connect' MONyog could hang during general log analysis
  • MONyog returned a garbage string to the Linux ‘ps’ command
  • Drastically improved performance in log analysis if the option to 'replace literals' was selected
  • Some of the Monitors/Advisors were not updating in All Time/Current and Delta timeframe

New in MONyog 4.72 (Dec 19, 2011)

  • Bug fixes
  • When connected to Linux distributions with a 3.x kernel the information about Disk I/O could fail to display properly in Dashboard and Monitors/Advisors pages of MONyog

New in MONyog 4.71 (Dec 19, 2011)

  • Bug fixes
  • Accessing the replication tab could crash MONyog in rare cases with specific replication setups and where SHOW MASTER STATUS returned an empty result
  • Fixed an issue where user defined generic (javascript) functions added for use by customizations did not work as expected
  • Small UI fixes

New in MONyog 4.7 (Dec 19, 2011)

  • Features
  • Added a MySQL replication overview page. Here MONyog shows the replication topology of all registered MySQL servers, as well as SLAVE STATUS and MASTER STATUS where it applies. The display gets updated at user-specified interval. (Note: This is available only in Ultimate version of MONyog)
  • Added a ‘Wayback Machine’. In this interface a graph displaying - as per user's choice - either of the status variables 1) Threads connected or 2) # of slow queries. The graph displays aggregated values on years/months/days/hours/ minutes depending on the data. If sniffer was running during this interval, aggregated sniffer information will be displayed. Also you can see first and last value of (optionally) all or changed variables aggregated values. The graph is zoomable by selecting a sub-interval with the mouse along with aggregated sniffer and changed variables you can also get point-in-time information by clicking on a point on the graph. When user clicks on a row in the query list of the Wayback machine a pop-up opens with information about thread-id, user and host along with full query.The list of queries in Wayback Machine will not be rendered if there are more than 2000 queries in the time period. There is a user control that can be activated in such case. The reason is that every 1000 queries take around 1 seconds to render on an average desktop system. This also means that we can now display the list of queries before zooming (provided still that there not more than 2000 queries to display). When we do a point in time select of one of the points on the graph, we get a bar chart that displays number of queries
  • With this release the dependency on Flash has been removed. Charts are now rendered using a Javascript library. Accordingly MONyog can now be handled from a browser on a device not supporting Flash (such as Ipad). These charts can be exported like was the case with Flash-based charts of previous versions. Conversion to various formats uses a web service
  • Bug fixes
  • Fixed an issue where MONyog did not logout user successfully
  • If the time is set to 12:XX:XX in Custom filter it resets to 00:XX:XX
  • Misc
  • Instructions to setup MySQL Proxy was added to MONyog interface

New in MONyog 4.62 (Dec 19, 2011)

  • Bug fixes
  • The counter for ‘thread cache hit rate’ could display incorrect values
  • Authentication with the admin password could fail in some cases on Windows. This bug was introduced in 4.61

New in MONyog 4.61 (Dec 19, 2011)

  • Bug fixes
  • In Dashboard & Monitors/Advisors page, the Delta & All-time/Current charts were showing incorrect values when values were plotted per second. This was introduced in MONyog 4.51
  • While connecting using SSH with key based authentication in Windows, the temporary file which contains the SSH private key was not being deleted. Before this release, the temporary files could run out of names which made it impossible to create new temporary files and hence the SSH tunnel was not being created
  • MONyog now writes default data into MONyog.ini file on all platforms when MONyog starts for the first time. Before this release MONyog for Linux did not write default data into MONyog.ini file
  • Fixed a crash occurring when there was no data directory path mentioned in the MONyog.ini file

New in MONyog 4.6 (Dec 19, 2011)

  • Features
  • MONyog is now bundled with a bunch of useful dashboard charts which can be enabled/disabled from the ‘manage dashboard charts’ in the Dashboard page. These charts can even be re-orderd
  • Added an option to ‘Alert on change in server configuration’. These alerts in the form of email's and/or SNMP traps are sent by MONyog whenever MONyog detects a change in the server variables using SET GLOBAL statements or in the MySQL configuration file
  • Added an option to copy/duplicate advisors. This is available when clicked on an advisor in the 'Monitors/Advisors' page
  • Bug fixes
  • Export as CSV in the 'Monitors/Advisors' page was showing '0' for some of the advisors when the group to which they belong was disabled
  • GUI fixes, including an issue where clicking a ‘next’-link in the ‘register server’ page did nothing

New in MONyog 4.51 (Dec 19, 2011)

  • Features
  • This release focuses on improving performance of the MONyog built-in HTTP daemon. You will find up to 10 times performance improvements for most MONyog pages. This has been achieved by internal code optimizations, use of compression (if browser supports) and minification/optimization of HTML, Javascript, CSS and graphics
  • Bug fixes
  • Prepared statements were not handled properly by the Query Analyzer
  • Events (as introduced in 4.5) stored in the MONyog embedded database did not purge as specified in the 'retention time frame' setting
  • Charts could display decimal numbers with a large number of decimals that made no sense and made charts less readable. We now round to 3 decimals

New in MONyog 4.5 (Dec 19, 2011)

  • Features
  • Added an EVENTS overview. An EVENT happens when any counter is changing its status to (yellow) WARNING alert level or to (red) CRITICAL alert level. An ‘alert condition’ (WARNING or CRITICAL) can be temporarily disabled (and re-enabled) for a specific server from the new EVENTS overview page as well as the Monitors/Advisors page. This can be disabled for non-admin users
  • Replication slaves can now be automatically registered. MONyog will detect the host/IP of active slaves. MySQL (port,username & password) and the SSH details of the slaves are assumed to be the same as that of its master. Connection details of the slaves can be edited if different from master. A slave will indent with its master in a hierarchy while displaying in the list of servers page. Auto-registering of slaves is also extended to multiple levels. 'Test Connection' in the 'Register/Edit server page' will test the slave connection details of that server in recursion, when 'Auto-register all slaves' is checked
  • In the process-list based sniffer there is now an option to alert (using mail and/or SNMP) for long-lasting LOCKs
  • Monitors/advisors groups can now be enabled/disabled on a per server basis. Before this release it was only possible to have same setting for all servers registered in MONyog in this respect
  • Added monitors/advisors for innodb_force_recovery, log_warnings, log_output, expire_logs_days
  • max_binlog_size and flush_time variables
  • Query Analyzer can now filter slow logs based on host and user information
  • The standard Linux daemon PID file is now created for MONyog. (If tools like 'Monit' are being used, then the PID file of MONyog would be required.)
  • Bug fixes
  • Padding while exporting slow log as CSV was incorrect
  • MONyog could hang while parsing a log file with binary data
  • With MONyog running behind a Load Balancer and similar network management system, user login to MONyog could fail
  • MONyog could hang while downloading slow or general logs from a server if the server wrote new entries to the log at download-time
  • The emails sent by MONyog were missing the date header
  • Monitors/advisors page was displaying error for MySQL 5.5.x when Innodb engine was disabled
  • Fixed an UI issue with the Group level display of alerts (red/yellow) in monitors/advisors page
  • Fixed a bug with the system graphs in the 'dashboard' feature where the graphs were not plotting the current values
  • Lots of GUI fixes and small GUI enhancements

New in MONyog 4.2 (Dec 19, 2011)

  • Bug fixes
  • MONyog could crash while monitoring hundreds of servers through SSH tunneling with a small data collection interval. (1 or a few seconds)
  • Charts in the I/O section under Monitor's/Advisors or Dashboard displayed wrong history. (last 14 seconds had the same values as the value in the 15th second)
  • Sometimes, while analyzing the slow query log, some timestamps contained the default unix time stamp
  • If the name of a counter or caption of dashboard chart contained single quotes, the chart displayed "Invalid XML Data"
  • Filtering while displaying the Sniffer output was not working when there was a change in the filter conditions
  • The Linux command 'Service MONyogd status' did not display the correct result
  • The 'Processlist page' in MONyog threw 'constraint failed' error when the process ID was a large number
  • At times, the 'Query Execution Time' of Query Analyzer displayed incorrect values for the milliseconds field
  • MONyog was not closing the file descriptors after reading from MySQL error log (introduced in 4.12) and sending SNMP traps
  • Miscellaneous
  • Every time MONyog (re)starts it logs "MONyog has started" in MONyog.log

New in MONyog 4.12 (Dec 19, 2011)

  • Bug fixes
  • MONyog was leaking memory while connecting through SFTP to analyze Slow/General logs
  • MONyog also leaked memory when 'Processlist' page was open
  • Stopping of Data collection could crash MONyog
  • Sometimes MONyog service could not be stopped gracefully
  • MONyog was not able to read the Error log via SFTP for data collection interval less than 25 seconds
  • Max open .idb files counter under Innodb-Others group sent a false 'warning alert'. (Yellow light would turn on even though the value of innodb_open_files did not exceed the threshold)

New in MONyog 4.11 (Dec 19, 2011)

  • Bug Fixes
  • Email alerts or SNMP traps related to counters were not sent. This was introduced in 4.1
  • Minor usability fixes

New in MONyog 4.1 (Dec 19, 2011)

  • Bug fixes
  • Fixed a performance regression issue (introduced in 4.0) in HISTORY/TREND analysis
  • Fixed an issue where Dashboard charts were not always populated properly with ‘old’ data when the Dashboard page was opened. The chart itself and the data-series for the chart are independent data streams which were not always ‘combined’ correctly
  • The process-level MONyog stack size on Linux is now always expandable up to 10 MB (Linux kernel default) even if the user has defined another value. We had a report wherFeatures
  • Implemented an easy-form based interface for customizing helper functions. Any customization of helper functions or user defined functions being used with earlier versions have to be migrated manually to this version. From this version and onwards a GUI-’conflict resolver’ will guide the users very similar to how it works for customized counters
  • MONyog now has an option to apply a group of settings to all the servers with a specific tag. (Please note: New servers registered later with the same tag are not considered)
  • MONyog logs from now on contain the server name along with error, making it easy to backtrack
  • We have automated deleting dump files of size zero
  • Earlier multiple alerts for same issue would be sent if the counter was alertable for more than the specified number of data collections. Now we only send once. Settings in register server page has been updated accordingly
  • Added an option to change the refresh interval from the processlist page
  • Processlist-based sniffer will no longer show the query 'SHOW FULL PROCESSLIST' executed by MONyog (Please note: This only applies to the processlist-based sniffer and not to the processlist page where user has configurable filtering options)
  • Bug fixes
  • Fixed a (SQLite) database lock resulting in failure to update Dashboards and Monitors/Advisors pages
  • When SFTP option was chosen to analyze 'MySQL general query log' and SSH was disabled, MONyog used SFTP to analyze the logs with out throwing any error
  • Small GUI enhancements
  • Resolved crashes found internallye MONyog would crash with a very low user setting (and this is basically an OS issue and not a MONyog issue)
  • If a MONyog build with a ‘lower’ license than ULTIMATE was installed ‘on top’ of the TRIAL some ULTIMATE functionalities would still run in the background – but not controllable by user. MONyog continued to collect data internally for counters not applicable to ENT or PRO edition and the MONyog.log would log errors irrelevant for the license model

New in MONyog 4.02 (Dec 19, 2011)

  • Bug fixes
  • Fixed a performance regression issue (introduced in 4.0) in HISTORY/TREND analysis
  • Fixed an issue where Dashboard charts were not always populated properly with ‘old’ data when the Dashboard page was opened. The chart itself and the data-series for the chart are independent data streams which were not always ‘combined’ correctly
  • The process-level MONyog stack size on Linux is now always expandable up to 10 MB (Linux kernel default) even if the user has defined another value. We had a report where MONyog would crash with a very low user setting (and this is basically an OS issue and not a MONyog issue)
  • If a MONyog build with a ‘lower’ license than ULTIMATE was installed ‘on top’ of the TRIAL some ULTIMATE functionalities would still run in the background – but not controllable by user. MONyog continued to collect data internally for counters not applicable to ENT or PRO edition and the MONyog.log would log errors irrelevant for the license model

New in MONyog 4.01 (Dec 19, 2011)

  • Bug fixes
  • Implemented code that makes OpenSSL (which is used by our SSH library) explicitly thread-safe, thus fixing an issue where specific cryptographic function calls under very heavy load could cause a crash
  • Fixed a SQLite corruption issue on Windows due to which MONyog service failed to stop
  • If both values for ‘user’ and ‘host’ were filtered in processlist-based sniffer the interface would display NULL for both

New in MONyog 4.0 (Dec 19, 2011)

  • Features
  • Compare Configuration: This feature enables the user to compare changes in configuration between two instances of MySQL. Through this feature, the user will gain a greater insight on why one server is performing better than the other as far as server configuration is concerned
  • Track Changes: This feature enables users to track changes to my.ini/my.cnf of a MySQL server over a period of time and compare changes between revisions
  • Added a new interface for customizing Monitors/Advisors and Dashboard charts requiring less knowledge of JavaScript than what was the case before
  • When upgrading an installation with customized Monitors/Advisors and Dashboard charts a 'conflict resolver' will now guide user to either migrate his old changes or discard them
  • All cache hit rate related monitors/advisors have been changed to display cache miss rate information as it more relevant when tuning databases. Also the advisor text for these monitors/advisors has been improved
  • Bug fixes
  • Fixed some issues with specific counters including issues where ‘undefined’ or ‘NaN’ were returned incorrectly
  • Graphs in ‘all time’ and ‘delta’ timeframes for the counter ‘Cache Misses’ for as well InnoDB Cache, MyISAM key cache and Query cache groups were not displaying but threw the error “Invalid XML data” (these counters were added in beta 1)
  • Previously accepted values for the “ChartValue” property in Dashboard charts were “Current” and “Latest”. This has caused confusion since both terms mean the same thing in this context, although technically “Current” refers to the current value of the metric and “Latest” to the “Delta” value. Moreover, the documentation mentions “Actual” and “Delta” as accepted values. To eliminate this confusion, the “ChartValue” property now accepts the values “Current” and “Delta” – “Current” referring to the current value of the metric, and “Delta” to the difference in the metric between the previous two collections
  • Monitors/Advisors Customization: The Group Name of a Monitor/Advisor can now be changed only when a new, custom, counter is created; once set it cannot be changed. Changing Group Names of Monitors/Advisors shipped with MONyog is not allowed
  • All cache hit rate related monitors/advisors have been changed to display cache miss rate information as it more relevant when tuning databases. Also the advisor text for these monitors/advisors has been improved
  • Miscellaneous
  • Windows 2000 is no longer supported

New in MONyog 3.8 (Dec 19, 2011)

  • Bug fixes
  • Monitors/Advisors on InnoDB Deadlocks were truncating the output message and hence in some cases, users were unable to view both queries involved in the deadlock. This has been changed such that the first 2048 characters of both queries are displayed
  • On Windows 7 systems changes to MONyog’s .INI file from external programs had no effect upon restart (as Windows reverted the changes). Now throughout MONyog’s lifetime the .INI file will be locked so that a user may only edit the file manually when MONyog is not running (but users can use the MONyog interface to change any setting while MONyog is running). Any changes made to the file when MONyog is not running will be reflected by it once it is restarted
  • If MySQL Error Log monitoring was enabled for a particular server, the first two data collections for that server would cause large network traffic to occur if the MySQL error log was very large. This was because the entire log fie is read in the first collection. Now only the last 1MB of the file is read
  • Miscellaneous
  • All libraries have been upgraded to their latest versions. Although, from a user-perspective, the changes are minimal, this has alleviated several memory leaks and other performance issues
  • This release has been checked in depth with the best leak-detection tools available for both Linux and Windows. All discovered leaks have been fixed
  • The cache parameters for the SQLite library have been modified with this release to allow for registering more servers on the same system as before. Before MONyog’s memory usage used to grow continually with time as each open SQLite handle has an associated cache which could grow to any size, irrespective of system capacity. The cache size per handle has been reduced and the total SQLite cache size will never exceed 1 GB with this build

New in MONyog 3.76 (Dec 19, 2011)

  • Miscellaneous
  • Added a ten server license

New in MONyog 3.75 (Dec 19, 2011)

  • Bug fixes
  • Failure to open the SQLite resource DB located in MONyog's installation directory could result in a crash. This crash has been fixed, but note however that MONyog is unable to function without this resource DB and will log an error message and perform a graceful exit
  • The Monitor/Advisor "Binary Log" --> "Transactions that got saved in temporary file" displayed "NaN" (JavaScript for Not-a-Number) for non-zero values of the associated MySQL counter
  • Miscellaneous
  • Internet Explorer 6.2800 on Windows 2000 may hang when trying to display MONyog's interface. The behavior is not seen in the next iteration of IE6

New in MONyog 3.7.4-3 (Apr 9, 2010)

  • Log analysis could use high CPU if the option to replace literals with a placeholder was not selected and the literal string ‘ “‘ (space + doublequote) occured in the log file.
  • CSV-export from Query Analyzer only exported 200 rows (the same number as displayed in the browser view). Now CSV-export will export all rows. Also the UI makes it now clear that the browser displays the 200 uppermost rows according to current sort criteria.
  • An error message regarding an integer overflow could occur in Monitor/Advisors page for some values. The SQLite datatype used could be too short for some specific data.
  • Login to MONyog could fail if MONyog was running behind a proxy.

New in MONyog 3.7.3-1 (Mar 30, 2010)

  • If SHOW ENGINE INNODB STATUS returned an error that was not privilege-related, MONyog reported MySQL as non-available. That could happen for instance if MySQL was started with –skip-innodb option. This bug was introduced in 3.71 with the support for InnoDB deadlock detection.
  • A bug in the MONyog startup script could on Linux have the result that MONyog was still reported as running if it had been killed or had crashed.

New in MONyog 3.7.0-2 (Feb 4, 2010)

  • From MONyog 3.7 we have introduced 3 editions of the commercial version of MONyog. When we had first released MONyog 2 years back, it was already an almost complete tool for monitoring MySQL servers based on what the MySQL server exposes on SHOW statements. Since then we have added features that are not basic server monitoring features in the strict sense but additional or supplementing features. Most important the Query Analyzer was added around one year ago.
  • Multi-user authentication is a long standing request from customers belonging to large organizations – or just having the need for monitoring lots of MySQL servers. There may be multiple server administrators. There may be development/test servers that the developers of that organization should be able to monitor, but is may also be unwanted to give them access to see details from servers having delicate information (customer data, payroll data etc.). We have completely rewritten the MONyog authentication system. It is now possible to create multiple user profiles and give access for a specific user to a subset of servers available only. Additionally specific ‘admin’ functionalities (access to edit server settings, to KILL queries and to execute FLUSH STATUS) can be disabled for a user.
  • As MONyog is no longer just a tool that organizes what the server exposes on SHOW statements – but rather a ‘bundle’ of tools – we have realized that not all tools are useful to every MONyog customer. MONyog is no longer a “one-size-fits-all” application. MONyog caters to a very diverse range to customers. In some organizations MONyog may be used by a single person only, and in other organizations by dozens of people. Some users will not use the Query Analyzer at all (because they only run standard applications where they are not in control of schema and query design anyway). And so on. The Ultimate edition is for those users in particular that have full control over their database and their applications and who need multiuser authentication. The Enterprise edition provides the basic monitoring functionalities as well as the Query Analyzer – but not multi-user authentication. The Professional edition is an entry-level version with the (original) basic monitoring functionalities. Refer to the comparison sheet for full details.
  • We thought it is now the right time to have multiple editions of MONyog. This also means that people can start with the lower edition and gradually move to a higher edition if the need arises. This will also reduce the overall complexity and total cost of ownership for several customers.
  • We have also migrated all existing MONyog customers to MONyog Ultimate and Ultimate upgrade prices are kept moderate. So if you are already a MONyog customer your Total Cost of Ownership remains same while you continue to enjoy the powerful tools and features of Ultimate.

New in MONyog 3.7.0-0 Beta 1 (Jan 18, 2010)

  • Features:
  • The MONyog ‘admin’ user can now create other users having access to a subset of available servers only. For those non-admin users access to edit server settings, to KILL queries and to execute FLUSH STATUS is optional. Also note that only ‘admin’ is allowed to create/delete server and user registrations.
  • Monitors/advisors page can now be exported as CSV.
  • Some counters in Monitors/advisors page were rearranged. Details about this:
  • “Security” and “Excessive Privileges” groups have been moved to the top.
  • “Table Cache” and “Table Locks” have been merged to a single group “Table Cache & Locks”
  • “Thread Cache” and “Slow Launch Threads” have been combined to a single group named “Threads”
  • “Commands” and “Schema Changes” have been merged to a single group “Commands & Schema Changes”
  • Counters in “Network Traffic” has been moved to “Connection History”
  • Counters in “Sort Buffers” has been moved to “Misc.”
  • Bug Fixes:
  • FLUSH STATUS was not working for servers having space(s) in their names.
  • Warning also displayed when global notifications are disabled.
  • Duplicate ‘Server restarted’ messages were sometimes sent when MONyog is restarted.

New in MONyog 3.6.5-1 (Dec 23, 2009)

  • Features:
  • You can now specify a comma-separated list of users to be ignored/excluded by notify and/or kill actions for long-running queries in ’query sniffer’ interface.
  • Added a ‘diagnostic info’ icon to servers in ‘list of servers’ page. Clicking this will generate a report in plain text with the most basic information about the server.
  • Added an option to stop/start data collection for a server in ‘list of servers’ page (without opening the detailed pages for this server).
  • Enabling/disabling data collection from and/or alerting about all servers can be done from tools .. preferences .. maintenance.
  • Enabling/disabling data collection from and/or alerting about specific servers can be done by calling the MONyog URL with parameters. This can be scripted and scheduled using any standard method available with the OS. Please refer to documentation for details.
  • Mail alerts will now have a direct link to open MONyog login page.
  • Added an option to customize colors used in Dashboard.
  • If global wait_timeout setting for a server is lower than the sample interval we will now increase session wait_timeout setting in order to avoid the MONyog.log to grow with a “MySQL server has gone away” message for each data retrieval.
  • Bug Fixes:
  • Fixed some issues with validation of user input. For specific data invalid and unusable input could be saved by MONyog. This includes 1) invalid separator between email addresses 2) Entering a decimal where an integer is required.
  • SMTP return codes were neither logged nor were specific messages displayed to the user based on them.
  • In history/trends an empty graph would display if server details were wrong. Now proper javascript errors are displayed.
  • In connection details page for a server the previous/next links would hide with specific menu items selected.
  • In History/Trends, warning message (”No data found in this range, try changing history range!”) didn’t show up for the time-frame in which server data collection was disabled.
  • If Adobe Flash was not installed, the message to “install the latest Adobe Flash Player” was displayed more than once.
  • Small GUI improvements and fixes.

New in MONyog 3.6.2-0 (Dec 10, 2009)

  • Bug fix:
  • When using the option (introduced in 3.6) to alert for long-running queries from the Query Sniffer interface, such long-running query could raise multiple alerts.
  • Miscellaneous:
  • Added ‘User and Host’ information for long running query alert.

New in MONyog 3.6.1-0 (Dec 1, 2009)

  • If notifications were enabled, program threads were not always closed properly what ultimately could lead to a program ‘hang’. This bug was introduced in 3.6.

New in MONyog 3.6.0-2 (Nov 30, 2009)

  • Real-time query monitoring and sniping
  • MONyog provides a whole bunch of tools for finding problem SQL (Slow Query Log, SHOW PROCESSLIST snapshots, MySQL Proxy, etc). These tools are great if you want to find problem SQL in an application and tune those queries. However, using these tools to find problem is almost always a post-mortem exercise. In certain situations you may want real-time notifications for long running queries. MONyog 3.6 gives you exactly that. MONyog can continuosly monitor queries in real-time and send notifications (on Mail or SNMP) for queries that take more than a specified amount of time to execute. You can also specify an option to kill such queries.
  • Better server management
  • Several of MONyog’s customers monitor hundreds of MySQL servers using a single instance of MONyog. Managing large number of servers has just gotten a whole lot easier. With tagging, you can categorize your servers into logical groups, and avoid clutter.
  • Many people had requested the option to add servers programatically. That was one of the primary motivations for documenting the entire MONyog schema. Some customers want to register hundreds of servers quickly without writing any code. For such situations, we introduced the ability to duplicate a connection with a single click. After duplicating a connection, most of the time you just need to change the MySQL IP or Port. You would probably want to retain all other settings.
  • Improved alerting system
  • Many users of MONyog have reported that they sometimes receive alerts for insignificant events. And, which is worse, because of this they tend to ignore important alerts! Some of the improvements in the alerting system are:
  • a) We have introduced the concept of “Delayed alert notifications”. It can now be defined that a problem must have existed for a number of sample intervals continuously (in a row) for an alert to be sent. A global setting for each server is available from GUI. For individual counters the global setting can be overridden by defining the RetryOverride (like ‘RetryOverride:3′) property of the (JavaScript) counter definition
  • b) You can also choose to be notified when MONyog detects that a problem, which existed previously, has been resolved.
  • I/O Monitoring for Linux servers
  • MONyog now provides several monitors on Linux I/O metrics.
  • Get notified on MySQL restart
  • We have also added an option to send alerts if server was restarted between two data retrievals. With managed hosting the MySQL server may be restarted automatically as part of routine maintenance or after a server crash. Knowing when this has occurred can be useful.

New in MONyog 3.6.0-1 Beta 2 (Nov 26, 2009)

  • Features:
  • Grouping of servers: one or more ‘tags’ can now be specified for a server. In ‘register servers’ page the list of servers are grouped as per tags. As more tags may be specified for a server, it may appear in more groups. A group established this way can be selected in one operation.
  • Added an option to send alert if server was restarted between two data retrievals. With managed hosting the MySQL server may be restarted automatically as part of routine maintenance or after a server crash. Knowing when this has occurred can be useful.
  • Process-list based sniffer now has an option to notify about and kill long running queries.
  • New and updated counters/advisors.
  • Added automatic and manual update check.
  • Bug Fixes:
  • With specific settings Dashboard graphs could hide other displayed dialogs.
  • Notification mails now have information about the value that triggered the alert.
  • In log analysis a divisor ‘1024′ was used for calculation of ‘kilo rows’. Now the divisor ‘1000′ is used.
  • Exporting charts as graphics did not use a consistent naming convention. Now files will be named ‘MONyog_chart_ConnectionName_Chart_Title.file_extension’.
  • GUI improvements, improved error messages etc.
  • For slave servers process-list options to “Kill”, “Copy”, “View Query” and “Explain” were not always accessible.
  • Miscellaneous:
  • Added a warning in Disk Info page that the calculation may be expensive. In particular with databases with thousands of objects the calculations may cause unacceptable load.

New in MONyog 3.6.0-0 Beta 1 (Nov 4, 2009)

  • Features:
  • Delayed alert notifications. It can now be defined that a problem must have existed for a number of sample intervals continuously (’in a row’) for an alert to be sent. A global setting for each server is available from GUI. For individual counters the global setting can be overridden by defining the RetryOverride (like ‘RetryOverride:3′) property of the (javascript) counter definition in Tools… Customize interface.
  • Added counters for monitoring I/O parameters on Linux systems (similar to ‘iostat’).
  • Host and user information is added (optionally) to the Query Analyzer output. Note: this option is currently not available for proxy based sniffer.
  • Duplicate/Clone Server functionality added to GUI.
  • Added direct link to customize counters from the Monitors/Advisors page.
  • Bug Fixes:
  • Notifications did not take ‘base time’ setting and/or ‘uptime_since_flush-status’ status variable into account.
  • If SSH setting for retrieving Linux system information were once selected and later deselected again, graphs without any information would appear in Dashboard and in MONyog.log errors were recorded.
  • Now ”busy” icon is displayed while saving/deleting a connection. When MONyog was controlled from a browser running on a remote machine the absence of this could cause confusion about if change had effect.
  • A garbage string like “0NaN/0NaN/NaN 0NaN:0NaN:0NaN” could be displayed when editing log analyzer filter settings.

New in MONyog 3.5.0-1 (Oct 15, 2009)

  • Features:
  • Alerts can now be sent as SNMP traps.
  • Support for MySQL error log. An alert can be sent when the error log has an entry of type [ERROR] and the error log entry can be viewed in MONyog web interface as well.
  • Query Analyzer data can now be exported as CSV.
  • Updated and added advisors.
  • EXPLAIN/view query from Processlist page will now open in a new browser tab.
  • Alerts (mails or traps) will now list the ip of the machine running the MONyog instance (request from users who had more than one MONyog instance).
  • Graphs/charts will now have new colors that make the graphs more readable.
  • Added next/previous links in register/edit servers page.
  • Bug Fixes:
  • Lots of fixes for browser-specific issues.
  • If identical queries were logged from more clients with same timestamp, Query Analyzer/slow query log would only count that query once.
  • Long BULK INSERTS would not display properly in Query Analyzer if the option to ‘replace literals’ was selected.
  • Deleting a server registered as number ‘0001′ did not delete the sniffer.data file for that server.
  • Windows Vista and higher could warn that MONyog was not properly installed due to lack of an Application Manifest. It was false alarm but now such Manifest is included with the installer.

New in MONyog 3.5.0-0 Beta 1 (Oct 7, 2009)

  • Features:
  • Alerts can now be sent as SNMP traps.
  • Support for MySQL error log. An alert can be sent when the error log has an entry of type [ERROR] and the error log entry can be viewed in MONyog web interface as well.
  • Query Analyzer data can now be exported as CSV.
  • Updated and added advisors.
  • EXPLAIN/view query from Processlist page will now open in a new browser tab.
  • Alerts (mails or traps) will now list the ip of the machine running the MONyog instance (request from users who had more than one MONyog instance).
  • Graphs/charts will now have new colors that make the graphs more readable.
  • Added next/previous links in register/edit servers page.
  • Bug Fixes:
  • Lots of fixes for browser-specific issues.
  • If identical queries were logged from more clients with same timestamp, Query Analyzer/slow query log would only count that query once.
  • Long BULK INSERTS would not display properly in Query Analyzer if the option to ‘replace literals’ was selected.
  • Deleting a server registered as number ‘0001′ did not delete the sniffer.data file for that server.

New in MONyog 3.1.6-1 (Sep 12, 2009)

  • Bug Fixes:
  • Some queries were not parsed correctly from server logs. Affected queries were queries enclosed in (brackets) and some queries with comments. Known issues still are 1) queries starting with a conditional comment 2) queries containing a ‘quoted string’ with a ” ; ” (semicolon) followed by a line-break.
  • Query time could fail to be read correctly from logs.
  • Fixed a memory issue when parsing logs.

New in MONyog 3.1.5-0 (Aug 21, 2009)

  • Bug Fixes:
  • More CPU optimizations with processlist-based sniffer.
  • When installing Windows version a js32.dll -error could stop installation (after waiting a few seconds and clicking ‘retry’ it installed successfully).
  • Some counters of YES|NO type had an icon for displaying graph what made no sense.

New in MONyog 3.12-4 (Jul 25, 2009)

  • Important note when upgrading from versions before 3.1:
  • MONyog now requires a registration code.
  • Do not forget to replace the MONyog.lua script if you use the Query Analyzer with proxy-based sniffing.
  • RPM users must uninstall pre-3.1 versions before installing this one.
  • Please read 3.1 release notes for details.
  • Changes as compared to 3.11 include:
  • Features:
  • All charts displayed by MONyog can now be exported as PDF/JPG/PNG (from chart context menu).
  • Query Analyzer will now sort in descending order as default first time (before it was ascending).
  • Bug fixes:
  • Validation of connection details was not proper when saving.
  • In Query Analyzer options that do not apply for sniffer and log files are now disabled where they do not apply.
  • In Query Analyzer ’show details’ did not preserve the original formatting of a query.
  • Max column in sniffer output in Query Analyzer could show erroneous values in some cases.
  • Mail alerts sent by MONyog displayed TRIAL at bottom even after registration of MONyog.
  • Various errors like “ErrCode:-1 ErrMsg:PathMgr::GetExeName readlink failed” could occur in MONyog.log. In some cases the error would cause failure to register.
  • Sniffer data are purged automatically as per the server ‘retention timeframe’ setting, but it could also happen that Sniffer data that were not old enough to qualify for purging were deleted automatically. This would result in some queries missing after analyzing.
  • Wrong error was logged by sniffer if MONyog.lua version 3.0 was used with MONyog version 3.1. However in connection details section, on “Test Proxy”, proper error was thrown.
  • Changes as compared to 3.12 beta include:
  • Bug fix:
  • It was only possible to export the same chart once unless refreshing the page.
  • Miscellaneous/known issues:
  • Due to a bug in specific builds of the MySQL proxy version 0.72 (it returns incorrect version) MONyog Query Analyzer will not work with those builds affected. Affected builds include versions for Windows and OS-X (but not Linux where this MONyog release works fine with proxy 0.72). We hope that MySQL will fix this soon, but if not we will consider a patch in MONyog itself.
  • With Internet Explorer versions 8.0.6001.18783 and higher (latest available for Vista and Win7) exporting graphics will not work. The ‘Save’ button (a FLASH object) does nothing in those browsers. We will release again as soon as a fix is possible.

New in MONyog 3.12-3 Beta 1 (Jul 22, 2009)

  • Features:
  • All charts displayed by MONyog can now be exported as PDF/JPG/PNG (from chart context menu).
  • Query Analyzer will now sort in descending order as default first time (before it was ascending).
  • Bug fixes:
  • Validation of connection details was not proper when saving.
  • In Query Anlayzer options that do not apply for sniffer and log files are now disabled where they do not apply.
  • In Query Analyzer ’show details’ did not preserve the original formatting of a query.
  • Max column in sniffer output in Query Analyzer could show erroneous values in some cases.
  • Mail alerts sent by MONyog displayed TRIAL at bottom even after registration of MONyog.
  • Various errors like “ErrCode:-1 ErrMsg:PathMgr::GetExeName readlink failed” could occur in MONyog.log. In some cases the error would cause failure to register.
  • Sniffer data are purged automatically as per the server ‘retention timeframe’ setting, but it could also happen that Sniffer data that were not old enough to qualify for purging were deleted automatically. This would result in some queries missing after analyzing.
  • Wrong error was logged by sniffer if MONyog.lua version 3.0 was used with MONyog version 3.1. However in connection details section,on “Test Proxy”, proper error was thrown.
  • Miscellaneous:
  • Due to a bug in specific builds of the MySQL proxy version 0.72 (it returns incorrect version) MONyog Query Analyser will not work with those builds affected. Affected builds include versions for Windows and OS-X (but not Linux where this MONyog release works fine with proxy 0.72). We hope that MySQL will fix this soon, but if not we will consider a patch in MONyog itself.

New in MONyog 3.1.1-2 (Jun 26, 2009)

  • Bug fixes:
  • Fixed a bug when converting timestamp format (human readable timestamp, unix_timestamp) when reading server logs. The bug could result in time being displayed 1 hour wrong in Query Analyzer if server was in a timezone using ‘daylight saving time’.
  • A SQLite database LOCK could prevent access to the ’system’ database. Linux Operating System counters would then not be available.
  • Fixed a GUI issue with IE browser in licensing form page (command button behavior while a command was in process).
  • MONyog could crash when user saved specific details (port and password) from ‘preferences’ .

New in MONyog 3.1.0-1 (Jun 19, 2009)

  • Packaging:
  • The same binary/installer is now used for any license model (whether TRIAL or whatever number of servers). A license key defines and controls how many servers can be registered. You may retrieve your license key from our Customer Portal. Before installation please ensure that you have registration details available and also soon after installation has completed please connect to MONyog from your browser and enter registration details. This change of packaging concept simplifies the release cycle for us, as there are now much fewer installers that will need to be built and tested.
  • Also now all distributed builds will run as a TRIAL will run for a month (not till a fixed date) and in the TRIAL period an unlimited number of servers can be registered.
  • Unfortunately and as a consequence of the changed packaging concept it is not possible to install a 3.1 RPM build on top of a previous version as the file name format (ie. version substring) will need to change to be functional by RPM installers (’rpm’ console command and various distribution-specific commands and GUI tools). Previous RPM versions installed must be uninstalled this time before installing 3.1 (but note that previously collected data will still be preserved and available after this). For Windows .exe and Linux .tar.gz builds there is no such issue.
  • Features:
  • Added option to purge all stored sniffer data. Also sniffer default settings were changed. Quite a lot of evaluating users experienced an empty report due to previous default settings.
  • Added support for MySQL Proxy version 0.7.1. A new MONyog.lua script is shipped with this build. The old script must be replaced with this one if you use the proxy-based sniffer option. This new script also works with MySQL Proxy 0.61.
  • Filtering options were re-arranged in Query Analyzer as per user requests.
  • Lots of GUI fixes, clarifications, usability improvements etc.
  • Bug fixes:
  • On RedHat type Linux ’service MONyogd start’ command would sometimes not start MONyog in first attempt if MONyog process had been killed or had crashed.
  • The mail header of MONyog mail alerts did not handle unicode. Now utf8 encoding is used everywhere.

New in MONyog 3.0.9-4 (Jun 4, 2009)

  • Bug fixes:
  • If MONyog user for monitoring a replicating slave did not have ‘replication client’ privilege, MySQL availability would be shown as ‘No’ in Monitors/Advisors page (even though ‘test connection’ was successful).
  • If mail alerts were enabled, a syntax error in customized javascript could cause a crash.
  • Charts for a server in Dashboard page would not resume updating after a disconnect and reconnect to that server. A browser refresh was required.
  • The chart ‘popups’ from Monitors/Advisors page would not populate with historical data from the MONyog database but only with fresh data sampled.
  • After sorting in Query Analyzer the expand/collapse state was lost.

New in MONyog 3.08-1 (May 9, 2009)

  • Bug fixes :
  • Query Analyzer did not show correct output when displaying a sorted result. A wrong LIMIT clause was generated when querying the temporary database containing queries.
  • Fixed a bug in checksum calculation on 64 bit builds. The checksum is used by Query Analyzer for indexing. On 64 bit wrong sort order could result from this.
  • If SSH-tunnelling to a MySQL server had been used and later the setting for ‘Use SSH’ was changed to “No”, MONyog would continue to use SSH tunnel as long as valid tunnelling details were available.

New in MONyog 3.07-4 (May 5, 2009)

  • Bug fixes :
  • With SMTP notifications turned “ON” various issues (connection failure, program crash) could occur if SMTP authentication was not used. This bug was introduced with SMTP authentication support in 3.05.
  • Fixed a crash with SSH-tunneling. Only 64 bit build for Linux was affected.
  • Counters “cache hit rate”, “pruned as percentage of inserts” and “queries not cached” reported wrong in ‘History/trends’ timeframe.

New in MONyog 3.05 (Apr 1, 2009)

  • atures added (as compared to 3.04):
  • SSL/TLS mail encryption is now supported for mail alerts.
  • Added an option to rebuild MONyog databases. Using this option periodically may result in better performance - including shorter startup time when OS is rebooted. Basically using this option will defragment the database including indexes. It is not possible to provide an ‘absolute’ advice on how this option should be used. But the larger the databases and the shorter the sample interval the faster there is a chance of fragmentation occurring after a huge amount of INSERTs and DELETEs to the database (note that only with databases files of around 1 GB and larger we have seen the need for this. A ‘general’ advice could be to execute monthly with large database files).
  • Improved error messages for Query Analyzer.
  • Bug fixes (as compared to 3.04):
  • When “Test Connection” or “Test Path” was clicked MONyog seemed inactive. Now the mouse cursor will change to an ‘active state cursor’ indicating that MONyog is performing the requested operation.
  • With query sniffer enabled the 64 bit Linux build could crash. Reports about this include RedHat and Ubuntu Linux distributions with very recent Linux Kernels.
  • Bug fixes as compared to 3.05 beta1 include.
  • Registering a server while SQLite VACUUM command was running could cause MONyog to hang.
  • The STOP option for SQLite VACUUM command would not work if more than one VACUUM command was executing.

New in MONyog 3.05 Beta 1 (Mar 17, 2009)

  • Features:
  • SSL/TLS mail encryption is now supported for mail alerts.
  • Added an option to rebuild MONyog databases. Using this option periodically may result in better performance - including shorter startup time when OS is rebooted. Basically using this option will defragment the database including indexes. It is not possible to provide an ‘absolute’ advice on how this option should be used. But the larger the databases and the shorter the sample interval the faster there is a chance of fragmentation occurring after a huge amount of INSERTs and DELETEs to the database (note that only with databases files of around 1 GB and larger we have seen the need for this. A ‘general’ advice could be to execute monthly with large database files).
  • Improved error messages for Query Analyzer.
  • Bug fixes:
  • When “Test Connection” or “Test Path” was clicked MONyog seemed inactive. Now the mouse cursor will change to an ‘active state cursor’ indicating that MONyog is performing the requested operation.

New in MONyog 3.0.4-2 (Mar 4, 2009)

  • Features:
  • In case of invalid javascript in a counter definition, MONyog will now tell details about this error.
  • Optimizations in the handling of the MONyog embedded database. In particular users with a very large retention timeframe setting and rather short sample interval (resulting in large databases) will benefit from that.
  • Bug fixes:
  • The above will also fix an issue where MONyog seemed to ‘hang’ when saving connection details for a connection having large database files.

New in MONyog 3.04 Beta 1 (Feb 28, 2009)

  • Features:
  • Optimizations in the handling of the MONyog embedded database. In particular users with a very large retention timeframe setting and rather short sample interval (resulting in large databases) will benefit from that.
  • Bug fix:
  • The above will also fix an issue where MONyog seemed to 'hang' when saving connection details for a connection having large database files.

New in MONyog 3.02 (Feb 28, 2009)

  • Bug fixes:
  • The alerts and advisors for slave 'read-only' mode were in conflict. We will now advise for a slave (in production) that 'read-only' mode should be ON (only the replication thread can write) and alert accordingly.
  • Add/Edit connection failed with connection names using SPACE character.
  • Proxy connection was not established when proxy was started for a server present in a remote system.

New in MONyog 2.9.0 (Dec 5, 2008)

  • Features:
  • MONyog can now be running behind an Apache server configured as ‘reverse proxy’. Before this release MONyog’s java script was not accessed due to absolute paths, as a result MONyog pages were not displaying properly.
  • Bug Fixes:
  • Fixed high CPU usage in the ‘query sniffer’ if sniffer “Minimum time taken ” value was set to “0″ (or left blank).

New in MONyog 2.9 Beta 1 (Nov 19, 2008)

  • This release adds a 'base time' setting in MONyog. This setting (if defined by user) will be used for calculation of uptime-base counters. The reason for this implementation is that if FLUSH STATUS is executed with a MySQL server, the server status variables will be reset to the same value as would be after a server restart. There is one important exception however and that is the 'uptime' status variable itself. This single status variable is not affected by FLUSH STATUS. So to get true uptime-based counters in MONyog with servers that do not support the 'uptime_since_flush_status' variable (and currently only 5.0 COMMUNITY servers from 5.0.37 do - not ENTERPRISE servers and not any other major branch than 5.0 and also not 5.0 before 5.0.37) you will need to define a 'base time' in MONyog greater than or equal to the time where FLUSH STATUS was executed last time. Refer to documentation for full details.
  • Improved the purging logic with the MONyog embedded database. Now also system CPU load is considered and purging operations will be skipped if CPU is high. This is a further improvement to the change in purging logic introduced in version 2.5.

New in MONyog 2.7.1 (Sep 12, 2008)

  • Fixed some issues with JSON strings that could prevent objects in the MONyog browser interface to populate with data. Most important ‘Monitors/Advisors’ page would fail to display if a username contained a doublequote character.

New in MONyog 2.7.0.0 (Sep 4, 2008)

  • Features:
  • CPU optimisations in both MONyog (server) process (in particular when ‘Monitors/Advisors’ page was being viewed) and browser processes (viewing Dashboard could cause high CPU usage in Firefox browser in particular).
  • Bug fix:
  • Fixed a dependency with the SSH library that could cause failure to install in Win2K. This was an issue with the updated SSH library introduced with version 2.5.
  • Miscellaneous:
  • The RPM installer scripts for Linux were updated in various ways. This solves issues on specific distributions including: 1) uninstall with the SuSE/YaST ’software management’ GUI was not possisble. 2) It was not always possible to install on top of a running MONyog service - sometimes it was necessary to stop service manually before upgrading. Also note: when updating from trial to single/multi server or from single server to multi server it is still necessary to uninstall the old version first. And when installing this version (applies only when using the RPM build) any older version will have to be removed with the “rpm -e ..” (rpm -e MONyog-trial/rpm -e MONyog-single/rpm -e MONyog-multi) command in advance (distribution-specific GUI tools may not work with versions before this one, so please use the RPM console command). We apologize for this but there is no other way.