I wasn't really referring to the described bug (glad its being fixed tho - since you lose trace history when you have to reset and restart - I often start a separate trace and pause the crashed one so I can preserve its history)
I was referring to the limitation of the remote agent that, say in a 30 second outage between the console and remote agent:
- The remote agent doesn't receive any instruction(s) to trace, and/or
- the remote agent doesnt retain any data from traces it does do
- ultimate causing no data to be displayed for the 30 second outage between the console and remote agent
I am suggesting Pingman find a way to overcome this limitation.
Obviously to accomplish this the remote agent would have to be made a little more complex and have the ability to:
- receive and store a list of trace instructions from the console
- act on those instructions autonomously for a certain period of time during disconnects (say 1 minute)
- Buffer the data from those traces made during the brief 'outage'
- transmit the buffered data back to the console (either on request or sensed reconnect)
- and either incorporate that data back into the 'ongoing' trace at the console, or even be able to display it as a separate trace - just so that data can be viewied.
I realize all of that would add quite a bit to the remote agent, and I know its important to keep the agent as light as possible.
But the remote capability is a great tool that suffers from that one big flaw: the time you really need its data the most - during network problems between the console and remote agent (which usually means when the remote user is having some sort of issue) - its not there for you.
If its just a problem with suddenly long latencies and/or high jitter, its ok, but for a period of sustained packet loss, you're blind: was it something in the users home network? was it the user's ISP? was it coming into the edge vpn device? you dont know.
As mentioned in the original post, we've worked around the issue by having the user install a free version of pingplotter, then email snips from it back to us.
It works but its very cumbersome for everyone involved. A built-in solution would be great!
Thanks for the great tool, its been a big help to us! I'm just suggesting something that I think could make it even better.