Action Restrictions

Tailored action restrictions for complex and situational action execution in response to alerts, such as time-specific activities, location-based notifications, and critical condition responses.

Each action can have its restrictions.

This makes action lists more flexible as you can limit the execution of the action to:

• Alert Severity
• Time Range (see Time Restriction Scheme)
• Node Importance (execute notification for critical nodes)
• Node Group
• Organization

This allows for defining complex conditions and action lists.

Usage Examples

Run different actions for different times of day or weekday

Define two actions and set different times of the day or different weekdays.

Run actions based on node location

You may want to notify different groups of administrators depending on the node location. NetCrunch creates Atlas views for locations. Also, you can create custom views based on custom fields (be it additional information like department or some organizational unit name) and assign each view to each action.

Restart the server if the alert is critical after some time. Weekend nights only.

You might assign a restart action to a specific alert, but you might also decide to restart servers after a certain amount of time if the issue remains unresolved. This needs limiting action only to nodes being members of the Servers view. As each action has time after it executes since the alert started, you can decide to run restart after some time. Additionally, you might want to repeat these steps only on weekend nights.