non global service check timeouts

[kendallchenoweth]

Is it possible to have a non global service check timeout where the values could be customized per service?

Thanks!

[tmcdonald]

The global service check timeout you speak of can be thought of as a "hard limit" for checks. If there is a "soft limit" for a particular check, it needs to be implemented at the plugin level. Some plugins will support this, usually with the -t option, but it is not a requirement.

[jolson]

Is it possible to have a non global service check timeout where the values could be customized per service?

Most plugins have their own individual timeouts that you are capable of setting. Using check_nrpe as an example:

Code: Select all

[root@localhost ~]# /usr/local/nagios/libexec/check_nrpe -h

NRPE Plugin for Nagios
Copyright (c) 1999-2008 Ethan Galstad ([email protected])
Version: 2.15
Last Modified: 09-06-2013
License: GPL v2 with exemptions (-l for more info)
SSL/TLS Available: Anonymous DH Mode, OpenSSL 0.9.6 or higher required

Usage: check_nrpe -H <host> [ -b <bindaddr> ] [-4] [-6] [-n] [-u] [-p <port>] [-t <timeout>] [-c <command>] [-a <arglist...>]

Options:
-n = Do no use SSL
-u = Make socket timeouts return an UNKNOWN state instead of CRITICAL
<host> = The address of the host running the NRPE daemon
<bindaddr> = bind to local address
-4 = user ipv4 only
-6 = user ipv6 only
[port] = The port on which the daemon is running (default=5666)
[timeout] = Number of seconds before connection times out (default=10)
[command] = The name of the command that the remote daemon should run
[arglist] = Optional arguments that should be passed to the command. Multiple
arguments should be separated by a space. If provided, this must be
the last option supplied on the command line.