README.md in fluent-plugin-netflow-0.2.8 vs README.md in fluent-plugin-netflow-1.0.0.rc1

- old
+ new

@@ -24,10 +24,11 @@ # optional parameters bind 192.168.0.1 port 2055 cache_ttl 6000 versions [5, 9] + definitions /path/to/custom_fields.yaml </source> **bind** IP address on which the plugin will accept Netflow. @@ -51,11 +52,20 @@ **switched_times_from_uptime** When set to true, the plugin stores system uptime for ```first_switched``` and ```last_switched``` instead of ISO8601-formatted absolute time. (Defaults: false) +**definitions** +YAML file containing Netflow field definitions to overfide pre-defined templates. Example is like below + + --- + 4: # field value + - :uint8 # field length + - :protocol # field type + + ## Performance Evaluation Benchmark for v5 protocol on Macbook Air (Early 2014, 1.7 GHz Intel Core i7): * 0 packets dropped in 32,000 records/second (for 3,000,000 packets) * 45,000 records/second in maximum (for flooding netflow packets) @@ -90,11 +100,11 @@ ### Use netflow parser in other plugins ```ruby require 'fluent/plugin/parser_netflow' -parser = TextParser::NetflowParser.new +parser = Fluent::Plugin::NetflowParser.new parser.configure(conf) # Netflow v5 parser.call(payload) do |time, record| # do something @@ -151,9 +161,14 @@ ... 48: - 1 # Some system exports in 2 bytes despite of RFC - :flow_sampler_id ``` + +### PaloAlto Netflow + +PaloAlto Netflow has different field definitionas: +See this definitions for PaloAlto Netflow: https://github.com/repeatedly/fluent-plugin-netflow/issues/27#issuecomment-269197495 ### More speed ? :bullettrain_side: Try ```switched_times_from_uptime true``` option !