ovpa performance manager

7/21/2019 ovpa performance manager

1/276

HP OpenViewPerformance Agent

Users Manual

Edition: 13

for UNIX

Manufacturing Part Number: None

J anuary 2003

Copyright 2003 Hew lett -P a ckar d Compan y.


2/276

2

Legal Notices

Warranty.

H ewl ett-Packard makes no war ran ty of any ki nd wi th regar d t o this

man ual, in clu di ng, but not l im ited t o, the im pl i ed w arr ant i es of

merchan tabi l i ty and fi tness for a part icul ar pur pose. Hewl ett-Packar d

shal l not be held li able for er r ors cont ain ed her ein or di r ect, i nd ir ect,special , in cid ent al or consequent i al d amages in conn ecti on wi th th e

fur ni shi ng, per forman ce, or use of t hi s mater ial .

A copy of the specific w a rra nt y term s applica ble to your H ewlett -P a ckard

product ca n be obta ined from your loca l Sa les an d Service Office.

Restricted Rights Legend.

U se, duplicat ion or disclosure by t he U.S. G overn ment is subject to

restr ictions a s set forth in subpa ra gra ph (c)(1)(ii) of th e Right s in

Techn ica l Da ta a nd C omputer S oftw a re cla use in D FARS 252.227-7013.

Hewlet t-Pa ckard Compan y

U nited St a tes of America

Rights for non-DOD U.S. Governm ent D epa rtm ents a nd Agencies are a s

set fort h in FAR 52.227-19(c)(1,2).

Copyright Notices.

Copyright 1983-2003 H ewlett -Pa ckard C ompan y, a ll rights reserved.

No pa rt of this document ma y be copied, reproduced, or t ra nsla ted t o

a nother langua ge without the prior wr itten consent of Hew lett -Pa cka rd

Company. The information contained in this material is subject to

cha nge w ithout notice.

Trademark Notices.Adobe is a tra dema rk of Adobe Syst ems Incorporat ed.

HP -U X Release 11.00 a nd la ter (in both 32 an d 64-bit configura tions) on

a ll HP 9000 comput ers a re Open G roup UNI X 95 bra nded products.

J ava is a U.S . t rademark of Sun Microsystems, Inc.

U NIX is a r egistered tra demark of The Open G roup.

All oth er product na mes a re th e property of their respective tra demar kor service mark holders a nd a re hereby a cknowledged.


3/276

3

Contents

1. This is OpenView Performance Agent

In t roduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Wha t OV Performa nce Agent Does . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

OV P erforma nce Man a ger Ma jor C omponent s. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Scopeux Da ta Collector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Collection P a ra meters File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

D S I L og Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Ext ra ct an d U til i ty P rograms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Da ta Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

ARM Tra nsa ction Tra cking C a pabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Rela ted P erforma nce P roducts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

2. Managing Data Collection

In t roduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Scopeux Da ta Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

S copeux Sta tus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

pa rm F ile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Modifying th e parm File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

pa rm F ile Pa ra meters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

P a ra meter D escriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Applicat ion D efinition P a ra meters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

St opping a nd Rest a rt ing D a ta Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

St opping D a ta Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Rest a rt ing D a ta Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Automa ting S copeux St a rtup a nd S hutd ow n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

E ffective Da ta Collection Man a gement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Cont rolling D isk Spa ce U sed by Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Set tin g Ma intt ime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Set tin g th e Ma ximum L og File Size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Ma na ging Your Resizing P rocesses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Da ta Archiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Ma na ging Your Archiving P rocesses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

H int . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

3. Using the Utility Program


4/276

Contents

4

In t roduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Run ning t he U tility P rogra m . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

U sing I nt era ctive Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Exa mple of Using In tera ctive a nd B a tch Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

U tility Comm a nd L ine Int erfa ce. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

E xa mple of Usin g th e Comma nd Lin e Int erfa ce. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

U tility Sca n R eport Det a ils . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Sca n Report I nforma tion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68In itia l Va lues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

In itia l Pa rm F ile G loba l Informa tion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

In itia l Pa rm F ile Applica t ion D efinitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Ch ronologica l Deta il . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

pa rm F ile G loba l Ch a nge Notifica tions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

pa rm F ile Applica tion Addit ion/D eletion Not ificat ions. . . . . . . . . . . . . . . . . . . . . . 69

S copeux Off-Time Not ificat ions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Applicat ion-S pecific Su mm a ry R eport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Su mm a ries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

P rocess Log Rea son Su mma ry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Sca n S ta rt a nd S top . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Applicat ion Overa ll Summ a ry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Collector C overa ge Sum ma ry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Log File Content s S umm a ry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Log File Em pty S pace Sum ma ry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

4. Utility Commands

In t roduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

a na lyze . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

checkdef . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

deta il . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

logfile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92pa rm file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93


5/276

5

Contents

qu it . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

resize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

sca n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

sh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

sta rt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

st op . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

5. Using the Extract Program

In t roduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Run ning t he Ext ra ct P rogra m . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

U sing I nt era ctive Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

E xtra ct Comma nd Lin e Int erfa ce . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Overview of the E xport Fun ction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

H ow t o Export Da ta . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Sa mple Export Ta sks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

G enera ting a P rinta ble CP U Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

P roducing a Cus tomized Export File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

E xport Da ta Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

E xport Templat e File Synt a x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

E xport F ile Title . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Cr ea ting a Cus tom G ra ph or Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Out put of Exported Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Notes on ASC II a nd D a ta file Forma ts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

H int s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Notes on B ina ry Forma t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

B ina ry H eader R ecord La yout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

B ina ry Title Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

B ina ry I tem Ident ifica tion Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

B ina ry S cale Factor R ecord. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Special S cale Factors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Applicat ion Na me Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Tra nsa ction Na me Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

D isk D evice Na me Record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Logica l Volume Na me Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Netif Na me Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143


6/276

Contents

6

6. Extract Commands

In t roduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

a pplica tion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

clas s. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

configura tion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

cpu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

extra ct . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

filesyst em . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

globa l. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172logfile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

lvolume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

men u . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

mont hly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

net if . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

qu it . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

sh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

sh ift . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

E xa mples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

sta rt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

st op . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

tr a nsa ction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

w eekdays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

w eekly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

yea rly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

7. Performance Alarms


7/276

7

Contents

In t roduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

P rocessing Alar ms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

H ow Alarm s Are P rocessed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

Ala rm G enera tor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Sen ding S NMP Tra ps to Netw ork Node Ma na ger . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Sen ding Messa ges to OpenView Opera tions (OVO) . . . . . . . . . . . . . . . . . . . . . . . . . 210

E xecutin g Local Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

E rrors in P rocessing Ala rms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

Ana lyzing H istorical D a ta for Alar ms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

Exa mples of Alar m Informa tion in Historica l Da ta . . . . . . . . . . . . . . . . . . . . . . . 212

Alar m D efinition Component s. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

Alar m S ynt a x Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

C onvent ions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Comm on Element s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

ALARM St a temen t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221ALE RT St a temen t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

E XEC St a tem ent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

P RIN T St a tem ent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

IF St a temen t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

LOOP St a tem ent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

INC LU D E S ta tem ent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

U SE St a temen t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236VAR S ta tem ent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

ALIAS S ta temen t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

SYMP TOM S ta tem ent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

Alar m D efinition Exa mples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

Cus tomizing Alarm Definit ions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

8. Communicating Across a Firewall

In t roduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

P orts U sed for C ommun ica tion w ith OVPA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

With H TTP P roxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

With out H TTP P roxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

Overview of OVPA Comm unicat ions C onfigura tion . . . . . . . . . . . . . . . . . . . . . . . . . 250

Comm unicat ions defa ult.t xt C onfigura tion File . . . . . . . . . . . . . . . . . . . . . . . . . . 251Configure OVPA Server P ort . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252


