A trivial Nagios (Monitoring Plugins compatible) checker for testing the availability of ZeroC ICE service objects.
-H
|--host
arg: Host name of service (defaultlocalhost
).-p
|--port
arg: Port number of service.-P
|--protocol
arg: Protocol name (defaulttcp
).-o
|--object
arg: Object name (can be specified multiple times).-w
|--warn
arg: Response time which will trigger a warning result (default1000
ms).-s
|--crit
arg: Response time which will trigger a critical result (default5000
ms).-h
|--help
: Show help
Example:
./check_ice --host my.service.lan --port 4000 --object auth --object api
Or in the short form:
./check_ice <host> <other options> <object 1> [<object 2> ... <object N>]
Example:
./check_ice my.service.lan -p 4000 auth api
define command {
command_name check_ice
command_line $USER1$/check_ice $HOSTADDRESS$ -p $ARG1$ $ARG2$ $ARG3$ $ARG4$ $ARG5$
}
define service {
use local-service
hostgroup_name api-servers
service_description MyAPI
check_command check_ice!4000!auth!api
}
ICE OK: auth 3.4723ms OK: api 0.928027ms
In keeping with the existing Monitoring Plugins specification:
0
OK; all objects responded in a timely manner.1
warning; at least one object took longer than warning time to respond.2
critical; at least one object took longer than critical time to respond or was unreachable.3
no checks performed; help, bad options, etc.
check_ice
creates a proxy for each object provided on the command line in turn and calls ice_ping()
on it.
The ping operation is timed for each object separately. It is likely that after the first object responds, connection reuse will result in much lower ping times for subsequent objects.
bjam
bjam install