[sllug-members]: Which Network Monitoring Solution?

[Nathan Lane]

Thanks John, was that config for nagios or zenoss?

On Nov 28, 2007 9:13 AM, John M. Anderson <sontek at gmail.com> wrote:

>
>
> On Nov 28, 2007 8:40 AM, Nathan Lane <nathamberlane at gmail.com> wrote:
>
> > Hi I am trying to get a network monitoring solution.  In the past we've
> > attempted to use Nagios, but couldn't figure out how to get it to monitor
> > whether a specific web page is accessible on a certain server.  Today I am
> > trying to set up an OpenNMS server to do the same thing, and I am still
> > running into road blocks - I can't find a straight forward solution and I've
> > been working on it for two days (same problem as with Nagios).  I just found
> > another one - Zenoss - and I'm wondering if it's any better/easier/simpler
> > to configure, or if it stands up to Nagios and OpenNMS.
> >
>
> In my experience OpenNMS was pretty  bad.  I'd suggest sticking with
> Nagios or going to Zenoss ( http://www.zenoss.com/ ).
>
> Here is a config that checks a specific website:
>
> define service {
>     name                generic-service
>
>     active_checks_enabled       1
>     passive_checks_enabled      1
>     parallelize_check       1
>     obsess_over_service     1
>     check_freshness         0
>     event_handler_enabled       1
>     flap_detection_enabled      0 ; just seems stupid to me
>     failure_prediction_enabled  0 ; kinda needless
>     process_perf_data       1
>     retain_status_information   1
>
>     max_check_attempts      1
>
>     check_period            24x7
>
>     notification_interval       0 ; only send updates on status change
>     is_volatile         0
>     notifications_enabled       1
>     notification_period     24x7
>     notification_options        w,u,c,r
>
>     contact_groups          everyone
>
>     register            0
> }
>
> define service {
>     use             generic-service
>     name                generic-web-site
>
>     max_check_attempts      1
>     normal_check_interval       5   ; 5 minutes
>     retry_check_interval        1  ; if down, recheck every 1 minutes
>     notification_interval       60  ; if down, renotify every 60 minutes
>
>     servicegroups           websites
>
>     register            0
> }
>
> define service {
>     use         generic-web-site
>     host_name       servername
>     service_description Name
>     check_command       check_http_by_ip!255.255.255.255!https://url
> }
>
>
>
>
> the first 2 are just generic settings that all services will have, and
> then the final one you can define per website that you need to monitor.
>
> ______________________________________________________________________
> See http://www.sllug.org/ for latest SLLUG news, information, links.
> Join SLLUG and other UT LUG members on irc.FreeNode.net channel #Utah
> sllug-members at sllug.org
> http://www.sllug.org/cgi-bin/mailman/listinfo/sllug-members
>
>


-- 
Nathan Lane
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://sllug.org/pipermail/sllug-members/attachments/20071128/dd565fa4/attachment-0001.htm