Message Generation
Event Integration Through Messages
Types of OVO Monitor Available
OVO supports the following types of threshold monitor:
❏ Monitoring With User-defined Programs or Scripts
This method uses a program or script provided by the user that is invoked by the OVO Monitor Agent (opcmona). It collects the monitored value and transmits it to the OVO management server using theopcmon(1|3) C library API or command.
Monitoring Performance Metrics
Performance metrics are collected by way of the embedded performance component. Use the following syntax in theMonitor Program or MIB ID field:
OVPERF\\<data source>\\<object>\\<metric>
Where:
<data source>
Identifies the data source. When collecting metrics from the embedded performance component
<data source> must be set toCODA.
<object>
Identifies the name of the object class to be monitored.
The performance component collects the following object classes:
• Global (object name:GLOBAL)
• CPU (object name:CPU)
• Network interface (object name:NETIF)
• File system (object name:FS)
• Disk (object name:DISK)
<metric>
Identifies the metric to be collected.
The metrics that are currently available for each object class are described in more detail on the following Web page:
http://<management_server>:3443/ITO_DOC/<lang>/
manuals/EmbedPerfAgent_Metrics.htm
Event Integration Through Messages
In this instance,<management_server> is the fully qualified hostname of the management server and<lang> is one of the following:
C for English environments
japanese for Japanese environments
Figure 3-9, Setting Performance Thresholds, shows how to enter the syntax explained above in threshold monitor templates.
Figure 3-9 Setting Performance Thresholds
The performance component constantly collects all platform-generic and typical metrics. The collection interval is by default five (5) minutes and cannot be changed. The data is kept in the data store for up to five (5) weeks. When the database is full after five (5) weeks of data have been collected, the oldest data is rolled out one week at a time and deleted.
See the OVO Administrator’s Reference for more information about troubleshooting the embedded performance component.
❏ External Monitoring
Event Integration Through Messages
❏ SNMP MIB variables
OVO can also monitor SNMP MIB variables. OVO queries SNMP MIB variables on the agents at defined intervals, and checks the output against the threshold values. If the result is above the maximum or below the minimum threshold value, OVO generates a message that is sent to the management server by way of the message agent.
Monitor scripts or programs should be provided by the integrator. The scripts or programs are either assumed to exist on the respective managed nodes (e.g., if they are part of a monitored application) or they can be distributed to the managed nodes by OVO. If it is required to distribute these scripts with OVO, they must be copied into the following directory on the OVO management server:
/var/opt/OV/share/tmp/OpC_appl/<app_name>/<lang>\
/EXECUTABLES/...
From this directory, the scripts can be downloaded automatically, uploaded to the customer’s management server, and distributed to the managed nodes.
Event Integration Through Messages
Integrating Monitors into OVO
A separate monitor is defined for each type of value to be monitored. You can specify message and suppress conditions for the monitor templates in the same way as for other message sources. To display a list of monitors, select the appropriate group in theMessage Source Templates window. To open this window, chooseWindow: Message Source Templates from any of the toplevel windows. You can use this window to add new monitors, as well as modify, copy, and delete monitors.
When you choose to add or modify a monitor, theAdd/Modify Threshold Monitor window is displayed, see Figure 3-10.
Figure 3-10 Add/Modify Threshold Monitor Template Window
Event Integration Through Messages
You can set conditions for a monitor template using theCondition No.
window in the same way as for other message sources. For information about the fields in theCondition No.window for monitors, see the OVO Administrator’s Guide to Online Information.
As in all condition definition windows, an[Instructions...] button enables you to specify help text, instructions, and information about the monitored object and the threshold value, and/or about the configured actions.
Event Integration Through Messages
Sending Values Over the OVO Monitoring API or Command OVO provides an API and a commandopcmon(1|3)to allow applications to send monitoring values from the managed nodes to the OVO
management server. This API/command should be used at the managed nodes for distributed, exception-based management.
The following steps describe the process flow and the interaction between the monitor agent of OVO (opcmona) running on the managed node, and the monitoring script or program provided by the user:
1. OVO checks the intervals defined to invoke the monitoring scripts.
2. OVO calls the specified script or program.
3. As part of the script or program, the actual monitoring values are collected.
4. The script callsopcmon(1|3) (usually once) to pass the value(s) to the monitor agent of OVO.
5. The monitor agent checks the value received fromopcmon(1|3) and returns a value to the caller of the script: zero for successful
execution, one for a failure.
6. The monitor agent reads the value against the predefined thresholds and generates a message if an exception occurs.
7. The return value ofopcmon(1|3) is checked in the script and the processing of the script continues.
OVO checks the exit value from the script and sends an error message if the script returns an exit value other than zero.
Event Integration Through Messages
Figure 3-11 Interaction Between the Monitor Agent and opcmon(1|3)
Monitor Agent
Event Integration Through Messages
MIB Data Collection
Setting up MIB Data Collection is described in detail in the section
“Collecting MIB Data” in the Managing Your Network with HP OpenView Network Node Manager manual.
Event Integration Through Messages