We performed a comparison between Catchpoint and LogicMonitor based on real PeerSpot user reviews.
Find out in this report how the two Network Monitoring Software solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The single dashboard is a valuable feature."
"We can manage the entire system across the network and troubleshoot the pain points."
"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."
"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."
"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 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."
"The solution offers three different ways of slicing data to look for abnormalities."
"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."
"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."
"One thing that's very valuable for us is the technical knowledge of the people who work with LogicMonitor. We looked at several products before we decided to use LogicMonitor, and one of the key decision-making points was the knowledge of the things that they put in the product. It provides real intelligence regarding the numbers that you see on the product, which makes it easy for us technical people to troubleshoot. Other products don't provide you with such information. You see a value going up, but you don't know what it means. LogicMonitor provides such information. For instance, if a value goes up, it says that it is probably because your disk area was too low."
"We get full visibility into whatever the customer wants us to monitor and we get it pretty rapidly. That is very important. Only having certain metrics that other platforms will give you out-of-the-box means you only get a small picture, a thumbnail picture. Whereas with LogicMonitor, you get the entire "eight by 10 picture", out-of-the-box. Rather than some availability metrics, you get everything. You get metrics on temperature, anything related to hardware failure, or up and down status."
"We only have one monitoring tool, and that is LogicMonitor. It does pretty much everything we need under one roof. They are very good at rapidly releasing new features. It's not like we have to wait six months or a year between new features and data sources. There is very quick development. If there is something that doesn't do it for us, I know I can just raise it with support or our delivery representative, and there is a good chance that that will be looked at. If it's not too much effort, we will see it released in the next few months. So, the solution is very good from that perspective. We have everything in LogicMonitor."
"The alerting would be number one in my book. The thresholds for getting alerts for different criteria are pretty well-thought-out. We don't get many false positives or negatives on the alerting side. If we do get an email alert or some similar alert, we know that it is something that has to be looked at."
"The solution’s overall reporting capabilities are pretty powerful compared to ones that I have used previously. It seems like it has a lot of customizations that you can put in, but some of the out-of-the-box reports are useful too, like user logon duration and website latency. Those type of things have been helpful and don't require a lot of, if any, changes to get useful content out of them. They have also been pretty easy to implement and use."
"Another feature from the technical aspect, the back-end, is the ability to allow individual users or customers to have their own APIs. They're able to make changes using the plugins covered by LogicMonitor. That is a very powerful feature that is more attractive to our techno-savvy customers."
"LogicMonitor saves time in terms of its ability to proxy a connection through a device. For example, if you are troubleshooting a device, which you may want to connect to, you can proxy this connection through the platform. As a support resource, I don't need to use multiple platforms to connect to a device to further investigate the issue. It is all consolidated. From that perspective, it saves time because a resource now only needs to use one platform."
"LogicMonitor is good for getting a full view of your topologies. They have LiveMaps, which give you a visual representation of your infrastructure."
"The technical support needs improvement."
"The Wi-Fi side needs improvement."
"A large selection of nodes are available but it is a challenge to test reliably in China and the Middle East."
"The old user version was better, it was more user-friendly."
"There are essentially a lot of quotas. Nobody wants to sit and manually create monitors for someone who uses synthetic monitoring."
"We would like the script creation feature of this solution to be improved, as it currently requires a complicated manual process to update the scripts."
"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."
"Catchpoint can be improved by focusing solely on network 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."
"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."
"The only functional area I can think of that has room for improvement would be the dashboards. They could use a refresh. It would be nice if there were more widgets and more types of widgets."
"We would like to see more functionality around mapping of topologies, in terms of networks. An improvement that we would like to see is added functionality to get more detail out of mapping. For example, if the LogicMonitor Collector identifies a connection between two network endpoints, it would be great to actually see which ports are connecting the two endpoints together. That functionality is something we greatly desire. It would actually make our documentation more dynamic in the sense that we wouldn't need to manually document. If this is something that the platform could provide, then this would be a great asset."
"The process of upgrading some of the collectors has been a little bit confusing. I need to understand that better."
"LogicMonitor should always improve AI because we are always striving for real intelligence. An additional feature we'd like to see in the next release of LogicMonitor is more in the area of identification of when the dominant workload is working. There are certain devices and applications that have cycles of their own. Some are used primarily during prime time, and some are used during the overnight timeframe, and better identification and classification of those workloads would be helpful. For example, we could then do some more planning about, for this particular set of devices, as it has a prime time environment, and we don't want to see a 24-hour average, as we want to see what is the 75th or 90th percentile utilization during the prime time when it is being used, whenever that prime time is."
"Automated remediation of issues has room for improvement. I don't know how best to handle it, but I know that they're kind of working on it. I know there are some resources that can do automated remediation. I would like them to improve this area so it could be completely hands-free, where it detects an issue, such as, if a CPU is running high. There are ways to do it even now, but it's a bit more involved."
"Their Logs feature is quite new. It is not as feature-rich as we would like it to be. There have been a couple of conversations internally around other log management tools, like Splunk, which may do more for us than LM Logs. The benefit of LogicMonitor is that our staff know how to use it, so we don't really want to move away from it, if we don't have to. I fully expect there to be more development in this area. It is their newest feature, so it is understandable that it hasn't evolved as some of the other stuff. It would be good to see a bit more development in this area, but I think the monitoring side of things is spot on."
"One drawback of LogicMonitor is its licensing model, which requires an additional license for each module. For example, if you need to use Azure monitoring, you'll need an additional license on top of the base license."
"Some more application performance type monitoring would be nice. For example, an APM type solution, which would not necessarily completely replace it, but be able to tie into to what we're seeing on the application performance side so we can correlate what's going on with the application versus the underlying infrastructure."
More Juniper Mist Premium Analytics Pricing and Cost Advice →
Catchpoint is ranked 31st in Network Monitoring Software with 12 reviews while LogicMonitor is ranked 16th in Network Monitoring Software with 25 reviews. Catchpoint is rated 8.2, while LogicMonitor is rated 9.0. The top reviewer of Catchpoint writes "The UI is well designed, so it's easy to get the visibility you want". On the other hand, the top reviewer of LogicMonitor writes "We went from nothing to full visibility across our internal and external estates of equipment". Catchpoint is most compared with Dynatrace, ThousandEyes, Datadog, Splunk Enterprise Security and AppDynamics, whereas LogicMonitor is most compared with ScienceLogic, SolarWinds NPM, Zabbix, OpsRamp and SCOM. See our Catchpoint vs. LogicMonitor report.
See our list of best Network Monitoring Software vendors.
We monitor all Network Monitoring Software reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.