Skip to content

Commit 3aac6b9

Browse files
authored
Add custom threshold rule exception to alerting set up docs (#2484)
1 parent a039843 commit 3aac6b9

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

explore-analyze/alerts-cases/alerts/alerting-setup.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,11 @@ Likewise, you can customize the **Rules Settings** sub-feature privileges relate
5151

5252
To create a rule that uses the [Cases connector](kibana://reference/connectors-kibana/cases-action-type.md), you must also have `All` privileges for the **Cases** feature.
5353

54-
The rule type also affects the privileges that are required. For example, to create or edit {{ml}} rules, you must have `all` privileges for the **Analytics > {{ml-app}}** feature. For {{stack-monitor-app}} rules, you must have the `monitoring_user` role. For {{observability}} rules, you must have `all` privileges for the appropriate {{observability}} features. For Security rules, refer to [Detections prerequisites and requirements](../../../solutions/security/detect-and-alert/detections-requirements.md).
54+
The rule type also affects the privileges that are required to create and edit rules. For example:
55+
* For {{ml}} rules, you must have `all` privileges for the **Analytics > {{ml-app}}** feature.
56+
* For {{stack-monitor-app}} rules, you must have the `monitoring_user` role.
57+
* For most {{observability}} rules, you must have `all` privileges for the appropriate {{observability}} features. However, for a custom threshold rule, you only need the `stack alerts` privilege.
58+
* For Security rules, refer to [Detections prerequisites and requirements](../../../solutions/security/detect-and-alert/detections-requirements.md).
5559

5660
::::
5761

0 commit comments

Comments
 (0)