If you search google, using "z/VM performance capacity planning", you should see
"velocitysoftware.com/whylps.html" as the first link. This is the description of
instrumentation requirements. I've also offered zMON (dirt cheap, by the way) as a real
time monitor that will produce records for MICS or MXG. The benefit to this is that you
have a monitor with a standard one minute granularity, but you write out the records that
MICS or MXG want every 15 minutes. This reduces your disk requirements by usually more
than factor of 100, and satisfies most basic needs for performance data AND capacity
planning data (as well as operational alerts).
Thomas Kern wrote:
Because as someone pointed out before (Barton, I think), for performance
monitoring, you want more event data and for capacity planning you need
appropriate sample data. I think PerfTK could deal with more data than it
needs for online real-time performance monitoring, while another process
selectively collects from the same source a subset of that data for capac
ity
planning using that other z/OS product.
/Tom Kern
On Tue, 18 Mar 2008 11:01:07 -0400, Jim Bohnsack <[EMAIL PROTECTED]> wro
te:
Unless the objective is to have a program that will collect some of the
records for one reporting function and another instance of the program
collecting a different selection of the monitor records for a different
reporting function, why not just limit the amount of records written to
the monitor segment in the first place?
Jim
