Catchpoint vs. Elastic Observability

Proactive Website and API performance testing, Synthetic monitoring, and third-party integration are where Catchpoint is best suited. Catchpoint is less appropriate in Deep Application Performance monitoring, debugging complex user journeys in real-time, Small businesses, and Mobile app performance monitoring. These are the scenarios where I find Catchpoint is well-suited and scenarios where it is less appropriate.

Incentivized

We can use this Elastic Observability in our business problems such as Creating internal/operational efficiencies issues, customer relations/service, and business process outcomes issues. This product has a lot of features for the above problems. But this product may be having some issues when charting purposes. But it can adjust for that purpose.

Incentivized

• Catchpoint Synthetics: We create our synthetic monitoring using catchpoint. Creating the synthetics monitors are easy and requires basic knowledge on selenium and javascript. It allows you to run the test from external(backbone) and internal enterprise nodes. The screenshot and filmstrip feature is an add-on along with various customisations. Once created, It provides a detailed insight of each request that is involved in the application flow which helps us in addressing the issue at the request level.
• Catchpoint API Test: This is another kind of test which we have explored in our organisation. This has helped us to maintain the health check of our APIs and also we have utilised it for a variety of our use cases.
• Catchpoint Dashboard: This is our one-stop shop for all our monitors. It has multiple widgets that displays various application performance metrics. We use this feature immensely and it is of great value to the business.
• Catchpoint UI: It is very user friendly and with basic introduction anyone can just get started with it.

Incentivized

• Open source code base
• Community support
• Is fast in processing

Incentivized

• 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

Incentivized

• Difficult to setup/maintain
• Search pattern bar could be more user-friendly
• Premium subscription features are very expensive

Incentivized

we are heavily dependent catchpoint system for the following functions * Detect end-user availability/performance-related problems * Ensures
service level objectives (SLO) are met, that prevents service level
agreement (SLA) breaches * Identify and understand the cause of any
network connectivity or application level issue * Improves the
availability and response time service levels

Incentivized

It's hard to find the functionalities that I am looking for in the application. Even if I did something in the past, after a time I have to re-learn again where the functionalities are. This is a powerful tool, but not user-friendly. Texts in the buttons and menus are not always meaningful or easily comprehensible.

Incentivized

The customer support is fantastic as they keep you updated and follow up even though we may not even follow up. Make sure they send a communication so that we remain updated. They value engineers who will get on a call with you to understand any requirement we have on any test, and they bring in the best developers on call.

Incentivized

very easy to implement as the product is user-friendly

Incentivized

Smart Bear Foglight Dynatrace CEM Catchpoint: I have used many synthetic monitoring products. Honestly, there are no big differences in features among all the products listed above or that I have used before. Probably, price and support might play big roles in selecting the products. I do not know the prices of these products.

Incentivized

Splunk is a very good product but the licensing costs are high; we utilise the best of both worlds by using both products for slightly different purposes. We put the voluminous data with simple use cases in Elastic where it doesn't cost too much and can be searched quickly while putting the less voluminous data with more complex use cases in Splunk so we can take advantage of Splunk's very comprehensive but often much slower SPL search query language

Incentivized

• The ROI has been very good with this product, we have seen multiple folds of time-saving by using this tool and preempting any risk associated with non-performant times of our server, hence increasing the team's capability to respond to certain downtime scenarios and the level of action that needs to be taken.
• Catchpoint’s observability solution makes it easier to have global visibility of our website's performance and to fix issues quicker
• I don't have any negatives, every good product comes with a cost, that is the fact but the Catchpoint tool has ultimately improved our ROI much beyond the changes that we pay

Incentivized

• Cost management.
• Good customer increment.
• Time management.

Incentivized