1. Home
  2. Digital Experience Monitoring (DEM) Tools
  3. Catchpoint Reviews
  4. User Review of Catchpoint
Monitor your web properties with a market leader
May 01, 2023

Monitor your web properties with a market leader

Anonymous | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Overall Satisfaction with Catchpoint

To monitor internal and external websites that are important for the Company
  • Easy to login with SSO
  • Easy to review the test runs over the last hour or specific time period
  • Easy to check the results of any Catchpoint test that ran. This helps to understand why the test results may or may not be what is expected
  • I can't wait for the new Symphony UI to be completed because it is so much richer that the previous UI
  • The ability to monitor the Catchpoint nodes with the ability to setup a take a recovery action based on specific criteria
  • The ability to tell us when we are at X% capacity so that we better plan or budget for increasing the "capacity" of the Catchpoint nodes before we get to an overloaded state. The capacity utilization graph is not a reliable indicator for this metric. How can the capacity utilization rate get above 100%, it does not make sense
  • Catchpoint is not the only monitoring tool we use for our web properties. The test alerts raised by Catchpoint serves as a confirmation of possible outages/problems with an application. This has helped to reduce false-positive alerts thus improving the response of the operations team; they don't have spend time chasing ghosts
  • The unlimited scheduled tests we can run on the enterprise nodes has been a very cost effective solution compared to similar web monitoring tools
  • The ability to quickly dive into the test result details help to get to the root cause of a test failure quickly
In general, Catchpoint support has been responsive to the initial ticket opening but when we get into an issue that may require an escalation it can take a longer time than expected. We would get the canned response "the issue has been escalated to XXX team and we will provide an update as soon as we get a response from them". I understand that some solutions may take some time but it would be better if we can get a response like "the issue has been reviewed and a solution is expected by MM/YYYY so that I can tell my customers that they can expect a solution by a certain date, even if the date is not met for one reason or another.
After the initial purchase, we were provided with access to the Catchpoint scripting team if/when necessary to make the transition faster. We did ask about the best practices for how we should arrange the scripts or for writing the scripts but we never received a best-practice document or guidelines. This was a few years ago so hopefully, the product has now matured and can provide future customers with a best-practice document today.
Both products are similar and have similar challenges but the Dynatrace pricing model is not as competitive as Catchpoint.

Do you think Catchpoint delivers good value for the price?

Yes

Are you happy with Catchpoint's feature set?

Yes

Did Catchpoint live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of Catchpoint go as expected?

Yes

Would you buy Catchpoint again?

Yes

The UI is very rich and allows the user to get into as much detail as they may need to analyze a test result. If a Catchpoint node is assigned to a specific division, say divisionA, it should NOT be available for users of divisionB to schedule to run scripts or even for running instant tests. Basically, users of divisionB should only be allowed to schedule scripts on divisionB nodes as well as to run instant test only on divisionB nodes. In the main division aka client division, Catchpoint admins should be able to BOTH see the performance of the Catchpoint nodes for all divisions as well as the ability to run an instant test against any division. Currently, a Catchpoint admin can see the performance of all the Catchpoint nodes but need to switch to divisionB (say) to be able to run an instant test on a divsionB node. Users with non-admin Catchpoint roles should NOT be allowed to do this. For easier maintenance, we need the ability to copy/move scripts from divisionA to divisionB, currently we can only copy/move scripts within the same division only.