Ability to set parameter windows on things like ping times
Status: Beta
Brought to you by:
brainarmada
Menu
▾
▴
#2 Ability to set parameter windows on things like ping times
Currently, the program lists "Success" and "Failures" rates, but I'm actually dealing with problems where the "Trip Time (ms)" is extremely long (on the order of 2000-3000+ ms), yet the packet does get through. So this doesn't really register as a "failure", though it makes the link fairly unusable for large portions of time.
It would be nice to have an option to set an "acceptable window", above which it would either trigger an alarm, or start another counter, similar to "failures", but perhaps like "degraded performance", etc. So, if I could set it to trigger any packets with a Trip Time above, say, 250ms would trigger an alert. Possibly even multiple levels like this which we could specify, so for example, you could say "Below 250ms = fine / 250-500ms = degraded / 500-1000 = really bad / 1000+ = unusable ("failure")."
These ways to tag and specify ranges, along with the logging request I just added, would make a nice addition to capabilities in a future version, and could help people do time-range analysis, rather than simple real-time and aggregate "success since start" reporting.
I quite like the program! Thanks for a cool tool! :-)
Nice suggestion, we'll try to implement it. Meanwhile we added in version 0.5 a timeout setting which allow you to change the time to detect a failure.
Awesome! Thanks, Brain!
I just got the new version, and I see the "Ping Timeout" entry in the Settings tab. I'm running it now, and (surprisingly!) my network is behaving itself perfectly at the moment, so I haven't seen it trigger, yet. But I'll definitely keep an eye on it!