Why it matters?

It's easy to feel packet-overload when searching for the root cause of a performance problem in a trace file. There are a few things that can lessen the "needle-in-the-haystack" feeling.

One is by making use of analysis tools that can graphically represent packet detail without burdening the analyst with too much information. Another is by setting simple capture filters while collecting traffic to minimize the bloat, and setting display filters after the fact to key in on important conversations.