- Added support for Cisco ASR 9000 (Netflow v9)
- Added support for Streamcore StreamGroomer (Netflow v9)
- Fixed docs so they can generate
- Fixed 0-length template field length (Netflow 9)
- Fixed 0-length scope field length (Netflow 9, Juniper SRX)
- Fixed JRuby 9K compatibility
- Added support for VMware VDS IPFIX although field definitions are unknown
- Fix/Refactor IPFIX microsecond/nanosecond interpretation (NTP Timestamp based)
- Note a possible bug in Netscaler implementation where the fraction is proabably output as microseconds
- Correct rspec testing for new/correct implementation of microseconds, never noticed the insane values before, mea culpa
- Add Netflow v9/v10 template caching, configurable TTL
- Add option for including flowset_id for Netflow v10
- Refactor/simplify Netflow v9/v10 templates processing
- Add variable length field support
- Add OctetArray support
- Add Citrix Netscaler (IPFIX) support
- Add spec tests and anonymized test data for all of the above
- Added support for MPLS labels
- Added support for decoding forwarded status field (Netflow 9)
- Confirmed support and tests added for 4 Netflow/IPFIX exporters
- Relax constraint on logstash-core-plugin-api to >= 1.60 <= 2.99
- Small update due to breaking change in BinData gem (issue #41)
- Added IPFIX support
- Republish all the gems under jruby.
- Update the plugin to the version 2.0 of the plugin api, this change is required for Logstash 5.0 compatibility. See elastic/logstash#5141
- Fixed exception if Netflow data contains MAC addresses (issue #26, issue #34)
- Fixed exceptions when receiving invalid Netflow v5 and v9 data (issue #17, issue 18)
- Fixed decoding Netflow templates from multiple (non-identical) exporters
- Add support for Cisco ASA fields
- Add support for Netflow 9 options template with scope fields
- Depend on logstash-core-plugin-api instead of logstash-core, removing the need to mass update plugins on major releases of logstash
- New dependency requirements for logstash-core for the 5.0 release
- Fixed JSON compare flaw in specs
- Plugins were updated to follow the new shutdown semantic, this mainly allows Logstash to instruct input plugins to terminate gracefully, instead of using Thread.raise on the plugins' threads. Ref: elastic/logstash#3895
- Dependency on logstash-core update to 2.0