Catchpoint vs Mezmo comparison

"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."

"Catchpoint is very flexible and also provides logs for troubleshooting purposes. It helps us fix issues within the SLAs signed with the end users. The tool is easy to learn."

"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."

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

"The product's most valuable feature is the ability to identify and troubleshoot network issues."

"During business hours, it has worked absolutely fine without any issues."

"One of the features, the scatter plot, is very useful. It shows red dots wherever there are issues."

"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."

"LogDNA consolidates all logs into one place, which is super valuable."

"The solution aggregates all event streams, so that if there are any issues, it's all in the same interface."

"The product could include global monitoring and predictive analytics to identify widespread issues and cyber threats."

"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."

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

"A large selection of nodes are available but it is a challenge to test reliably in China and the Middle East."

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

"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."

"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."

"As part of the improvement, there are certain categories, like for the China market, where we face issues."

"Every once in a while, our IBM cloud operational implementation gets behind. Sometimes, when we have a customer event, we do not get access to the latest logs for about 30 minutes, particularly for the sites that are heavily utilized. This is clearly not good. It is impossible to RCA when you can't look at the logs that pertain to the time period in which the event occurred. It could be more of an operational problem than a feature problem. I don't have visibility about whether it is a LogDNA issue or just an operational issue."

"No ability to encapsulate a query or a filter, and communicate or share that among the team."

"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 solution's pricing varies based on services and licensing models."

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

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

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