Jorrit Folmer

Oops thanks, somehow I missed this in the IPFIX compliance list I keep over at https://github.com/logstash-plugins/logstash-codec-netflow/blob/master/RFC_COMPLIANCE_IPFIX.md.

This could be related to #13. You seem to be running MacOS and possibly Little Snitch. You may find that the Cloudflare profile is disabled and cannot be enabled in...

Thanks for your clear explanation! The patch below seems to fix this issue by concatenating the chunks as strings before splitting on newline into a list at output. ```diff ---...

What have been the reasons to change this plugin from filter to codec? I couldn't find any through Google. Not having the source IP information available makes this codec ignore...

Ah yes ok that makes sense, thanks for your explanation. Perhaps it is time to open an issue for this in the main logstash repository?

For easy reference: current issues (both open/closed) already in logstash repo that touch on codecs and/or metadata: elastic/logstash#3725: Split Codecs into Encoders and Decoders elastic/logstash#3694: Use of `@metadata` in 2.0...

I've added commit jorritfolmer@fca329f7a2b4845020d26c925540851093ba61f1 to address this, as experienced in issue #21. Besides the above commit, it also requires a small patch to logstash-input-udp, to send metadata to the codec,...

There has been an update to elastic/logstash#4289. With regard to the netflow codec needing packet metadata, I quote Guy Boertje from that thread: > If this is true, you are...

Following up on the suggestion of @guyboertje, I've started with the transition from codec to logstash-input-netflow in the branch `logstash-input-netflow`, based on the udp input plugin. It works! There is...

There is no easy fix. The library we use to parse doesn't support multiple identical fields. Similar issues for reference: #93 #142