Logical node details view

The logical node details view enables you to create and edit customizable members that capture specific Resource Manager event states.

Logical nodes allow you to represent multiple resources or services; they rarely relate to events from a single member. For resources that Resource Manager monitors, logical nodes enable you to capture event states from arbitrary classes. Logical nodes might be external events from third-party monitoring products that are not monitored by Resource Manager.

For example, a bookstore website uses a third-party financial service to process credit cards. Resource Manager has no access to that third-party environment, but the monitoring systems forward events to Resource Manager. Their member names are prefixed with FincCC (that is, FincCC-AppSvr01, FincCC-AppSvr02, FincCC-OraDB01, and so on). To match events from that system and relate them to the "bookstore" service, you create a logical node that matches any event with a resource name that includes the prefix FincCC.

A logical node can be a child of a service model member, but no other type.

Logical node details view


The Criteria rules allow you to define event triggers and associate the triggers with availability and performance states.

Availability state

In Events for this node in this event class, specify the event class or subclass that is associated with the trigger.

The following examples illustrate how to specify event classes.

Only the /Status class.
Only the Web subclass of /Status
The /Status class and all of its subclasses.

In will result in these availability states, map event severity levels to availability states.

Performance State

The fields and options in this area differ only in that the mapping of event severity levels to performance states uses different states.