cool Nagios + DNX tutorial

[Paulus, Jake]

Thank your buddy Pat for me. Even when something turns out to be
relatively simple (as the steps in the article lead me to believe is the
case for this example) it is always helpful to see a how-to lay out some
steps to follow. For me, it shows how much work is involved and more
easily allows me to decide whether the cost/benefit ratio hits the sweet
spot for the project to get onto my to-do list. 

 

One note:

Pat might find the following link useful to help finish the Files
section:

http://nagioswiki.com/wiki/index.php/Special:Upload

 

(consider help sent :-) )

 

Thanks, -Jake

 

________________________________

From: Roger [mailto:Roger at nagioswiki.com] 
Sent: Saturday, November 08, 2008 1:08 AM
To: Nagios Users Mailinglist
Subject: [Nagios-users] cool Nagios + DNX tutorial

 

My buddy Pat at Petta Tech just put up a great DNX + Nagios tutorial 

http://nagioswiki.com/wiki/index.php/Nagios_%2B_DNX 

He did a good job of documenting how he worked out the various kinks.
He's running about 5000 checks on 800 hosts, and the servers that have
this running are HP DL360 G5s, dual quad cores, and 16Gb of RAM 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20081108/4b45f442/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null