Skip to content

Commit 2df9c63

Browse files
Update add-manage-exceptions.md (#2932)
included note that exceptions do not work with fields appended to the output such as es|ql eval statements --------- Co-authored-by: florent-leborgne <[email protected]>
1 parent 1db4543 commit 2df9c63

File tree

1 file changed

+10
-7
lines changed

1 file changed

+10
-7
lines changed

solutions/security/detect-and-alert/add-manage-exceptions.md

Lines changed: 10 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -78,6 +78,9 @@ You can add exceptions to a rule from the rule details page, the Alerts table, t
7878
When you create a new exception from an alert, exception conditions are auto-populated with relevant alert data. Data from custom highlighted fields is listed first. A comment that describes the auto-generated exception conditions is also added to the **Add comments** section.
7979
::::
8080
81+
::::{note}
82+
When using ES|QL, you can append new fields with commands such as [`EVAL`](https://www.elastic.co/docs/reference/query-languages/esql/commands/eval), but you can't apply exceptions to these appended fields. Exceptions are only applied to the index source fields.
83+
::::
8184
8285
1. **Field**: Select a field to identify the event being filtered.
8386
@@ -125,9 +128,9 @@ You can add exceptions to a rule from the rule details page, the Alerts table, t
125128
:screenshot:
126129
:::
127130
128-
4. Click **AND** or **OR** to create multiple conditions and define their relationships.
129-
5. Click **Add nested condition** to create conditions using nested fields. This is only required for [these nested fields](#nested-field-list). For all other fields, nested conditions should not be used.
130-
6. Choose to add the exception to a rule or a shared exception list.
131+
5. Click **AND** or **OR** to create multiple conditions and define their relationships.
132+
6. Click **Add nested condition** to create conditions using nested fields. This is only required for [these nested fields](#nested-field-list). For all other fields, nested conditions should not be used.
133+
7. Choose to add the exception to a rule or a shared exception list.
131134
132135
::::{note}
133136
If you are creating an exception from the Shared Exception Lists page, you can add the exception to multiple rules.
@@ -138,14 +141,14 @@ You can add exceptions to a rule from the rule details page, the Alerts table, t
138141
If a shared exception list doesn’t exist, you can [create one](create-manage-shared-exception-lists.md) from the Shared Exception Lists page.
139142
::::
140143
141-
7. (Optional) Enter a comment describing the exception.
142-
8. (Optional) Enter a future expiration date and time for the exception.
143-
9. Select one of the following alert actions:
144+
8. (Optional) Enter a comment describing the exception.
145+
9. (Optional) Enter a future expiration date and time for the exception.
146+
10. Select one of the following alert actions:
144147
145148
* **Close this alert**: Closes the alert when the exception is added. This option is only available when adding exceptions from the Alerts table.
146149
* **Close all alerts that match this exception and were generated by this rule**: Closes all alerts that match the exception’s conditions and were generated only by the current rule.
147150
148-
10. Click **Add rule exception**.
151+
11. Click **Add rule exception**.
149152
150153
151154
## Add {{elastic-endpoint}} exceptions [endpoint-rule-exceptions]

0 commit comments

Comments
 (0)