I agree on your assessment.

I would like to see things like......who is hitting the disk (i/o
mapping).....cpu utilization trend analysis (not just who is hitting it,
now!),   communications bottlenecks  (is the nic saturated?

Yes I realize there is a hodge-podge of various tools from various places
that do various bits and pieces of some of this and that............



"Allen S. Rout" <asr AT UFL DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
04/29/2008 09:37 AM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
Re: [ADSM-L] DB Bufferpool sizing - continued






>> On Tue, 29 Apr 2008 09:12:57 -0400, Zoltan Forray/AC/VCU
<zforray AT VCU DOT EDU> said:

> All disk are internal.  We needed quantity vs speed (more for the LZ
than
> DB) so we didn't have a choice (Dell) other than the big SATA drives
> (biggest SAS was around 300GB).

> Unfortunately (please correct me if I am wrong) there doesn't seem to be
> any really good, all inclusive system monitoring tools for Linux (I miss
> Omegamon!)


What do you think of nmon?  What aspects of linuxen do you want to
monitor, yet can't?


However much I like linux, (and it's "lots") I think that omegamon for
mainframes is probably going to be more detailed than products you'll
find for linux.  Omegamon's had decades of practice, with a single
stable platform, and big business motivations to get detailed.  The
data is increasingly _there_ for linux, but /proc is not a convenient
or pleasant interface.


- Allen S. Rout