From: Yves <yme...@pe...> - 2006-06-22 12:27:14
|
HI, I move this thread to perfparse-devel@... I consider the subject as closed for users. This is now a developer's sub= ject :) > Hi, > > According to > http://nagiosplug.sourceforge.net/developer-guidelines.html#THRESHOLDFO= RMAT > it should return: > > SWAP OK - 100% free (973 MB out of 980 MB) |swap=3D973MB;@490;@245;0;98= 0 > and not > SWAP OK - 100% free (973 MB out of 980 MB) |swap=3D973MB;490;245;0;980 Ooops, I missed that one. > does pp already parse the "@"? Yes, as far as I remember (I coded it myself, but 2 years ago), the parse= r conforms to http://nagiosplug.sourceforge.net/developer-guidelines.html#THRESHOLDFORM= AT. However, the parsed data are dropped because the database schema does not= understand a lot of http://nagiosplug.sourceforge.net/developer-guidelines.html#THRESH= OLDFORMAT. In fact, the parser reads 973, MB, 490, 245, 0, 980 and sends those data = to the mysql plugin. That plugin stores 973MB as the value, 490 as the threshold betwe= en OK and warnin, and 245 as the threshold between warning and critical. If you want to check, you can hack the print module and you will see what= perfparse parses. Yves --=20 - Homepage - http://ymettier.free.fr - http://www.logicacmg.com - - GPG key - http://ymettier.free.fr/gpg.txt - - Maitretarot - http://www.nongnu.org/maitretarot/ - - Perfparse - http://www.perfparse.org/ - |