You can review the default alerting behaviors from monitoring policies and determine if those actions are in line with your SLAs and business needs.
Choosing whether to monitor an item can be vastly different than monitoring that item and taking action based on a circumstance of that monitor.
Alerts that are self-healed delete themselves, reducing alert noise, and keeping you from wasting time investigating and actioning them. Enabling the self-heal functionality of an alert sets the software to automatically delete an alert if the condition is no longer present. You can also configure the behavior to send out a notification that the alert has been self-healed.
To configure the alert, you need to use the same process as with optimizing monitoring policies. For each failure point or negative condition you identify, ensure that the alert meets one of these criteria:
- It is covered in the current Service Level Agreement (SLA) and is therefore already paid.
- It is an actionable item outside the current SLA and subject to billing.
- It is not currently billable but feeds into project work recommendations.
You can also control your alerting as another means of establishing tiers of service. This is done by configuring well-planned alert schedules.
For more information
- Setting an Alert to Send an Email
- Setting an Alert to Create a Trouble Ticket
- Setting an Alert to Self-heal
- Setting an Alert to Run a Script
- Escalating an Alert