NRPE vs. check_by_ssh vs. nagios_statd

[Karl DeBisschop]

On Tue, 2003-01-14 at 12:04, Carroll, Jim P [Contractor] wrote:
> A common question, one which burned in my mind when I came to that
> crossroads, and perhaps one which should be added to the FAQ.
>  
> I'll throw my $0.02 in, but YMMV, and I'm sure you'll get some
> variance in opinions.
>  
> - check_by_ssh -- great for punching through firewalls where port 22
> is already open (saves you having to punch more holes); doesn't scale
> well, because of the crypto computations
>  
> - NRPE -- it's what I'm using; many aren't thrilled with having to
> manage multiple nrpe.cfg files across every client; I've managed to
> make do
>  
> - nrpep -- not terribly familiar with it; basically a variation on the
> NRPE theme, I believe, except in Perl
>  
> - nagios_statd -- for starters, you'd have to install Python on ever
> client you wish to install this on; I also seem to recall reading a
> post to the list where someone was having problems expanding on the
> functionality
>  
> - check_snmp -- this is something I've been pondering for a while, and
> would like to try; someone posted very recently that it's quite
> lightweight; you'll need the SNMP binaries installed on the Nagios
> host as well as every client; not sure, but I'm guessing that the
> lion's share of the SNMP effort is peeling back the layers to find
> exactly what things you can monitor

I made the recent post, and I'm crafting a reply to it now. But your
guess is correct, determining what you can monitor is the lions share of
the work. But even so, it's usually not hard, and you can generally
monitor quite a lot. More to follow.

--
Karl




-------------------------------------------------------
This SF.NET email is sponsored by: Take your first step towards giving 
your online business a competitive advantage. Test-drive a Thawte SSL 
certificate - our easy online guide will show you how. Click here to get 
started: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0027en