OVNPM 1.5.2 - Performance Agent for NonStop Server Monitoring Guide

OVNPM Monitoring Overview 11
1 OVNPM Monitoring Overview
1-1 Goals
OVNPM monitors NonStop server and customers application along with the hardware and system software
components. Installation procedure adds most of the information in the OVNPM monitoring configuration.
Monitoring user specific applications requires more analysis. This guide provides the information to build a
monitoring configuration adapted to the specific need of the production.
1-2 Definitions
An instance is a system resource to be measured. Entity, object and unit are synonyms of instance.
The different type or class of instances is called a domain. The instances belong a domain have the same
characteristics. For example; $system is an instance of domain disk.
A metric is a scalar that contains a specific performance data. A domain is associates with a set of predefined
metrics.
For example disc-space-busy.% is a metric of domain disk. All instances belong domain disk will have
performance data named disc-space-busy.%.
A metric instance is the value of metric for an instance.
For example: disk[$system].free.nb or free.nb[$system] in abbreviation is a metric instance.
If we create a translation table between Measure and OVNPM, we can say that:
• An OVNPM instance is a Measure Entity.
• An OVNPM metric is a Measure Counter.
• An OVNPM Domain is a Measure Entity Type.
Building configuration checks and validates user description in edit files to build binary files used by OVNPM
processes. User description defines the metrics and the instances to be monitored. Metric are defined in the
USERMT file. Instances are defined in the USERCFG file.
1-3 Main monitoring files
OVNPM Monitoring is located in the OVNPM configuration subvolume. The main monitoring configuration files
are DCPRM, USERMT. USERCFG and APPCFG.
The DCPRM file defines the collection parameter like the collect interval.
The USERMT file defines the metrics collection.
The USERCFG file contains the instances to be monitored.
The APPCFG defines the Applications for Application Availability.
Changing the DCPRM file requires a restart of OVNPM Core. Changing USERMT and USERCFG requires a build
configuration and Core restart. Only APPCFG can be modified without restarting OVNPM Core.
OVNPM Monitoring
Overview