Page 2 of 2
Re: CRITICAL Socket Timeout Errors When Monitoring HTTP Site
Posted: Sun Apr 24, 2016 7:11 am
by Brooks
I'm sure the site does have multiple ip addresses. Why if I'm monitoring the url this needs to know an IP address. What is the best way to add this without requiring a specific ip?
Re: CRITICAL Socket Timeout Errors When Monitoring HTTP Site
Posted: Sun Apr 24, 2016 10:29 am
by rkennedy
You'll want to navigate to Configure -> Core Config Manager -> Click 'Services' -> Find the one in question.
Then, remove the
-I x.x.x.x part from your check_command. It'll work fine and only use DNS, without validating the IP that DNS returns. The -I is used in conjunction when a specific IP should be returned.
Here's another example -
Code: Select all
[root@localhost libexec]# ./check_http -H google.com -f ok -u "/" -S -p 443
HTTP OK: HTTP/1.1 301 Moved Permanently - 654 bytes in 0.113 second response time |time=0.113418s;;;0.000000 size=654B;;;0
Re: CRITICAL Socket Timeout Errors When Monitoring HTTP Site
Posted: Sun Apr 24, 2016 12:05 pm
by Brooks
That makes sense. I'll give that a shot.
Thanks
Re: CRITICAL Socket Timeout Errors When Monitoring HTTP Site
Posted: Mon Apr 25, 2016 10:37 am
by rkennedy
Sounds good - let us know if you need any further assistance.