-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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.
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
Mark flow elephant/v2 #12123
Mark flow elephant/v2 #12123
Conversation
1. Add user defined elephant flow definition based on rate of bytes easily configurable in suricata.yaml. 2. Add an elephant flow counter. Feature 5647
This is to allow a way to match on the rate of the flow through rule language. This serves as a trivial first step to a more elaborate path to defining and detecting elephant flows.
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #12123 +/- ##
===========================================
+ Coverage 62.68% 83.14% +20.46%
===========================================
Files 840 910 +70
Lines 153669 257927 +104258
===========================================
+ Hits 96323 214466 +118143
+ Misses 57346 43461 -13885
Flags with carried forward coverage won't be shown. Click here to find out more. |
Need to find a way to keep time blocked data structures for flow management so this can be done on any interval. Victor suggested we could start w this trivial keyword though. Interested in hearing if it makes sense to others too. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would like to see this split between a PR for the flow.rate and the elephant marking.
Also please add user docs.
Other comments inline.
Information: ERROR: QA failed on SURI_TLPR1_alerts_cmp.
Pipeline 23324 |
Link to ticket: https://redmine.openinfosecfoundation.org/issues/5647
SV_BRANCH=OISF/suricata-verify#2130
Previous PR: #11645
Changes since v1: