Skip to content

Commit 74dd69d

Browse files
author
yelevin
committed
Added screenshot
1 parent cfeb17f commit 74dd69d

File tree

3 files changed

+23
-0
lines changed

3 files changed

+23
-0
lines changed

articles/sentinel/create-manage-use-automation-rules.md

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -130,6 +130,29 @@ Select the **+ Add** expander and choose **Condition (And)** from the drop-down
130130

131131
Again, for setting complex **Or** conditions with different fields, see [Add advanced conditions to automation rules](add-advanced-conditions-to-automation-rules.md).
132132

133+
#### Conditions based on tags
134+
135+
You can create two kinds of conditions based on tags:
136+
137+
- Conditions with **Any individual tag** operators evaluate the specified value against every tag in the collection. The evaluation is *true* when *at least one tag* satisfies the condition.
138+
- Conditions with **Collection of all tags** operators evaluate the specified value against the collection of tags as a single unit. The evaluation is *true* only if *the collection as a whole* satisfies the condition.
139+
140+
To add one of these conditions based on an incident's tags, take the following steps:
141+
142+
1. Create a new automation rule as described above.
143+
144+
1. Add a condition or a condition group.
145+
146+
1. Select **Tag** from the properties drop-down list.
147+
148+
1. Select the operators drop-down list to reveal the available operators to choose from.
149+
150+
:::image type="content" source="media/create-manage-use-automation-rules/tag-create-condition.png" alt-text="Screenshot of list of operators for tag condition in create trigger rule.":::
151+
152+
See how the operators are divided in two categories as described before. Choose your operator carefully based on how you want the tags to be evaluated.
153+
154+
For more information, see [*Tag* property: individual vs. collection](automate-incident-handling-with-automation-rules.md#tag-property-individual-vs-collection).
155+
133156
#### Conditions based on custom details
134157

135158
You can set the value of a [custom detail surfaced in an incident](surface-custom-details-in-alerts.md) as a condition of an automation rule. Recall that custom details are data points in raw event log records that can be surfaced and displayed in alerts and the incidents generated from them. Through custom details you can get to the actual relevant content in your alerts without having to dig through query results.
27.8 KB
Loading
32 KB
Loading

0 commit comments

Comments
 (0)