Actions
Bug #7884
openexceptions: handle logging for per-packet policies
Description
When implementing #6215 the implications of flow.memcap
and defrag.memcap
affecting only packets weren't taken into consideration.
This means that Suricata is able to generate stats for when these are triggered, but can't actually log the triggered policy with a flow, as there isn't one associated when we apply the policies.
Updated by Victor Julien 5 days ago
Wonder if we should make this a new subtype of the anomaly type
- anomaly:
enabled: yes
types:
# decode: no
# stream: no
# applayer: yes
exception-policy: yes
#packethdr: no
Actions