User Actions

Resync the resource’s alarm state: if the resource’s displayed alarm state was incorrect, perhaps because it is a parent or child of a resource whose alarm state has changed, then this corrects it.

If this action changes the alarm state and this resource’s most severe alarm is service affecting, then resync makes alarm states propagate to any associated services and customers. If the deployed services have the incorrect alarm state, then resync corrects that inaccuracy.

Viewing alarms associated with a service:

• If the service is deployed, and the target resource has open service affecting alarms, all open service affecting alarms for the target resource appear.

• If the service is deployed, but the target resource has only cleared or non-service affecting alarms against it, no alarms appear.

• If the service is deployed, and the target resource does not have open service affecting alarms, but at least one descendent entity of this resource has open service affecting alarms against it, those alarms propagate up to the resource. All open service affecting alarms that propagate up (Resource Propagation is Impacts top level) for the target resource’s descendants appear

• If the target resource does not have service affecting alarms, and neither do any service affecting alarms exist for its descendent entities, no alarms appear.

• If the service is undeployed, no alarms appear.

Viewing alarms associated with a given customer:

• If at least one service associated with the customer has open, service affecting alarms, all open service affecting alarms for all services associated with this customer appear.

• If none of the services associated with this customer have open, service affecting alarms, so alarms appear

User views the services impacted by a particular alarm:

• If the alarmed resource has at least one deployed service that depends on it, all deployed services depending on the alarmed resource appear.

• If the alarmed resource does not have any deployed services that depend on it, no services appear.

Deploying a service whose target resource has service affecting alarms:

• Before deploying, no alarms appear for the service. After deploying, all open, service affecting alarms for the target resource appear.

Undeploying a service whose target resource has service affecting alarms:

• Before undeploying, all open, service affecting alarms for the target resource should appear. After undeploying, no alarms appear.

Editing a deployed service to change the target from one resource to another:

• If the original resource has service affecting alarms but the new one does not, all open service affecting alarms for the original target resource should appear before the edit. After the edit, no alarms appear.

• If the original resource does not have service affecting alarms but the new one does, before editing, no alarms appear. After editing, all open service affecting alarms for the new target resource appear.