-
Notifications
You must be signed in to change notification settings - Fork 22
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
Goflow parse #361
Goflow parse #361
Conversation
…if, outif which resolves a bug where proto 0 (ICMP) is dropped from the entry
|
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.
LGTM
|
Codecov Report
@@ Coverage Diff @@
## master #361 +/- ##
==========================================
+ Coverage 73.16% 73.26% +0.11%
==========================================
Files 123 124 +1
Lines 7860 7947 +87
==========================================
+ Hits 5750 5822 +72
- Misses 1623 1633 +10
- Partials 487 492 +5
Continue to review full report at Codecov.
|
Description of Changes
structs.Map()
call (converting goflow message to map[string]interface{} in favor of manual parsing.This new behavior means test cases need to set the following to their zero values:
Proto, InIf, OutIf are always present (from what I have seen in the field). If they are not present, the user will see zero values and the
proto_name
"HOPOPT". It is possible a future version of the Goflow package will allow us to detect if the fields were sent from the client.I observed significant performance increase
Master:
This PR:
Please check that the PR fulfills these requirements