-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
Product / Portfolio Work
-
False
-
None
-
False
-
5
-
None
-
None
-
NetObserv - Sprint 208
Currently we run goflow2 binary and pipe with kube/loki plugins via stdout/in.
We should see if, instead, it's possible to create a kube-enricher that consumes goflow2 as a library in order to receive flows, decode ipfix, etc. It would avoid having to unmarshal/marshal between goflow and kube-enricher. The loki-exporter would as well be aggregated into this program.
If changes are necessary in goflow2, evaluate them with goflow2 maintainer for potential upstream merge.
If not desired upstream, evaluate/discuss the solution to fork and patch versus stick to our current i/o pipe solution (maintainability over performances?)