Re: [Perfparse-devel] nagios-3.0a and plugin output

[Florian G. <fl...@bi...>]

Hi Yves,

yes, this morning i've seen the announcement too. The biggest problem is
the separator i think. For the parser i once had the idea to use the
regex library. With this we could use a well known "parser" that is
fairly easy to configure.

I don't know why the nagios people don't use something like XML for the
plugin output. It would bloat the output a bit, but there would not be
any limitation in characters or whatever any more ...

Flo

Yves Mettier wrote:
> Hi Flo,
> 
> I have problems with the mailing-list (on my side, not sourceforge). So I'm sending this
> to you, not to perfparse-devel@... Feel free to forward it to perfparse-devel@...
> 
> It is about the new nagios-3.0a. I'm reading the "what's new" and I found this :
> 
> http://nagios.cvs.sourceforge.net/*checkout*/nagios/nagios/html/docs/pluginapi.html
> The plugin output spec will be this :
> 
> TEXT OUTPUT | OPTIONAL PERFDATA
> LONG TEXT LINE 1
> LONG TEXT LINE 2
> …
> LONG TEXT LINE N | PERFDATA LINE 2
> PERFDATA LINE 3
> …
> PERFDATA LINE N
> 
> 
> This will affect perfdata parsing in perfparse : the whole parser assumes that there is
> one event per line and one line per event.
> With multi-line events, we have 2 problems.
> 1st problem : don't stop at the end of the line. This should be not very difficult.
> 2nd problem : in a stream of perf data (like a pipe or a socket), how to know the start
> of a new multiline event ? Should the perfparse plugin in nagios echo an ending
> separator ?
> 
> If you have no idea, ask the nagios guys. If they don't have any idea either, maybe it's
> still time for them to change the plugin spec ?
> 
> And don't forget, I've not worked on perfparse for years. Maybe I'm obsolete ? :)
> 
> Yves
> 
>