Patch for Plugin "No Output"
Thomas Sluyter
nagios at kilala.nl
Wed Dec 27 15:22:39 CET 2006
Hey guys...
Sorry, I'm a bit late to the party :)
>> Personally, I would prefer not to skip empty lines of plugin
>> output in an effort to find the first line of text - that should
>> be fixed in plugins.
>
> True, but it will save some on support effort on nagios-help
I'd agree with Andreas on this one. I also see no reason not to skip
any blank lines coming in. You're absolutely right that a "proper"
plugin doesn't give blank lines anyway, but why not take into account
that some plugins aren't "perfect"?
>> If so, how would the output from stderr be treated? Would it go
>> into a macro other than $HOST/SERVICEOUTPUT$, or would it be best
>> to tag it onto the end?
>>
> stderr output is probably mostly useful in the gui only. I wouldn't
> want
> to get notified about UNKNOWN states that only has debug output in
> them
> (unless the stderr output is the *only* output).
Agree on this one as well.
> The "(no output returned from plugin)" shouldn't appear if there is
> output on stderr.
And this one as well.
Cheers!
Thomas
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
More information about the Developers
mailing list