In the previous section, we saw how many operating system data collection tools are available to provide information about the performance of the managment environment. Several of the tools are already integrated within OVO via the Application Bank. Others could add functionality within OVO. The following example demonstrates use of the OVO monitor template to collect file system metrics using the external command
opcmon to feed the metric data into. The metric value is compared with the threshold and if the threshold is violated a message is created and delivered to the message browser using the
opcmsg command. Refer to the man pages for the complete command syntax.
The opcmon (API) could be incorporated into scripts or integrated within a scheduled actions template. In the example opcmon is executed from the command line. A brief explanation is provided with each step in the following external monitor program example.
Create a monitor template. Refer to section 16.1.4.1 for the overall process to create, customize, assign, and distribute a monitor template.
Leave the Monitor Program or MIB field blank and change the monitor type from Program to External. Add the monitor name. See Figure 16-12.
Add a new threshold condition as shown in Figure 16-13.
Assign and distribute the template to the managed node.
Use the
opcmon command to trigger a performance event that exceeds the template threshold.
/opt/OV/bin/OpC/opcmon montest=90 object /var option device=/dev/vg00/lvol6
View the results in the message browser.