Checking CPU Utilization

[Mark Reis]

I'm doing this for Solaris and Linux. I understand that load is a true
indication of the stress. The reason I want to monitor %CPU is that I work
for a Computer Science Department at a University and we have multiple
machines that are for processing jobs. Most of the jobs that students run
are CPU intensive, but they don't drive the load up very high. So what I
would like to do is provide a web page that students can go and see at a
glace which compute servers are idle.

Thanks to Jason Martin for suggesting iostat, which does exactly what I
want. The problem I had with top is that on our Solaris boxes, it takes a
while for the %CPU fields to populate and sometimes they are blank.

I appreciate all of the help from the list.

-Mark

-----Original Message-----
From: jeff vier [mailto:jeff.vier at tradingtechnologies.com] 
Sent: Monday, January 19, 2004 4:12 PM
To: Mark Reis
Cc: nagios-users
Subject: Re: [Nagios-users] Checking CPU Utilization

On Mon, 2004-01-19 at 14:49, Mark Reis wrote:
> I'm looking for a light weight command which will return current cpu
> percentages and then quits like uptime, but with percentages and not load?
> What I'd ideally like to do is to combine this tool with NRPE and mrtg so
I
> can graph the %CPU usage on compute servers our students use to run jobs.
> 
> Does anyone have a suggestion for a tool?

What OS?

Unix doesn't really work that way - Load is the correct measurement of
CPU activity in Unix.

For Windows, apan does good work checking load. ('nt-load' service)



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null