Overview of using rules and images


Monitor rules determine how the data is collected from a monitored Linux or z/VM system. You can add, delete, and change rules. MainView for Linux — Servers searches the rules when the PAS discovers a Linux system to be monitored.

When MainView for Linux — Servers is monitoring a Linux system, the monitored system is called an image. These monitored Linux system names can be many characters. MainView for Linux — Servers requires an image name that is up to eight characters in length. Unique image names let you identify remote Linux systems quickly.

You can add, edit, and delete Linux rules by using the ADLRULER view.

 >W1 =ADLRULER==========LNX01CS==*========(00 BROWSE    )====MVLNX====D====4=======
CMD  Image   Monitor HeartBeat   Reply Backgrnd   Demand Min  Demand Idle      History
--- Pattern  (Y/N)   Interval  TimeOut Samp Int Samp Int Mode  Dur   Threshold Start
    $DEFAULT Yes            60      20       60       10         300         0 00:00:00
    *        Yes            60      20       60       10         300         0 00:00:00
    JMW*     Yes            60      20       60       10         300         5 00:00:00

You can add, edit, and delete z/VM rules by using the VMLRULER view 

 W1 =VMLRULER==========SYSLBMC==*========(00 BROWSE   )====MVLNXV===D====3=====
CMD Image   Monitor HeartBeat   Reply Backgrnd   Demand Min Demand VM Rdev History
--- Pattern (Y/N)    Interval TimeOut Samp Int Samp Int   Mode Dur Min I/O Start
    $ZVMDFLT Yes           60      20       60       10        300 100 00:00:00
    *        Yes           60      20       60       10        300 100 00:00:00
    TEST*    Yes           60      20       60       10        300 100 00:00:00

Following table describes the monitor rules that apply to the Linux systems, where the names start with the characters JMW (as shown in Linux ADLRULER view ).

Field

Value

Description

Image Pattern

JMW*

indicates that all of the Linux systems having image names beginning
with the characters JMW will be monitored according to the
parameter values in this rule

Monitor

Yes

indicates these Linux systems are to be monitored

Heartbeat Interval

60

indicates the heartbeat interval is set to 60 seconds

Reply TimeOut

20

indicates the reply time-out is 20 seconds

Backgrnd Samp Int

60

indicates the background sampling interval is set to 60 seconds

Demand Samp Int

10

indicates the demand sampling interval is set to 10 seconds

Min Demand Mode Dur

300

indicates a 300 second minimum demand mode duration

Idle Threshold

5

indicates the Linux image will be placed in idle status when the CPU
Util% falls below 5%

The monitoring of idle Linux images is stopped to reduce CPU
overhead.

History Start

 06:00:00

indicates the time of day to start collecting historical data on the
managed systems

Following table describes the monitor rules that apply to the z/VM systems, where the names start with the characters TEST (as shown in  Description of monitor rule example).

Field

Value

Description

Image Pattern

TEST*

indicates that all of the z/VM systems having image names
beginning with the characters TEST will be monitored according to
the parameter values in this rule

Monitor

 Yes

indicates these z/VM systems are to be monitored

Heartbeat Interval

60

indicates the heartbeat interval is set to 60 seconds

Reply TimeOut

20

indicates the reply time-out is 20 seconds

Backgrnd Samp Int

60

indicates the background sampling interval is set to 60 seconds

Demand Samp Int

10

indicates the demand sampling interval is set to 10 seconds

Min Demand Mode Dur

300

indicates a 300 second minimum demand mode duration

VM Rdev Min I/O

100

indicates 100 is 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

History Start

06:00:00

indicates the time of day to start collecting historical data on the
z/VM managed systems


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*