Aug 6, 2012 11:31 AM
Starting with Core 4 - simple web monitor
-
Like (0)
Hi,
I looked at Zenoss a couple of years ago in a previous job but decided against it for various reasons (performance, pay-only windows zenpacks, etc.). With all the improvements and now I'm in a new company, I am seriously considering deploying Core 4. Or rather I have installed the latest (2012-08-03) and would like to start using it in production :-).
I have done some basic discovery and am now at the point where I'd like to start adding "real" (application) monitors. I want to monitor 3 websites on two machines and a loadbalancer (same three sites on two lb'ed machines and the lb). I am a little confused at the best way to do things - the howtos seem pretty involved for just adding an http monitor - are the FAQs/howtos in the forum for previous versions generally valid?
I come from a system (Intellipool INM/KNM) that had a very machine/physical object-centric vision of things - you tied all monitors to a specific machine/object. Is that the Zenoss way? It seemed to be but then I saw the howtos suggesting that I should create a new device category (or class) /Web. I'm not sure I understand why we would do this, at least if we are object/machine based like INM.
I have looked at everything that seemed relevant on the youtube channel and I've looked through the admin docs. Maybe I didn't look hard enough - can you point me to something that will explain the best way forward?
Thanks.
ps. Is there a firm RTM date yet for 4.*?
Here's three ways to set up website monitoring.
1) Add a website device to the http device class. Useful for websites that you don't manage the infrastructure for. Useful for monitoring multiple webservers behind a load balancer where you want an overall picture.
(From Infrastructure tab, add a single device of class http)
2) Bind the httpmonitor template to an existing device. Useful for seeing how the response time performance is affected by that server's resource utilization.
(From the device details page select the Actions/Gear menu, select bind templates, select the httpmonitor template)
3) Create a new device class, e.g. /Server/SSH/Linux/WebServer and associate the httpmonitor template with the new class. The new class will inherit all the templates of the parent classes. Drag your web servers from /Server/SSH/Linux to /Server/SSH/Linux. Good for visualizing a monitoring policy.
Wow. Very nice. Thanks for the great reply!
I have looked around and I still can't find out where I can add the website hostname. Basically what I want to do is add several monitors for the particular websites present on the different servers. The apaches have several virtual hosts, and I want to test each site. Each site has a separate DB and in each case things can go wrong without the default virtual host seeing anything. So for host 192.168.20.1, I want three separate indicators/monitors to test for response time, uptime, etc. for EACH website www.mydomain1.com, www.mydomain2.com and www.mydomain3.com. I am obviously not the only one to need this but I can't see for the life of me where to put the domain!
Thanks again.
Message was edited by: Anton Melser Further clarification asked for.
Follow Us On Twitter »
|
Latest from the Zenoss Blog » | Community | Products | Services Resources | Customers Partners | About Us | ||
Copyright © 2005-2011 Zenoss, Inc.
|
||||||||