logged_reverse_pkts field is missing in logged sessions matching the SLO.
sample of logged session where logged reverse pkt is missing, client and server sessions:
client:
Mar 5 12:36:35 nodec12 contrail-vrouter-agent[17770]: 2018-03-05 Mon 12:36:35:199.683 IST nodec12 [Thread 140070267983616, Pid 17770]: [SYS_INFO]: SessionData: [ vmi = default-domain:ctest-SecurityLogging-60929462:139d6bc8-cb70-4a76-9580-b2e337f12f63 vn = default-domain:ctest-SecurityLogging-60929462:ctest-vn-29910274 ] security_policy_rule = 00000000-0000-0000-0000-000000000001 remote_vn = default-domain:ctest-SecurityLogging-60929462:ctest-vn-01283380 is_client_session = 1 is_si = 0 vrouter_ip = 10.204.216.69 local_ip = 92.238.44.3 service_port = 0 protocol = 1 logged_forward_bytes = 98 logged_forward_pkts = 1 logged_reverse_bytes = 98 ip = 204.218.160.3 port = 1819 forward_flow_info= [ logged_bytes = 98 logged_pkts = 1 flow_uuid = e039e73d-2468-4058-897b-7025605189e9 tcp_flags = 0 setup_time = 1520233586094133 action = pass sg_rule_uuid = 28ff0745-909a-44f6-b141-8c1aca8116d3 nw_ace_uuid = 94cf33b5-d95f-463f-8c10-ac8b38df20da underlay_source_port = 63166 ] reverse_flow_info= [ logged_bytes = 98 logged_pkts = 1 flow_uuid = 40eb67bf-55c3-446b-9c6d-89fc98be0738 tcp_flags = 0 setup_time = 1520233586094133 action = pass sg_rule_uuid = 0a1e87bd-036c-4fa3-9f03-c387f1abaf9f nw_ace_uuid = 94cf33b5-d95f-463f-8c10-ac8b38df20da underlay_source_port = 60303 ] vm = cc9d3dba-56f5-46f7-82a7-6f91c541be61 other_vrouter_ip = 10.204.216.69 underlay_proto = 0 ]
server:
Mar 5 12:36:35 nodec12 contrail-vrouter-agent[17770]: 2018-03-05 Mon 12:36:35:199.839 IST nodec12 [Thread 140070267983616, Pid 17770]: [SYS_INFO]: SessionData: [ vmi = default-domain:ctest-SecurityLogging-60929462:93ca94ea-75eb-428e-9f44-d3398ce314d8 vn = default-domain:ctest-SecurityLogging-60929462:ctest-vn-01283380 ] security_policy_rule = 00000000-0000-0000-0000-000000000001 remote_vn = default-domain:ctest-SecurityLogging-60929462:ctest-vn-29910274 is_client_session = 0 is_si = 0 vrouter_ip = 10.204.216.69 local_ip = 204.218.160.3 service_port = 1819 protocol = 1 logged_forward_bytes = 98 logged_forward_pkts = 1 logged_reverse_bytes = 98 ip = 92.238.44.3 port = 0 forward_flow_info= [ logged_bytes = 98 logged_pkts = 1 flow_uuid = 40eb67bf-55c3-446b-9c6d-89fc98be0738 tcp_flags = 0 setup_time = 1520233586093785 action = pass sg_rule_uuid = 0a1e87bd-036c-4fa3-9f03-c387f1abaf9f nw_ace_uuid = 94cf33b5-d95f-463f-8c10-ac8b38df20da underlay_source_port = 60303 ] reverse_flow_info= [ logged_bytes = 98 logged_pkts = 1 flow_uuid = e039e73d-2468-4058-897b-7025605189e9 tcp_flags = 0 setup_time = 1520233586093785 action = pass sg_rule_uuid = 28ff0745-909a-44f6-b141-8c1aca8116d3 nw_ace_uuid = 94cf33b5-d95f-463f-8c10-ac8b38df20da underlay_source_port = 63166 ] vm = cdb949fa-2637-4f87-876f-79fbd8b40c21 other_vrouter_ip = 10.204.216.69 underlay_proto = 0 ]
Note: this test was for intra node traffic.
with fix for Bug 1797317, we see same issue for logs in agent file too.
Also check related bug 1798294.