Catchpoint is an Internet Resilience solution offering services for retailers, Global2000, CDNs, cloud service providers, and xSPs that help increase their resilience by catching any issues in the Intenet Stack before they impact their business.
$10,000
per year
DX Application Performance Management
Score 9.0 out of 10
N/A
DX Application Performance Management (formerly CA APM, or CA Application Performance Management) is an application performance management platform designed to correlate and analyze data in real-time. DX APM supports hybrid environments and customizable failure thresholds.
N/A
Pricing
Catchpoint
DX Application Performance Management
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Catchpoint
DX Application Performance Management
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
- White glove migration services
- Annual subscription
- Professional Services
- Competitive Benchmarking
I like the synthetic test feature it has from the edge which mimics the real user - that for me is one of the best features. The certificate expiration, the API monitoring, the slowness breakdown to show where the slowdown happens, and more.
CA Wily is well suited for monitoring the load balanced application nodes and determine their main performance bottlenecks like if problem exists in heap or in some connection issues. But I think when it comes to providing the entire report of the application, it is less appropriate as there is no way to create the entire report of the test for all the counters monitored. Also there is no way to detect some issues based on the system configuration.
Our standard operating material documents Catchpoint’s breadth on HTTP/Browser, API, Streaming, DNS, FTP, TCP, SMTP, Ping, Traceroute, SSH with content validation and custom widgets/dashboards. This gives SREs and L0/L1 a single place to validate both page flows and the underlying network/application protocols.
Product runbooks use Catchpoint to validate critical steps (for ex, login, overview dashboard, unit dashboards) and to detect DNS issues that break those journeys. so we catch experience regressions even when the backend looks healthy.
We’ve standardized Catchpoint alert categories/templates with ITSM so L0 includes the right analysis in handoffs. This tightened “first message, best message” during incidents.
Our operating procedures use Catchpoint for alwayson availability checks with email notifications and multi‑location verification when a site is down. This is useful for unambiguous “is it up/where is it failing” signals.
Visualization of the metrics and data presented to provide a unique and attractive interface.
Flexibility to manage actions and commands that we deem important for each application. The ability to define these and customize the metrics reported for each individual application is huge for us.
Missing Functionality: For our organisation, we use multiple observability tools and what we miss in Catchpoint is its ability to display a list of muted monitors in the dashboard. This was a business requirement for our company where the business wanted to know at any given point of time, a list of monitors that were muted during an outage or a scheduled maintenance. This feature was unavailable in Catchpoint, however, we hope to see some enhancements in the future.
We are facing challenges to meet RFP requirements in few areas where I would recommend CA to improve.
We are facing challenges for non (java and dotnet application) which CA APM does not support. SAP is another solution where CA APM is not able to address our business requirement.
The Catchpoint tool has now become an integral part of our DevOps toolkit due to its extensive range of capabilities, including application performance monitoring, network health tracking, DNS visibility, and edge performance analysis. Its seamless integration with our existing monitoring infrastructure has significantly enhanced our ability to detect potential issues proactively, analyze root causes in real time, and resolve incidents much faster, ultimately improving overall system reliability and user experience.
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.
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.
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.
We only have 1 application using DX APM, while most of other applications are instrumented using Dynatrace. Dynatrace provides a better monitoring and instrumentation for applications. The required effort to setup monitoring capability using DX APM is way more work compared to Dynatrace, also the amount of KPIs offered from Dynatrace is more than DX APM.
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
Introscope is deeply utilized within the organization. However, CEM and Team Center not as much. Those that use one piece don't generally use the others. Partially because of the curve in learning how to use the consoles effectively.
reporting is pretty well configured and easy to setup if you know how to use the tools. So this can be easy to use and takes less time to configure for the different groups within the organization.
