Then for procs you may need to present that data is 'ps -ef' format:
UID PID PPID C STIME TTY TIME CMD
root 1 0 0 Oct18 ? 00:00:01 init [5]
root 2 1 0 Oct18 ? 00:00:00 [ksoftirqd/0]
root 3 1 0 Oct18 ? 00:00:00 [events/0]
root 4 1 0 Oct18 ? 00:00:00 [khelper]
root 9 1 0 Oct18 ? 00:00:00 [kthread]
root 19 9 0 Oct18 ? 00:00:08 [kacpid]
root 116 9 0 Oct18 ? 00:00:00 [kblockd/0]
root 156 9 0 Oct18 ? 00:00:00 [pdflush]
Some of the data here doesn't really apply to z/VM, but it should be possible to come up with some sort of value for each column. UID and CMD would probably be the same thing, PID can be a counter, PPID would be 1, STIME would be the logon date or time, TTY is not relevant and TIME would be the CPUTime.
Kern, Thomas wrote:
Actually I do provide data to the PROCS test but I would like to provide it in a more 'STANDARD' format so that we don't have different columns for essentially the same data. What I would really like is to have the user count and proc count plotted properly, so I need to find the 'STANDARD' test parsing.
/Thomas Kern
/XXX-XXX-XXXX
Thu Oct 19 11:43:43 EDT 2006 There are 38 users logged on.
&green VMUTIL Ctime=3 09:28:53 Vtime=0 00:00:01 Ttime=0 00:00:01 IO=9295
&green PERFSVM Ctime=152 02:03:05 Vtime=0 02:03:50 Ttime=0 02:09:20 IO=1594094
&green TCPIP Ctime=12 16:51:29 Vtime=0 00:00:25 Ttime=0 00:00:36 IO=208
&green TCPHSF Ctime=199 21:03:23 Vtime=0 00:15:32 Ttime=0 00:29:51 IO=161
&green VSWCTRL1 Ctime=199 21:19:18 Vtime=0 00:00:11 Ttime=0 00:09:29 IO=188
&green VSWCTRL2 Ctime=199 21:19:18 Vtime=0 00:00:11 Ttime=0 00:13:56 IO=700
-----Original Message-----
From: Rich Smrcina [mailto:user-cf452ff334e0@xymon.invalid] Sent: Thursday, October 19, 2006 11:29 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] format for CPU data?
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: XXX-XXX-XXXX
Ans Service: XXX-XXX-XXXX
user-61add9955ef9@xymon.invalid
Catch the WAVV! http://www.wavv.org
WAVV 2007 - Green Bay, WI - May 18-22, 2007
--
Rich Smrcina
VM Assist, Inc.
Phone: XXX-XXX-XXXX
Ans Service: XXX-XXX-XXXX
user-61add9955ef9@xymon.invalid
Catch the WAVV! http://www.wavv.org
WAVV 2007 - Green Bay, WI - May 18-22, 2007