You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/sentinel/automate-incident-handling-with-automation-rules.md
+53-1Lines changed: 53 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -91,7 +91,7 @@ Even without being onboarded to the unified portal, you might anyway decide to u
91
91
92
92
### Conditions
93
93
94
-
Complex sets of conditions can be defined to govern when actions (see below) should run. These conditions include the event that triggers the rule (incident created or updated, or alert created), the states or values of the incident's properties and [entity properties](entities-reference.md) (for incident trigger only), and also the analytics rule or rules that generated the incident or alert.
94
+
Complex sets of conditions can be defined to govern when actions (see below) should run. These conditions include the event that triggers the rule (incident created or updated, or alert created), the states or values of the incident's properties and [entity properties](#supported-entity-properties) (for incident trigger only), and also the analytics rule or rules that generated the incident or alert.
95
95
96
96
When an automation rule is triggered, it checks the triggering incident or alert against the conditions defined in the rule. For incidents, the property-based conditions are evaluated according to **the current state** of the property at the moment the evaluation occurs, or according to **changes in the state** of the property (see below for details). Since a single incident creation or update event could trigger several automation rules, the **order** in which they run (see below) makes a difference in determining the outcome of the conditions' evaluation. The **actions** defined in the rule are executed only if all the conditions are satisfied.
97
97
@@ -168,6 +168,58 @@ In this example, in *Incident 1*:
168
168
169
169
In *Incident 2*, the outcome is the same, regardless of which type of condition is defined.
170
170
171
+
#### Supported entity properties
172
+
173
+
The following entities and entity properties can be used as conditions for automation rules:
Copy file name to clipboardExpand all lines: articles/sentinel/create-manage-use-automation-rules.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -151,7 +151,7 @@ Use the options in the **Conditions** area to define conditions for your automat
151
151
152
152
| Property | Operator set |
153
153
| -------- | -------- |
154
-
| - **Title**<br>- **Description**<br>- All listed **entity properties**| - Equals/Does not equal<br>- Contains/Does not contain<br>- Starts with/Does not start with<br>- Ends with/Does not end with |
154
+
| - **Title**<br>- **Description**<br>- All listed **entity properties**<br> (see [supported entity properties](automate-incident-handling-with-automation-rules.md#supported-entity-properties))| - Equals/Does not equal<br>- Contains/Does not contain<br>- Starts with/Does not start with<br>- Ends with/Does not end with |
155
155
| - **Tag** (See [individual vs. collection](automate-incident-handling-with-automation-rules.md#tag-property-individual-vs-collection)) |**Any individual tag:**<br>- Equals/Does not equal<br>- Contains/Does not contain<br>- Starts with/Does not start with<br>- Ends with/Does not end with<br><br>**Collection of all tags:**<br>- Contains/Does not contain |
@@ -160,7 +160,7 @@ Use the options in the **Conditions** area to define conditions for your automat
160
160
161
161
| Property | Operator set |
162
162
| -------- | -------- |
163
-
| - **Title**<br>- **Description**<br>- All listed **entity properties**| - Equals/Does not equal<br>- Contains/Does not contain<br>- Starts with/Does not start with<br>- Ends with/Does not end with |
163
+
| - **Title**<br>- **Description**<br>- All listed **entity properties**<br> (see [supported entity properties](automate-incident-handling-with-automation-rules.md#supported-entity-properties))| - Equals/Does not equal<br>- Contains/Does not contain<br>- Starts with/Does not start with<br>- Ends with/Does not end with |
164
164
| - **Tag** (See [individual vs. collection](automate-incident-handling-with-automation-rules.md#tag-property-individual-vs-collection)) |**Any individual tag:**<br>- Equals/Does not equal<br>- Contains/Does not contain<br>- Starts with/Does not start with<br>- Ends with/Does not end with<br><br>**Collection of all tags:**<br>- Contains/Does not contain |
165
165
| - **Tag** (in addition to above)<br>- **Alerts**<br>- **Comments**| - Added |
166
166
| - **Severity**<br>- **Status**| - Equals/Does not equal<br>- Changed<br>- Changed from<br>- Changed to |
0 commit comments