I’ve been looking over the documentation lately and trying to find ways to improve the installation experience for new users. That said, I’ve written a short but useful description of the easiest way to install all of the Perl and PHP requirements for Kontrollbase. You can find it here: http://kontrollsoft.com/kontrollbase/userguide/installation-install_overview.php#simple – or in the Installation [...]

A new version of Kontrollbase – the enterprise monitoring, analytics, reporting, and historical analysis webapp for MySQL database administrators and advanced users of MySQL databases – is available for download. See the downloads page or run “svn update” to get your new version today. http://kontrollsoft.com/software-downloads

CMON - the Cluster Monitor has recently been released and here is a little how to about how to install from binary and source (at the end), deployment etc.

1. Download the cmon binary package to a monitoring host
Currently there are binaries available for Linux 64-bit and 32-bit (statically linked) and works for MySQL Cluster 7.0.9 and later.

In this case the monitoring host will be on 'ndb05' (IP address 10.0.1.5) - see 9. Suggested Deployment for a picture describing the setup.

The Monitoring machine should have installed:

• a mysql server up and running that will store the cmon database (if you build from source you need to have the mysql cluster libraries and include files)
• apache (if you want to have the web interface) + php_mysql
• rrdtool (if you want to have graphs in web interface)
…

Good news for everyone that has wanted the performance tuning abilities of Kontrollbase – the opensource enterprise monitor for MySQL – but didn’t want to install a centralized monitoring application for their MySQL database servers. Now the same performance tuning reports are available in a single script that can be run from the command line [...]

I’m really proud to announce the release of the version 1.0 of mysql-snmp.

What is mysql-snmp?

mysql-snmp is a mix between the excellent MySQL Cacti Templates and a Net-SNMP agent. The idea is that combining the power of the MySQL Cacti Templates and any SNMP based monitoring would unleash a powerful mysql monitoring system. Of course this project favorite monitoring system is OpenNMS.

mysql-snmp is shipped with the necessary OpenNMS configuration files, but any other SNMP monitoring software can …

It just works. In absence of any MySQL monitoring for your site, I have found no solution that gets you operational as quickly and easily. MONyog can be deployed in 60 seconds, and configured in another 60 seconds. Within 5 minutes you can have visual monitoring of your MySQL environment.

MONyog is an agentless process, which is an advantage for easy install, but does not provide for monitoring redundancy in the capture of information due to agentless nature. It’s a static standalone executable which is great if you need something to work out of the box. You can easily configure multiple servers in a replication topology, or different servers in your environment. You get the ability to monitor all the usual information, with a dashboard and detailed graphs. While MONyog does provide customizations of rules for the graphs and presentation order, that’s about it. You can’t at this time …

“Show Slave Status” command has a last column “Seconds_Behind_Master”, which gives us idea about how much time slave is lagging behind master. It is an important to be considered parameter…

The post Replication slave lag monitoring using heartbeat and windows batch scripts first appeared on Change Is Inevitable.

There is a nagios plugin available on the MMM's google-code page, but if you didn't find it yet, here it is:

http://code.google.com/p/check-mysql-all/wiki/check_mmm

You can call this plugin over nrpe. I'm already working on to fork a version which more useful with passive checks.

This plugin was developed by Ryan Lowe (Percona).

Before a monitoring and notification system for MySQL (and other infrastructure) can be fully conceived, a variety of questions must be asked. I’ve attempted to put some of the most important of them together in this post.

These are what I feel are some best practice recommendations.



#1 Define what is to be monitored.

• 
  
• Is it a HOST?
  
• Is it a SERVICE?
  

#2 Determine what level of health monitoring is desirable.

• 
  
• Basic Monitoring Probes (typically active checks)
  
  • 
    
  • Simple TCP/IP port up/down
    
  • Disk space, free memory, swap utilization, etc
    
  • File exists (or does not exist, or is not of at least X size)
    
  …

Ronald Bradford wants to know what kind of Monitoring you use..
He specifically wants to know about Alerting tools

There's different cases , looking at it from a full infrastructure point my current favourite is Zabbix or good old Nagios,

But when looking at it from a debugging perspective you have MySQLAR or Hyperic, but those aren't in the alerting list.

However, when you are building HA clusters, you have custom scripts running either from mon or from pacemaker ..

Still .. Ronald probably wants more input :)

Technorati Tags: ha monitoring msql …