We performed a comparison between ControlUp and LogicMonitor based on real PeerSpot user reviews.
Find out in this report how the two IT Infrastructure Monitoring solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."ControlUp has an easy installation process."
"ControlUp has some good functionalities, such as remotely pushing scripts in the device through the tool."
"When using ControlUp, the core feature that we have found valuable is its UI. It is a valuable tool to view the analysis reactions of a base core Level 2 or Level 1 team so that they can complete the necessary troubleshooting."
"It has a great career time monitoring tool."
"It shows you so many details of what's going on in that log-on that, if there's a problem, you can identify it in five minutes."
"Security, uptime, and reduced capital expenditures are the main reasons we use ControlUp. So basically, the money that we consume is based on the amount of time we are using a service."
"The most valuable feature is the granularity of visibility into the resources that are in use by our applications."
"The most valuable features in ControlUp are endpoint monitoring and the many features that are available."
"LogicMonitor added AI technology to help understand what's normal and that has helped quite a bit, so that's the feature I found most valuable in the product. The product is also doing quite well with identifying devices and customizing a particular Cisco version or model number. LogicMonitor continues to be active in updating what is available to be monitored, and it's been very good with keeping those things current, so that's another valuable feature of the product."
"LogicMonitor helps us prevent potential downtime. It's pretty good. It generates low-level warnings that aren't necessarily preemptive but can still alert us to issues we should investigate. These warnings allow us to correlate data and identify areas where we should take action, even if the issues aren't critical."
"The breadth of its ability to monitor all our environments, putting it in one place, has been helpful. This way, we don't have to manage multiple tools and try to juggle multiple balls to keep our environment monitored. It presents a clear picture to us of what is going on."
"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 plugins are easy to integrate, and LogicMonitor provides these add-ons for vendors like VMware. It becomes very easy to integrate them and take the data sources."
"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."
"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."
"Whenever we reach out to our customers, we give LogicMonitor as a dashboard to them so they don't need to monitor the hardware side separately. For example, if my service is running on their hardware X, that means they don't need to monitor hardware X and our services too. LogicMonitor has the capability of monitoring their hardware as well as our services. This is how LogicMonitor helps us."
"This solution be improved by including load throttling tools. For example, I can identify a service where we spend a lot of CPU but I cannot restrict the service from ControlUp. I have to use another tool like AppSense."
"Integration is always a problem, and we feel that we are doing our best and the service provider thinks they are doing their best. I guess if ControlUp's system could be more capable or if people could understand the integration part, that would be better."
"ControlUp could improve the integration. Microsoft Azure Virtual Desktop monitoring has better integration."
"The most common complaint that I have heard, at least within our organization, is about reporting. They have their own reporting. It's just that it doesn't yet include everything that you can look at within the application. You can only report on specific metrics or collections."
"There was some lag earlier, and reports pulled from the dashboard would sometimes be half an hour old. But now, the information provides real-time status, which is greatly appreciated. Overall, I've seen improvement in the product."
"We'd like to see the mobile app working again so that we can get alerts 24/7. This is especially useful for the person on call."
"It can be improved by including script-based scheduling."
"Most reports give information about the top 100 devices, but not all of the devices."
"LogicMonitor's reporting capabilities definitely could use an improvement. We have made do with the dashboarding and done what we can to make that work for our customers. However, there are definitely customers who would like a PDF or some kind of report along those lines, where we have been utilizing other tools to provide them. The out-of-the-box LogicMonitor reporting is the only thing that we have been less than impressed with."
"The topology mapping is all based on the dynamic discovery of devices that could talk to each other. There is no real manual way that you can set up a join between two devices to say, "This is how this network is actually set up." For example, if you have a device, and you're only pinning that device and not getting any real intelligent information from it, then it can't appear on the map with other devices. Or if it can appear, then it won't show you which devices are actually joined to it."
"LogicMonitor has good features, but the ease of use is a little bit confusing. Additionally, we are looking for workflow automation, which is a little bit tricky for LogicMonitor."
"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."
"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."
"There is a lack of automation, especially in terms of remediating problems. The problem is seen and identified, but there is a need and a gap where LogicMonitor can help us automate the remediation of the problem."
"LogicMonitor should improve its logging features. It can become expensive and should be cost-effective. It would be great to see prebuilt templates for alerting methods in LogicMonitor that are similar to the prebuilt dashboards. Currently, users have to build their alerting configurations."
"The ease of use with data source tuning could be improved. That can get hairy quickly. When I reach out for help, it's usually around a data source or event source configuration. That can get challenging."
ControlUp is ranked 22nd in IT Infrastructure Monitoring with 11 reviews while LogicMonitor is ranked 14th in IT Infrastructure Monitoring with 25 reviews. ControlUp is rated 8.6, while LogicMonitor is rated 9.0. The top reviewer of ControlUp writes "Great for troubleshooting and reporting with a controller that allows for configuration comparisons". 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". ControlUp is most compared with Nexthink, Goliath Performance Monitor, Liquidware Stratusphere UX, eG Enterprise and PRTG Network Monitor, whereas LogicMonitor is most compared with ScienceLogic, SolarWinds NPM, Zabbix, OpsRamp and AppDynamics. See our ControlUp vs. LogicMonitor report.
See our list of best IT Infrastructure Monitoring vendors.
We monitor all IT Infrastructure Monitoring 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.