Optimizing Network Security with Packet Intelligence (by Tom Rowley)
First Day Takeaways from NETSCOUT Engage 2016 (by Chris Greer)

Wireshark Use Case: Slow Response Times - Part 4 (by Paul Offord)

Now we step into the data center to look a bit deeper into a slow response time problem using PCAP traces, Wireshark and markers.

So far we believe that we have proven that the problem isn't a network problem but is due to a slow response from the web server. Luckily we have matching traces captured in the data center.

Capture topology

Better still the data center trace shows browser to web server and web server to database traffic.  So let's crack on ...

... and see if we can narrow the problem down further.  Ideally we want to know if it's a web application problem or a database problem.

 

 

[MP4 version here in case YouTube is blocked]

 

You can download the MRK02 Sample Traces set used in this series of videos from here.

You can get a free copy of TribeLab Workbench through the TribeLab Community site.  For full details see the Workbench details page.  The TRANSUM plugin is also available totally free of charge - see the TRANSUM information page on the TribeLab website.

Best regards...Paul

  

Picture of Paul OffordAuthor Profile - Paul Offord has had a 38-year career in the IT industry that includes roles in hardware engineering, software engineering and network management. Prior to founding Advance7, he worked for IBM, National Semiconductor and Hitachi Data Systems.

Paul and the problem analysts at Advance7 help IT support teams in many business sectors to troubleshoot difficult performance and stability problems. Paul played a key role in the development of the RPR problem diagnosis method and is currently leading the TribeLab project to explore new ways to help IT support people learn troubleshooting skills.

Comments