Showing entries 61 to 70 of 81
« 10 Newer Entries | 10 Older Entries »
Displaying posts with tag: MONyog (reset)
MONyog 3.5 introduces Error Log Monitoring, SNMP traps, new advisors and UI enhancements


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 …

[Read more]
MONyog 3.12 Has Been Released

Important note when upgrading from versions before 3.1:
* MONyog now requires a registration code.
* Do not forget to replace the MONyog.lua script if you use the Query Analyzer with proxy-based sniffing.
* RPM users must uninstall pre-3.1 versions before installing this one.
Please read 3.1 release notes for details.

Changes as compared to 3.11 include:

* All charts displayed by MONyog can now be exported as PDF/JPG/PNG (from chart context menu).
* Query Analyzer will now sort in descending order as default first time (before it was ascending).

Bug fixes:
* Validation of connection details was not proper when saving.
* In Query Analyzer options that do not apply for sniffer and log files are …

[Read more]
Interview with Rohit Nadhani, founder of Webyog

At the MySQL Conference, I had the chance to interview Rohit Nadhani, founder of Webyog, the folk that make SQLyog and MONyog. Watch the video, for more.

Generally based out of Bangalore (I visited them when I was last there), Webyog just started an office in Santa Clara, and are expanding. They boast 15,000 paid customers so far, with some big name customers: Google, Yahoo!, executive office to the US president, and more.

SQLyog is termed as an upgrade from phpMyAdmin. There is a GPL community edition, with some “power tools” that is part of the Enterprise Edition. It is very Win32 based, but easy enough to run on other OSes via WINE or some sort of virtualisation tool.

MONyog is an agentless monitoring tool. It …

[Read more]
MySQL Conf. 2009 special – Get 20% discount on all products, MONyog 3.06 released!


We will be present at MySQL Conference & Expo, 2009. If you are around Silicon Valley, don’t forget to meet the team behind your favorite MySQL tools at Booth #317. We are happy to offer a flat 20% discount on all purchases made during this month. Use the coupon code: uc2009 during the purchase.

Also, we are pleased to announce the release of MONyog 3.06.

Changes (as compared to 3.05) include:

Bug fixes:
* Installation on Windows could fail with a js32.dll-related error. Waiting a few seconds and ‘retry’ would solve this but now the error does not come.
* Fixed a ‘false alert’ related to settings for temporary tables (the error occurred because of comparing an integer with a non-integer).
* With slow query logs generated from servers greater than 5.1 Query Analyzer “Max” column would show a value without …

[Read more]
MONyog 3.0 Query Analyzer introduces MySQL Proxy Support and completely new Advisors by Percona


We are pleased to announce MONyog 3.0 - a major new release. MONyog is rapidly becoming a cost-effective alternative to expensive proprietary tools for MySQL monitoring.

Unlike databases like SQL Server & Oracle, MySQL does not provide powerful APIs to gather extensive profiling information about each and every query. MySQL developers and DBAs have largely used on a combination of the following techniques to find problem SQL:

  2. Slow Query Log and General Query Log
  3. SHOW PROFILES (available from MySQL Community version 5.0.37)
  4. Capturing and filtering tcpdump output

To overcome the shortcomings of profiling features in the MySQL server, MySQL Proxy was introduced which allows developers to route queries via MySQL Proxy and then extract profiling information from MySQL Proxy. (It also provides other features like load balancing, query …

[Read more]
MONyog 3.0 beta 1 Has Been Released

* The ‘query sniffer’ can now connect to and retrieve data from a running instance of the MySQL-proxy program used by one or more clients to connect to MySQL.  A LUA script for controlling the proxy for use with MONyog is provided with this build.  With this sniffer option the SHOW FULL PROCESSLIST statement will not be sent and thus use of ‘query sniffer’ will not put any load on MySQL.
* SSH connections will now attempt more authentication methods in case the first method attempted failed.  This will solve problems reported with tunneling to MySQL on FreeBSD that as per default does not support the full range of SSH authentication methods (and possible similar problems).


[Read more]
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 …

[Read more]
MONyog 2.8 Has Been Released
Dashboard view of the Top 5 tables being used by this blog. Current release of MONyog shows the disk usage even at table level.

Changes (as compared to 2.72) include:

* Added new monitoring module displaying disk usage information for databases and tables.
* Display of slow log data in Log Analyser had added more information (about when query occured, information about number of rows examined and sent)

Bug fixes:
* When a multibyte character was used in a connection name the display would garble and also the connection could not be deleted from GUI.
* When connection was not available the caption for counters should display “n/a”. Since 2.71 it would instead display a string exposing an internal …

[Read more]
MONyog 2.7 Has Been Released

* CPU optimisations in both MONyog (server) process (in particular when ‘Monitors/Advisors’ page was being viewed) and browser processes (viewing Dashboard could cause high CPU usage in Firefox browser in particular).

Bug fix:
* Fixed a dependency with the SSH library that could cause failure to install in Win2K. This was an issue with the updated SSH library introduced with version 2.5.

* The RPM installer scripts for Linux were updated in various ways. This solves issues on specific distributions including: 1) uninstall with the SuSE/YaST ’software management’ GUI was not possisble. 2) It was not always possible to install on top of a running MONyog service - sometimes it was necessary to stop service manually before upgrading. Also note: when updating from trial to single/multi server or from single server to multi server it …

[Read more]
MONyog 2.6 Has Been Released

Changes (as compared to 2.51) include:

* Log Analyzer code has been completely refactored resulting in better performance and stability and more maintainable code.
* The progress indicator for downloads in Log Analyzer page is now a true quantitative progress bar.
* Error messages in Log Analyzer were rewritten. Every single possible error is now differentiated by a specific message providing help for the situation.

Bug fixes:
* “Group by” option in history/trends page could deliver incorrect results if MySQL and MONyog were using different timezones.
* With SFTP connection to the log file selecting “ALL” for log size to be downloaded in Log Analyzer page could have the result that the log file download would last forever.
* Analyzing log chunks containing BULK INSERT statements could in special situations cause a program …

[Read more]
Showing entries 61 to 70 of 81
« 10 Newer Entries | 10 Older Entries »