[hobbit] CPU info

[Kevin.Hanrahan at novainfo.com]

Henrik,
 This requires me to copy sar-grapher.cgi to the same place you have
larrd-grapher.cgi. Where would that be on Hobbit?

-----Original Message-----
From: John Turner [mailto:jturner at ns.wcpss.net] 
Sent: Saturday, April 30, 2005 3:20 PM
To: hobbit at hswn.dk
Subject: Re: [hobbit] CPU info



On Apr 30, 2005, at 11:41 AM, Henrik Stoerner wrote:

> On Sat, Apr 30, 2005 at 11:32:05AM -0400, kevin hanrahan wrote:
>>  Does anyone know how to get the info (and graphs hopefully) on CPU 
>> utilization for unix machines? Currently, we see CPU load which is 
>> different, and I believe a true measure of how hard the box is 
>> working but I have people who feel the need to also see cpu 
>> utilization....any ideas?
>
> How about enabling the vmstat module in the LARRD client ? That gives 
> you cpu utilization split into system-time, user-time and idle-time as 
> percentages. Just tell them that the green part is unused, and the 
> red/yellow parts are when it is busy.
>
>
> Henrik
>

We use the bb-sar extension from www.deadcat.net on many of our hosts. 
I haven't tried to get it working with Hobbit yet, but it does CPU 
utilization in percentages.

John


To unsubscribe from the hobbit list, send an e-mail to
hobbit-unsubscribe at hswn.dk


Note:  The information contained in this email and in any attachments is
intended only for the person or entity to which it is addressed and may
contain confidential and/or privileged material.  Any review,
retransmission, dissemination or other use of, or taking of any action in
reliance upon, this information by persons or entities other than the
intended recipient is prohibited.  The recipient should check this email and
any attachments for the presence of viruses.  Sender accepts no liability
for any damages caused by any virus transmitted by this email. If you have
received this email in error, please notify us immediately by replying to
the message and delete the email from your computer.  This e-mail is and any
response to it will be unencrypted and, therefore, potentially unsecure.
Thank you.  NOVA Information Systems, Inc.