Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[8.8] [Redo][8.6-8.13] Highlight that rule exceptions are case-sensitive (backport #4805) #4830

Merged
merged 2 commits into from
Feb 19, 2024
+10 −3
Merged

[8.8] [Redo][8.6-8.13] Highlight that rule exceptions are case-sensitive (backport #4805) #4830

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f73c4fe
[Redo][8.6-8.13] Highlight that rule exceptions are case-sensitive (#…
nastasha-solomon Feb 16, 2024
4f525ca
Fixed conflict
nastasha-solomon Feb 19, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 10 additions & 3 deletions docs/detections/add-exceptions.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,9 +62,11 @@ image::images/add-exception-ui.png[]

+
Add conditions that define when the exception prevents alerts:
+
IMPORTANT: Rule exceptions are case-sensitive, which means that any character that's entered as an uppercase or lowercase letter will be treated as such. In the event you _don't_ want a field evaluated as case-sensitive, some ECS fields have a `.caseless` version that you can use.

.. *Field*: Select a field to identify the event being filtered.
+
+
[NOTE]
=======
Fields with conflicts are marked with a warning icon (image:images/field-warning-icon.png[Field conflict warning icon,13,13]). Using these fields and might cause unexpected exceptions behavior. For more information, refer to <<rule-exceptions-field-conflicts,Troubleshooting type conflicts and unmapped fields>>.
Expand Down Expand Up @@ -169,9 +171,14 @@ image::images/endpoint-add-exp.png[]

. If required, modify the conditions.
+
NOTE: Refer to <<ex-nested-conditions>> for more information on when nested conditions are required.
IMPORTANT: Rule exceptions are case-sensitive, which means that any character that's entered as an uppercase or lowercase letter will be treated as such. In the event you _don't_ want a field evaluated as case-sensitive, some ECS fields have a `.caseless` version that you can use.
+
NOTE: Fields with conflicts are marked with a warning icon (image:images/field-warning-icon.png[Field conflict warning icon,13,13]). Using these fields might cause unexpected exceptions behavior. For more information, refer to <<rule-exceptions-field-conflicts, Troubleshooting type conflicts and unmapped fields>>.
[NOTE]
=======

* Refer to <<ex-nested-conditions>> for more information on when nested conditions are required.
* Fields with conflicts are marked with a warning icon (image:images/field-warning-icon.png[Field conflict warning icon,13,13]). Using these fields might cause unexpected exceptions behavior. For more information, refer to <<rule-exceptions-field-conflicts, Troubleshooting type conflicts and unmapped fields>>.
=======

. You can select any of the following:

Expand Down