Hmmm, the HTTPMonitor with 2.2.4 "just works" for us. I created a template which we've bound to a subclass called /Devices /Server /Linux /Web I named it IndexPageCheck.
Datasource IndexPage, type HttpMonitor, enabled true Set port to 80, SSL off, URL to / ... Graph is ResponseTime, Datapoint named time, IndexPage_time . . . for graph point... -- James Pulver Information Technology Area Supervisor LEPP Computer Group Cornell University breun wrote: > The HttpMonitor seems to be what I need, but the names of the sites are also > the hostnames of the machines that are already being monitored by SNMP. The > Monitoring Websites with HttpMonitor HOWTO at > http://www.zenoss.com/community/docs/howtos/monitoring-websites-with-httpmonitor > doesn't really help either. Like the comment on that page says: > > > jdb wrote: >> I've got to say that this "Complications" paragraph completely throws me for >> a loop. I'm in this situation, trying to do what should be the simplest >> thing in the world: configure zenoss to monitor http on a server, and I run >> across this paragraph which states this problem which must affect a lot of >> users, but then doesn't tell me what to do. > > > Can anyone who has gotten this to work help out? All I want is to monitor > whether the webservers on our monitored hosts return 200 OK messages or not. > > > > > -------------------- m2f -------------------- > > Read this topic online here: > http://forums.zenoss.com/viewtopic.php?p=28193#28193 > > -------------------- m2f -------------------- > > > > _______________________________________________ > zenoss-users mailing list > [email protected] > http://lists.zenoss.org/mailman/listinfo/zenoss-users _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
