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

[Yves M. <yme...@fr...>]

> Sometimes it is better to think about things one time more.
>
> As is see now we can circumvent the problem: We just have to deliver a
> custom process-service-perfdata command that takes the $SERVICEOUTPUT$
> and $LONGSERVICEOUTPUT$ and merges or parses them or adds a custom line
> separator. The easiest way would be if the $SERVICEPERFDATA$ would
> contain all perfdata. Then we would not have to parse them. I'll ask at
> the nagios-devel list.

With such a command, we can use our own separator. This is where we can use "\n||" for
example. No problem :)

Another one is to use the plugin feature of nagios called "Event Broker" if someone
wants to code it :)

> The only drawback would be that we are not able to use the file that
> nagios can generate for parsing..

Yeah ! :)
If I'm not too far from reality, I found the bug !
How do you find the beginning and the end of an event in the file that nagios-3.0
generates ? If the nagios developers can answer that question, we have the solution for
perfparse. If not, I consider that as a bug. What do you think ?
Now, I'm going to sleep :)

$ date
mercredi 7 mars 2007, 23:53:32 (UTC+0100)

Yves

-- 
- Homepage    - http://ymettier.free.fr - http://www.logicacmg.com -
- GPG key     - http://ymettier.free.fr/gpg.txt                    -
- Maitretarot - http://www.nongnu.org/maitretarot/                 -
- C en action - http://www.oreilly.fr/catalogue/2841772896.html    -