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 2 months 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
Updated by Victor Julien about 2 months ago
- Target version changed from 8.0.2 to 9.0.0-beta1
Updated by OISF Ticketbot about 2 months ago
- Label deleted (
Needs backport to 7.0)
Updated by Juliana Fajardini Reichow 14 days ago
- Status changed from New to Assigned
Actions