message source configuration: monitoring values

Message Source Configuration:Monitoring Values

2 Message Source Configuration:

Monitoring Values[vpo_mgr_src_monitor]

Section Overview

• Monitor Configuration GUI• Monitor Types

– Program– MIB Object– External

• Monitor Conditions– Thresholds– Duration– Reset

• Message Generation Policy• Monitoring Command Interface• Object Monitoring• Distribution of Monitors to Managed Nodes• Threshold Monitor Examples



Monitor Configuration GUI



Monitor Types

• Program

– Script/program distributed and scheduled by VPO

• MIB Object

– Object ID of a MIB instance to be checked

• External

– Script/program scheduled externally



Monitor Conditions

This area layout is unique to Threshold Monitor

Conditions



Message Generation Policy

Message Generation with RESET

Message Generationwithout RESET

ContinuousMessage Generation

time [min]

ResetThreshold

3 min 3 min

3 min 3 min 3 min

3 min 3 min 3 min



Program/MIB Monitoring with Duration Specification

3 min

Reset

Threshold

time [min]1 3 4 5 62

Internal Monitoring (Scripts)

External Monitoring (opcmon)

time [min]1 3 4 5 62

Reset

Threshold

3 min



Monitoring Command Interface

Command Syntax to submit monitored values:

opcmon <parameterlist>

Parameter ValueRequired

monitor_name= name of monitor to deliver value to yes

object= component which caused/detected no or was affected by the problem

-option <var>= additional parameter of any kind no supplying a value; may be given multiple times



Customer Specific Scripts

#!/usr/bin/sh

# set path to prevent trojan horsesPATH=/usr/bin:/opt/OV/bin/OpC

# determine the number of running processesvalue=`ps -e|grep -v grep|wc -l`

# forward the value to the VPO monitor agentopcmon ExampleMonTmpl=$valueexit $?# return status to the monitor agent



Object Monitoring

• Identification of data value

– Monitor name

– Object

• Multiple monitor conditions

– Pattern match for object

– Threshold check for data value

– Duration check

• Set attributes

– Severity, Node, Application, Message Group, Object, Message Text

• Example:

– Control usage of multiple disks with one monitor

/usr

/var

/opt

multi_disk_util



Distributing Threshold Monitors

Select Templatesand Monitors

VPO will identify which nodes require

the update



Example 1 - Monitor & Conditions

90

65

70

85

60

55

time [min]1 3 4 52

Monitor Template disk_util with 3 Conditions

Only one message (the most severe)is generated, but immediately

Condition 1 matches

Cond Thresh Reset

1

2

3

90

70

85

65 55

60

opcmon disk_util=93

Monitor Program performs disk checks and calls

opcmon



Example 2 - MIB Object

200

140

150

180

120

110

time [min]5 15 20 2510

Monitor Template num_procs with 3 Conditions

MIB Object cut and pastedinto template

Cond Thresh Reset

1

2

3

200

150

180

140 110

120

Condition 1threshold exceeded



Example 3 - External Program

90

65

70

85

60

55

time [min]1 3 4 5 62

Monitor Template with 3 Conditions:

Only one message from Condition 3is generated after timer has terminated

Condition 3 Timer:

Condition 2 Timer:

Cond Thresh Reset

1

2

3

90

70

85

65 55

60

Duration

-

3 mins

4 mins

opcmon disk_util=67

External Program called by cron every minute:

* * * * * /home/velma/disk_check.sh



Example 4 - opcmon using -object

Condition Object Pattern Threshold1 ^/$ 902 ^/$ 803 ^/$ 754 ^/var$ 955 ^/var$ 856 ^/var$ 757 ^/disk1$ 958 ^/disk1$ 859 ^/disk1$ 75

opcmon disk_util=91 -object / matches condition ??opcmon disk_util=77 -object /disk1 matches condition ?? opcmon disk_util=75 -object /var matches condition ??opcmon disk_util=91 -object /usr matches condition ??



Example 5 - opcmon -object -option

opcmon disk_util=91 -object / -option device=/dev/dsk/c0t6d0

message source configuration: monitoring values

Documents