#Pingplotter number of times to trace pro

Nessoft, bless their hearts, haven’t documented the RESTful calls that can be made to PingPlotter’s Web server, so we’re just going to have to poke around a bit. Here’s what the default Web output looks like:Īh! If you can set a new host to trace through the UI then you can add that and anything else the UI permits from a command line with curl, an incredibly rich tool that lets you make protocol-based requests including HTTP and is available for just about every platform other than vacuum cleaners and toasters. This nifty addition lets you expose the PingPlotter display, albeit in a slightly condensed form, to a Web browser or to be used with simple command line tools to get data and configure the application.

#Pingplotter number of times to trace pro

This latter facility would be great except for the fact that it uses the Windows Scripting host, which is not a platform I particularly care for, and the API isn't documented except by a number of scripts (decoding them seemed like a lot of work).īut wait! The Pro version of PingPlotter (cheap at $199.95) has a built-in Web server. PingPlotter is, as I discussed, extremely useful for this kind of problem or, indeed, as just a general host availability monitor, and in its bag of tricks is the ability to be scripted.

As I explained, it looks like AT&T default DNS servers are behaving badly and I’m waiting to hear back from the “powers that be” at AT&T.

Last week I wrote about PingPlotter and my quest to diagnose AT&T U-verse’s flaky service.