Store in Embedded
Performance Component: You can enter a data source, object and
metric of your own invention here. The policy will create them in
CODA and will store the data from the policy's source each polling
interval. The data in the metric can be used to create graphs that
the operator can create in response to a message. See Add
operator-initiated commands to a policy rule for more
information
Select CODA if you want to measure performance
metrics. CODA is an especially useful data source because it is
available on all agent operating systems. You can define one policy
that measures performance metrics on all your managed nodes. For
each source, you will need to indicate the following
parameters:
- Data Source: for example, CODA
- Object: for example, GLOBAL
- Metric: for example, GBL_CPU_TOTAL_UTIL
You can view a of list of available metrics in the HP
Performance Agent Dictionary of Operating System Performance
Metrics which is available at http://ovweb.external.hp.com/lpe/doc_serv/. (Select
the product Performance Agent, the required version, OS, and
language.)
If you do not know the parameters that you need, you can click
the Browse on node... button to view the parameters
available on a specific node.
NOTE:
The embedded performance component, Coda, must have the Physical
Disk Object available to report the disk metrics. To get the disk
metrics reported on a node, you must run
diskperf -Y to
enable the counters under the Physical Disk Object. The following
metrics are affected:
GBL_NUM_DISK GBL_DISK_PHYS_IO
GBL_DISK_PHYS_IO_RATE GBL_DISK_PHYS_BYTE GBL_DISK_PHYS_BYTE_RATE
BYDSK_ID BYDSK_DEVNAME |
BYDSK_PHYS_IO BYDSK_PHYS_IO_RATE BYDSK_PHYS_BYTE
BYDSK_PHYS_BYTE_RATE BYDSK_PHYS_READ BYDSK_PHYS_READ_RATE
BYDSK_PHYS_READ_BYTE |
BYDSK_PHYS_READ_BYTE_RATE BYDSK_PHYS_WRITE
BYDSK_PHYS_WRITE_RATE BYDSK_PHYS_WRITE_BYTE
BYDSK_PHYS_WRITE_BYTE_RATE BYDSK_BUSY_TIME BYDSK_UTIL |
Select MIB if you want
to use entries in a Management Information Base as the source for a
threshold alarm. You must type the MIB ID, as well as the node
where the ID is produced.
NOTE:
The default community public
is used for SNMP queries.
If the MIB object resides in another community, the community name
must be set on the managed
node where the MIB monitoring takes place. The syntax for
defining the community name is: SNMP_COMMUNITY
<community>
. On DCE agents, you can set the community
name in the opcinfo file; on HTTPS agents, you can set the
parameter locally in the eaagt
namespace on the node.
(See ovconfchg.)