Netflow v9 not forwarding to Kafka when v9 element not recognized. about vflow HOT 4 OPEN

@ericavijay good catch! I'll fix this soon.

from vflow.

from vflow.

Seconding this, seeing it on IPFIX where there are enterprise-specific information elements sent through. I'm going to start working through the decoder tomorrow to start handling it.

With IPFIX at least, I think the output format would need to change the handle outputting the enterprise number. What are your thoughts on the best way to handle that?

// ENTERPRISE_NUMBER = 123
// ENTERPRISE_INFORMATION_ELEMENT_ID = 4567

// Stick it on the existing ID
{"I":123.4567,"V":"192.16.28.217"}

// Add a top level field
{"E":123 "I":4567,"V":"192.16.28.217"}

// Make I an object
{
    "I": {
        "E": 123, 
        "I": 4567
    },
    "V":"192.16.28.217"
}

Of those, adding a top-level field makes the most sense to me. String concat just forces consumers to add parsing logic and making I an object would break any current parsers. For non enterprise elements, E could not be serialized, or serialized as a nil/0?

from vflow.

Hello, has this issue been fixed? I think I am having a similar issue with my Cisco ASA Netflow v9.

from vflow.