Thoughts about a custom plugin

[Andy Shellam]

Hi,

NRPE could do this job, sure you could write a custom plugin, but there 
are 2 possible alternatives already there (albeit they might be overhead 
for what you're trying to do, unless you want to monitor the  services 
on the dual-homed machine with Nagios as well.)

You could run NRPE on each target, and on the dual-homed machine, then 
Nagios would request the plugin to be executed on the targets and send 
the request via NRPE to the dual-homed machine, which would in turn 
request the plugin to be run on the appropriate host.  I do a similar 
thing to ping a router that cannot be reached from my Nagios machine, 
but can from one of the servers being monitored by Nagios.

e.g. Nagios -- check_nrpe -- asks dual-homed to check disk space on 
target1 -- check_nrpe -- dual-homed asks target1 to check diskspace -- 
check_disk -- DISK: OK

I have a feeling, however, that NCSA might be a more appropriate tool 
for this task, but I have no experience of it.  From what I understand, 
I believe it would be possible to run NRPE on the targets, use NCSA on 
the dual-homed host to execute the plugins on the targets via NRPE and 
submit the results to Nagios.

Hope this gives you some food for thought!

Regards,

Andy

dave stern - e-mail.pluribus.unum wrote:
> This can be done without NRPE. We have a cluster on a private net.
> The head node is visible from nagios so I wrote a plugin that lives
> on the head node (The dual homed machine, in your case). On the nagios
> side, a plugin ssh'es to the head node, runs the script which talks to
> hosts on the private net and returns the output/status.
>
> On Sun, Jul 20, 2008 at 11:17 AM, stan <stanb at panix.com> wrote:
>   
>> On Sun, Jul 20, 2008 at 10:46:39AM -0400, Paulus, Jake wrote:
>>     
>>> You should really look into NRPE (Nagios Remote Plugin Execution)
>>> http://nagios.sourceforge.net/docs/3_0/addons.html#nrpe
>>>
>>> There are alternate versions of NRPE that run on Windows, etc. if you
>>> must do that. Check out NagiosExchange.org for those.
>>>
>>> You should find that you can use normal plugins you already use
>>> elsewhere with NRPE to do what you need.
>>>
>>>       
>> I'm not certain this is intended for exactly the application I have. perhaps
>> it is, and I am misunderstanding it. let me clarify my application a bit
>> with an ASCI diagram:
>>
>>   ------------           -------------        --------------
>>   |          |          |            |        |            |
>>   | NAGIOS   |----------| DUAL       |        | TARGET     |
>>   | Host     |          | HOMED      |---+----|            |
>>   |          |          | Machine    |   |    |            |
>>   |          |          |            |   |    |            |
>>   ------------           -------------   |    --------------
>>                                          |
>>                                          |    --------------
>>                                          |    |            |
>>                                          |    | TARGET     |
>>                                          +----|            |
>>                                          |    |            |
>>                                          |    |            |
>>                                          |    --------------
>>                                          ~
>>
>> The Nagios host can get to the dual homed machine, and I can use all the
>> standard plugins to get status from it. What I want to do is get status from
>> the TARGETS.
>>
>> Are you suggesting using NAPE running on the dual homed machines? And somehow
>> using this to query the targets? The web page you pointed out makes me
>> believe that NAPE is intended to allow me to execute checks on a reachable
>> machine, by using local scripts there, rather than having the NAGIOS machine
>> use the more traditional check_* plugins.
>>
>> Am I confused?
>> --
>> One of the main causes of the fall of the roman empire was that, lacking
>> zero, they had no way to indicate successful termination of their C
>> programs.
>>
>> -------------------------------------------------------------------------
>> 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=/
>> _______________________________________________
>> 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
>>
>>     
>
> -------------------------------------------------------------------------
> 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=/
> _______________________________________________
> 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
>   

-------------------------------------------------------------------------
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=/
_______________________________________________
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