[Nagiosplug-devel] RFC: Nagios 3 and Embedded Perl Plugins

[Thomas Guyot-Sionnest]

> -----Original Message-----
> From: nagiosplug-devel-bounces at lists.sourceforge.net 
> [mailto:nagiosplug-devel-bounces at lists.sourceforge.net] On 
> Behalf Of Andreas Ericsson
> Sent: January 9, 2007 8:39
> To: Nagios Plugin Development Mailing List
> Subject: Re: [Nagiosplug-devel] RFC: Nagios 3 and Embedded 
> Perl Plugins
> 
> Thomas Guyot-Sionnest wrote:
> > Actually I think now it's getting interesting. If done 
> properly, this
> > could be a nice way of doing distributed active checking.
> > 
> > Using the same system Stéphane described Nagios could have open
> > connections to remote execution hosts that runs the checks 
> and read back
> > results. Different services properties would determine if 
> the service
> > can be run directly on the host (if Nagios has an open 
> connection to it)
> > or if it has to be remote. Check execution load could be run on
> > dedicated servers, or even be spread out across monitored hosts.
> > 
> 
> 
> Yes, but a distributed static mesh redundancy thing is pretty 
> different 
> from an NRPE-daemon with an option to keep connections alive. A nice 
> example of where "think big" doesn't work, but "think bigger" does.
> 
> I'm working on a module that does just that, but it requires 
> a fullblown 
> Nagios installation on each of the poller nodes and the decision of 
> which host is monitored by what system is determined by hostgroups 
> instead of through some automagic solution that could possibly (and 
> would probably) get things wrong from time to time.

Sounds great. Just to make things clear my idea wasn't a NRPE replacement but rather an addition. For ex. you could have something like this (Lets't call my thing NRCE, Nag[...] Command Executor):

+---------+
| Nagios  |
+---------+
    |
    |
+---------+
| NRCE    |
+---------+
    |
    |
+---------+
| NRPE    |
+---------+

The NRCE host could be a monitored host as well and remote network checks could be either coming from Nagios itself or from another NRCE host.

It wouldn't require a full blown Nagios but your solution has the advantage of cascading checks. With that and by reducing the logic involved in the main Nagios process your solution is much more scalable.

Do you plan on having the "child" Nagios processes receive their config automatically from the main process? That would simplify a lot the setup.

Thomas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3076 bytes
Desc: not available
URL: <https://www.monitoring-plugins.org/archive/devel/attachments/20070109/40ef647e/attachment.bin>