Problems

When users are complaining about a slow network, we all know it’s often not the network, but network engineers must be able to troubleshoot both the network and the application that is being used to determine the root cause. Measuring network latency vs. application latency is the proof the network engineer needs. Latency monitoring can help determine if problems are localized to a specific user or server, or more global, but simple latency monitoring lacks the details needed to correlate areas of latency with other relevant statistics, including other network traffic occurring at that time.

Is the network slowdown due to my network or applications?

Is the network slowdown due to my network or applications?

How do I establish a baseline for application and network usage?

How do I establish a baseline for application and network usage?

How much of my network bandwidth is being used by my critical applications?

How much of my network bandwidth is being used by my critical applications?

Solution

Use Savvius Omnipliance and Savvius Insight to capture packets at the appropriate network segment. This allows you to see network and application latency across multiple segments, determine bandwidth hogs, and monitor network utilization. With Savvius Spotlight you can instantly see the worst performing flows across your network and drill into the packets associated to those flows if necessary.