Coupon Code: BYE14
Hurry up, offer expires soon!
Blog

MONyog 3.6 introduces real-time query monitoring and sniping, better server management, improved alerting and major new features

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

3 thoughts on “MONyog 3.6 introduces real-time query monitoring and sniping, better server management, improved alerting and major new features

  1. Pingback: Webyog » MONyog 3.6 introduces real-time query monitoring and … | nighshift@inertz.org

  2. Hi Team,
    I would like to ask if MONyog have an option in the functions, that if host that is not “a, b, c” connects to Database i will get an alert about it.

    Thank You,

    Rotem.

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>