There are many ways to analyze network traffic. Flows provided by network devices to reflect traffic volumes are one way; packet analysis is the other way.
Every IT Operations team faces complaints indicating that the network is slowing down or poorly delivering applications. Their very first focus is on checking the network performance (latency, packet loss, etc.).
Nevertheless, the network is not the sole driver of data transfer speed and of the end user experience.
- What should you do?
- What patterns should you look for?
You are willing to move away from the "Mean Time to Innocence" Approach and implement collaborative performance troubleshooting and optimization; how can you achieve this with performance analytics extracted from your network traffic?
Well, let's first define what Mean Time to Innocence means?
This is when your main purpose is to prove that you are not to blame if something goes wrong somewhere. It can be seen as a more politically correct variation of the famous C.Y.A. - Cover Your Ass approach.
Topics: performance troubleshooting