Coupon code: mysql14
Hurry up, offer expires soon!

MONyog 2.9 Has Been released

Changes (as compared to 2.83) includes:


* This release adds a ‘base time’ setting in MONyog. This setting (if defined by user) will be used for calculation of uptime-based counters. The reason for this implementation is that if FLUSH STATUS is executed with a MySQL server, specific server status variables will be reset to the same value as would be after a server restart. However the ‘uptime’ status variable itself is not affected by FLUSH STATUS. And as uptime-based counters will relate the value of cumultive status variables with some intial time, using the ‘uptime’ variable as the initial time will result in calculation of misleading values if FLUSH STATUS was executed. 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. Also you can now discard data older than a specific time by using this setting. 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.

As compared to 2.9 Beta1 this also includes:


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


One thought on “MONyog 2.9 Has Been released

  1. Edit December 10th 2008: The wording of the first item above was slightly changed. With the original wording it was not clear that the issue with FLUSH STATUS affected *specific* counters only (the most important one affected is/was “Highest number of concurrent connections” (and the derived “Percentage of max allowed reached”) .. refer to “(FLUSH STATUS)… sets Max_used_connections to the current number of open connections”).

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>