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
SolarWinds Engineer's Toolset
Score 8.0 out of 10
N/A
SolarWinds® Engineer’s Toolset (ETS) helps users monitor and troubleshoot a network with over 60 tools for network management. ETS allows users to monitor and receive alerts in real time on network availability and health, and perform network diagnostics for faster troubleshooting and resolution of complex
network issues. With ETS users can deploy an array of network discovery tools including Port Scanner, Switch Port Mapper or advanced Subnet Calculator, manage Cisco®
devices with specialized…
$1,585
Per Instance
Pricing
Catchpoint
SolarWinds Engineer's Toolset
Editions & Modules
No answers on this topic
One Time Price
$1,585
Per Instance
Offerings
Pricing Offerings
Catchpoint
SolarWinds Engineer's Toolset
Free Trial
No
Yes
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.
I have found the toolset especially useful for scanning subnets to discover devices, and for setting up temporary real-time monitors when we are troubleshooting or setting up new connections. The most useful aspect has been the ability to apply the tools to help troubleshoot and pinpoint intermittent issues. More general tools like Orion often do not have the granularity to detect issues like intermittent packet loss which are especially impactful to applications like Voice. The toolset gives us another level of capability to dig into issues.
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.
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.
The unifying component that is intended to be the initial interface to the tools seems clunky. I prefer to start the tools individually rather than using it.
The port scanner could use some improvements to make it easier to use.
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.
I haven't compared any tools similar to SolarWinds Engineer's Toolset. This might be because I'm pretty biased when it comes to monitoring, and reporting solutions. I've found that SolarWinds provides the biggest bang for the buck in my opinion. I'm sure there are other solutions on the market that compete, but I haven't tried any of them because I've been very satisfied with SolarWinds.
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
