perfparse-users

[Perfparse-users] Check Swap status value

[Christophe <cgo...@gm...>]

Hello,
 config: Nagios 2.0b4 and perfparse 0.105.6.
 I have a problem with the value reported by check_swap, in nagios the valu=
e
is OK and it is reported as critical in perfparse.
I have this problem only with chek_swap plugin.
 SWAP OK: 100% free (2102 MB out of 2102 MB) |swap=3D2101MB;420;210;0;2101
1131966271 lblnagios1 Swap SWAP OK: 100% free (2102 MB out of 2102 MB) OK
swap=3D2101MB;420;210;0;2101
  Perfparse result --> Swap swap  2005-11-14 11:59:31  2101  MB  CRITICAL

--
Christophe

Re: [Perfparse-users] Check Swap status value

[Yves <yme...@pe...>]

Hi Christophe,

This is a bug in the conception of Perfparse : it considers that low valu=
es are OK and
high values are critical.
This bug has already been fixed in the parser.
We need to fix it in the GUI too.
If you need a fix soon, the best is probably to reverse the plugin value =
and have "%
used" instead of "% free".

Yves

> Hello,
>  config: Nagios 2.0b4 and perfparse 0.105.6.
>  I have a problem with the value reported by check_swap, in nagios the =
value
> is OK and it is reported as critical in perfparse.
> I have this problem only with chek_swap plugin.
>  SWAP OK: 100% free (2102 MB out of 2102 MB) |swap=3D2101MB;420;210;0;2=
101
> 1131966271 lblnagios1 Swap SWAP OK: 100% free (2102 MB out of 2102 MB) =
OK
> swap=3D2101MB;420;210;0;2101
>   Perfparse result --> Swap swap  2005-11-14 11:59:31  2101  MB  CRITIC=
AL
>
> --
> Christophe
>


--=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/                          -

Re: [Perfparse-users] Check Swap status value

[J P. <pa...@gm...>]

On 11/14/05, Yves <yme...@pe...> wrote:
> This bug has already been fixed in the parser.

How?

Re: [Perfparse-users] Check Swap status value

[Yves <yme...@pe...>]

> On 11/14/05, Yves <yme...@pe...> wrote:
>> This bug has already been fixed in the parser.
>
> How?

It uses the extended data from the plugins : warning and critical zones i=
nstead of
limits between zones.

Except if you are a developer and want to help on the database storage, t=
his should not
be very helpful.
Ask me for more info on per...@li... if you can =
do something
for perfparse ! :)

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/                          -