8/276

Contents

8

C onfigur e Reporter a nd /or OVPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

Configure Reporter/OVPM w ith H TTP P roxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

Con figur e Report er/OVP M w ith out H TTP P roxy . . . . . . . . . . . . . . . . . . . . . . . . . 253

Oth er Considera tions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254

About Sy stem s w ith M ultiple IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254

default . txt File a nd C onfigurat ion P a ra meters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254

defau lt.t xt C onfigura tion File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254

defau lt.t xt C onfigura tion P a ra meters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

A. Appendix

Viewing M P E L og Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

Viewing a nd P rint ing D ocument s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

View ing D ocum ent s on t he Web. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

Adobe Acroba t F iles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265


9/276

9

Contents


10/276

Contents

10


11/276

11

Tables

Ta ble 1. Typogra phica l Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Ta ble 2. Ch a nges in t his D ocument E dition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

Ta ble 2-1. par m F ile Pa ra met ers U sed by S copeux . . . . . . . . . . . . . . . . . . . . . . . . . . .36

Ta ble 3-1. Comma nd L ine Argum ent s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Ta ble 4-1. U tility Comma nds: S ynt a x an d P a ra meters . . . . . . . . . . . . . . . . . . . . . . . .79

Ta ble 4-2. Defa ult Resizing P a ra met ers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97

Ta ble 5-1. Comma nd L ine Argum ent s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117

Ta ble 6-1. E xtra ct Comma nds: S ynt a x an d P a ra meters . . . . . . . . . . . . . . . . . . . . . .147Ta ble 6-2. E xtra ct Comma nds: E xtra cting a nd E xport ing Da ta . . . . . . . . . . . . . . . .151

Ta ble 8-1. OVPA Defa ult P orts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .250

Ta ble 8-2. OV P erforma nce Agent Document a t ion Set . . . . . . . . . . . . . . . . . . . . . . .263


12/276


13/276

13

Publication History

New edit ions a re complete revisions of th e ma nua l. The publicat ion da tes

for ea ch edition a re listed below. This ma nua l is not prin ted. It is

published in Adobe P orta ble Document File (.pdf) forma t a nd can be

view ed online and printed as needed. No pa rt numbers w ere assigned for

Editions 4 a nd 5 an d w ill not be a ssigned beginning with Edition 9.

E dit ion 1 11/95 B 4967-90001

E dit ion 2 12/97 B 4967-90016

E dit ion 3 10/99 B 4967-90023

E dit ion 4 07/00

E dit ion 5 12/00

E dit ion 6 03/01 B 4967-90040

E dit ion 7 09/01 B 4967-90049

E dit ion 8 09/01 B 4967-90052

E dit ion 9 01/02

E dit ion 10 05/02

E dit ion 11 09/02

E dit ion 12 12/02

E dit ion 13 01/03


14/276

14


15/276

15

Conventions

The following typographical conventions a re used in t his ma nua l .

Table 1 Typographical Conventions

Font Type What the Font Type Represents Example

I t a l i c B ook or ma nual t i t les , and ma n page

names

Refer to the H P OpenVi ew

Oper ati ons Admi ni str ators

Refer ence Volume Iand the opc(1M )

ma npage for more informa tion.

P rovides empha sis You mustfollow th ese steps.

Specif ies a va riable tha t you must

supply when entering a comma nd

At t he prompt t ype:

rlogin your_namew here yousupply your login na me.

P a ra met ers t o a funct ion The oper_namepara meter returns

an integer response.

Bold New t erms The monitor agent observes...

Computer Text a nd it ems on t he comput er

screen

The system replies: Press Enter

C omma nd na mes U se t he grepcommand . ..

Funct ion na mes U se t he opc_connect()function to

connect ...

File a nd directory na mes /opt/OV/bin/OpC/

P rocess na mes C heck t o see if opcmonais running.

Window /dia log box na mes In t he Add Logfilew indow...

Computer

Bold

Text t ha t you must ent er At t he prompt , t ype: ls -l

Keycap K eyboa rd keys P ress Return.

[Button] B ut t ons on t he user in t er fa ce. C lick [Operator].

Click on t he [Apply]but ton.


16/276

16

Menu

Items

A men u na me follow ed by a colon (:)

mean s tha t you select the menu,

then the i tem. When th e i tem is

follow ed by an a rrow (->), a

cascading menu follows.

Select Actions:Utilities->

Reports

Table 1 Typographical Conventions (Continued) (Continued)

Font Type What the Font Type Represents Example


17/276

17

Revisions

The edition number on th e title page of th is document in dicat es the

edition of this document. The print da te on t he t i t le page chan ges each

time th is document is upda ted.

You w ill receive upda ted or n ew editions if you subscribe to t he

a ppropriate product support service. C onta ct your H P sa les

representa tive for deta ils.

Table 2 Changes in this Document Edition

Chapter Changes

The Support an d this

Revisions prefaces

These prefaces w ere a dded.

Cha pter 1, This is

OpenView Performance

Agent, on pa ge 21

Figure 1-1 on page 24wa s upda ted to

incorpora te the chan ged dat a f low for

OVPA4.0 an d beyond. A note w a s a lso

a dded to describe the chan ged

term inology for some of the funct ions.

C hap t er 2, Mana g ing D a t a

Collection, on pa ge 31

Removed the St a rting t he Scopeux

Collector subsection fr om th eScopeux Data Collector section.



In th e section parm Fi le on page 34,

1) incorpora ted t he Sa mple File

section an d informa tion from t he HP

OpenVi ew Per form ance Agent

In sta l la t i on and Conf igurat i on Guide.

2) Removed the D efault Va lues

subsection a nd t a ble 2-2 th ese

values a re described in t he parmfile.



In Ta ble 2-1 on pa ge 36and

Pa ra meter Descr ipt ions on page 37,

a dded the subprocinterval

parameter.


18/276

18



Added th e memoryoption description

a nd more informat ion on the

shortlivedoption in Threshold on

pa g e 39.

C hap t er 2, Mana g ing D a t aCollection, on pa ge 31 In Managing Your ArchivingP rocesses on page 54, removed

references to extractsummary, since

summa ry da ta can only be exported.

Chap ter 5, Us ing the

Extra ct P rogram , on

page 111

Added a note in th e Int roduction on

pag e 112tha t summary da t a can only

be export ed, not extra cted. Any

mention of extracted summary dat a

wa s removed.

Chapter 5, Us ing the

Extra ct P rogram , on

page 111

Added a simila r n ote in Ta ble 5-1 on

pag e 117a bove the summary

arguments .

Cha p ter 6, Ext ract

Commands, on pa ge 145

Added th e sa me note a bout summa ry

da ta in the Intr oduction on pa ge 112.

Cha pter 7, Per forma nce

Alarm s, on page 207

1) In corporat ed the new term inology

th roughout the cha pter.

2) Removed the Communicating

Alar m Notifica tion to OV Performa nce

Agent section.

Cha pter 8, Communicat ing

Across a Firew a ll, on

page 247

This cha pter wa s a dded the f irewa ll

informa tion wa s previously in the

Insta l l Guide.

Table 2 Changes in this Document Edition(Continued)

Chapter Changes


19/276

19

Support

P lease visi t the H P OpenView w eb site at :

http://openview.hp.com/

There you will f ind cont a ct informa tion a nd det a ils a bout th e products,

services, an d support tha t HP OpenView offers.

You ca n go directly t o the H P OpenView eCa re w eb site a t :

http://support.openview.hp.com/

The eC a re support sit e includes:

D ow n loa d a ble docu men t a t ion

Tr ou bles hoot in g in for m a t ion

P a t ches and upda tes

P roblem report in g

Tr a in in g in for ma t ion

