Is the decision to leave ping, tcp, and udp tests out of the RMA, a developement timetable issue, a techincal issue, or simply a choice.
RMA support tests
Here is the original post before I reread it and thought it was a bit agressive, not to mention lengthy.
----------------------
Two reasons it is desireable to include
More and more corporate firewalls are being implemented, not all are in one's control. Even if the firewall is in one's control, it is more secure to only open one port for RMA than to open each port needed, or the ip of the HM. Or to pass it over an already open port. And even if you could and would, there is no way to monitor servers on an intranet private network (i.e. non-routable addresses). VPN would work for one site, but not multiple.
Secondly, if the RMA pings machines on the local network, most results will be less than 10ms. If a server slows to 100ms, you see a problem. If you are relying on public networks for monitoring remote sites, that 100ms may become marginally small and overlooked. So instead of catching a potential problem, you must wait for all out failure.
I think the above are going to be universsal concerns at the enterprise level of any organization that supports branch offices across the country.
Personally, I an testing over a modem at the moment, and openning your pricing page was enough to fail half a dozen ping test at a 5000ms time out.
And as soon as I choose a highspeed internet provider outside the campus firewall, ping is blocked at the campus edge.
----------------------
Two reasons it is desireable to include
More and more corporate firewalls are being implemented, not all are in one's control. Even if the firewall is in one's control, it is more secure to only open one port for RMA than to open each port needed, or the ip of the HM. Or to pass it over an already open port. And even if you could and would, there is no way to monitor servers on an intranet private network (i.e. non-routable addresses). VPN would work for one site, but not multiple.
Secondly, if the RMA pings machines on the local network, most results will be less than 10ms. If a server slows to 100ms, you see a problem. If you are relying on public networks for monitoring remote sites, that 100ms may become marginally small and overlooked. So instead of catching a potential problem, you must wait for all out failure.
I think the above are going to be universsal concerns at the enterprise level of any organization that supports branch offices across the country.
Personally, I an testing over a modem at the moment, and openning your pricing page was enough to fail half a dozen ping test at a 5000ms time out.
And as soon as I choose a highspeed internet provider outside the campus firewall, ping is blocked at the campus edge.
We just need time for testing...