Check_by_ssh benchmarks

[jmarquart at planalytics.com]

Karl,
     Could you give an example on how to do multiple ssh checks in a single
invocation?
     I have seen mention of this, but never an example of how to perform this
multi-check.

     I am also very interested in the check_by_ssh plugin - since I perform 99%
checks using it.  I perfer it to some of the other options because I KNOW ssh
will be on all platforms (even NT - gives us easy way to do some NT monitoring
w/out SNMP) and it is secure.

     I had written a passive check submission system for Netsaint which would
dynamically get its list of services for a particular host and then perform
scheduled passive check submissions.  This gave me the multi-check ability w/
lower ssh overhead, but I never rewrote it for Nagios template style configs.


thanks,
-john





Jeff McKeon <jsm at inpro.net> on 11/01/2002 11:09:06 AM




To:   Karl DeBisschop <karl at debisschop.net>
cc:   Sean Knox <sean.knox at sbcglobal.net>, Nagios Users
      <nagios-users at lists.sourceforge.net> (bcc: John J. der Schalla
      Marquart/Planalytics)

Subject:  Re: [Nagios-users] Check_by_ssh benchmarks




Just lurking in the posts...

Is there more in depth documentation anywhere for how/why to use
check_by_ssh?

On Fri, 2002-11-01 at 08:48, Karl DeBisschop wrote:
> On Thu, 2002-10-31 at 17:09, Sean Knox wrote:
> > Currently we use check_by_ssh to check private resources (disk, uptime,
> > etc) on a small group of machines, as opposed to using nrpe. As ssh uses
> > a good deal more resources than nrpe, at what point would unreasonable
> > to use ssh to check machines? For the sake of conversation, say the
> > Nagios monitor is is a PIII 1gig with 256 megs of ram.
>
> I seems like it's not often brought up, but when I wanted a lighter
> alternative, I switched to check_snmp, since each nagios server I use
> only operates within a fairly well firewalled environment.
>
> I switched after about 100 services (10 each on 10 hosts). Not so much
> because of the load per say, but when ssh fails, it does so much less
> cleanly than snmp, in my experience.
>
> Another reason is when a server is really hammered, say by a DOS attack,
> ssh may fail, while snmp still works. I've had this happen, where it
> took 15 minutes or more to get a session on ssh, but we were still able
> to minitor the box. When we finally got in, we shut the port down
> (typing blind because of the DOS) and everything cleared. But
> snmp/netsaint never failed, and gave us the info we needed to quickly do
> what was needed with ssh.
>
> One other thing to keep in mind is that you can run multiple checks on
> one check_by_ssh invocation. That could keep ssh viable longer.
>
> --
> Karl
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: See the NEW Palm
> Tungsten T handheld. Power & Color in a compact size!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users




-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users





-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm 
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en