Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: netobserv-1.4.1
Affects Version/s: netobserv-1.3, netobserv-1.4
Component/s: Kafka
Labels:
- pre-merge-tested

Blocked:
False
Blocked Reason:
None
Ready:
False
Release Note Text:
Previously, the when sending to kafka, the kafka message key was ignored causing error with connection tracking. Now the key is used for partitioning so each flow from the same connection are sent to the same processor.
Intelligence Requested:
Market:

Sprint:
NetObserv - Sprint 234, NetObserv - Sprint 235, NetObserv - Sprint 236, NetObserv - Sprint 237, NetObserv - Sprint 238, NetObserv - Sprint 239, NetObserv - Sprint 240, NetObserv - Sprint 241, NetObserv - Sprint 242

Target Version:

netobserv-1.3

SFDC Cases Links:
SFDC Cases Counter:
SFDC Cases Open:

Connection tracking is processed per node (FLP) and maintains counter states. As traffic comes from EBPF agents that are also bound to a node, there is an automatic consistency in the n-tuple ids that are processed.

When Kafka is used, FLP receives "random" flow data - loosing that n-tuple ids consistency. So the counter that it produces will be flawed, ie. they might not reflect the actual total of bytes/packets received.