From 49542d0f1bb35d889f798a50c04f4a257b816695 Mon Sep 17 00:00:00 2001 From: Juliana Fajardini Date: Wed, 6 Apr 2022 11:54:52 -0300 Subject: [PATCH] doc/userguide: explain packet-alert-max config Task #4207 --- doc/userguide/configuration/suricata-yaml.rst | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/doc/userguide/configuration/suricata-yaml.rst b/doc/userguide/configuration/suricata-yaml.rst index f4783199fa..60ff51e799 100644 --- a/doc/userguide/configuration/suricata-yaml.rst +++ b/doc/userguide/configuration/suricata-yaml.rst @@ -145,6 +145,21 @@ is: pass, drop, reject, alert. This means a pass rule is considered before a drop rule, a drop rule before a reject rule and so on. +Packet alert queue settings +--------------------------- + +It is possible to configure the size of the alerts queue that is used to append alerts triggered by each packet. + +This will influence how many alerts would be perceived to have matched against a given packet. +The default value is 15. If an invalid setting or no value is provided, the engine will fall +back to the default. + +:: + + #Define maximum number of possible alerts that can be triggered for the same + # packet. Default is 15 + packet-alert-max: 15 + Splitting configuration in multiple files -----------------------------------------