Well, sure it's supposed to do *something*, but it's not always obvious
*what*. Also, I guess I was surprised that they'd go to the trouble of a
zenpack + howto for HTTP Monitoring if you can just do it from the IP
service for port 80... Or that they wouldn't even mention that you can
do some lite-weight monitoring right from CORE.
*sigh*
Maybe I oughtn't be surprised at all anymore.
--
James Pulver
Information Technology Area Supervisor
LEPP Computer Group
Cornell University
Digitante wrote:
jmp242 wrote:
I'd be interested in hearing what people are using those options for
(and if they even work or are supposed to work).
What do you mean by "are supposed to work"? I mean surely if it's there, it's
"supposed" to work?
The documentation is the admin guide:
http://www.zenoss.com/community/docs/zenoss-guide/2.2.0/ch11s02.html
But you're right that these options are not actually documented. OTOH, a great
deal of Zenoss is undocumented, so that means nothing. The page also clearly
out of date, since it refers to text fields that do not exist in the interface
(it wasn't too hard to figure out how to add an IP Service, but the procedure
doesn't fit the description -- I presume it's been changed).
ISTM that monitoring availability of an HTTP server has got to be one of the biggest use
cases for something like Zenoss, so this ought to work, ought to be documented, and
really, there ought to be "one obvious way to do it".
-------------------- m2f --------------------
Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=22422#22422
-------------------- 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
