hJon wrote:We're using a "big-name" monitoring solution that is based on HTTP tests of our website, and our new application runs AJAX and now the monitoring doesn't work. Do we have to give up our "big-name" reporting solution to get a benefit from eValid?
No, there's no reason to give up the "big-name" monitoring solution. You probably are used to how it works
and how it appears, so keeping it running is a good thing.
What we usually recommend, when the old HTTP-based systems begin to fail because the applications have switched to AJAX, is to use eValid agents to collect the required performance data -- and issue performance alerts via email or text messages -- and graft the data into the existing reporting scheme.
We've done this for a variety of different reporting systems, ranging from the open source solutions (like GWOS) to the one from the "big-name" firm you're dealing with. We're sure we can do it with your system.
eValid runs perfectly reliably from an windows machine -- including one that is running in the clout -- and feeds data about how AJAX applications perform that you can't measure any other way.
eValid Monitoring Team