check_http timeout

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
Locked
cmort
Posts: 11
Joined: Tue Feb 07, 2012 3:32 pm

check_http timeout

Post by cmort »

First of all please let me appologize in advance I am new to Nagios and am not extremely literate in Linux.
I am using Nagios XI HTTP checker I believe it is check_http to verify sites are available. It is configured and appears to be fine, can someone tell me what the default timeout is for this checker before it determines the site is not available and can the timeout be adjusted for slow sites or maybe to ensure a site is responding withing a specific length of time?

Thank You
User avatar
jsmurphy
Posts: 989
Joined: Wed Aug 18, 2010 9:46 pm

Re: check_http timeout

Post by jsmurphy »

check_http timeout can be adjust with the -t <seconds> switch... the default is 10 seconds. You can also adjust the warning and critical thresholds with the -w <seconds> and -c <seconds> switches respectively.
cmort
Posts: 11
Joined: Tue Feb 07, 2012 3:32 pm

Re: check_http timeout

Post by cmort »

Thank you for the response.
Can you tell me if I would modify the check_http command in the nagios core config manager "command' area? or from within the monitoring/services area for a specific service? If I were to modify the check_http command in the core config does it apply to any existing services that use the check_http command or only new monitoring services that are configured?
Can I create new versions of the http_check commamd in the core config commands (I see it give the option for new!) for customized parameters like timout , warning or critical?
Thank You
User avatar
jsmurphy
Posts: 989
Joined: Wed Aug 18, 2010 9:46 pm

Re: check_http timeout

Post by jsmurphy »

All of the above are valid solutions to your problem. If it's an exception to the normal stick it on the end of the actual service definition... if you want to update it for all hosts then change the base check_http command definition and if you expect a mix of the two then create a new command definition (just copy the old definition, give it a new name and stick on the extra switches).
Locked