AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Pingplotter sampleing menu9/16/2023 ![]() Turn on time graphs for the intermediate hop you think is causing the problem (double-click on the hop number to toggle the visibility of the time graph) and then compare the packet loss and latency periods. Look for the first hop that is showing the latency or packet loss problems you're seeing at the final destination. Once you've focused the time graph, the upper 'trace' graph will show the statistics for that time period for all hops. You'll see a 'focus rectangle' that shows the time period you're looking at - change 'Samples to Include' to make that time period big enough to get a good sampling of the problem - 50 or more samples is recommended in most cases, but if your disturbance was very short, then a smaller number might work. Double-click on the time graph for the final destination to focus the upper graph on that period. Then, go back and look at previous hops to see if you can find things that happened in common at the times when you're seeing problems.Ī good technique to locate which hop is the most likely problem point is to set 'Samples to include' to an appropriate number based on the network disturbance you're seeing. Look for patterns in the final destination - packet loss periods, latency. If you can establish this pattern, then you might be able to determine where this pattern first occurs (ie: which hop or combination of hops) - which can help you understand what's causing the problem, and who to complain to. ![]() That happens when performance problems occur. Your mission here is to locate a pattern, recognizable in the PingPlotter graph of the final destination, Sometimes, this might take multiple days to get both - just keep PingPlotter running constantly (see our knowledge base for tips on long-term monitoring). Ideally, you'll have some periods where there were no problems and some periods where there were problems. When (and if) you experience a problem, switch over to PingPlotter and create a comment for the time period it happened (See the 'Creating a comment or note' in our Getting Started Guide for instructions on how to do this).Īs you run into more problems, continue to collect information and create comments. Now, go about your business doing whatever you normally do. When you're expecting to experience a problem, start PingPlotter and trace to the target of the service you'll be using (example: if you're going to be using telnet to access your remote web server, run PingPlotter against that server). ![]() See the problem here?', that can be a call to action for them, rather than just a random data point. ![]() Look at this PingPlotter data I collected during one session. If you can say ' I normally play X game in the evening, but I keep getting disconnected. PingPlotter data, by itself, can often help track down problems, but most providers need you to complain about some real service problems before they will act on it. Ideally, you're looking to correlate a performance problem in some other application (i.e.: web, online game, stock trading, telnet, etc.) with graphical data in PingPlotter. What kind of conditions should I be looking for in PingPlotter? I get occasional timeouts in applications I'm using - how do I know what's causing those problems? ![]()
0 Comments
Read More
Leave a Reply. |