[
https://issues.apache.org/jira/browse/METRON-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ian Abreu updated METRON-1002:
------------------------------
Description:
Hello,
After talking in #apache-metron, we've agree'd that metron needs proper support
for netflow parsing.
Specs:
Input: Input should be standard Netflow V9 as defined in [RFC
3954|https://www.ietf.org/rfc/rfc3954.tx[]t] Note, on page 17, the section on
Field Type Definitions is defined.
Output: Output should be data that is able to be processed higher up in metron
via the generic kafka parsing topology.
was:
Hello,
After talking in #apache-metron, we've agree'd that metron needs proper support
for netflow parsing.
Specs:
Input: Input should be standard Netflow V9 as defined in
(RFC3954)[https://www.ietf.org/rfc/rfc3954.txt] Note, on page 17, the section
on Field Type Definitions is defined.
Output: Output should be data that is able to be processed higher up in metron
via the generic kafka parsing topology.
> Add Netflow Parser, to import data directly from Netflow Feed.
> --------------------------------------------------------------
>
> Key: METRON-1002
> URL: https://issues.apache.org/jira/browse/METRON-1002
> Project: Metron
> Issue Type: New Feature
> Reporter: Ian Abreu
>
> Hello,
> After talking in #apache-metron, we've agree'd that metron needs proper
> support for netflow parsing.
> Specs:
> Input: Input should be standard Netflow V9 as defined in [RFC
> 3954|https://www.ietf.org/rfc/rfc3954.tx[]t] Note, on page 17, the section on
> Field Type Definitions is defined.
> Output: Output should be data that is able to be processed higher up in
> metron via the generic kafka parsing topology.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
