How policies work
The following example outlines the Service Impact policy information work-flow using a monitored switch as a device member.
- A switch that is monitored by Resource Manager goes down.
- Resource Manager generates an event about the switch.
- Service Impact reads the switch-down event and changes the actual state of the device member that represents the switch.
- For each service context in which the device member participates, Service Impact evaluates the state triggers to identify that member's derived state within the service context.
- Service Impact propagates state data according to the context or global policies that are defined for the parent members of the device member.
- If the device member's state causes a change in the derived state for the top-level member in the member's service context, Service Impact generates a service event and sends it to Resource Manager. (You can customize service event notifications.)
- Service Impact performs a RCA and generates confidence rankings of how the switch-down event affects each service model to which the switch belongs.