Catchpoint vs Rigor comparison

"The most valuable features of Catchpoint are basically the transaction monitors on the API and UI."

"The best feature in Catchpoint is the alert or the notification my company gets frequently, in particular, every five minutes. It's the notification you get whenever a respective market has an issue. There's also a dashboard in Catchpoint that shows the markets you support, so all the markets will be highlighted graphically in the dashboard whenever there's downtime that could affect you. If there's no issue for a specific market, it will be in green, so in this way, anybody would be able to understand which market has issues and which market has no issues through Catchpoint. The tool is very useful for monitoring activities."

"Catchpoint's customer service and support are valuable."

"Catchpoint provides a great amount of information."

"The thing I like most is the tech support in this company, because they have 24/7 chat support. We can chat immediately and ask them about an issue and they keep responding. They create tickets on our behalf and respond."

"The drill-down feature of this product was very good. It allowed us to identify the exact page or area of the site that was causing our customers an issue."

"Catchpoint helped us establish that something is in a provider network, so we could tell our customers to check their internet provider because the traffic is not getting to us. You need to be gentle when you tell them that, but the fact that we could do it was crucial."

"We really need the API monitoring, as well as client side session monitoring, the global synthetic monitoring, to track the availability of the systems from the customer side."

"The most valuable feature of Rigor is the ability to test the whole website, including the homepage design and all the sub-pages, in one test. It provides an overview of the whole service."

"Trending needs improvement. Currently, out-of-the-box, they provide only seven days availability. So, we have to do queries and we have to go into a separate analysis module, we have to run lot of queries to long-term trends."

"There are essentially a lot of quotas. Nobody wants to sit and manually create monitors for someone who uses synthetic monitoring."

"if we need to do performance analysis, we have to click too many times. For example, if there is an issue that is caught by Catchpoint, we need to understand what the error is and at which step it failed, or which transaction that is impacted. To drill down, we have to click too many things to get the answer."

"Catchpoint can be improved by focusing solely on network monitoring."

"The old user version was better, it was more user-friendly."

"There's still too much manual involvement in getting customized test configurations out there. It's good, but it still takes a lot of effort. In other words, it's when you need to configure it to collect a specific variable and that kind of thing."

"It would be great if Catchpoint could incorporate its alerting system instead of relying on separate tools like ServiceNow."

"A room for improvement in Catchpoint is that it lacks an automated page updating feature. My company receives all the alerts and notifications it needs, but the page doesn't update automatically. You need to manually refresh the page, so every five minutes you need to refresh it to see the most updated information. If there's an automated page refresh feature, that would help my company. It's a feature that Grafana has. The page auto-refreshes in Grafana, so you don't have to manually refresh the page. If that feature is implemented in Catchpoint, it'll be useful for the users. Another area for improvement in the tool is you have to do a manual task, for example, when you have a notification for a market, you get a zip code that the user could have entered, but if the zip code is incorrect, you have to manually go into Catchpoint and update that parameter, so that manual step is another area in the tool that needs improvement."

"I feel that Rigor can improve their customer service for time zones outside of the United States. When I post a question on their chat, I usually need to wait a couple of hours for the answer. I believe the service desk is in the United States, while I am working in Europe, requiring me to wait for them to start their work day."

"The solution's pricing is comparable to the last tool we were using."

"In terms of licensing fees, I believe they were slightly higher."

"The solution's pricing varies based on services and licensing models."

"The pricing is based on consumption and works on a point scale. For example, let's say I want to look at www.google.com, and I'm going to test it to see if it's there. It will bring back all this data that tells me how long it took to connect and how long it took to get the first byte. It will list all the resources on the page, showing that they all work and there are no broken links. It brings that data back. That test has an assigned point value depending on what you decide to extract from that test. If all I do is check to see whether it's available, it might be one point. I don't know the exact point values off-hand. This is just an example."

"The price and licensing are very, very high. They have to come down on the pricing to match with the industry standard."