NRPE vs. check_by_ssh

[Christopher McAtackney]

2009/3/24 Michael Schwartzkopff <misch at multinet.de>:
> Am Dienstag, 24. März 2009 10:45:08 schrieb Christopher McAtackney:
>> Hi all,
>>
>> I was wondering if someone could give a brief overview of the pros /
>> cons of using NRPE to monitor my remote hosts versus using the
>> check_by_ssh command?
>>
>> I'm aware that check_by_ssh increases the CPU overhead, but I'm not
>> clear on the level of impact here - does this increase the load on the
>> monitoring machine in direction relation to the number of hosts being
>> monitored? For example, if I was using check_by_ssh to monitor, say,
>> 2000 services spread across 200 hosts, would I experience significant
>> slowdown on my monitoring machine?
>>
>> Cheers for any info,
>>
>> Chris
>
> hi,
>
> ust SNMP! No need to install anything on the target system. SNMP Agents are
> already installed on nearly all systems.
>
> Since everything speaks SNMP you can gather info about hardware, operation
> system AND applications, independent of any OS.
>
> nagios: check_snmp
>
> Greetings,
>
> --
> Dr. Michael Schwartzkopff

This sounds interesting Michael. I searched around a bit, but wasn't
able to find a good introduction to using check_snmp. Could you
suggest an article / tutorial / blog entry somewhere that would be
suitable for a Nagios newbie?

Cheers,
Chris

------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
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