MySQL, like any other production service, needs to be monitored whether it be for potential performance problems, availability issues, or utilization as part of capacity planning. But with so many metrics exposed by our operating systems and MySQL, what exactly should one monitor and alert on? This can be a daunting question to answer with just a few servers, let alone in dynamic environments deployed in the cloud.
Why would ANYONE use that garbage? MySQL is junk.
PostgreSQL for the win!
Ha. Came to ask the same question.
At this point, mysql is only useful where acid isn't desired.
I never answered your question but blasted mysql.
To monitor part of the DB, make a page on a site that produces something from the db. Like a math problem that requires a select from the DB. You already know the answer to the this math problem so you just look for it. Every 1 or 2 minutes or so you can use wget or whatever you like to get the contents of this page.
This will let you know the DB is at least up on that domain... to a point.
Again, I strongly recommend postgresql.
(post is archived)