S uppor t pr og ra m in for ma t ion
http://openview.hp.com/


20/276

20


21/276

Chapter 1 21

1 This is OpenView PerformanceAgent


22/276

This is OpenView Performance Agent

Introduction

Chapter 122

Introduction

This cha pter is a n int roductory overview of OV Performa nce Agent , its

components, and related products. It discusses:

w h a t OV P er for ma n ce Agen t does

da t a sources

t he scopeuxcollector

t he parmfile

utilityand extractprogra ms

r ela t ed per for m a n ce pr od uct s

NOTE OV Performa nce Agent (OVPA) for U NIX in th is document refers only toversion 4.0 a nd beyond, a nd OV Performa nce Man a ger (OVP M) refers to

version 4.0 and beyond for UN IX a nd Window s plat forms. OVP M 3.x

(Per fView) will conn ect to OV Performa nce Agent 4.0 a nd beyond for a ll

U NIX plat forms except for OVPA for Lin ux. In t he futu re, connectivity t o

OVP M 3.x will be discontinu ed.


23/276


What OV Performance Agent Does

Chapter 1 23

What OV Performance Agent Does

OV Performance Agent collects, summarizes, time stamps, and detects

a larm conditions on current a nd hist orical resource da ta a cross your

syst em. It provides performa nce, resource, an d end-to-end tr a nsa ction

response time measur ements, a nd supports network and da ta base

measurement information.

Da ta collected outside OV Performa nce Agent can be integrat ed using

da ta source integrat ion (DS I) ca pabil it ies. For exa mple, netw ork,

dat a base, a nd your own a ppl icat ion da ta ca n be brought in thr ough DS I

a nd is tr eat ed the sa me a s da ta collected by OV Performan ce Agent. All

DS I da ta is logged, t ime sta mped, a nd can be alar med on. (For deta ils,

see the HP OpenVi ew Per formance Agent for UN I X D ata Sour ce

I ntegrat ion Gui de.)

All of t he da ta collected or received by OV Performa nce Agent can bea na lyzed using spreadsheet progra ms, Hewlett-P a cka rd a na lysis tools

such as OV P erforma nce Mana ger, or third-part y a na lysis products.

The comprehensive da ta logged by OV Performa nce Agent a llow s you to:

C har ac t er iz e t he wor kl oad s in t he env ir onment .

Ana l yz e r es ou r ce us ag e for l oad b a l anci ng.

Per form t rend ana lys is to i sol a te and ident i fy bot t lenecks.

Per form serv ice-level mana gement ba sed on t r a nsac t ion response

time.

P er for m ca pa cit y pla n n in g.

R espon d to a la r m con dit ion s.

S olv e s y st em mana g ement p r ob lems b ef or e t hey a r is e.

OV Performance Agent gathers comprehensive and continuous

informa tion on syst em a ctivity w ithout imposing signif icant overhead on

th e system. It s design offers considera ble opport unit y for customiza tion.

You ca n a ccept default configurat ions or set para meters t o collect da ta

for specific condit ions.


24/276


OV Performance Manager Major Components

Chapter 124


The following d iagra m show s th e rela tionships a mong the ma jor

component s of th e OV Performa nce Agent s yst em.

Figure 1-1 OVPA Major Components

Thi i O Vi P f A t


25/276



Chapter 1 25

NOTE Substa nt ia l changes were made to the interna l data f low of metr ic datain OVPA 4.0 and beyond releases. The codada emon ha s replaced the

function of the perflbdand rep-server da emons, the datasourcesfile

ha s replaced the perflbd.rcf i le, and t he perfalarmdaemon ha s

replaced alarmgen. The OVP M 3.x (P erfView) monitor int erface ha s been

obsoleted; however, the external functionality is otherwise unchanged.

The scopeuxda ta collector is described in Chapter 2, Manag ing

Da ta Collect ion, on pa ge 31.

The codada emon a nd i ts da ta sources a re described lat er in this

cha pter a nd in the H P OpenVi ew Per forman ce Agent I nstall ati on &

Configur at ion Gui de.

The default.txtfile, which is the comm unicat ions configura tion

file used to customize communication parameters for HP OpenViewa pplica tions, is described in Cha pter 8, Communicat ing Across a

Firewa ll, on page 247.

Ala r m g ener a t i on componen t s a r e d es cr ib ed i n C hap t er 7,

Performan ce Alarm s, on page 207.

D a t a s ou r ce in t eg r a t ion (D S I ), inclu d ing dsilogand other DS I

components, a re described in t he H P OpenVi ew Per form ance Agent

for U N I X Dat a Sour ce I ntegrat i on Gui de.

Scopeux Data Collector

The scopeuxda ta collector collects performa nce dat a from the opera ting

system on w hich OV Performan ce Agent resides, summa rizes i t , a nd logs

it in ra w log files, depending on th e types of informa tion desired.

For deta iled informa tion a bout scopeux, see C hap t er 2, Mana g ing D a t aCollection, on pa ge 31.

Collection Parameters File

The ty pe of da ta collected is det ermined by pa ra meters set in th e OV

Performan ce Agent program s a nd in the collection para meters (parm)

file, a n ASC II file used to customize th e collection environm ent. This file



26/276



Chapter 126

cont a ins inst ructions tha t t ell scopeuxto log specific performa nce

mea surement s. The collection para meters file is comm only referred to inth i s manual as the parmfile.

For deta iled informa tion about t he parmfile, see Cha pter 2, Manag ing

Da ta Collect ion, on pa ge 31.

DSI Log Files

DS I log files conta in self-describing da ta th a t is collected outs ide of OVPer forma nce Agent . These log files a re creat ed by OV Performa nce

Agent's DS I program s. DSI processes and the creat ion of DS I log f iles a re

described in deta il in t he H P OpenVi ew Per forman ce Agent for UN IX

Dat a Sour ce I ntegrat ion Gui de.

Extract and Utility Programs

Tw o OV Performa nce Agent pr ogram s, extractand utility, providethe means for ma na ging both scopeuxlog files a nd D SI log files.

The extractprogra m lets you extra ct dat a from ra w or previously

extracted scopeuxlog files a nd w rite it to extra cted log files. The

extra cted log files conta in selected performa nce dat a for specific a na lysis

needs. The extractprogra m a lso lets you export scopeuxand D S I d a t a

for use by spreadsh eet program s a nd other a na lysis products. For more

informa tion about extractand extractcomma nds, see C hap t er 5,

Using the Extract P rogram, on page 111and Cha pter 6, Ext ract

Commands, on page 145.

The utilityprogra m lets you generate reports on raw a nd extra cted

scopeuxlog files, resize ra w scopeuxlog files, a nd check parmfile

synt a x. I t a lso lets you check the synta x in your ala rm definitions f i le

a nd a na lyze a larm conditions in historica l scopeuxa nd DS I log f ile dat a .

For more informat ion a bout utilityand utilitycomm a nds, see

Cha pter 3, Using the Ut i li ty Program, on page 57and C hap t er 4,Ut i li ty Commands, on page 77.

Data Sources

OV P erform a nce Agent uses t he codada emon to provide log file dat a to

the a larm generator a nd t he OV Performa nce Ma na ger an alysis product .

There is one codaserver for a ll dat a sources including scopeuxand D S I

log files.



27/276



Chapter 1 27

You configure da ta sources in t he datasourcesf i le tha t r esides in the

var/opt/OV/conf/perf/ directory. This a llow s y ou to select ively m a kedat a ava i lable for a larm processing an d a na lysis .

NOTE P revious versions of OVPA 3.x an d ea rlier, used a D CE -ba sed fa cility t oserve da ta for an a lysis.

When you inst a ll OV P erforma nce Agent , the datasourcesfile cont a insa single ent ry for a da ta source na med SCOPEtha t te l ls codato read the

