Interpreting Results

Finding the source of the problem - part 2


Let’s apply and build on what we've learned and dig deeper.

The black line on the Timeline Graph shows you the latency over time. As you zoomed in on the graph earlier you saw that really what you’re seeing is pixel-wide entries that represent the round trip time, or latency for the host/device who's Timeline Graph you’re looking at.


Interpreting Results - A Quick Example


So let's get into some specific examples of how to interpret the results from PingPlotter.

For the first example, you're getting intermittent packet loss to What can we determine from the graph below?


Event - Send Email


A very popular event type is the "Send Email" event.

Before you can create an event to send an email, you must configure your SMTP server and return email address.  Note that your SMTP server must be accessible on the network to be able to send emails, so it's possible a network failure may not be able to email you.  PingPlotter will continue to try to send emails once a minute until it is able to get an email out.


Related and interesting links


Occasionally, we run across an interesting topic, link or web site. We have no affiliation with any of these sites, and some of them may not even be up. Enter at your own risk (arrrggghhhh - pirate thoughts abound after reading the Traceroute and Pirates article).


Building a Compelling Case


If you find a network problem, you'll most likely want to try and solve that problem. In some cases you might be able to solve this network problem yourself - possibly by upgrading the BIOS on a hardware device, replacing a network cable or changing network service providers. In most cases though, the network problem will need to be fixed by someone else. If this happens, you'll want to build a compelling case that clearly demonstrates the problem, and then also convey (or present) that information.


Voice over IP (VoIP) troubleshooting


Using an IP Network (like the internet) to conduct a voice conversation (VoIP) is becoming easier and easier for people to do. It can be inexpensive and relatively reliable.It can, however, also be challenging - with poor voice quality, the inability to hear and communicate, delays and other problems.


Interpreting Results - Bandwidth Saturation


Every network connection has a limit, and in this example we'll talk about how to recognize bandwidth limits on a local DSL / Cable modem.

The scenario here is a 30Mbps downstream, 10Mbps upstream cable modem running a 2.5 second trace interval to our target. The computer running PingPlotter was connected to the cable modem via a wireless network card, which loses packets occasionally.


Interpreting Results - Longterm Monitoring


PingPlotter allows you to use the timeline graphs to zoom in on any particular time, so even if you weren't there (or didn't save an image) when something was happening, you can still recover that exact image later. You shouldn't ever have to be sitting in front of your computer when an outage happens, or you experience other problems on your network, to get the data you need from PingPlotter.