I'm having a bit of trouble understanding the HTTP IpService check. We have a Zenoss Core 2.2.4 installation monitoring a number of Linux servers.
I went into /Services/IpService/Privileged and enabled all services that we like to monitor on our servers. We also created Process checks for the processes we'd like to monitor. This is generally working just fine, but somehow Zenoss only shows 1 host in the list of monitored devices for the HTTP and HTTPS IpService, while most of our servers run Apache. For all other IpServices that we monitor this is working as expected, but somehow the HTTP and HTTPS IpService checks 'detect' only one device, while a lot more than 1 are running Apache. I don't know if it's significant, but this one device is the only one running CentOS 3, all others run a more recent release of CentOS. QUESTION 1: What could be the reason that other devices running Apache are not detected? The other day Apache httpd on the only device that is being monitored by the HTTP IpService check stopped responding. The httpd processes were still running, but they were not serving any websites. Now, since the httpd processes were still in the process table I understand that the Process checks did not generate any events, but I expected the HTTP IpService to generate one. Restarting Apache on the device got things to work again, but Zenoss did not notice anything going wrong. QUESTION 2: What does the HTTP IpService check do exactly? Doesn't the HTTP IpService check for 200 OK responses? Do I need to use the check_http Nagios plugin as described http://www.zenoss.com/community/docs/zenoss-guide/2.2.4/ch15s02.html ? (That seems like a lot of work for just a 200 OK response check, so I'd rather just use the built-in HTTP IpService check if possible.) Thanks. -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=27441#27441 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