scopeuxlog file set. You ca n a dd a dditiona l da ta sources a s needed.

When you sta rt OV Performa nce Agent, t he codada emon reads t he

datasourcesf i le and ma kes th e dat a ava i la ble over da ta comm l inkages

to a na lysis tools for ea ch dat a source it f inds. For m ore informa tion a bout

configuring da ta sources, see the " Configuring D a ta Sources" section in

Cha pter 2 of your HP OpenVi ew Per forman ce Agent I nstall ati on &Configur at ion Gui de.

ARM Transaction Tracking Capabilities

OV Performan ce Agent includes tra nsa ction t ra cking capabil i t ies th a t

a llow informa tion t echn ology (IT) ma na gers t o measu re end-to-end

response time of business a pplica tion tra nsa ctions. To ta ke a dva nt a ge of

this functiona lity, you must h a ve a process running t ha t is instrum entedw ith th e Applicat ion Response Mea surement (ARM) AP I. For more

informa tion, see the H P OpenVi ew Per forman ce Agent & Gl ance Plu s for

UN IX Trackin g Your Transact ionsguide.



28/276


Related Performance Products

Chapter 128


OV P erforma nce Agent is one of several compliment a ry performa nce

products from H ewlett-Pa ckar d. E a ch of these products fulf il ls a

part icular need within the ra nge of resource a nd performa nce

ma na gement. This lets you purcha se as much functionali ty a s you need

a nd a dd products over t ime w ithout risking incompat ibil it ies or

overla pping product ca pabilities.

Related HP performance products include the following:

OV Performance Manager

OV Performan ce Ma na ger provides integra ted performa nce ma na gement

for mult i-vendor distribut ed netw orks. It g ives you a single interfa ce a nd

a common meth od for cent ra lly monitoring, ana lyzing, a nd compar ing

resource mea surement da ta supplied by OV Performa nce Agent r unning

on m an y systems.

GlancePlus

G lan ceP lus (or G lan ce) is a n online dia gnostic tool th a t displays current

performa nce da ta directly to a user termina l or w orkstat ion. I t is

designed to a ssist you in identifying a nd t roubleshooting system

perform a nce problems a s t hey occur.

OV Reporter

OV Reporter creat es web-ba sed reports from da ta of tar geted systems i t

" discovers." D iscovery of a sy stem ca n occur if th e system is runn ing

OpenView a gent a nd suba gent softwa re such a s OV Performa nce Agent.

Reporter ca n a lso genera te reports on syst ems ma na ged by OV

Opera tions. After Reporter ha s run thr ough i ts discovery, i t ga th ers dat a

ba sed on pre-defined an d user-specified lists of metr ics, th en forma ts t he

collected da ta into w eb pa ge reports.OV Operations

OV Opera tions (OVO) a lso displa ys a nd a na lyzes a larm informa tion sent

by OV Performa nce Agent . OVO is a dist ributed client -server softw a re

solution designed t o help system a dministra tors detect , solve, a nd

prevent problems occurring in networks, systems, and applications in

a ny enterprise. OVO is a sca lable an d f lexible solution t ha t ca n be

configured t o meet t he requ irements of an y informa tion technology (IT)orga nizat ion a nd i ts users. .



29/276

p g


Chapter 1 29

For more informa tion a bout a ny of these products, see th e product

documenta tion on th e HP OpenView Ma nua ls web site at :

http://ovweb.external.hp.com/lpe/doc_serv

Select from t he productlist box, select t he releas e

version, a nd click [Search].



30/276

p g


Chapter 130


31/276

Chapter 2 31

2 Managing Data Collection

Managing Data Collection


32/276

Introduction

Chapter 232

Introduction

This cha pter tells you how t o ma na ge the follow ing da ta collection

a ctivit ies tha t a re involved in using OV Performa nce Agent.

using t he scopeuxda ta collector

t h e collect ion pa r a m et er s (parm) f i le and i t s para meters

s t oppin g a n d s t a rt in g da t a collect ion

cont rol ling the amount o f d isk space used by log f il es

a rchiving da ta


S D C ll


33/276


Chapter 2 33


The scopeuxda emon collects a nd sum ma rizes performa nce

mea surements of system-resource uti l iza tion an d logs th e dat a into the

follow ing log files, depending on t he da ta cla sses specified in t he log line

of t he parmfile.

The logglobfile conta ins mea surement s of syst em-w ide, or globa l,

resource uti l iza tion informat ion. G loba l dat a is summ a rized an d

recorded every five minut es.

The logapplf i le cont ains a ggregat e measur ements of processes in

each u ser-defined a pplica tion from t he parmfile. Applica tion da ta is

summa rized every five minutes an d ea ch a pplica tion tha t ha d any

a ctivity during t he f ive minute interva l is recorded.

The logproc file contains measurements of selected interesting

processes. P rocess da ta is summa rized every m inut e. How ever, only

inter esting processes a re recorded. The concept of interest ing

processes is a filter tha t helps minimize the volume of dat a logged

a nd is cont rolled via the parmfile.

The logdevfile conta ins mea surement s of individua l device (such a s

disk and netif) performance. Device data is summarized every five

minutes and da ta f rom each device tha t ha d a ny a ct iv ity during the

five minut e interva l is recorded.

The logtranf ile cont a ins measurements of ARM tra nsa ction da ta .

This dat a is summ a rized every f ive minut es and each tr a nsa ction

tha t ha d a ny a ctivity is recorded. (For more informa tion, see the HP

OpenVi ew Per forman ce Agent & Glan ce Plu s for UN I X Tr acki ng Your

Transactionsguide.)

A sixt h log file, logindx, conta ins informa tion needed to access dat a

in t he oth er log files.

Scopeux Status

The/var/opt/perf/status.scopefile serves a s a sta tu s/error log for

the scopeuxprocess. New informa tion is a ppended t o this file each t ime

the scopeuxcollector is st a rted, stopped, or w hen a wa rning or error is

encount ered. To view th e most recent sta tus a nd error informa tion from

scopeux, use the perfstat -tcomma nd.


parm File


34/276

parm File

Chapter 234

parm File

The parmf i le is a text f i le conta ining th e instructions t ha t t ell scopeuxt o

log specific perform a nce measu rement s. The la test default parmfile is

insta l led with OV P erforma nce Agent in t he/opt/perf/newconfig/

directory (/usr/lpp/perf/newconfig/on IB M AIX) a nd is copied into

t he/var/opt/perf/ directory during installation if one does not

a lready exist from a previous insta l la tion. scopeuxreads the/var/opt/perf/parmf ile when i t sta rts up.

If you ha ven't r un t he product before, you ca n use th e

/var/opt/perf/parmf i le to become fam ilia r w ith t he type of dat a

collected. The default va lues for each pa ra meter a re explained in t he

parmfile.

Once you a re fam ilia r w ith t he OV Performan ce Agent environment, you

should ta i lor the /var/opt/perf/parm f i le to your performa nce dat acollection n eeds.

The parmfile is set up t o collect a n a vera ge a mount of log file da ta . The

ma ximum a mount depends on your system. For more informa tion, see

Disk Spa ce in C ha pter 1 of your H P OpenVi ew Per form ance Agent

In sta l la t ion & Conf igurat ion Gui de. Also see t he descript ion of t he size

para meter in Pa ra meter Descr ipt ions on page 37.

If you alrea dy ha ve experience w ith OV Performa nce Agent a nd a refamil iar w i th the parmf i le pa ra meters, you might wa nt to modify this f i le

before sta rting t he scopeuxcollector.

Modifying the parm File

You can modify th e parmf i le using a ny w ord processor or editor t ha t ca n

sa ve a f i le in ASC II forma t.

