Nagios Checks for HandlerSocket
February 11th, 2011 Posted in HandlerSocket, MySQL, Nagios, Random Tech, Uncategorized
I’ve written some new Nagios checks for HandlerSocket. check_handlersocket is a part of http://code.google.com/p/check-mysql-all/, and is meant to be called locally on the HandlerSocket server (usually via NRPE), but the perl-Net-HandlerSocket module must be installed. Feedback is welcome, usage is as follows:
Usage:
check_handlersocket -K [options]
Options:
-K, --check= The check to run
--columns= Comma-separated list of column names
-c, --critical= The level at which a critical alarm is raised.
-d, --database= The database to use
-h, --help Display this message and exit
-H, --host= The target server host
--index The name of the index to open
--index-value The key to find
--limit The maximum number of records to retrieve
--offset The number of records skipped before retrieving records
--port= The port HandlerSocket is listening on
--table The table to use
-t, --timeout= Seconds before connection/query attempts timeout
-v, --verbose Increase verbosity level
-V, --version Display version information and exit
-w, --warning The level at which a warning is raised.
Defaults are:
ATTRIBUTE VALUE
-------------------------- -------------------------------
check No default value
columns No default value
critical Check-specific
database No default value
help FALSE
host localhost
index No default value
index-value No default value
limit 1
offset 0
port 9998 for reads, 9999 for writes
socket No default value
table No default value
timeout 10 seconds
verbose 1 (out of 3)
version FALSE
warning Check-specific
The following checks are supported:
read_connect write_connect read_exec delete_exec
Tags: HandlerSocket, Nagios
