-
Notifications
You must be signed in to change notification settings - Fork 114
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
FlowDirection is commented out #369
Comments
Hi @fionera In an effort to reduce some fields that were only available in NetFlow/IPFIX, I ended up making flow direction configurable via the mapping file. goflow2/cmd/goflow2/mapping.yaml Lines 30 to 33 in 99f3629
The following should automatically add the direction goflow2 -mapping mapping.yaml Please note that v2.2.0 made some changes to the producer libraries to support custom parsing more programmatically. Don't hesitate if you have more questions |
I am using goflow as a library including the protofile. Is there any documentation on how to use this new way? |
Unfortunately, I didn't get around to write proper documentation. But in short: You need to use a To be passed to Or if you want to call The CLI/app does a YAML configuration conversion to a structure with the |
In my case I create the flow proto struct manually https://github.com/monogon-dev/NetMeta/blob/main/cmd/portmirror/iface.go#L135. So I guess CreateProtoProducer would be the way to go? |
Currently the FlowDirection field is missing in the proto file because it was commented out
goflow2/pb/flow.proto
Line 20 in 99f3629
The text was updated successfully, but these errors were encountered: