Archived community.zenoss.org | full text search
Skip navigation
2126 Views 2 Replies Latest reply: Aug 7, 2012 1:50 PM by Anton Melser RSS
Anton Melser Rank: White Belt 10 posts since
Aug 6, 2012
Currently Being Moderated

Aug 6, 2012 11:31 AM

Starting with Core 4 - simple web monitor

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.*?

  • kerickson ZenossEmployee 75 posts since
    Sep 14, 2009
    Currently Being Moderated
    1. Aug 6, 2012 2:58 PM (in response to Anton Melser)
    Re: Starting with Core 4 - simple web monitor

    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.

More Like This

  • Retrieving data ...

Legend

  • Correct Answers - 4 points
  • Helpful Answers - 2 points