Rule parameters

Image Pattern

8-character
string

N/A

specifies the rule

The Image Pattern field is used by the product to apply
monitoring parameters to monitored systems.

This field accepts wildcard characters. For more information, see Wildcard-characters.

Monitor

Yes

Yes

Heartbeat
Interval

0

30–3600

60

specifies how often, in seconds, the monitored system should
send its heartbeat status and data to the PAS

The value 0 disables sending heartbeat data.

Reply Timeout

 1–300

20

specifies the amount of time, in seconds, the PAS should
wait for a reply from the monitored system for a data request

If time-outs occur in views when you request large amounts
of data, you might want to increase this value.

Background
Sampling
Interval

0

30–3600

60

specifies the interval length, in seconds, of background
sampling

This value specifies the maximum age of data that can be
retrieved.

Background mode sampling ensures that data is always
available when requested.

The value of 0 is allowed only if the Heartbeat Interval is 0;
otherwise, the Background Sampling Interval must range
from 30 to 3600.

Lower values increase overhead on the Linux system
because sampling occurs more frequently than higher
values.

Demand
Sampling
Interval

10–3600

10

specifies the interval length, in seconds, of demand sampling

This value specifies the maximum age of data that can be
retrieved when the system is being actively monitored
(demand mode) or when requests for data are issued during
the Minimum Demand Mode Duration. Demand Sampling
ensures that data is up to date when it is requested.

Lower values increase overhead on the Linux system
because sampling occurs more frequently.

Minimum
Demand Mode
Duration

10–1800
(must be
greater than
or equal to 2×
Demand
Sampling
Interval)

300

specifies the minimum amount of time, in seconds, that
demand sampling stays active

Higher values increase overhead on the Linux system
because demand sampling remains active longer than with
lower values.

History Start

00.00.00–
23.59.00

00.00.00

specifies the time of day to start collecting historical data

History End

00.59.00–
23.59.59

23.59.59

specifies the time of day to stop collecting historical data

Idle Threshold

0 (means
disable idle
testing) or
1 — 100

0

indicates the CPU Util% at which the Linux image is placed
in idle status

When the Linux image is placed in idle status, the history
data is not collected and the bgscollect program will shut
down to reduce CPU overhead. The Linux image needs to
stay below the specified CPU Util% for a continuous 5
minutes before it is placed in idle status.

If the CPU Util% rises above the specified threshold for 2
sample periods (or 20 seconds), the Linux image is taken out
of idle status, and history data collecting and the bgscollect
program are turned back on.

Configuration
History

Yes

No

Yes

indicates whether you want to collect configuration-related
historical data for systems identified by the Image Pattern
field

File System
History

Yes

No

Yes

indicates whether you want to collect file system-related
historical data for systems identified by the Image Pattern
field

Kernel History

Yes

No

Yes

indicates whether you want to collect kernel-related
historical data for systems identified by the Image Pattern
field

IPC History

Yes

No

Yes

indicates whether you want to collect IPC-related historical
data for systems identified by the Image Pattern field

Device History

Yes

No

Yes

indicates whether you want to collect device-related
historical data for systems identified by the Image Pattern
field

Network
History

Yes

No

Yes

indicates whether you want to collect network-related
historical data for systems identified by the Image Pattern
field

Process History 

Yes

No

Yes

indicates whether you want to collect process-related
historical data for systems identified by the Image Pattern
field

User History

Yes

No

Yes

indicates whether you want to collect user-related historical
data for systems identified by the Image Pattern field

Virtual Device
History

Yes

No

No

indicates whether you want to collect virtual device history
for Linux systems identified by the Image Pattern field,
which run on z/VM

Note: Be careful when specifying Yes for this field, because it
is possible that many virtual devices for each Linux image
are identified by the Image Pattern field. Normally, this field
should be No.

VM Real Device
Minimum I/O
Requests

Integer

100

specifies the minimum number of I/O requests that have
been issued by a z/VM system to a real device during a CP
Monitor sampling interval (typically one minute) for the
purpose of collecting statistics on that device for the interval

VM History

Yes

No

Yes

indicates whether you want to collect z/VM system
historical data for systems identified by the Image Pattern
field

VlyLnx Hist

Yes

No

No

indicates whether you want to collect Velocity Linux
historical data for z/VM systems that use the Velocity Linux
data monitor, and that are identified by the Image Pattern
field