On 12/22/06, Bob Miller <[EMAIL PROTECTED]> wrote:
I'd like to recommend gkrellm as the *best* way to understand a Linux
system's workload.  It continuously plots the last 60 seconds'
utilization of CPU (per-CPU and/or aggregate), disk (per-disk,

Gkrellm is indeed a good tool if you're actively profiling and/or you
have it running on a machine you are constantly sitting near. I used
to use it all the time. I've found it more effective in the long term
though to figure out what you consider to be "bad" thresholds and have
one of the various monitoring tools watch those thresholds locally and
then raise the alarm via email, sms, whatever when those thresholds
are hit. That way you don't have the polling traffic (which can be
substantial if you have a lot of machines and/or datapoints to watch)
and you get an alert when something goes sideways, even if it happens
while you're away from your desk and corrects itself before you get
back.

--
-Regards-

-Quentin Hartman-
_______________________________________________
EUGLUG mailing list
[email protected]
http://www.euglug.org/mailman/listinfo/euglug

Reply via email to