Announce: check_mysql_perf

[Gerhard Lausser]

Hi Nagios users,

allow me to offer you my plugin check_mysql_perf.
It was written to monitor (primarily) performance related characteristics of
a MySQL database.
The -m option tells the plugin the desired mode. Possible keywords are:

threads-connected (Check 'Threads connected')
qcache-hitrate    (Check 'Query cache hitrate')
keycache-hitrate  (Check 'Key cache hitrate')
connection-time   (Check 'Seconds to get a connection')
tmp-disk-tables   (Check 'Percent of temp tables created on disk')
slave-lag         (Check 'Seconds behind master')
slave-io-running  (Check for 'Slave io running: Yes')
slave-sql-running (Check for 'Slave sql running: Yes')

Example:
check_mysql_perf -m qcache-hitrate
OK - Query Cache Hitrate at 93.93%|qcache_hitrate=93.93%;90:;80:

check_mysql_perf -m qcache-hitrate -w 95: -c 90:
WARNING - Query Cache Hitrate at 93.93%|qcache_hitrate=93.93%;95:;90:

Please take into account that you need also the nagios-plugins package (i
recommend 1.4.11) for a successful build.
The steps are:
- tar zxvf nagios-plugins-1.4.11.tar.gz
- cd nagios-plugins-1.4.11; ./configure; make
- cd ..
- tar zxvf check_mysql-perf-1.1.tar.gz
- cd check_mysql-perf-1.1
- ./configure --with-officialplugins=/absolute/path/to/nagios-plugins-1.4.11
- make

Of course a mysql-dev installation has to be found (or provided with
--with-mysql) either in step 2 or step 6.

You can find more documentation and the download link at 
http://www.consol.com/opensource/nagios/check-mysql-perf

Greetings from Munich,
Gerhard


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null