Re: [Perfparse-users] swap performance data showing up as critical state

[Weytens, R. J. <Ran...@AC...>]

Flo,

Are you saying that the output from the Nagios plugin check_swap is not
in the correct format?


<lnx00:~>$ ~nagios/libexec/check_swap -w 50% -c 25%
SWAP OK - 100% free (973 MB out of 980 MB) |swap=3D973MB;490;245;0;980


Thanks,

Randy Weytens


-----Original Message-----
From: Florian Gleixner [mailto:fl...@bi...]=20
Sent: Wednesday, June 21, 2006 3:19 PM
To: Weytens, Randy J.
Cc: per...@li...
Subject: Re: [Perfparse-users] swap performance data showing up as
critical state


Perfparse only gets the performance data. There are guidelines how these

have to look like:

http://nagiosplug.sourceforge.net/developer-guidelines.html#AEN143

In this case it is also worth reading:
http://nagiosplug.sourceforge.net/developer-guidelines.html#THRESHOLDFOR
MAT

unfortunately while pp was developed the definition of the ranges was=20
not yet complete. We have to include the @ and the guidelines in the=20
determination what is outside a range and what is inside. Multiple=20
ranges are not yet defined.

I personally would prefer a more flexile format for performance data.=20
Maybe a simplified xml format or similar. But this has to be developed=20
by others :-)

Flo


Weytens, Randy J. schrieb:
> The subject pretty much says it all.  Perfparse is always showing swap
> as critical, for everything, even when it is not.  I'm not sure how it
> determines the state, and why it would not use the state returned from
> the plugin.
>=20
> Randy Weytens
>=20
>=20
> _______________________________________________
> Perfparse-users mailing list
> Per...@li...
> https://lists.sourceforge.net/lists/listinfo/perfparse-users