State triggers

A trigger defines a condition that the member's children must reach before the state
change is propagated. For contextual policies, a state change is propagated to the parent
members of the current context. For a global policy, a state change is propagated to the parent
members of all service models with the same child member.

A policy includes one or more user-defined state triggers. If a policy
contains multiple triggers, each trigger is evaluated before the state data is sent.

Members with custom state providers provide specialized options for defining
state triggers. Service Impact always collects information from events that belong
to most /Status subclasses, and all /Perf classes. You can
customize Resource Manager to gather state data from events belonging to other
classes. For example, you can customize state providers to define state triggers for device
and component members that are monitored through customized classes provided by the
ZenVMware and CiscoUCS ZenPacks.

Note: If you create a policy with a state trigger that
cannot be met, a state change will go undetected and unreported, leaving a service model in
an inaccurate state. For example, you might create a policy and define the state trigger to
be met when two child members go down. However, if the service model that is applied to the
policy contains only a single child member, the trigger will never be met and the state data
will always be shown as UP. Because you applied a policy to the member, the default policy
is also negated.