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).

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:rsmrcina at wi.rr.com] Sent: Wednesday, November 15, 2006 1:56 PM To: hobbit at hswn.dk 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: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com

Catch the WAVV! http://www.wavv.org WAVV 2007 - Green Bay, WI - May 18-22, 2007