Changes (as compared to 4.0) include:

Bug Fixes:
* Implemented code that makes OpenSSL (what is used by our SSH-library) explicitly thread-safe and thus fixing an issue where specific cryptographic function calls under very heavy load could cause a crash.
* Fixed a SQLite corruption issue that on Windows could cause failure to stop the MONyog service. The issue did not mean that MONyog as such stopped working as long as it was running.
* If both value for ‘user’ and ‘host’ were filtered in processlist-based sniffer the interface would display NULL for both.

Downloads: http://webyog.com/en/downloads.php
Purchase: http://webyog.com/en/buy.php

Comments(0)

Hi,

We are delighted to unveil MONyog 4.0 — a major new release. Listed below are overviews of some of the major features.

Tracking changes to your MySQL configuration

Maintaining server configuration and tracking changes to it plays a vital role in the maintenance of MySQL servers. DBAs may be responsible for hundreds of servers and keeping an eye on the configuration settings for all of them could be difficult to say the least. With MONyog 4.0 now you can compare global MySQL configuration of multiple servers side-by-side, with all changes highlighted so that differences are visually discernible at a glance. Wondering why server A isn’t performing as well as server B when they share the exact same load? The answer could lie in the configuration files!

What’s more is that MONyog now lets you track changes to the global configuration of your MySQL server no matter if the configuration parameters were specified in my.ini/my.cnf, are server defaults or if somebody with SUPER privilege has executed a SET GLOBAL statement.

Improved customization framework

Many MONyog users have long since complained that the customization feature was complex and hard to use: One had to be well-versed in object-oriented JavaScript concepts to even make a minor change. Moreover, unless you manually backed up your customizations, you’d loose all of them if you decided to upgrade! That was motivation enough for us to redesign the entire framework.

With MONyog 4.0 knowledge of writing basic JavaScript functions is more than sufficient to customize any Monitor/Advisor or roll out your very own set. A simple form-based interface with verbose instructions makes it very easy to define a new Monitor/Advisor.

We understand that not every user will make use of the 220+ Monitors/Advisors that we ship with MONyog. So why waste all the computing power? You can now disable a subset of the Monitors/Advisors and keep only the ones you use. If you change your mind later, you can always re-enable them again.

MONyog 4.0 provides a unique customization interface. Now you won’t have to worry about loosing your changes, making mistakes (you can always revert to the original!), or feel scared to experiment.

Improved stability and lots of minor features and bug fixes

As always, this release too contains a lot of bug fixes. MONyog has undergone severe stress testing and is monitoring 200 without issues in our test environment now. From this release we have reduced the number of Linux binaries. In version 3.72 we introduced packages specific to glibc versions. It was necessary at that time to ensure stability on both older Linux distros (RHEL3-generation) as well as the most recent distros using glibc version 2.5. But we never liked it ourselves. It could confuse users – and sometimes did. Since then we have been researching and testing different packaging concepts so that a single binary will do the job on all distros.  This release contains a single 32 and a single 64 binary – each with the option of a .tar.gz archive and a RPM installer.

MONyog customers can download the latest installers from Webyog’s Customer Portal.

We are very excited about this release, and hope that you will like it. We would love to hear from you.

Regards,

Team MONyog

Comments(4)

Important note: Please note that a 4.0 release cannot be downgraded to 3.x as the database schemas are incompatible and the installer will not handle downgrades – only upgrades. However you can install this 4.0 beta 3 on top of any previous release.

Changes (as compared to beta2) include:

Features:
* All fixes and features already released in 3.x have been ported to this build.  This includes the handling of SQLite caches now requiring much less memory.  Also this build has been checked in depth with leak-finder tools on both Linux and Windows.  Refer 3.8 release notes for details.

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 between the metric in the previous two collections.

Downloads: http://webyog.com/en/downloads.php
Purchase: http://webyog.com/en/buy.php

Comments(0)

Important note: Please note that if you have installed a MONyog 4.0 (beta) release you cannot install this one unless first completely removing the 4.0 installation including the complete MONyog data folder.

Changes (as compared to 3.77) include:

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 file was 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 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.

Downloads: http://webyog.com/en/downloads.php
Purchase: http://webyog.com/en/buy.php

Comments(0)

Important note: Please note that if you have installed a MONyog 4.0 (beta) release you cannot install this one unless first completely removing the 4.0 installation including the complete MONyog data folder.

Changes (as compared to 3.76) include:

Bug Fixes:
* Fixed an issue with SQLite where incorrect handling of journal files could lead to corruption of the MONyog embedded database .

Downloads: http://webyog.com/en/downloads.php
Purchase: http://webyog.com/en/buy.php

Comments(0)

Important note: Please note that a 4.0 release cannot be downgraded to 3.x as the database schemas are incompatible and the installer will not handle downgrades – only upgrades. However you can install this 4.0 beta 2 on top of any previous release.

Changes (as compared to beta1) include:

Features:
* Added an option to compare server configurations. 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.
* Also changes in server configurations are tracked and recorded by MONyog. This feature enables users to track changes to global configuration of a MySQL server over a period of time and compare changes between revisions.

Bug Fixes:
* 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.
* Helper functions’ migration: User-defined helper functions were not being migrated in 4.0 Beta 1. If the user wrote his/her own function to use in his/her custom Monitors/Advisors, he or she would lose all changes upon upgrading. Now all helper functions are migrated transparently.

Downloads: http://webyog.com/en/downloads.php
Purchase: http://webyog.com/en/buy.php

Comments(0)

Changes (as compared to 3.76) include:

Features:
* Added a new interface for customizing counters/advisors requiring less knowledge of javascript than what was the case before.
* When upgrading an installation with customized counters a ‘conflict resolver’ will now guide user to either migrate his old changes to the updated version or discard them.
* All cache hit rate related monitors/advisors have been changed to display cache miss rate information as it is more relevant when tuning databases. Also the advisor text for these monitors/advisors has been improved.

Miscellaneous :
* With the above changes parts of the MONyog database has been reorganized, what also means that the Monitors/Advisors and Dashboard pages will load much faster. Note however that with this beta the documentation on the ‘MONyog database schema’ is not fully updated.
* The SQLite library within MONyog has been upgraded to the latest version. The new version of SQLite improves stability as compared to the previous version where a possible journal file corruption was not handled.

Downloads: http://webyog.com/en/downloads.php
Purchase: http://webyog.com/en/buy.php

Comments(0)

Changes (as compared to 3.74) include the 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. This behavior is not seen in the next iteration of IE6.

Comments(0)

Changes (as compared to 3.73) include the bug fixes:

* 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.

Downloads: http://webyog.com/en/downloads.php
Purchase: http://webyog.com/en/buy.php

Comments(0)

Changes (as compared to 3.72) include:

* 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.

Downloads: http://webyog.com/en/downloads.php
Purchase: http://webyog.com/en/buy.php

Comments(0)