-
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/v3 #12237
base: master
Are you sure you want to change the base?
Mark flow elephant/v3 #12237
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 brings us down from 2 holes of 2 bytes and 4 bytes to one hole of 5 bytes. There may be more room for improvement.
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #12237 +/- ##
=======================================
Coverage 83.18% 83.18%
=======================================
Files 912 912
Lines 257169 257185 +16
=======================================
+ Hits 213914 213949 +35
+ Misses 43255 43236 -19
Flags with carried forward coverage won't be shown. Click here to find out more. |
# number of bytes a flow has seen in either direction divided by the time a | ||
# flow has been alive. | ||
elephant-flow: | ||
rate: 1000000 |
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.
to me a rate needs a time element, how would that be expressed here?
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.
yeah. will make it take two args instead: bytes and seconds just like the flow.rate
keyword
Link to ticket: https://redmine.openinfosecfoundation.org/issues/5647
Previous PR: #12123
Changes since v2:
Flow
struct (still a WIP)