Create an alert management rule
Create an alert management rule to track alerts and resolve them by determining the required response, for example, to open an incident or launch remediation action.
Before you begin
To enable remediation with a subflow, you can use a subflow that is available with the base system, or you can create your own subflow. For details, see Create a custom subflow for alerts.
Role required: evt_mgmt_admin, flow_designer
About this task
Use alert management rules to track and resolve alerts.
To automate alert responses with an easier interface, you can also create a respond automation in Service Operations Workspace. For more information, see Create Respond automation.
While working in the alert management rule designer, you can work in multiple sections without losing information in any section.
- Alert management rules that are not configured to perform any action are skipped and the rule is automatically set to inactive.
- If an alert is bound to a CI by a user action (such as an alert management rule) and the CI is in the Maintenance state, you must manually bind the CI to the alert and mark it with the In Maintenance status.
- Locate other alert management rules that have relevance to the selected alert.
- Determine when the execution of the rule takes place.
Alert management rules do not necessarily complete in the order in which they are invoked.
- Automatically generate and link incidents, tasks, or knowledge articles to alerts.
- Automatically apply a remediation workflow or enable users to manually run remediation.
- Automatically construct a URL according to the value of specified fields in the alert.
To assist you, several alert management rules are provided with the base system. You can use them as presented or you can use them as examples to build custom alert management rules.
| Rule | Description | Active |
|---|---|---|
| Open sensor dashboard in PRTG | The sensor dashboard in the Paessler PRTG Network Monitor (PRTG) application opens. | Yes |
| Oracle EM Launch Target Status and View Events | Launch Oracle Enterprise Manager to view:
|
Yes |
| Drilldown to OMI | Drill down to the HP Operations Manager i (OMi) application. | Yes |
| Create Incident on Primary Critical Alert | Create an incident for primary critical alerts. The incident can be created automatically or manually. | No |
| Search Google for "description" | Open Google Search in a browser to search for data according to the description that appears in the alert. | Yes |
| Create Incident | Create an incident for all alerts that are not in maintenance state. The rule runs automatically on selective update. | No |
| Create Incident Manually | Manually create an incident for alerts that are not in maintenance state. | Yes |
| Create Major Incident Candidate | Create a major incident candidate for all alerts that are not in maintenance state and are not secondary alerts. A major incident candidate can be promoted to become a major incident. |
No |
| Create Major Incident | Create a major incident for all alerts that are not in maintenance state and are not secondary alerts. | No |
Alert management rules run 5 seconds after an alert is updated, resetting the timer if updates occur within that window. This delay ensures remediation actions, such as incident creation, are triggered only when the issue is clear and stable, reducing duplicates and unnecessary noise. To change the default 5-second delay, create the evt_mgmt.alert_rule_delay property on the and change the value. To know how to create a property, see Add a system property.