But then you get a column for VM-CPU, a column for MVS-CPU, a column for W2K-CPU, a column for WinXP-CPU, a column for Solaris-CPU (not really a linux), a column for AIX-CPU (another not really a linux) and finally a column for CPU (for the real linux systems). Now repeat that for DISK, MSGS, PROCS, FILES, MEMORY, PORTS, BACKUP, etc.
You need a very WIDE screen when management wants it ALL on one page.
/Thomas Kern /301-903-2211
-----Original Message----- From: Charles Goyard [mailto:cgoyard at cvf.fr] Sent: Thursday, October 19, 2006 10:55 AM To: hobbit at hswn.dk Subject: Re: [hobbit] format for CPU data?
Hi,
Mike wrote:
I'm writing agents for other systems than linux and I want the data to be graphed just like the linux data is graphed. Can someone please post the expected format for CPU data so the data will be graphed?
The real good way is to implement the native format of your OS on the server-side of hobbit. If it's a Unix-POSIX-like system, it's roughly a matter of cut and paste of the existing code. I did it for Sco's Unix (bleh!), and it made me understand hobbit internals much.
Regards,
-- Charles Goyard - cgoyard at cvf.fr - (+33) 1 45 38 01 31
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
Not at all.
Here I have something like 5 or 6 Unix flavors, all are reporting under the same cpu/disk/procs/whatever.
From the osname reported by the client, hobbitd can hand the data to the appropriate backend (it even has different backends for a few Linux flavor, such as RHEL3 or Debian). The idea it to put together a native backend for your OS.
Kern, Thomas a écrit :
But then you get a column for VM-CPU, a column for MVS-CPU, a column for W2K-CPU, a column for WinXP-CPU, a column for Solaris-CPU (not really a linux), a column for AIX-CPU (another not really a linux) and finally a column for CPU (for the real linux systems). Now repeat that for DISK, MSGS, PROCS, FILES, MEMORY, PORTS, BACKUP, etc.
You need a very WIDE screen when management wants it ALL on one page.
-- Charles Goyard - cgoyard at cvf.fr - (+33) 1 45 38 01 31
There is a native backend for z/VM, it was integrated into Hobbit some time ago. It appears that Thomas wants to consolidate the CPU, Users and Procs into one column. I took a different approach, that since there was already a procs column reported by other clients, that the information that translated best to procs on z/VM was reported there.
The concept of users and procs is somewhat blurred on z/VM, so I didn't differentiate the two. Some shops (it appears that his is one of them) have a clear demarkation of who a user is, based on their userid.
Charles Goyard wrote:
Not at all.
Here I have something like 5 or 6 Unix flavors, all are reporting under the same cpu/disk/procs/whatever.
From the osname reported by the client, hobbitd can hand the data to the appropriate backend (it even has different backends for a few Linux flavor, such as RHEL3 or Debian). The idea it to put together a native backend for your OS.
Kern, Thomas a écrit :
But then you get a column for VM-CPU, a column for MVS-CPU, a column for W2K-CPU, a column for WinXP-CPU, a column for Solaris-CPU (not really a linux), a column for AIX-CPU (another not really a linux) and finally a column for CPU (for the real linux systems). Now repeat that for DISK, MSGS, PROCS, FILES, MEMORY, PORTS, BACKUP, etc.
You need a very WIDE screen when management wants it ALL on one page.
-- 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
participants (3)
-
cgoyard＠cvf.fr
-
rsmrcina＠wi.rr.com
-
Thomas.Kern＠hq.doe.gov