Create alert rules for a service
You can create alert rules to trigger an action for a service. You can also create conditions in alert rules and create more actions to associate with alert rules. SR Ops supports the execution of actions such as creating an incident or sending notifications when an alert is received or an incident is created.
Vorbereitungen
Role required: sro_user or sro_admin
Prozedur
-
Click the Services page icon (
).
-
On the form, fill in the fields.
Tabelle : 1. New Alert Rule form Field Description Details Service Trigger Type Types of the service that you want to trigger the alert rule for. You can set a trigger for any of the following types:- Service: The alert is triggered only for the service that you are creating the alert rule for.
- CI: The alert is triggered only for the impacted configuration item (CI) for the service that you are creating the alert rule for.
- Service + CI: The alert is triggered for both the service that you are creating the alert rule and the impacted CI for the service.
Hinweis:For the CI and Service + CI types, the rule triggers only if the CI is a child of a service or a Technical Service. If the CI is more than one level deep, the rule does not trigger.Service Name of the service. The field is automatically set based on the service that you are creating the alert rule for. Order Order in which you want the actions to be executed. Conditions Conditions Condition that the trigger action is based on. When the service associated with the alert matches the value in the Service field and all these conditions are met, the action is executed.
As long as the conditions in the alert rules are met, the action triggers. The order in which the actions are executed between the actions at the integration level and at a service level is not guaranteed.
All alert rules are evaluated and processed in order. Anytime that a rule matches the condition, an action runs once for this matching rule. This action may happen when there is an update to the alert. Initially, a rule may not trigger but a subsequent rule may change the alert so that the previous non-matching conditions, when matched, triggers the action.
You can create a custom condition, or you can also add more available conditions.
To create a custom condition, complete these steps:- Click Create custom condition.
- On the New custom condition form, fill in the
fields.
- Name: Name of the condition.
- Short description: Brief description of the condition.
- Mode: The mode that you
want to use to create the condition. You can
either create a condition based on criteria or
based on a script.
Based on the mode that you select, enter the condition that must be met or add a script.
- Click Save.
If you want to add more available conditions for this alert rule, click + Add Condition.
Action Add an action Action that you want to execute for this alert rule. You can select an available action tile.
If you want to use another action that is not available in the tile, click More actions and then select the name of the action.
If you want to create more actions, click the more UI actions icon (
) that appears next to the
Save button on the New Alert
Rule page, and then select Create
Action.Hinweis:While setting the action for the alert rule, if the action selected has the Configuration required field value as true, the Configuration field appears. The variables required for configuration are determined by the action. These variables are specified in the Description field when you create an action on the Action page.Configuration The action is executed with the configuration that you select from the list. To enter a value in the Configuration field, point to this field and click inside it. The field shows a list of the available configurations to select from.
If you want to create a new configuration to associate with the action, click the more UI actions icon (
) that appears next to the
Save button, and then select
Create
Configuration.