One of the previous blogs explained a 3-step troubleshooting approach if applications, cloud services and networks are not behaving as expected.
Part of this is step 2: user plane, network visibility as a way of identifying which parts of the application chains are causing this unexpected behavior.
In this post 5 fact sheets helping you with the interpretation of this big-“TCP-connection”-data.
Taking this approach is a very valid one since networks and TCP connections are the linking pin between all your users, business applications and cloud services.
Diagnosing all these connections is best done with a TCP number cruncher. Because assuming the right level of modelling and visualization, these TCP number crunchers have proven more then once to deliver the shortest turnaround time for to the point and substantiated answers on the 5 most relevant questions:
(1) – what is impacted | (2) – which sites | (3) – how many users | (4) – what is failing |
(5) – source-of-failure
- Contextual aspects of the question (i.e. meaning and relevancy)
- Pointers as to what TCP session data to look for (i.e. OSI-layer 4, session related TCP events and metrics)
- An example of the representation and its interpretation.
Combined, this gives you a jump-start in providing to the point and substantiated answers to the business and your service providers.
Sounds interesting? Want learn more?