Eliminating the reporting of MEMSWAP

list Anatoli Bogajewski
Wed, 21 Sep 2005 14:02:03 +0200
Message-Id: <user-e377b96ac341@xymon.invalid>

Ok, thanks. 
But what about the vmstat data collected by hobbitclient and sent to server? Irrelevant on hp-ux at the moment? Why it is collected? =)

Greetings

user-1fecd3eafd52@xymon.invalid schrieb am 21.09.2005 13:40:25:

Hi,

they are both external scripts run from the hobbit-client. You could 
find 
them at deadcat.

regards
Lars


----- Original Message ----- From: <user-4d3800b5a33a@xymon.invalid>
To: <user-ae9b8668bcde@xymon.invalid>
Sent: Wednesday, September 21, 2005 1:30 PM
Subject: [hobbit] Antwort: Re: [hobbit] Eliminating the reporting of

MEMSWAP

Dear Lars,

i am wondering about the vmstat & iostat columns for hpux systems.

Those

both are present in your hobbit pages
http://leopg9.no-ip.org/hobbit/bb.html but i am missing them in my 
test
implementation. However, the vmstat data is collected by client and
reported to my server. Which screws you turned to get this running?

Would

you give me a hint?

Many Thanks!


user-1fecd3eafd52@xymon.invalid schrieb am 21.09.2005 08:57:47:

Hi

If you change to
MEMSWAP 100 101

it will not go red

Regards
Lars
----- Original Message ----- >> From: "Rich Smrcina" <user-cf452ff334e0@xymon.invalid>
To: <user-ae9b8668bcde@xymon.invalid>
Sent: Wednesday, September 21, 2005 7:06 AM
Subject: [hobbit] Eliminating the reporting of MEMSWAP

I have a situation where the MEMSWAP value for a SLES9 machine 
running
the Hobbit client is reporting the high 90% range.  Specifying:

HOST=gonotessmtp
 MEMSWAP 95 99

still causes a red condition to be reported.  Until this can be
resolved, is there a way to turn off the MEMSWAP report?

Thanks.
-- >> > Rich Smrcina
VM Assist, Inc.
Main: (262)392-2026
Cell: (XXX)XXX-XXXX
Ans Service:  (360)715-2467
user-61add9955ef9@xymon.invalid

Catch the WAVV!  http://www.wavv.org
WAVV 2006 - Chattanooga, TN - April 7-11, 2006