On 4/19/07, MoreDakka <[EMAIL PROTECTED]> wrote:
Thanks Chet, I'm still trying to find some answers for:I'm trying to setup the Nagios plugin check_http. There are a couple things: 1. The site that they are trying to check is password protected. So I get a HTTP WARNING: HTTP/1.0 401 Unauthorized in the check. I'm not sure if ZenOSs will see this as a positive or a negative thing (I need it to see it as a Positive thing, if not how would I change the command to work with a password protected page?) 2. Like above, I'm unsure if this is actually reporting properly. Is there a way to tell if ZenOSs is checking every 60 seconds. Now that I've done some more testing I have a couple more things: 3. I've setup just a basic apache server on a centos4.4 box to see if I can get a proper message out of this thing with one of my boxes. I can access the server by going to it's IP, I get the basic Apache page. Tried to have zenoss run the check_http command on the IP and I get "HTTP WARNING: HTTP/1.1 403 Forbidden" which doesn't make any sense as I can access the page via IE or Firefox. The command I'm running is " /usr/local/zenoss/libexec/check_http -I ${dev/manageIp} -t1000 -s "Apache HTTP Server Test Page" " 4. My boss has asked if Zenoss can have multiple things fail before alerting via email or pager? Example - We are running telnet/http/ping on remote devices. Sometimes we might not get a response from a ping but no problem on http, same with telnet. He would like to see Zenoss have the ability to monitor all three and if all three go down to alert, not one or two but all three.
1. You can read all about the options that check_http takes by running "~/libexec/check_http -h" as the zenoss user. Doing authentication only requires adding "-a username:password" to the command line. 2. If Zenoss doesn't get the heartbeat message from zencommand in between each cycle it will generate a heartbeat failure event at the error level. As long as you don't have this event, zencommand is working. 3. Maybe you're using virtual hosting or something similar that requires that the HTTP request come in with the proper hostname. You can make this happen by using the -u <uri> option of the check_http plugin. 4. Zenoss currently doesn't do this kind of alert correlation very easily. It would require some non-trivial custom extension. -- Chet Luther [EMAIL PROTECTED] _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
