It's been a while since I released an update to innotop, but I have not been idle. I'm currently working hard to add major new features and functionality. Here's a quick list of what's coming.

A kind soul has contributed a Debian/Ubuntu package for the innotop MySQL and InnoDB monitor. Thanks Sebastien Estienne!

I recently tested installing innotop on Microsoft Windows. There was one slight glitch, but I changed a couple lines of code, and now it runs out of the box under ActivePerl. Version 0.1.156 contains those changes for Windows compatibility.

I recently got a message letting me know FreeBSD users will soon be able to install the innotop MySQL and InnoDB monitor through ports. Gentoo GNU/Linux users can find innotop in Portage.

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.

Version 0.1.152 of innotop is a small maintenance and bug-fix release. I found some more ways to make it deal with garbage input without crashing. Of course, that means it's harder to find errors because it doesn't complain and let me know they exist, but that's what you are for :-)

Version 0.1.149 of the innotop MySQL and InnoDB monitor is a major upgrade. As of this version I'm declaring innotop "stable," meaning I've put some work into making it deal with unexpected input. It should be very resistant to any sort of crash now. You can download innotop from the original article.

MySQL issues a cryptic error message, "Error on rename," when you try to alter a table in such a way that it would break a foreign key constraint.

I've released version 0.1.146 of the innotop MySQL and InnoDB monitor. You can download innotop from the original article.

I re-arranged some information to be more compact and readable in this version, but there isn't really much new functionality. This is mostly a bug-fix release to prevent crashes when innotop encounters unexpected information, or doesn't find some information it expects to exist. It's still very much beta software, so it may die unexpectedly. See this article about what information I need to debug and fix crashes.

Crashes should not cause any loss of information or other problems, by the way. It's completely safe to run, because it doesn't modify anything, it just reads status information. Up till now I've preferred …

This is one in a series of articles on how to use innotop, a MySQL and InnoDB monitor. In this article I'll explain how innotop can make it much easier to collect useful information from SHOW STATUS and SHOW VARIABLES into one place. There are three modes in innotop that do this in different ways, so one of them may meet your needs.