Xymon Mailing List Archive search

CPU Monitoring

6 messages in this thread

list James Wade · Wed, 15 Nov 2006 13:47:16 -0600 ·
Hello All,

 
I'm looking for best practices with regard to CPU monitoring.

I have systems where the CPU is overloaded, and we really

can't do much about it. What do most folks do with the CPU

monitor with regard to showing RED all the time?

 
Thanks.James
list Rich Smrcina · Wed, 15 Nov 2006 13:55:33 -0600 ·
Set the thresholds high enough where they aren't red anymore.  If you have no control over CPU Utilization on those systems there isn't much more that you can do.
quoted from James Wade

James Wade wrote:
Hello All,

 
I’m looking for best practices with regard to CPU monitoring.

I have systems where the CPU is overloaded, and we really

can’t do much about it. What do most folks do with the CPU

monitor with regard to showing RED all the time?

 
Thanks…James

 
-- 

Rich Smrcina
VM Assist, Inc.
Phone: XXX-XXX-XXXX
Ans Service:  XXX-XXX-XXXX
user-61add9955ef9@xymon.invalid

Catch the WAVV!  http://www.wavv.org
WAVV 2007 - Green Bay, WI - May 18-22, 2007
list Pnixon · Wed, 15 Nov 2006 14:58:12 -0500 ·
While others may disagree, I think that Hobbit should be configured for what
you expect to be normal situations and notify you when it goes above those
situations.
 
If you think ServerA's Load can be 2.00 without an issue, go ahead and
configure it that way.  Yellow - 2.00, Red 2.25 (or whatever you consider
appropriate).
 
--Pat
quoted from James Wade


From: James Wade [mailto:user-659655b2ea05@xymon.invalid] 
Sent: Wednesday, November 15, 2006 2:47 PM
To: user-ae9b8668bcde@xymon.invalid
Subject: [hobbit] CPU Monitoring


Hello All,

 
I'm looking for best practices with regard to CPU monitoring.

I have systems where the CPU is overloaded, and we really

can't do much about it. What do most folks do with the CPU

monitor with regard to showing RED all the time?

 
Thanks...James
list James Wade · Wed, 15 Nov 2006 14:23:04 -0600 ·
Hi Rich,

But eventually you are going to want to improve resources.
At least when management asks for new equipment requests, etc...

You would not be able to track it if you disable the red.

Is there a way to keep the background green, but maybe use
another color to keep track of improvement areas.
Just brainstorming a bit.

Thanks...James
quoted from Rich Smrcina

-----Original Message-----
From: Rich Smrcina [mailto:user-cf452ff334e0@xymon.invalid] Sent: Wednesday, November 15, 2006 1:56 PM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] CPU Monitoring

Set the thresholds high enough where they aren't red anymore.  If you have no control over CPU Utilization on those systems there isn't much more that you can do.

James Wade wrote:
Hello All,

 
I'm looking for best practices with regard to CPU monitoring.

I have systems where the CPU is overloaded, and we really

can't do much about it. What do most folks do with the CPU

monitor with regard to showing RED all the time?

 
Thanks.James

 
-- 
Rich Smrcina
VM Assist, Inc.
Phone: XXX-XXX-XXXX
Ans Service:  XXX-XXX-XXXX
user-61add9955ef9@xymon.invalid

Catch the WAVV!  http://www.wavv.org
WAVV 2007 - Green Bay, WI - May 18-22, 2007
list Rich Smrcina · Wed, 15 Nov 2006 14:27:04 -0600 ·
If by track you mean the graph, it is still populated with the high load values, so that can be used to show management that over time this machine has had excessive utilization.

You may be able to find a thresshold where the machine bounces between green, yellow and red during the day.  Be aware though that each time it goes between colors that a histlog entry is made (which may require more disk space, depending upon how often it bounces and how long you let it bounce).
quoted from James Wade

James Wade wrote:
Hi Rich,

But eventually you are going to want to improve resources.
At least when management asks for new equipment requests, etc...

You would not be able to track it if you disable the red.

Is there a way to keep the background green, but maybe use
another color to keep track of improvement areas.
Just brainstorming a bit.

Thanks...James

-----Original Message-----
From: Rich Smrcina [mailto:user-cf452ff334e0@xymon.invalid] Sent: Wednesday, November 15, 2006 1:56 PM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] CPU Monitoring

Set the thresholds high enough where they aren't red anymore.  If you have no control over CPU Utilization on those systems there isn't much more that you can do.

James Wade wrote:
Hello All,

 
I'm looking for best practices with regard to CPU monitoring.

I have systems where the CPU is overloaded, and we really

can't do much about it. What do most folks do with the CPU

monitor with regard to showing RED all the time?

 
Thanks.James

 
-- 
Rich Smrcina
VM Assist, Inc.
Phone: XXX-XXX-XXXX
Ans Service:  XXX-XXX-XXXX
user-61add9955ef9@xymon.invalid

Catch the WAVV!  http://www.wavv.org
WAVV 2007 - Green Bay, WI - May 18-22, 2007
list Ralph Mitchell · Wed, 15 Nov 2006 21:40:09 -0600 ·
quoted from James Wade
On 11/15/06, James Wade <user-659655b2ea05@xymon.invalid> wrote:
I'm looking for best practices with regard to CPU monitoring.

I have systems where the CPU is overloaded, and we really

can't do much about it. What do most folks do with the CPU

monitor with regard to showing RED all the time?
I don't have a different suggestion to those already made, but I do
have a related question for everybody:  would there be any value in
having a CPU minimum load setting that would trigger a red flag??  I'm
thinking that in a normally heavily loaded system, a sudden drop in
cpu activity could indicate a problem.  Or is there already a way to
invert the condition??  I don't have a set of manual pages handy to
check right now...

Ralph Mitchell