Skip to content

Commit a14d229

Browse files
author
Jill Grant
authored
Update detect-threats-custom.md
1 parent 5dfa636 commit a14d229

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/sentinel/detect-threats-custom.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -138,7 +138,7 @@ In the **Set rule logic** tab, you can either write a query directly in the **Ru
138138
>
139139
> For more information, see [Handle ingestion delay in scheduled analytics rules](ingestion-delay.md).
140140
141-
1. Use the **Alert threshold** section to define the sensitivity level of the rule. For example, set **Generate alert when number of query results** to **Is greater than** and enter the number 1000 if you want the rule to generate an alert only if the query returns more than 1000 results each time it runs. This is a required field, so if you don’t want to set a threshold – that is, if you want your alert to register every event – enter 0 in the number field.
141+
- Use the **Alert threshold** section to define the sensitivity level of the rule. For example, set **Generate alert when number of query results** to **Is greater than** and enter the number 1000 if you want the rule to generate an alert only if the query returns more than 1000 results each time it runs. This is a required field, so if you don’t want to set a threshold – that is, if you want your alert to register every event – enter 0 in the number field.
142142
143143
### Results simulation
144144

0 commit comments

Comments
 (0)