ASAP OpenView Smart Plug-In Manual

Configuring the ASAP OpenView Adapter
HP NonStop ASAP OpenView Smart Plug-In Manual—529444-001
4-9
Service Population Scheme
Chicago\CPU\03 are added to the Services tree view. The same strategy applies to
all other entities and objects monitored by ASAP:
The advantage of populating all services is that it allows you to drill down to the
NonStop Kernel object level to retrieve state information. This approach also
greatly simplifies OpenView message filtering. As you drill down, you see only
messages that pertain to the selected object. However, a cost is associated with
this approach in terms of the number of services and objects added to OpenView.
If you use ASAP to monitor a large network of systems and objects, you might not
want to populate all services and objects.
•
Populate Container Services
This option specifies that only services that contain subservices are added to the
OpenView Services tree view. You see a tree view containing true categories of
services, but the actual objects that make up those services are not present. The
number of levels in the resulting OpenView hierarchy can vary from service to
service. For example, if ASAP is monitoring CPUs on \Chicago, the Adapter adds
the services Chicago and Chicago\CPU to OpenView. If ASAP is also monitoring
the Spooler $SPLS on \Chicago, the Adapter also adds the services
Chicago\Spooler and Chicago\Spooler\$SPLS because the $SPLS Spooler
contains a set of subservices such as its supervisor, collector, and so on. In this
VST024.vsd