Changes (as compared to 3.71) include:

Features:
* The number of builds for Linux has been increased to the double number of what it was before.  In addition to the builds based on glibc version 2.3 we now distribute builds based on glibc 2.5.  Also we add builds for use with even older glibc 2.3 based Linux that what we had before. There are now builds based on both glibc-2.3.2  and 2.3.4 (the one based on 2.3.4 is the one we had before). We had a few  reports of random crashes (typically occurring up to a few times per week) occurring on recent 64 bit CentOS servers and in one case also a RHEL5.  The glibc 2.5-based build fixes this. Although we only had such reports on 64 bit Linux of  ‘Red Hat Family’ we also included 64 bit tar.gz for all Linux platforms and 32 bit RPM builds.  The general advice on which build (glibc 2.3-based versus 2.5-based) should be used in every case would be that if glibc 2.5 or higher is available on the system you should use the 2.5-based build.  Or simply use the one based on 2.5 if it installs and starts on your system. Upgrading users that are in doubt can continue with 2.3.4-based builds if they have no stability issues.

Bug Fixes:
* When MONyog encountered an SSH error while trying to read a file using SFTP  it could crash. This has been fixed.
* Redundant “Server Restarted” alerts concerning monitored Linux systems could be sent by MONyog. Now MONyog will notify users only once when a system is restarted, and alert will be sent as soon as MONyog detects it.
* When restarting MONyog an error message could be written to the log indicating that an ALTER TABLE SQLite query failed to execute. Technically it was an issue with a Schema version table in the MONyog database.

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

Comments(0)

Changes (as compared to 3.7) include:

Features:
* Added a monitor for InnoDB deadlocks (as exposed by SHOW ENGINE INNODB STATUS -statement).
* In case of a program crash on Linux, MONyog will save a core dump like the Windows version already does.  The dump is saved in ../MONyog/bin folder.

Bug Fixes:
* EXPLAIN from Processlist page could fail with syntax error due to a missing SPACE character in the statement.

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

Comments(0)

Changes (as compared to 3.7) include:

Features:
* Added a monitor for InnoDB deadlocks (as exposed by SHOW ENGINE INNODB STATUS -statement).

Bug Fixes:
* EXPLAIN from Processlist page could fail with syntax error due to a missing SPACE character in the statement.

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

Comments(0)

MONyog MySQL Monitor 3.7  Has Been Released.

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.

Release notes in traditional form can be viewed here.

Feel free to leave your feedback in the comments section.

Comments(3)

This release has (as compared to beta 1) no technical changes that should affect users.  Changes between the beta and this one are internal only – like code refactoring/cleanup, some very small GUI fixes etc.

However note that the full-featured “MONyog” (as you know it) was was renamed to “MONyog Ultimate”.  Full details will be available with the upcoming GA release. A new licensing scheme is planned from 3.7 GA. But note: this will not affect existing users.

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

Comments(0)

Changes (as compared to 3.65) include:

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.

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

Comments(1)

Happy new year!

Just before Christmas the number of downloads of MONyog (from distinct email addresses) crossed 100,000. Here is the situation as of now:

This is of course a nice Christmas present for us to have. But more important: it reflects that today – as opposite to the situation just a few years ago – that even average MySQL users have understood that tuning the server configuration as well as the schemas and the queries used by applications is essential.

The default settings for the MySQL server are not appropriate for a heavy-loaded server and even the standard configuration files (or configuration ‘templates’) shipped with the server will not have the specific settings required for optimal configuration in most situations. And even the best server configuration won’t help much if databases and queries are poorly designed. We benefit from the growing understanding of this but also believe we have contributed significantly to it by making MONyog available. Its agentless design and the total lack of dependencies on external programs (database, web server, scripting environments) makes MONyog the easiest deploy-able solution for MySQL monitoring. You are up and running in less than 5 minutes. Additionally it is a very rich application providing functionalities you do not find anywhere in any other integrated solution.

Recent additions to MONyog include (just mentioning the most important things added in last few weeks before Christmas):

• Exports of Query Analyzer output for import to spreadsheets and databases for further analysis.
• Extended alerting options: now alerts can be send as mails or SNMP traps (or both) and alerts can be sent for long-running queries as you define it.
• The MONyog API: An HTTP-based (and thus totally cross-platform) interface for controlling MONyog from shells as well as scripting and programming environments. Introduced in 3.65 just before Christmas, it is far from complete as of now, but it is extensible – and will be extended.

And MONyog development does not stop here. We develop it aggressively and have recently increased the MONyog developer team. Stay tuned!

Regards,
Team MONyog

Comments(4)

Changes (as compared to 3.62) include:

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.

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

Comments(0)

Changes (as compared to 3.62) include:

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 report’ 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.

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.
* Small GUI improvements and fixes.

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

Comments(0)

Happy Holidays from Webyog!

It’s been a great year. We have shipped major versions of our products, had record number of downloads and acquired thousands of customers. We wouldn’t be where we are without your support.

As as small token of our appreciation, we will be giving away 2 Kindles to our supporters. To take part in this giveaway all you need to do is:

1. Follow @webyog on Twitter.
2. Tweet on how some specific feature of our products has been useful to you. The two most original and feature-specific entries will win a Kindle.

   For example, rather than Tweeting: “SQLyog rocks!” you should Tweet:
   “The autocomplete feature of SQLyog saves me countless hours of typing everyday”
   OR
   “MONyog has made MySQL replication monitoring less painful”

We’ll choose the winners by searching Twitter for “SQLyog” and “MONyog” among followers. Please send in your entries by 31st Dec 09, 23:59 PST. We will announce the winners in our blog in 1st week of Jan, 2010.

You can also avail a flat 20% Christmas discount on all Webyog products till 31st Dec 09, 23:59 PST. Use coupon code “xmas09″ to avail this discount from our webshop.

Cheers and best of luck!
Team Webyog

Comments(0)