Parses netflowv5 byte ingest and add to NiFi flowfile as attributes or JSON content.

Additional Details...


network, netflow, attributes, datagram, v5, packet, byte


In the list below, the names of required properties appear in bold. Any other properties (not in bold) are considered optional. The table also indicates any default values.

Display NameAPI NameDefault ValueAllowable ValuesDescription
Parsed fields destinationFIELDS_DESTINATIONflowfile-content
  • flowfile-content Parsed data routes as flowfile JSON content
  • flowfile-attribute Parsed data routes as flowfile attributes
Indicates whether the results of the parser are written to the FlowFile content or a FlowFile attribute; if using flowfile-attribute, fields will be populated as attributes. If set to flowfile-content, the netflowv5 field will be converted into a flat JSON object.


successAny FlowFile that is successfully parsed as a netflowv5 data will be transferred to this Relationship.
failureAny FlowFile that could not be parsed as a netflowv5 message will be transferred to this Relationship without any attributes being added
originalThe original raw content

Reads Attributes:

udp.portOptionally read if packets are received from UDP datagrams.

Writes Attributes:

netflowv5.header.*The key and value generated by the parsing of the header fields.
netflowv5.record.*The key and value generated by the parsing of the record fields.

State management:

This component does not store state.


This component is not restricted.

Input requirement:

This component requires an incoming relationship.

System Resource Considerations:

None specified.