I recently published an article on O’Reilly about monitoring tools for MySQL. Of course I believe innotop is the best in its class, so I mentioned it. But I also recently added some features to innotop, and made a stability fix too.
Innotop upgrade: new features, stability
Now you can easily monitor open tables with innotop. Just get the latest version (your configuration file will be upgraded seamlessly) and press the ‘O’ key (that’s capital “oh”).
This can be useful when a table is in use by a query, and things are timing out with a lock wait, yet you can’t find any transaction that has a lock. At least you can see which table (of potentially many accessed by a query) is causing the problem.
There’s a default filter to only show tables in use by one or more queries. As always, press the ‘w’ key to add or remove ‘where’ clauses (regular expression filters) on any column in the display. Press ‘c’ to choose columns, and ‘s’ to choose a sort column. Press ‘r’ to reverse sort. Press ‘$’ to see every configuration variable relevant to this screen, and ‘?’ to see every key mapping for this screen.
I’m also continuing on the epic quest to make innotop handle basically any crap input you throw at it. Since the output of
SHOW INNODB STATUS can be truncated right in the middle of something due to it being large, this means the InnoDBParser module might return hashes with half the expected keys, or keys whose values are undefined, and so forth. It may sound easy to handle this, until you realize the sheer size and complexity of the data in the status monitor. Checking each and every thing for complete and defined values (and providing defaults if something is missing) is tedious, and I hate to do it because it makes the code messy, but it’s a necessary evil. If you have problems with innotop crashing, please send me a crash report (see this article to find out what information I need). The good news is I haven’t received a crash report in a long time now, so perhaps it’s getting pretty good at “garbage in, useful information out.”
Article on O’Reilly Network
O’Reilly just published my article on Open Tools for MySQL Administrators, where I discuss the tools I’ve found useful for monitoring MySQL. I’ve learned a good bit from writing this, such as how to spell Giuseppe Maxia’s name right (apparently it’s pretty common to misspell it, my apologies for adding to that).
I am also watching the comments with interest. Someone has already mentioned a tool I didn’t know existed, moodss. It is a modular system for monitoring lots of things, with what looks like very nice MySQL monitoring functionality. I haven’t tried it, but I’m strongly considering installing it at work next week. I’ll let you know what I think.
I also got to work with chromatic — he edited the article. It’s a pleasure to be supported by someone so knowledgeable. In case you don’t know, chromatic is a great Perl programmer and has written a book on Extreme Programming.
Someone sent me a message about a particular module I used in my MySQL Query Profiler tool for debugging purposes. Apparently, when I took out all the places I actually used it but didn’t remove the reference to the module, it caused some earlier versions of Perl to complain. I fixed that too.
Stay tuned for more goodness to come! At some point I’ll finish some of my 65 draft articles and publish them. Yep, I have 65 articles in various states of completion…! Yikes. You can subscribe if you want to be notified as soon as I publish anything new.