Why it matters?
One thing that can make the difference between quickly resolving network problems and letting them linger is having a good baseline. The reason for this is that when a problem strikes, it is important to know what component in the application delivery changed. For example, during a problem, we may notice that it takes a client 150ms to establish a connection with an application server. Questions that may come up are – Is this normal? What is the connection time under normal conditions? What is the traffic load the server usually handles? What servers does it connect to for support when delivering applications to end users?
The time to answer these questions is not during a problem. With an application performance baseline, we answer questions about normal performance before the issue strikes, which allows us to save a ton of time when the triage begins.