Observe every captured TCP segment here.

Number of times we got an assembler context of the wrong type; this probably shouldn't happen at all.

Nunmber of times we got a nil assembler context; this can happen when the payload resides in a page other than the first in the reassembly buffer.

or when we flush old data?.

What is a reasonable worst case? We should have enough so that if the packet is retransmitted, we will get it before giving up.

Maximum size of gopacket reassembly buffers, per interface and direction.

TODO: packet capture timeouts are tuned using the packet capture tests on a particular developer's machine.

The maximum time we will leave a connection open waiting for traffic.

The maximum time we will wait before flushing a connection and delivering the data even if there is a gap in the collected sequence.

NetworkTrafficObserver is the callback function type for observing packets as they come in to a NetworkTrafficParser.