Tuesday, April 12, 2011

MySQl Enterprise Monitor 2.3.2

It's the second point release of MySQL Enterprise Monitor 2.3. And there some nice new features and bugfixes.

It's now possible to enable or disable event blackout for specific servers easily.

It should now graph InnoDB with multiple buffer pools correctly. It won't work for 5.5.8 however, see Bug #60777 and Bug #60831 for more info on that.

Read the complete changelogs for all the details.

The Advisors/Rules were also updated. But there is still room for improvement:
  • Bug #60828 Add rule to detect duplicate foreign keys
  • Bug #60697 False Positives for Root Account Can Login Remotely
  • Bug #60695 False positives for tables w/o keys for 5.5 with perf schema
  • Bug #60677 "User Has Rights To Database That Does Not Exist" gives false positives
  • Bug #60676 Add rule to monitor if the timezone info is loaded
  • Bug #60587 Advice for Root Account Without Password is not correct
  • Bug #60586 key buffer size check gives false positives
See also my previous blog posts:
MySQL Enterprise is very easy to install, update and configure. Extending is very well possible using custom SQL queries and Lua scripting, but not really easy. Adding more graphs is also quite hard.

The graphs look way better than many other tools available. The size is easily configurable so that the graph is as wide as your screen.

The combination with the Query Analyzer is nice, but I'm not really using it very often as it requires a MySQL Proxy instance to capture the query info. They're fixing that my integrating query capture in Connector/J, Connector/NET and the PHP Connector (the later is only a beta). There are also other ways to capture queries in MySQL: using the sqlstats plugin, so there are lots of possibilities for the query analyzer to become much more useful.

The downside of MySQL Enterprise Monitor is that the tool itself is not free or opensource. It does use an opensource environment: Tomcat, Lua and many opensource Java classes.

Reporting Bugs and Feature request works really well, and lots and lots of issues which I encountered were fixed.

MySQL Monitor is one of the top reasons to choose the MySQL Enterprise Subscription.

And some questions for the readers of this post:
  • What are you using for monitoring?
  • Are you using MEM? Are you satisfied with it? Why? Why not?
  • If you are using Nagios/Cacti: Which checks/templates do you use?

No comments:

Post a Comment

Post a Comment