You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the conntrack module looks for the protocol in the field Proto to filter out non-transport flowlogs.
This breaks make ocp-deploy in a way that connections aren't being tracked. The reason is that Proto is missing (because it was renamed to proto) so all flowlogs are filtered out.
I suggest to add ProtocolFieldName setting to the conntrack configuration to allow specifying a custom field name for the protocol field other than Proto. If this setting is not set, Proto could be set as a default for backward compatibility.
The text was updated successfully, but these errors were encountered:
Currently, the conntrack module looks for the protocol in the field
Proto
to filter out non-transport flowlogs.This breaks
make ocp-deploy
in a way that connections aren't being tracked. The reason is thatProto
is missing (because it was renamed toproto
) so all flowlogs are filtered out.flowlogs-pipeline/contrib/kubernetes/flowlogs-pipeline.conf.yaml
Lines 42 to 43 in 914d470
I suggest to add
ProtocolFieldName
setting to the conntrack configuration to allow specifying a custom field name for the protocol field other thanProto
. If this setting is not set,Proto
could be set as a default for backward compatibility.The text was updated successfully, but these errors were encountered: