Typical Alert Handling Scenarios

When an alert is raised, it appears in the Zone Alerts window for all users whose open Operations Sentinel zone includes the system to which the alert applies. If the object to which the alert applies is not a part of your open zone, the alert appears in the Other Alerts window. The following three scenarios describe typical actions you can take when handling alerts.

Scenario 1. Mark an Alert Seen

Sometimes you might want to mark an alert as seen in your Alerts window. When you mark the alert seen, it no longer contributes to the overall alert state for your instance of Operations Sentinel Console, but it does not signify you are taking responsibility for it. This is a convenience that allows you to concentrate on other tasks while still being notified by a visible change in the overall alert state when a new alert arrives. Meanwhile, other operators still see the alert and know that it needs attention.

Scenario 2. Acknowledge an Alert

In contrast, acknowledging an alert signifies you are taking responsibility for it. The alert is marked as acknowledged in all instances of Operations Sentinel Console, and it no longer contributes to the overall alert severity. However, someone else could still view the alert to see whether the alert you acknowledged was being handled.

Scenario 3. Clear an Alert

Finally, you can clear an alert. An alert that is cleared is removed from the memory of Operations Sentinel, and disappears from all instances of Operations Sentinel Console. Do not clear an alert until the condition that caused it has been resolved.

Decide which scenario best fits your alert handling needs at the time. Additionally you can take other steps when handling alerts, such as

Note: Alerts can also be acknowledged or cleared automatically by external alert actions defined in the active alert policy and by automated responses initiated by AMS.