myq gadgets

MyQ Gadgets 0.0.9 released

A new version of myq_gadgets has been released and you can download it here.

Changelog since the last released version here:
Version 0.0.9 -
    - Documented new reports in README
    - Updated 'thds' column in the 'cttf' report to read 'crtd' instead.
Version 0.0.8 -
    - Added a bunch more innodb reports, looking for the good stuff.
Version 0.0.7 -
    - Added an 'innodb' mode to myq_status to support 5.0+ STATUS variables.
      'myq_innodb_status' continues to handle SHOW INNODB STATUS output,
      mostly for 4.1 and earlier.
    - Beefed up the format_memory function to use recursion to determine the
      appropriate output multiplier (tera, giga, mega, kilo, etc.)

MyQ Gadgets 0.0.6 released

Thanks to those who tried it out and left feedback, much appreciated.

  • Changed /usr/local/bin/perl to /usr/bin/env perl to make the open source crowd happy.  Make sure the proper perl directory is first in your $PATH    
  • Made the usage string contain the valid modes in myq_status
  • Added check for mysql binary in
  • Quoted the --password option in to handle passwords with strange characters in them.
  • Setup default options string to be clearer which options are available to the scripts (like -? and -d)
  • Bumped the minimum repeat time for myq_status down to 1 second.  Note that it still might take more than 1 second for the check to run.

Whoops! First faux pas in releasing software

Thanks to the few people who pointed out a copyright infringement with the name 'MySQL Gadgets' for my tool. It has now been renamed 'MyQ Gadgets'. This is actually more appropriate (but hopefully not a violation of some other copyright), since I use the 'myq' prefix on my MySQL scripts as an easy, unique prefix for command line tab completion in bash.

Introducing MyQ Gadgets

Today I am introducing my first open source contribution to MySQL: MyQ Gadgets. These are a small collection of tools I wrote to make it easier to see what is going on inside of a running MySQL server. There's nothing magical about them, they simply collect values from SHOW STATUS, SHOW SLAVE STATUS, and SHOW INNODB STATUS and present them in an easier-to-digest format similar to that of iostat (for those who are familiar with it). Here's an example of some data from SHOW INNODB STATUS:

./myq_innodb_status -h -u user -p password -t 20
row      Inno Engine (/sec)   Buffer (/sec) (%)            Log  OS (/sec)       Semaphores
time     read  ins  upd  del  new read wrte full dirt  hit io/s read wrte fsyc  spw rnds  osw
16:10:55 3.8k  9.8  9.7    0  0.3    0 13.7   93   13  100 14.1    0 19.4 14.7  30m  94m 485k 
16:11:15 1.0k 10.0  4.8    0  0.3  0.1 17.6   93   13  100 11.5  0.1 20.0 12.4  3.0 21.0  1.0 



Recent comments

About Me

Jay Janssen
Yahoo!, Inc.
jayj at yahoo dash inc dot com

High Availability
Global Load Balancing

View Jay Janssen's LinkedIn profileView Jay Janssen's Facebook profile

User login