MONyog MySQL Monitor 6.34 Has Been Released

  • peter_laursen
  • September 7th, 2015
  • MONyog, Releases
  • Important notice: With the 6.32 release we changed registration keys. Please have your new key available when upgrading from a pre-6.32-version. As always you will get it from our Customer Portal.

    Changes (as compared to 6.33) include:


    * Added more monitors and charts for monitoring a galera cluster. By default, these monitors are hidden. To display these monitors in Monitors page you can enable “Galera” monitor group from Customize -> Manage Monitor Groups. Charts for these new monitors can be enabled from Customize – > Manage charts.
    * Optimized system charts for faster loading.

    Bug Fixes:

    * EXPLAIN option was not available in Wayback Machine.
    * In some rare cases, MONyog logged SQLite errors if deadlock details contained double quotes.
    * In Wayback Machine interface, MONyog showed wrong time in queries tab when a point was selected in the chart.


    SQLyog MySQL GUI 12.14 Released

  • peter_laursen
  • August 26th, 2015
  • Releases, SQLyog
  • Changes as compared to 12.13 include:


    * Added an option in “Export as SQL Dump”, “Export Table Data As..” and “Scheduled Backup” not to write the SQLyog version to SQL dumps. This will reduce ‘noise’ for users comparing dumps for auditing purposes, when SQLyog has been upgraded.
    * In both “Export as SQL Dump”,  and “Scheduled backup” there is now an option to add a linebreak between rows if BULK  INSERTS are written.  This will increase readability and help to prevent truncation of lines if the dump is opened in an editor or similar and saved again from there.


    * Increased contrast for better identification of selected row in GRID as well as increased visibility of which tab is currently selected.


    Monitoring your Amazon Aurora Databases using MONyog

  • Chetan
  • August 19th, 2015
  • MONyog, MySQL
  • We’re excited to announce the general availability of MONyog for Amazon Aurora. Amazon Web Services’ (AWS) latest offering, the Aurora database combines the speed and availability of commercial databases with the cost-effectiveness and simplicity of open source databases. Designed to provide up to 5x improved performance than MySQL at a price that’s one-tenth of any commercial RDBMS, Aurora definitely looks promising.

    Aurora is fault-tolerant by design, since it replicates data into three locations, making it highly available. To monitor your Aurora databases, you can always rely on MONyog to do the job for you.

    Aurora doesn’t allow to install anything on your Aurora database. Since MONyog is built on an agent-less architecture, it can connect to Aurora without any hassle.

    Connecting to Aurora
    Enter the DNS address of your Aurora instance in ‘Add server’ screen, enter your credentials and you’re done. MONyog will start monitoring your Aurora database right away.

    You can download and install MONyog locally or launch the MONyog AMI from the Amazon Marketplace. If you’re new to MONyog, do check out the top features of MONyog.

    Go ahead, download a free trial of MONyog and start monitoring your Aurora instance right away. If you have any feedback or questions, drop a comment below.

    Manage your Amazon Aurora databases with SQLyog

  • Karthik Suroju
  • August 18th, 2015
  • MySQL, SQLyog
  • We are elated to announce the availability of SQLyog for Amazon Aurora Databases. You can now manage Amazon Aurora databases with SQLyog, the most powerful database manager, admin and GUI tool.

    About Amazon Aurora:
    Amazon Aurora is a MySQL-compatible, relational database engine that combines the speed and availability of high-end commercial databases with the simplicity and cost-effectiveness of open source databases.

    SQLyog + Amazon Aurora:
    It is very easy to connect Aurora database using SQLyog: just enter the DNS address of the Aurora instance as the host parameter, port number from the endpoint as the port parameter and key in your credentials. You can manage your Aurora databases with powerful tools like Synchronisation, Import External Data, Backup Wizard, Job Scheduler etc.

    Not only these, you get all the top features of SQLyog to work with Amazon Aurora databases.

    Download a free trial of SQLyog and start managing your Aurora databases now!

    If you have any feedback or queries, drop us an email or leave a comment below.

    SQLyog MySQL GUI 12.13 Released

  • peter_laursen
  • August 5th, 2015
  • Releases, SQLyog
  • Changes as compared to 12.12 include:

    Bug fixes:

    * Due to use of an old Plink version in older versions of SQLyog, SSH-tunnel could not be created to servers running OpenSSH 6.9x (as now available with Fedora 22 and possibly other ‘bleeding-edge’ Linux distros). We upgraded Plink to version 0.64 (latest) in this release.
    * In rare cases, with an orphaned Plink process started by SQLyog running, the sqlyog.ini file could be locked and thus could not be edited in a text editor for instance.


    Monitoring High Availability on Galera Clusters for MySQL using MONyog

  • Chetan
  • July 29th, 2015
  • MONyog, MySQL
  • Monitoring-High-Availability-on-Galera-Cluster-for-MySQL-using-MONyog

    For every online business, there are millions of transactions happening every second including crucial revenue bearing transactions. Therefore downtime, both planned and unplanned has a cost attached to it and results in lost revenue every second. As the technology improved to meet this demand, the importance of High Availability (HA) became the focus point.

    The introduction of Galera Cluster for MySQL bought true Multimaster Cluster thanks to its synchronous replication. In this article, we’ll show how using MONyog in tandem with Galera provides a simple and best-in-class High Availability solution for MySQL users.

    How to register a Galera Cluster Node in MONyog

    1. Enter the Hostname, port and credentials in “MySQL settings”, test the connection and save it.
    2. Enable “Galera” group from “Customize” > “Manage monitor groups”
    3. In Monitors page, select the “Galera” group and you’re all set.


    Setting up Galera Charts

    With the monitors setup, it would be nice to have a chart to monitor the health of the MySQL cluster. In the Charts tab, click on the gear icon on the right and select ‘Add a new Chart’.

    Let’s create a Chart to view bottleneck in replication between the Galera nodes. This can be done by monitoring the status variable wsrep_local_send_queue_avg
    Add a Series Caption and in Series Value add: [MONyog.MySQL.GlobalStatus.wsrep_local_send_queue_avg] also set the ChartValue to Current.


    Let’s create another Chart to show the %time Galera replication was paused.
    Add a Series Caption and in Series Value, add: [ToInt(MONyog.MySQL.GlobalStatus.wsrep_flow_control_paused) * 100]

    Once the Galera Charts are setup, your Monitors tab will look something like this.


    Galera monitors shipped with MONyog

    Here are the monitors currently available in MONyog. You can hover on them to view advisors and customize as per your requirement.
    Galera monitors shipped with MONyog

    Alerts for Galera

    With Galera Charts in place, all you need is alerts to complete the Galera Cluster monitoring setup. Using this, you can make MONyog alert you when a condition is triggered.

    MONyog supports one default alert for wsrep_ready status variable in the Galera Monitors tab. You can manually enable alerts for any variable. For example, if you want to setup an alert to find out network bottlenecks, here’s how you do it:

    1. Go to Monitors tab, select the Galera group, click on ‘Find network bottleneck’.
    2. In the popup, click on Customize.
    3. On the top-right part of the page you’ll find an option to ‘View advanced’. Click on it and scroll down to see a textarea for ‘Alert condition’.
    4. Now you can write your own alert condition like this:
      function() {
      if( parseInt(this.Value) >= 1)
      return "Critical";
      else if ( parseInt(this.Value) > 0.5)
      return "Warning";
      else return

    If you’re new to MONyog, give it a try and start monitoring your MySQL/MariaDB Galera Clusters. If you have any feedback or questions, drop a comment below.

    Introducing actionable charts in MONyog MySQL Monitor

  • Chetan
  • July 23rd, 2015
  • MONyog, MySQL
  • While MONyog MySQL Monitor is being embraced by DBAs and DevOps around the world, we are constantly adding more features to make MONyog the most complete MySQL monitoring tool.

    MONyog ships 40+ MySQL and system metric charts. It also lets you add custom charts. With the latest update, we have made Charts more powerful by adding few important features to help you find problem queries with ease.

    Here’s a 1 minute video to walk you through the new features.

    Existing customers can download MONyog 6.33 from Customer Area. To evaluate MONyog 6.33, please download a 14-day trial.

    We are really excited about this update and we hope you like the new features. Please feel free to share your feedback.

    Team MONyog

    MONyog MySQL Monitor 6.33 Has Been Released

  • peter_laursen
  • July 23rd, 2015
  • MONyog, Releases
  • Important notice: With the previous 6.32 release we changed registration keys. Please have your new key available when upgrading from a pre-6.32-version. As always you will get it from our Customer Portal.

    Changes (as compared to 6.32) include:


    * Added monitoring of the MySQL –tmpdir volume with the “Free Disk Space” Monitor for Linux (introduced in 6.32).
    * Added an option to view X-Axis labels for large time based charts.
    * The Performance_Schema -based “query sniffer” has been optimized.

    Bug Fixes:

    * Fixed a rare case, where “Charts” page was not loading properly.


    MONyog MySQL Monitor 6.32 Has Been Released

  • peter_laursen
  • July 16th, 2015
  • MONyog, Releases
  • Important notice: With this release we have changed registration keys. Please have your  new key available when upgrading. As always you will get it from our Customer Portal.

    Changes (as compared to 6.31) include:


    * Added a “Free Disk Space” Monitor for Linux. This new feature will collect information directly from the file system (unlike the existing ‘Disk Info’ that uses MySQL “SHOW TABLE STATUS”). Information is collected from volumes storing both MySQL data directory and InnoDB data directory (if different), and user will be alerted if either crosses a specified threshold.
    * In Charts page added an option to select a time interval for display by zooming a chart using mouse and similar input devices (touchpad etc.). Note that zooming one chart will change the timeframe of all the charts displayed.
    * Added an option to view queries for a selected time range in time range based charts in Charts page.

    Bug Fixes:

    * In rare cases, Monitors page could show wrong data for Linux counters if the HISTORY timeframe was selected for the page.  Other available timeframes were not affected.
    * When monitoring a MariaDB server using a galera-based replication setup we will now execute SHOW ALL SLAVES STATUS rather than just SHOW SLAVE STATUS. Before this MONyog replication page showed an empty result and alerts were not sent. However due to limitations with current MONyog architecture we are only able to handle the first row of SHOW ALL SLAVES STATUS with this release, if more are returned, and only information from one slave node will be available.


    MONyog MySQL Monitor 6.31 Has Been Released

  • peter_laursen
  • June 25th, 2015
  • MONyog, Releases
  • Changes (as compared to 6.3) include:

    * What is plotted in “Charts” (formerly “Dashboard”) page may now be specified as a time interval and not only as a number of latest sample points. This increases usability of the page.
    * Long running query log now includes action (kill/notify/notify and kill) and the time of action.
    * Locked and locking queries tab in Real-Time interface is optimized and loads faster.
    * Added w    ildcard filtering using the “*” character as wildcard for user and host in Query Analyzer for Slow Query Log.

    Bug Fixes:
    * MONyog failed to send notification for an InnoDB deadlock if deadlock details (as recorded by SHOW ENGINE INNODB STATUS) contained double quotes.


    Page 1 of 4612345...102030...Last »