Collection Services support for system monitoring

Collection Services now fully supports the concept of system monitoring. Collection Services can be configured to collect system monitor performance metrics, even without configuring and running a IBM® Navigator for i System Monitor.

Configuring Collection Services system monitoring

System monitoring can be enabled in Collection Services several different ways:
  • Creating and starting a IBM Navigator for i System Monitor
  • Using the Configure Performance Collection (CFGPFRCOL) command
  • Using the Change Collection Services Attributes (QypsChgColSrvAttributes) API

When system monitoring is enabled, the Collection Services collector collects configured categories at the specified system monitoring collection interval. All other categories are collected at their normal collection interval.

Note: A IBM Navigator for i System Monitor might override other system monitoring configuration settings that were made by using the CFGPFRCOL command or QypsChgColSrvAttributes API if the monitor requires data to be collected more frequently.

System monitor database files and collections

The set of QAPMSMxxx database files provide system monitor metrics. Monitored metrics are most often calculated as percentages (ex: CPU utilization) or rates (ex: bytes per second). Monitored metrics are also system level metrics, which means data for multiple entities (jobs, disk, …) is grouped, summarized, or averaged.

System monitor database files can be created for any Collection Services collection, even when system monitoring is not enabled.
  • Use the “Create Standard Summary Data (CRTPFRSUM)” parameter on the Configure Performance Collection (CFGPFRCOL) command. This parameter enables the creation of the system monitor files for the system created standard database file collection.
  • Use the “Create Standard Summary Data (CRTPFRSUM)” parameter on the Create Performance Data (CRTPFRDTA) command. This parameter enables the creation of system monitor files for the user created standard database file collection.
Note: When the system monitor database files for a standard database file collection are created, the interval in the QAPMSMxxx files is the same as specified for CRTPFRDTA to be consistent with the rest of the collection.
When Collection Services system monitoring is enabled, a second create performance data job (CRTPFRDTA2) is submitted to create a second Collection Services file based collection that consists of the system monitor database files. This job (CRTPFRDTA2) operates similar to the existing CRTPFRDTA job and uses the configured collection library. The following are the differences between the system monitor CRTPFRDTA2 job and the CRTPFRDTA job:
  • The interval for the CRTPFRDTA2 job is fixed at 15 seconds. The interval for the CRTPFRDTA job is the configured default collection interval (usually 15 minutes).
  • The CRTPFRDTA2 job only creates database files for the categories that are identified as a system monitor category in the configuration. The CRTPFRDTA job generates database files for all categories that are defined in the configured collection profile.
  • The collection name for CRTPFRDTA2 is based on the *MGTCOL name except that the name begins with “R” rather than “Q”.
In the collection that is created by the CRTPFRDTA2 job, both the system monitoring database files and the normal collection database files are created for the collection categories that are selected for system monitoring for the following reasons:
  • Metrics that are defined in the system monitor files require that CRTPFRDTA process the categories that contain the data. If the source data for a metric category is not processed, nothing can be output for the metric.
  • To support drill down capabilities within Performance Data Investigator.

Data retention for system monitor collections

The data retention and expiration for system monitor database file collections works similar to the data retention and expiration for standard Collection Services file based collections. The only differences are that a separate retention period is configured and used for system monitor collections and the expiration of system monitor collections is not affected by the PM Agent data reduction status.