tshark expired flow drops to zero then spikes
Has anyone seen an ingestion profile like such that the expired flow rate drops to zero, then spikes, and fails. See the attached. The event is happening at different intervals, but normally every 2 to 3 hours.
was not able to upload the data flow graph, but I have several that show the issue.
Could you give a bit more information since no image?
We are seeing this on multiple systems. We are not running out of memory or CPU. We are sending data into tshark as a pcap file written to stdin (with a -r flag).
hey - I know you! ;-)
Let me see if I can pull more details from the team.