Description:
Parses netflowv5 byte ingest and add to NiFi flowfile as attributes or JSON content.
Additional Details...
Tags:
network, netflow, attributes, datagram, v5, packet, byte
Properties:
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 Name | API Name | Default Value | Allowable Values | Description |
|---|
| Parsed fields destination | FIELDS_DESTINATION | flowfile-content | - flowfile-content
 - flowfile-attribute
| 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. |
Relationships:
| Name | Description |
|---|
| success | Any FlowFile that is successfully parsed as a netflowv5 data will be transferred to this Relationship. |
| failure | Any FlowFile that could not be parsed as a netflowv5 message will be transferred to this Relationship without any attributes being added |
| original | The original raw content |
Reads Attributes:
| Name | Description |
|---|
| udp.port | Optionally read if packets are received from UDP datagrams. |
Writes Attributes:
| Name | Description |
|---|
| 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.Restricted:
This component is not restricted.Input requirement:
This component requires an incoming relationship.System Resource Considerations:
None specified.