When y ou modify the parmfile, or crea te a new one, the follow ing rules

a nd conventions a pply:

Any para meter you speci fy over r ides a def au lt . See the parmfile for

the default va lues.

The or d er i n wh ich t he pa r ame t er s a r e en t er ed in t o t he parmfile is

not importa nt except a s follows:


parm File
http://-/?-http://-/?-


35/276

parm File

Chapter 2 35

If a para meter is entered more tha n once, the las t one entered is

used. The file, user, group, or, and prioritypara meters must

follow th e applications ta tement tha t they define.

Applicat ion para meters should be lis ted in order so that a

process wil l be aggrega ted int o the a pplica tion w hen i t is f irst

matched.

You can use upperca se let ters , lowercase let ters , or a combinat ion of

both for a l l comma nds a nd para meter s ta tements.

You can use b lanks or commas to separa te key words in each

statement .

You ca n com ment t he parmf i le. Any l ine star ting w ith a comment

code (/*) or pound sig n (#) is ig nor ed.

After m odifying t he parmfile, you must issue th e ovpa restart

comm a nd in order for th e cha nges to ta ke effect. This comm a nd ca usesscopeuxt o stop, restart, and rereadthe parmfile.

parm File Parameters

Scopeuxis cont rolled by specific par a meters in t he collection pa ra meters

(parm) file th a t d o the following:

S et m a x im u m a m ou nt of dis k s pa c e for t h e r a w scopeuxlog files.

S pecify w h ich d a t a t y pes a r e log ged .

Speci fy a t t r ibu tes of processes to be logged .

Define types of per formance da ta to be col lected and logged .

Speci fy wha t user-def ina ble sets of appl ica t ions should be monitored .

An a pplica tion ca n be one or m ore progra ms t ha t a re monitored as a

group.

S pecify w hen scopeuxshould perform da ily log file ma int ena nce

a ctivit ies so tha t t hey do not impa ct syst em ava ilabili ty.

You ca n modify these par a meters t o tell scopeuxto log mea surements

tha t ma tch the requirements of your part icular syst em (see Modifying

the parm Fi le on page 34).


parm File


36/276

parm File

Chapter 236

The parmf i le para meters l isted in Ta ble 2-1a re used by scopeux. Some

of th ese para meters a re for specific systems a s indica ted in t he ta ble. Fordetailed descriptions of these parameters, see Parameter Descriptions

on page 37and Applica tion Definition P a ra meters on pa ge 42.

NOTE The items in t he following t a ble tha t a re a pplicable only t o HP -U X a redescribed in deta il in C ha pter 2 of th e HP OpenVi ew Per form ance Agent

In sta l la t ion & Conf igurat ion Guide for H P-UX.

Table 2-1 parm File Parameters Used by Scopeux

Parameter Values or Options

id system ID

log all

global

application [=prm] [=all]

([=prm]onH P -U X only)

process

device=disk,lvm,cpu,filesystem,all

(lvm on HP -U X only)

transaction=correlator,resource

(resourceon HP -U X only)

threshold cpu=percent

disk=rate(not on Linu x or Windows)

memory= nn (values in MB s)

nonew

nokilled

shortlived=[TRUE| FALSE]

wait cpu=percent (H P -U X only)disk=percent (H P -U X only)

mem=percent (H P -U X only)

sem=percent (H P -U X only)

lan=percent (H P -U X only)

application application name

file= file name [, ...]


parm File
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


37/276

parm File

Chapter 2 37

Parameter Descriptions

Follow ing a re descriptions of ea ch of the parmf i le para meters.

ID The system ID value is a st ring of cha ra cters tha t identif ies yoursystem. I f you do not wa nt t o rely on t he defa ult ID a ssigned (th e

systems hostname), and are specifying this string explicitly, then make

sure dif ferent systems h a ve different I D strings so a s not t o confuse

cent ra lized a na lysis. This identifier is ca rried wit h t he log files to

ident ify the syst em on w hich t he da ta wa s collected. You ca n specify a

ma ximum of 40 cha ra cters.

Log The logpar a meter specifies th e dat a ty pes to be collected byscopeux.

logglobalwr ites globa l records to the logglobfile. You must ha ve

globa l dat a r ecords to view a nd a na lyze performa nce da ta on your

syst em. G loba l metrics ar e not a ffected by logging options or va lues

of a pplica tion or process da ta .

user= user login name [, ]

group= groupname [, ]

or

priority= low value-high value(range varies by platform)

size global=nn (values are in MBs)

application=nn

process=nn

device=nn

transaction=nn

mainttime hh:mm (24 hours time)

scopetransactions on

off

subprocinterval= value in seconds(not on H P -U X)

Table2-1 parm File Parameters Used by Scopeux (Continued)

Parameter Values or Options


parm File


38/276

p

Chapter 238

log applicationw il l ca use scopeuxt o write a ctive a pplica tion

records t o the logapplfile. The defau lt beha vior is th a t onlya pplications th a t h ave a ctive processes during an interval a re logged.

log application=allin the parmfile t o force scopeuxt o log a ll

a pplications t o the logapplf i le at every int erval , regar dless of

w hether t he applications ar e active or not.

The application=alloption ma y be desira ble in specific

circumsta nces in relation to t he use of applica tion a larm s. For

example, you ca n a larm on a n a pplication becoming inactive(APP_ALIVE_PROC).

En a bling t his option causes logapplt o fill more quickly since all

a pplicat ions a re logged a t every interval . You ca n use the

utilityprogra ms scanfunction t o monitor t he uti l izat ion of th e

scopeuxlog files.

On HP -UX only, you may speci fylog application=prmto write

active Process Resource Manager (PRM) groups to the logapplfile. S election of th is log specifica tion w ill ca use scopeuxt o

ignore user-defined a pplica tion sets listed in t he parmfile. In

a ddition, a ll a pplicat ion met rics collected w ill reflect a P RM

cont ext a nd be grouped by t he APP_NAME_PRM_GROUPNAMEmetr ic.

NOTE Applica tion logging options do not a ffect globa l or process da ta .

log processw ill w rite informa tion a bout interesting processes t o

the logprocfile. A process ma y become int eresting w hen it is first

crea ted, w hen i t ends, a nd w hen i t exceeds a parm -defined threshold

for a ctivity. P rocess thr eshold logging options ha ve no affect on global

or a pplication dat a .

log device=disk,lvm,cpu,filesystemw i ll request tha t scopeuxlog informa tion a bout individua l disks, logical volumes (HP -U X

only), cpus, a nd /or file syst ems t o the logdevfile. The defa ult

behavior is t ha t only disks, volumes an d interfa ces t ha t h a d I/O

generated th rough them during an int erval ar e logged. Note th a t

netif(logica l LAN device) records a re a lwa ys logged rega rdless of

th e selected log device opt ions.

For exa mple, to request logging of records for individua l disks, logical


parm File


39/276

Chapter 2 39

volumes, cpus, netw ork interfa ces, but notindividua l file systems,

the log para meter in the parmfile would includedevice=disk,lvm,cpu.

When filesystemis specified, a ll mounted loca l file syst ems a re

logged every int erva l, regar dless of a ctivity.

log device=allin the parmfile w ill force scopeuxt o log all

disk, logical volume, cpu, a nd n etw ork interfa ce devices to th e

logdevf i le at every int erval , rega rdless of wh ether t he devices

a re a ctive or not.

En a bling t his option causes logdevt o fill more quickly since a ll

devices a re logged at every int erval . U se the utilityprogra ms

scanfunction to monitor logfile utiliza tion a nd sizing.

log transactionw il l w rite ARM tr a nsa ction records to th e

logtranfile. In order for scopeuxto collect the da ta , a process tha t

is instru ment ed wit h t he Applica tion Response Mea suremen t (ARM)

AP I m ust be runn ing on your system. (For m ore informa tion, see theHP OpenVi ew Per forman ce Agent & Gl ance Plu s for U N I X Tr acki ng

Your Tr ansacti onsguide.)

The defa ult for t he log transactionpara meter is no resourceand

no correlator.

To turn on resource da ta collection (HP -U X only) or correlat or da ta

collection, specify log transaction=resourceor

log transaction=correlator. B oth ca n be logged by specifyinglog transaction=resource, correlator.

All of th e log files a re creat ed au t oma tica lly regar dless of logging options.

If a par ticula r t ype of logging is disa bled, the corresponding log file is not

removed.

If you specify logw ithout options, th e default global a nd process dat a

a re logged.

Threshold The thresholdpar a meter is used to set a ctivity levels tospecify criteria for interest ing processes. It is used only if process logging

is ena bled. Thr esholds only a ffect w ha t processes a re logged a nd do not

a ffect a ny other cla ss of da ta . For example, not logging process da ta a t a l l

w ould not a ffect collection or values of applica tion or globa l da ta .

En ter th e options for thresholds on the sa me para meter l ine (sepa ra ted

by comm a s).


parm File


40/276

Chapter 240

Threshold Options:

cpu Sets the percent a ge of CP U uti l iza tion th a t a processmust exceed to become int eresting a nd be logged.

The va lue percent is a real num ber indica ting

overall CP U use. For exa mple, cpu=7.5indica tes that a

process is logged if it exceeds 7.5 percent of CP U

util iza tion in a 1-minute sa mple.

disk (Not a va ilable on Linux or Window s). Set s th e ra te of

physical d isk I/O per second th a t a process mu st exceedto become interestin g a nd be logged.

The va lue is a rea l num ber. For exam ple, disk=8.0

indicat es tha t a process w ill be logged if it exceeds

eight physical I /Os per second a vera ge in a 1-minu te

sample.

memory Sets the memory th reshold tha t a process must exceed

to become interestin g a nd be logged.

The va lue is in mega byte units a nd is a ccurate t o the

near est 100KB. I f set , t he memory th reshold is

compa red with th e value of the PROC_MEM_VIRTmet ric.

Ea ch process t ha t exceeds t he memory t hreshold w ill

be logged, similarly to the disk a nd C P U process

logging thresholds.

nonew Turn s off logging of new processes if th ey ha ve not

exceeded any th reshold. If not specified, a ll new

processes a re logged. On H P -U X, if shortlivedi s not

specified, then only new processes tha t la sted m ore

th a n one second ar e logged.

nokilled Turn s off logging of exited processes if t hey did not

exceed a ny th reshold. If not specified, a ll killed (exited)

processes a re logged. On H P -U X, if shortlivedi s notspecified, th en only killed processes great er th a n one

second a re logged.

shortlived Turn s on logging of processes th a t ra n for less th a n one

second in a n int erva l. (This often significa nt ly

increases th e num ber of processes logged.) If scopeux

f inds t hreshold shortlivedin the parmfile, it logs

shortlivedprocesses, rega rdless of the cpuor diskthreshold, as long a s the nonewand nokilledoptions


parm File


41/276

Chapter 2 41

a re removed. The defa ult is n o shortlivedprocesses

w ill be logged. (Do n ot specify sh ortlived in t hethresholdpara meter i f you do not wa nt shortlived

processes logged.)

Scopetransactions The scopeuxcollector itself is inst rum ented w ithARM (Applica t ion R esponse Mea suremen t) AP I ca lls to log its own

tra nsa ctions. The scopetransactionsf lag determines wheth er or not

scopeuxtra nsa ctions w ill be logged. The default is

scopetransactions=on; scopeuxw il l log tw o tra nsa ctions,

Scope_Get_Process_Metricsand Scope_Get_Global_Metrics. If you

do not wa nt t hese scopeuxtr a nsa ctions t o be logged, specify

scopetransactions=off. A th ird tra nsa ction, Scope_Log_Headers, will

a lwa ys be logged; it is not a ffected byscopetransactions=off.

For more informa tion a bout ARM, see your HP OpenVi ew Per form ance

Agent & Glance Plus for UN I X Tr ackin g Your Transact i onsguide.

Subprocinterval The subprocintervalpa ra meter, if specified,overrides the defa ult tha t scopeuxuses to sa mple process da ta . Most

cla sses of dat a a re logged once every 5 minut es, the exception being

process da ta , wh ich is logged every 1 minu te. How ever, scopeuxprobes

its inst rum ent a tion every few seconds t o cat ch short-term a ctivities. This

instrum enta tion sam pling interva l is 5 seconds by default .

On some systems w ith t housands of a ctive threa ds or processes, the

subprocintervalshould be ma de longer t o reduce overa ll

scopeuxoverhead. On oth er systems w ith m a ny sh ort-l ived processes tha t y ou

ma y w ish to log, sett ing the subprocintervallower could be cons idered,

a lthough t he effect on scopeuxoverhea d sh ould be monitored closely in

this case. This setting must ta ke va lues th a t a re factors of the process

logging in t erva l of 60 second s. Therefore, va lid sett ings in clude: 1, 2, 3, 4,

5 (th e defa ult if not s pecified or comm ent ed out), 6, 10, 12, 15, 20, an d 30.

Size The sizepar a meter is used to set t he ma ximum size (inmega bytes) of a ny ra w log file. You ca nn ot set th e size to be less tha n one

megabyte.

The scopeuxcollector reads t hese specificat ions w hen it is initia ted. If

a ny of these log files a chieve th eir ma ximum size during collection, th ey

w ill continue to grow until mainttime, wh en th ey w ill be rolled ba ck

a utoma tically. During a roll back, the oldest 25 percent of the dat a is

removed from t he log file. Ra w log files ar e designed to only h old a


parm File


42/276

Chapter 242

ma ximum of one year's worth of da ta i f not l imited by the size

para meter. See Log File Contents S umma ry a nd Log File Em pty Spa ceSummary in Ut i li ty Scan Report D etai ls on page 66.)

If t he size specificat ion in t he parmfile is chan ged, scopeuxdetects i t

during sta rtup. I f th e ma ximum log f i le size is decreased to t he point

w here existing da ta does not f it , a n a utoma tic resize w ill ta ke place at

the next mainttime. I f the exis t ing data f its w i thin the new ma ximum

size specified, no act ion is t a ken.

Any cha nges you ma ke to the ma ximum size of a log f i le ta ke effect a t t hetime s pecified in t he mainttimepa ra meter.

WARNING Partial loss of old data will occur if logs are allowed to collectmore than 365 days of data. Please configure theparmfile sizeentry so that old data is rolled out before any of the log filescontain 365 days of data.

Mainttime Log files a re rolled ba ck if necessa ry by scopeuxonly a t aspecific tim e ea ch day. The defa ult t ime can be cha nged using t he

mainttimepa ra meter. For exa mple, sett ing mainttime=8:30, caus es log

fi le ma intena nce to be done a t 8:30 a m ea ch day.

We suggest s ett ing mainttimeto a t ime when the system is a t i ts lowest

uti l ization.

Application Definition Parameters

The following parameters pertain to application definitions:

application, file, user, group, or, and priority.

OV P erform a nce Agent groups logically relat ed processes togeth er int o

a n a pplicat ion t o log t he combined effect of those processes on comput ing

resources such a s memory and C P U.

NOTE In P RM mode (for H P -U X only), a ctive P RM groups are logged a nd t heuser-defined applica tion sets listed in t he parmfile a re ignored.


parm File


43/276

Chapter 2 43

An a pplicat ion ca n simply be a list of files combined wit h users, groups,

orpriority

ra nges, individua lly or in conjunction w ith ea ch oth er. Ifuser, file, and prioritypara meters a re al l specif ied for the sa me

a pplicat ion, a process must meet t he specifica tions of all th ree, user,

fileand priority,to belong to tha t a pplication.

NOTE Any process on t he sy stem belongs to only one a pplicat ion. N o process iscount ed into tw o or more a pplica tions. P rocesses ar e collected ba sed on

progra m n a me, not progra m pa th. Therefore, tw o processes with thesa me program na me but dif ferent pa th s (f i le system loca tions) w ould be

bucketed into t he sa me a pplication.

Application The a pplica tion na me defines a n a pplica tion or cla ss th a tgroups together m ultiple processes an d reports on t heir combined

activities.

The appl ica t ion nam e is a s t r ing of up to 19 chara cters used to

identify the application.

Appl ica t ion names can be lowercase or uppercase and can conta in

letters, num bers, underscores, an d embedded bla nks. Do not use the

sa me application na me more tha n once in the parmfile.

An equa l sign (=) is optiona l betw een t he a pplica tion keyword a nd

the a pplica tion nam e.

The applicationpar a meter must precede an y combina tion of file,

user, group, or, or prioritypara meters tha t refer to it , w i th a l l

such para meters applying a ga inst the last a pplication workload

definition.

Ea ch para meter can be up to 170 chara cters long includ ing the

carria ge return char a cter, with no continua tion cha ra cters

permitt ed. If your list of files is longer th a n 170 cha ra cters, continuethe l ist on the next l ine a f ter an other file, user, or group

s ta tement .

You can def ine up to 128 a ppl icat ions. OV Performa nce Agent

predefines an a pplica tion na med other. The other application

collects a ll processes not capt ured by applications ta tements in the

parmfile.

For exa mple:


parm File


44/276

Chapter 244

application Prog_Devfile vi,cc,ccom,pc,pascomp,dbx,xdb

application xyzfile xyz*,startxyz

You can ha ve a ma ximum of 1000 file, 300 user, a nd 300 group

specifica tions for a ll a pplica tions combined. The previous exa mple

includes n ine file specifica tions. (xyz* counts a s only one specifica tion

even th ough i t ca n ma tch more th a n one program fi le.)

If a progra m file is included in more tha n one applica tion, it is loggedin the f irst a pplica tion tha t cont a ins it .

The defa ult /var/opt/newconfig/parmfile cont a ins some sa mple

a pplica tions t ha t you can modify. The examplesdirectory a lso

cont a ins other sa mples (in a file called parm_apps) you can copy int o

your parmfile an d modify as needed.

File The filepara meter specifies w hich progra m files belong t o a n

a pplicat ion. All int era ctive or ba ckground executions of these progra msa re included. I t a pplies to the last applicationsta tement issued. An

error is generat ed if no applicationsta tement is found.

The file namecan be an y of the following:

A s in gle U N I X pr og ra m f ile s uch a s vi.

A group of UNIX program f iles (indica ted wi th a wi ld card) such as

xyz*. In this case , any program na me tha t s ta r ts w i th the let ters xyzis included. A file specifica tion w ith w ild ca rds counts a s only one

specifica t ion t owa rd t he ma ximum of 1000 ea ch for a ll files, 300

user, a nd 300 group specifications.

The na me in th e filepar a meter is l imited to 15 cha ra cters in length . An

equa l sign (=) is optiona l between t he f i le keyword a nd t he f i le na me.

You ca n ent er multiple f ile nam es on t he sa me para meter l ine (sepa ra ted

by comma s) or in separa te f i le sta tements. File nam es ca nnot bequa lified by a pa th na me. The file specifica tions a re compar ed to the

specific met ric PROC_PROC_NAME, w hich is set t o a processs argv[0]

value (typically i ts ba se na me).

For exam ple:

application = prog_devfile = vi,vim,gvim,make,gmake,lint*,cc*,gcc,ccom*,cfront

file = cpp*,CC,cpass*,c++*file = xdb*,adb,pxdb*,dbx,xlC,ld,as,gprof,lex,yacc,are,nm,gencat


parm File


45/276

Chapter 2 45

file = javac,java,jre,aCC,ctcom*,awk,gawk

application Mailfile = sendmail,mail*,*mail,elm,xmh

If you do not specify a filepara meter, a l l program s tha t sa t is fy the

oth er para meters qua li fy.

I f you wa nt to bucket J ava or shell progra ms int o dif ferent a pplications,

you ma y wa nt t o look at the /opt/perf/examples/tools/procarg

scr ipt , w hich shows a wa y to s tar t program s wi th a unique argv[0]

value.

NOTE The a sterisk (*) is the only w ild ca rd cha ra cter support ed by the parmfile.

User The userpar a meter specif ies wh ich user login n a mes belong to a n

application.

For exam ple:

application Prog_Dev

file vi,xb,abb,ld,lint

user ted,rebecca,test*

U ser specifica tions th a t include wildcar ds count a s only one specifica tion

towa rd t he ma ximum of 1000 ea ch for a l l file, 300 user, a nd 300 group

specifications.

If you do not specify a userpara meter, a l l program s tha t sa t is fy the


The na me in t he userpara meter is limited to 15 cha ra cters in length.

Group The group par a met er specifies w hich user group na mes belongto an a pplica tion.

For exam ple:

application Prog_Dev_Group2

file vi,xb,abb,ld,lint

user ted,rebecca,test*

group lab, test

If you do not specify a grouppara meter, a l l programs tha t sa t is fy th e



parm File


46/276

Chapter 246

The na me in t he grouppara meter is l imited to 15 cha ra cters in length.

Or Use the orpara meter t o al low more tha n one application definitionto a pply to th e sa me a pplica tion. Within a single applica tion definition, a

process must ma tch a t least one of each cat egory of pa ra meters.

Pa ram eters separa ted by the orpara meter are t reat ed as independent

definitions. If a process ma tches th e conditions for a ny definition, it w ill

belong t o th e applica tion.

For exam ple:

application = Prog_Dev_Group2

user julie

or

user mark

file vi, store, dmp

This defines t he a pplica tion (Prog_Dev_Group2) th a t consists of any

progra ms run by t he user julieplus other progra ms (vi,store,dmp) if

they a re executed by t he user mark.


parm File


47/276

Chapter 2 47

Priority You ca n rest rict processes in an a pplicat ion t o those belongin gto a specified ra nge by specifying va lues in the prioritypa ra meter.

For exam ple:

application = swapping

priority 128-131

P rocesses can ra nge in priority from -511 to 255, depending on w hich

pla tform OV Performan ce Agent is runn ing.

NOTE The parmfile is processed in the order entered a nd t he first m a tch ofprogra m na me a nd/or user login as w ell a s groupand priority(if used)

defines the a pplica tion to w hich a pa rt icula r process belongs.

The priority can be changed over the life of a process. The scheduler

a djusts t he priority of time-sha re processes. You ca n a lso cha nge

priorities programmatically or while executing.

The process priority is sa mpled a t t he end of each one-minut e sa mple

interva l . I f th e process ha s cha nged priority, i t can cha nge a pplica tions.

All activity for a process during t he one-minu te int erva l is assum ed to

ha ve occurred a t t he new priority a nd is a tt r ibuted to the application

tha t m a tches the process a t t he end of each one-minute sa mple interval .

Application Definition Examples The following exam ples s howa pplicat ion definitions.


file vi,dbx,abb,ld,lint

user bill,debbie


file vi,dbx,abb,ld,lint

user julie,mark

group rdlab

application Other_Editors

file ed,sed,awk

application Compilers

file cc,ccom,xlc,c++,fe,sh

application Users

user bruce,ted,julie,anna


parm File


48/276

Chapter 248

The following is a n exa mple of how severa l of th e progra ms w ould be

logged using th e preceding parmfile.

Program User Login Application

vi bill P rog_D ev_G roup1

awk da n Ot her_E dit ors

vi ma rk P rog_D ev_G roup2

cc gene C ompilers

dbx da n ot her


Stopping and Restarting Data Collection


49/276

Chapter 2 49


The scopeuxda emon a nd th e oth er daemon processes th a t a re pa rt of

OV Performa nce Agent a re designed t o run continuously. The only t ime

you should stop them a re wh en a ny of the follow ing occurs:

You are updat ing OV Per formance Agent sof tware to a new re lease.

You a r e ad d ing or d elet i ng t r ans act ions in t he t r ans act ion

configura tion file, ttd.conf. (For more informa tion, see the HP

OpenVi ew Per forman ce Agent & Glan ce Plu s for UN I X Tr acki ng Your

Transactionsguide.)

You are modify ing d is tr ibut ion ra nges or service level object ives

(SLOs) in the transaction configuration file, ttd.conf. (For m ore

informa tion, see the H P OpenVi ew Per form ance Agent & Gl ance Pl us

for UN I X Tr ackin g Your Tran sact ionsguide.)

You are ch a ngin g t he parmf i le and w a nt t he cha nges to ta ke effect .

Cha nges made to the parmfile ta ke effect only w hen scopeuxis

s tar ted .

You a re using t he utilityprogram's resizecomma nd t o resize a

OV Performa nce Agent log file.

You a re sh ut t in g d ow n t h e s yst em .

OV Performa nce Agent provides t he ovpascript t ha t in cludes options forstopping an d resta rt ing th e daemon processes. For a d escription of these

options, see t he ovpama n page.

Stopping Data Collection

The ovpascript's stopoption ensures tha t no dat a is lost w hen scopeux

a nd t he other OV Performa nce Agent da emon processes ar e stopped. To

ma nua lly stop da ta collection, use/opt/perf/bin/ovpa stop.




50/276

Chapter 250

Restarting Data Collection

You have different options for resta rt ing da t a collection a fter t he OVPer forma nce Agent d a emon processes ha ve stopped or configura tion files

ha ve been chan ged and you wa nt t hese cha nges to take effect .

To st a rt scopeuxa nd t he other OV Performa nce Agent processes a f ter

the system h a s been dow n, use/opt/perf/bin/ovpastart.

When you resta rt scopeux, OV P erform a nce Agent cont inues to use the

sa me log files (logglob, logappl, logproc, logdev, logtran, and

logindx) used before stopping t he program . New r ecords a re a ppended

to th e end of the existing files.

For m ore informa tion, see St a rting a nd S topping OV Performa nce

Agent in Cha pter 2 of your H P OpenVi ew Per form ance Agent

In sta l la t ion & Conf igurat ion Gui de.

Automating Scopeux Startup and Shutdown

OV Performan ce Agent's sta rtup can be aut omat ed to ensure tha t

scopeuxi s a lwa ys running whi le the system is opera t ing an d tha t a ny

shut dow n of the system includes a shu tdown of scopeuxw i thout a ny loss

of da ta . The process of sta rt ing OV Perform a nce Agent a nd its pr ocesses

a utoma tically w hen t he system r eboots is cont rolled by t he configurat ion

fi le in th e system sta rtup directory. For more informa tion a bout th is f i le

a nd how t o modify i t , see Sta rting a nd St opping Automa tically in

Cha pter 2 of your HP OpenVi ew Per forman ce Agent I nstall ati on &Configur at ion Gui de.


Effective Data Collection Management


51/276

Chapter 2 51


Efficient a na lysis of performa nce depends on h ow ea sy i t is to a ccess the

performa nce da ta you collect. This section discusses effective st ra tegies

for a ctivit ies such as ma na ging log f i les, da ta a rchiving, and syst em

a na lysis to ma ke the da ta collection process ea sier, more effective, an d

more useful.

Controlling Disk Space Used by Log Files

OV Performa nce Agent provides for a utoma tic ma na gement of the log

files it creat es. You ca n configure th is au toma tic process or use a lterna te

ma nua l processes for specia l purposes. The a ut oma tic log file

ma na gement process works as follow s:

Ea ch log fi le has a conf igured maximum s ize. Defau lt ma ximum s izes

a re provided w hen t he OV Performa nce Agent is f irst insta l led.How ever, you can r econfigure these va lues.

As ea ch log f ile reaches its ma ximum size, a rol l back is per formed

a t mainttimeby the scopeuxda ta collect or. Dur ing th is roll back,

th e oldest 25 percent of th e dat a in th e log file is removed to ma ke

room for new da ta to be added.

Automa tic log f i le ma intena nce is similar, but n ot identica l , for da ta

collected by scopeuxa nd by t he DS I logging process. For more

informa tion on DS I log f ile maint enan ce, see the H P OpenVi ew

Per forman ce Agent for U N I X Data Sour ce I ntegrat ion Gui de.

Setting Mainttime

Normally, scopeuxw ill only perform log file roll ba cks at a specific time

ea ch day. This is to ensure th a t t he opera tion is perform ed at off pea k

hours a nd does not impact norma l system usa ge. The t ime the log f ilesa re exam ined for roll ba ck is set by th e mainttimepara meter in the parm

file.




52/276

Chapter 252

Setting the Maximum Log File Size

Ch oosing a ma ximum log f i le size should be a bala nce betw een h ow muchdisk spa ce is used a nd how m uch historica l dat a is ava ila ble for

immediat e an a lysis. Sm a ller log f ile sizes save disk space, but l imit h ow

much time can be graphed by t ools such a s OV Performa nce Mana ger.

Some wa ys t o reconfigure the scopeuxlog file sizes a re discuss ed below.

Scopeuxlogs different t ypes of da ta int o their own log files. This is to

a llow y ou to choose how m uch disk spa ce you wa nt to dedica te to each

ty pe independent ly. For exam ple, globa l da ta is fairly compa ct, but youwil l of ten wa nt t o go back and gra ph dat a for a month a t a t ime. This

a llow s a good sta tistical base for trending a nd capacity pla nning

exercises.

P rocess dat a can consume more disk space th a n global da ta beca use i t is

possible to ha ve ma ny int eresting processes every minut e. Also, th e

time-value of process da ta is not a s high a s for global da ta . I t ma y be

very importa nt to know deta ils a bout w hich process was run ning today

a nd y esterda y. You might occa siona lly need to know w hich processesw ere running last w eek. However, i t is unlikely t ha t kn ow ing exa ctly

which processes were run last month would be helpful.

A ty pica l user might decide to keep the follow ing da ta online:

Three months of g loba l da t a for t rend ing purposes

O ne we ek of pr oces s d a t a f or t r ou bles hoot i ng

Three months of appl ica t ion da ta for t rend ing and load ba l anc ing

Two mont hs of d ev ice d a t a f or d is k load b a l ancing

You ca n edit t he parmfile to set t he sizepara meters for ea ch different

log file. The sizes are specified in megabytes. For example:

SIZE GLOBAL=10.0 PROCESS=30.0 APPLICATION=20.0 DEVICE=5.0

The num ber of mega byt es required to hold a given num ber of da ys of

dat a can vary by dat a type, system conf igurat ion, a nd system a ct iv ity.

The best wa y to determin e how big to ma ke the log files on your syst em is

to collect da ta for a w eek or so, th en use the utilityprogram's resize

comm a nd t o cha nge your log file size. The resizecomma nd scans t he log

fi les an d determines how much da ta is being logged each day. I t then

convert s from day s to mega bytes for you. This function a lso upda tes t he

parmfile.



M i Y R i i P


53/276

Chapter 2 53

Man

Documents

ovpa performance manager