NSCA and long output

[Marc Powell]

On May 28, 2008, at 11:54 AM, Aaron Mills wrote:

> What I'm really trying to get is multi-line output. Nagios/NRPE  
> supports
> this (v3.x) e.g.:
>
> TEXT OUTPUT | OPTIONAL PERFDATA
> LONG TEXT LINE 1
> LONG TEXT LINE 2
>
> This works for NRPE, but not with NSCA, since NSCA can only take a
> single line as an argument.
>
> What I'm trying to achieve is sending process monitoring data back
> passively like so:
>
> PROCS OK:
> Proc1: 3 processes running
> Proc2: 1 process running
> Proc3: 1 process running
>
> Any ideas?


AFAIK, you're in uncharted territory. Based on what I've seen, the  
longer output support has only really been applied to active commands  
but the documentation does indicate that support for passive results  
is there. NSCA hasn't been updated to handle multi-line output as  
you've seen nor have I seen any talk that it's coming soon. I also  
expect that you might see problems using the normal mechanism of  
writing the check results to the external command _pipe_ due to OS  
size limitations there (~1K typically). I expect that would only be a  
problem with large data returns (nagios internally supports $OUTPUT$ +  
$LONGOUTPUT$ of about ~4K). At this point I think you're going to have  
to roll your own check result return mechanism that either writes  
appropriately sized commands to the external pipe or larger ones to a  
file and uses the external command PROCESS_FILE to reap the results.

--
Marc

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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