RE: {bb} vmstat-larrd.pl patch that graphs both RHL and RHEL clients?

[brent.mccrackin@bell.ca]

A solution is to define different versions of redhats in
vmstat-larrd.pl, and have the vmstat-bf.sh script on the different
Redhat systems return the appropriate version of redhat in the output
(you can either change the BBOSTYPE for BB, or hardcode it into the
script).

It's in the OS detection of vmstat-larrd.pl that defines which column is
for which data.

For redhat 3.0AS, I use:

          redhat3 => { cpu_r    => 0,
                       cpu_b    => 1,
                       mem_swpd => 2,
                       mem_free => 3,
                       mem_buff => 4,
                       mem_cach => 5,
                       mem_si   => 6,
                       mem_so   => 7,
                       dsk_bi   => 8,
                       dsk_bo   => 9,
                       cpu_int  => 10,
                       cpu_csw  => 11,
                       cpu_usr  => 12,
                       cpu_sys  => 13,
                       cpu_idl  => 14,
                       cpu_wait => 15,
                     },

---
Brent B McCrackin
UNIX Systems Specialist - Bell Sympatico
Brent.McCrackin@Bell.ca   PH: 416-353-0692
"Serenity through viciousness."
 


-----Original Message-----
From: owner-bb@bb4.com [mailto:owner-bb@bb4.com] On Behalf Of Tom
Georgoulias
Sent: October 26, 2004 5:30 PM
To: bb@bb4.com
Subject: Re: {bb} vmstat-larrd.pl patch that graphs both RHL and RHEL
clients?


Richard Westlake wrote:

> The problem is that vmstat-larrd.pl doesn't know which version of
vmstat
> the values came from. A possible solution would be for vmstat-bf.sh to
> include the column headers in the data it sent to the server. The
> vmsta-larrd.pl could identify what each column did.

Right.  I've been kicking around some ideas to make this work on my RHEL

2.1 systems (which is where this problem occurs), but none are very 
efficient since I'm not much of a programmer nor an expert with 
bb/larrd.  I though about using a wrapper/script that reorders the 
vmstat data before it is logged or having vmstat-larrd.pl check a list 
of hostnames that need the old ordering and using a different alias, but

I dunno.  I don't have that many 2.1 systems to justify a lot of extra 
work getting vmstat graphing up and running when I could use that time 
to work on the 3.0s.  bb-memory.sh might be the extent of the 2.1 
monitoring...

Tom
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, or to subscribe to the bb-digest list
send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
subscribe bb-digest in the BODY of the message.


--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, or to subscribe to the bb-digest list
send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
subscribe bb-digest in the BODY of the message.