6. DATA SOURCES › 6.2 Processing Considerations › 6.2.2 Data Volume - VM Monitor

6.2.2 Data Volume - VM Monitor

The VM Monitor is a high-volume data source.  While the
number of records is dependent on system size, the absolute
volume is determined by the Monitor domains that are enabled.
Sample data (domains 0, 3, 4, 5, and 6) is produced once per
interval (usually once per minute).  Event data is produced
when a discrete event occurs.

Domain 0 and domain 3 records that represent system-wide
measurements are combined into a single observation in the
CA MICS Database. For a 24-hour period with a one-minute
interval, this results in 1440 observations.  The domain 0
and domain 3 records that represent CPU specific measurements
and the domain 5 records are combined into a single
observation per CPU in the CA MICS Database. For a 24-hour
period with a one-minute interval, this results in 1440
observations per CPU.

Domain 3 records that represent shared system information are
kept in the CA MICS Database at the rate of one per saved
system per monitor interval.  Domain 3 records that provide
CP-owned volume data are kept at the rate of one observation
per CP volume per interval.  Block paging data is kept at the
rate of one observation per interval.  Channel path
contention data is kept at the rate of one observation per
CHPID per interval, which can be as much as 256 observations
per interval.

Domain 4 sample records are produced at the rate of two per
logged-on virtual machine per interval.  If an average of 100
users log on over a 24-hour period, this results in 288,000
observations in the CA MICS Database. This class of records
builds the VMX User Activity Sample Data File (VMXVXU) and
VMX User Transaction Sample Data File (VMXVXT), which are the
largest interval files in the VMX Information Area.

Domain 6 records are produced at the rate of one per
subchannel per interval, and an additional one per cached
DASD per interval.  The number of observations depends on how
many devices are monitored in the I/O domain.

Event records (domains 2, 4, and 7), when enabled, produce
two to four times as much volume as interval records for the
same period.  This data is normally collected for short
periods when detailed system analysis is required.  Other
event records, which report configuration changes, produce
very small amounts of data.