Changes (as compared to  3.61) include:

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.

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

Comments(0)

Changes (as compared to 3.6) include.

Bug Fix:
* 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.

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

Comments(0)

Hi,

We are pleased to announce MONyog 3.6 – a major new release. Listed below are the major features included in this release.

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.

Lot of minor features and bug fixes

This release also contains many bug fixes, UI improvements and minor features. You can find the complete release notes in the ‘Version History’ section of MONyog’s Help, available online here.

MONyog customers can download the latest installers from Webyog’s Customer Portal.
To evaluate MONyog, please download the 30-day trials.

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(1)

Changes (as compared to first 3.6 beta) include:

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.

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

Comments(0)

Changes (as compared to 3.5) include:

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.

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

Comments(0)

Hi,

We are pleased to announce MONyog 3.5 – a major new release. Listed below are the major features included in this release.

Error Log Monitoring

Monitoring the MySQL error log is absolutely critical for any MySQL DBA. Ignore the error log at your own peril! Many of our customers wanted an out-of-the-box solution for monitoring the error log. With the latest release, MONyog becomes the first MySQL Monitoring Tool to monitor the MySQL Error logs. MONyog can optionally send notifications over SMTP or SNMP for MySQL error log events that require attention.

As usual, none of the features of MONyog require you to install agents or additional software on hosts running MySQL.

SNMP Traps

We have introduced SNMP traps support in MONyog 3.5. SNMP traps enable MONyog to notify the management station of significant events.

Query Analyzer (QA) Output can now be exported

MONyog customers love the ability to find problem SQL without being forced to configure their applications to connect through MySQL Proxy. While MONyog’s Query Analyzer has complete support for MySQL Proxy, MONyog can also find problem SQL by parsing the Slow Query Log and/or by taking a snapshot of SHOW PROCESSLIST at regular intervals.

The report created by Query Analyzer can now be exported as CSV. This means that you can further customize the report using a spreadsheet or by simply importing the CSV output into a MySQL table for further analysis.

New advisors

We have introduced a bunch of new advisors that help MySQL DBAs manage more MySQL servers, tune their current MySQL servers and fix problems with their MySQL database applications before they can become serious problems.

MONyog 3.5 now supports 220+ monitors and advisors created by top-notch MySQL experts.

Lot of minor features and bug fixes

This release also contains many bug fixes, UI improvements and minor features. You can find the complete release notes here.

MONyog customers can download the latest installers from Webyog’s Customer Portal.
To evaluate MONyog, please download the 30-day trials.

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(0)

Changes (as compared to 3.15) include:

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.

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

Comments(2)

Changes (as compared to 3.15) include:

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.

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

Comments(2)

Changes (as compared to 3.14) include:

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.

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

Comments(2)

Changes (as compared to 3.13) include:

Bug Fixes:
* Significant CPU optimization with processlist-based sniffer.
* Saving mail settings with Linux version could cause a program ‘hang’.

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

Comments(0)