No more typing reviews! Try our Samantha, our new voice AI agent.

LogicMonitor vs Loom Systems comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Oct 9, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

LogicMonitor
Ranking in IT Infrastructure Monitoring
8th
Average Rating
9.0
Reviews Sentiment
7.1
Number of Reviews
34
Ranking in other categories
Application Performance Monitoring (APM) and Observability (13th), Network Monitoring Software (6th), Container Monitoring (4th), Cloud Monitoring Software (7th), AIOps (5th)
Loom Systems
Ranking in IT Infrastructure Monitoring
61st
Average Rating
8.0
Reviews Sentiment
6.9
Number of Reviews
4
Ranking in other categories
Anomaly Detection Tools (5th)
 

Mindshare comparison

As of March 2026, in the IT Infrastructure Monitoring category, the mindshare of LogicMonitor is 2.8%, up from 2.2% compared to the previous year. The mindshare of Loom Systems is 0.5%, up from 0.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
IT Infrastructure Monitoring Mindshare Distribution
ProductMindshare (%)
LogicMonitor2.8%
Loom Systems0.5%
Other96.7%
IT Infrastructure Monitoring
 

Featured Reviews

Anshuman Thakur - PeerSpot reviewer
Site Reliability Engineer at a comms service provider with 501-1,000 employees
Monitoring has reduced downtime and now enables proactive alerts across cloud workloads
When it comes to the improvement of LogicMonitor, I think there are a few points that can be improved. The first one is alert tuning, which takes time. It requires effort when trying to understand it for the first time. The defaults do not always match our workload patterns, so I have to adjust the thresholds to reduce noise and avoid alert fatigue. While the dashboards are solid, I sometimes wish that the UI was a bit more intuitive when drilling down quickly during an incident. There are many options and finding the exact view where I can identify the exact problem takes a few extra clicks. When an alert comes and I click on a LogicMonitor alert, it takes time to understand what the alert actually is and to go through the data points. The alert page specifically could be better. The alert tuning part can also be made more simple. The first area that could be better is alert clarity and routing. Sometimes alerts do not include enough immediate context, so I still have to spend a few minutes correlating data across views. Adding more actionable details directly in the alert would make the response even faster. LogicMonitor sometimes gives false alerts as well. For example, if an EC2 instance is down, it will not determine whether the EC2 instance has been deliberately turned off or if it is actually not responding. At that time, it will give false alerts. The clearing of alerts is also an issue. Once an issue is fixed, the alert should be cleared, but it takes a little time for that alert to be cleared. Another improvement that would be helpful is simpler customization for complex dashboards. It is powerful, but building highly tailored dashboards, especially across multiple environments, can feel heavy and time-consuming. I would also appreciate a stronger out-of-the-box AWS correlation, such as automatically grouping related issues across EC2, EBS, and ALBs in a way that reads as a single incident story. This would reduce the mental overhead during outages. Grouping incidents together, such as all the EC2 alerts, all the EBS alerts, or all the load balancer alerts would be beneficial. Overall, none of these are blockers, just some improving areas. There could be smarter anomaly detection out of the box that can catch unusual but important behavior without manual tuning of every threshold. Better tagging and dynamic grouping for EC2 instances would also be helpful. Cleaner alert de-duplication so a single underlying issue does not generate multiple redundant alerts would improve the system. More guided root cause workflows would be beneficial, such as providing the most likely causes based on correlated metrics. Faster search navigation across devices, dashboards, and alerts during incidents would also improve the platform.
Keerthi Kumar Sangaraju - PeerSpot reviewer
Technology Manager at a tech services company with 10,001+ employees
Stable, easy to set up, flexible, and has multiple functionalities, but needs to define priority levels for each incident
What's lacking in Loom Systems is the level of priority for each incident. For example, after implementation and there was a huge impact on the client, and the client comes back to you and says that there's an incident, that there needs to be an immediate resolution for it, you'll see severity one, severity two, etc., in Loom Systems, rather than priority levels. It would be better if the incidents can be defined as low priority, medium priority, or high priority.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"LogicMonitor has actually helped reduce our downtimes, helping us reduce downtime to about 40 to 50% by warning us before servers get heavy on usage or CPU load so we can take action in advance."
"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."
"LogicMonitor gives us visibility into issues that we didn't even know existed."
"LogicMonitor really improved our workflow as a company."
"Compared to other monitoring platforms I've used in the past, LogicMonitor seems to be the most powerful and robust that I've dealt with."
"LogicMonitor enables us to consistently really wow the customers by sorting that out."
"It's the depth of data that it gathers that I find really useful because there's nothing worse, when you're trying to find information about something or dig deeper into something, than hitting the bottom of the information really quickly and not having enough information to work with. With LogicMonitor, there is a load of information to dig through. It's a really good solution for that."
"It is a really solid tool for the on-premises, physical and virtual infrastructure; I have had nothing but good things to say about it, and it has been a pleasure using it for those use cases."
"What I like best about Loom Systems is that you can use it for infrastructure monitoring. I also like that it's a flexible solution."
"You can develop your own apps within Loom, and they can be configured very simply."
"The solution is absolutely scalable."
"What I like best about Loom Systems is that you can use it for infrastructure monitoring and that it's a flexible solution."
"The solution is very scalable; a company wouldn't have any issues expanding it if they needed to, and we have a few thousand users on the solution."
"The RFS portion of the solution is the product's most valuable feature."
"Bringing Loom in ensures that the incident process, request process, change, all of these processes are improved."
"The solution is absolutely scalable. If an organization needs to expand it out they definitely can."
 

Cons

"It needs better access for customizing and adding monitoring from the repository."
"One thing I would like to see is parent/child relationships and the ability to build a "suppression parent/child.""
"LogicMonitor should always improve AI because we are always striving for real intelligence."
"Automated remediation of issues has room for improvement."
"The reporting capabilities are within average."
"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 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."
"LogicMonitor has a very steep learning curve."
"The discovery and mapping still takes a lot of human intervention, it's quite resource heavy, especially in the initial setup which can take six months of work, especially when you have a large estate that you're dealing with."
"The change management within the solution needs to be improved. There needs to be more process automation."
"The reporting is a bit weak."
"What's lacking in Loom Systems is the level of priority for each incident. For example, after implementation and there was a huge impact on the client, and the client comes back to you and says that there's an incident, that there needs to be an immediate resolution for it, you'll see severity one, severity two, etc., in Loom Systems, rather than priority levels. It would be better if the incidents can be defined as low priority, medium priority, or high priority."
"The change management within the solution needs to be improved. There needs to be more process automation."
"The reporting is a bit weak. They should work to improve this aspect of the product."
"The discovery and mapping still takes a lot of human intervention, it's quite resource heavy,"
"What's lacking in Loom Systems is the level of priority for each incident."
 

Pricing and Cost Advice

"In terms of pricing, I would rate LogicMonitor four out of five."
"We are on an enterprise license plan, we are paying $7.75 per device a month. That is for a commitment of 350 devices. Anything that is over the 350 is charged at 1.2 times the rate; 1.2 times $7.75 would be the overage charge. We are looking at increasing our commitment to either 450 or 500 devices. It changes our pricing if we go to 450 devices, bringing it from $7.75 down to $7.70. If we go for 500 devices, it brings it from $7.75 down to $7.50. We will probably factor in the volume discount drop from $7.75 to $7.50 in our decision of whether we uplift or not. We also have some cloud monitors, which are about $500 a month."
"It's affordable. The price we get per license is a lot cheaper than what we were getting with some of the other tools. There are other monitoring tools out there that are cheaper, but what you get with LogicMonitor, out-of-the-box, makes it worth the cost."
"We have definitely seen ROI with LogicMonitor. We used to provide 24/7 IT support for our users. We have since been able to change to operating just within normal business hours for IT support, and LogicMonitor was a large part of being able to accomplish that."
"The pricing can be a little aggressive. Right now, it's a bit much for smaller organizations to adopt it. But comparatively, it also provides good features."
"As a managed services provider, the licensing model that LogicMonitor provides us is excellent. We are able to scale up and scale down as needed. The pricing is reasonable for the amount of features and support that they provide."
"The solution is not expensive."
"It is pretty expensive, but we now need one less full-time engineer. With on-prem, we used to have one more engineer in our department. That engineer has now moved to another department. Our capacity is better with this product than the previous one. It is easy for us to manage the sites. You have to choose between the standard account and the premium account. With the premium account, you get a lot more than the standard one, and you can also buy some extra features. It is a good thing to look at them because you would probably want to buy them. You should take your time and negotiate the price. They are easy. Like all cloud providers, they are able to discuss the price and if necessary, change the price."
Information not available
report
Use our free recommendation engine to learn which IT Infrastructure Monitoring solutions are best for your needs.
885,311 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
11%
Computer Software Company
10%
Financial Services Firm
9%
Healthcare Company
8%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise11
Large Enterprise11
No data available
 

Questions from the Community

What is the best network monitoring software for large enterprises?
It actually depends on the exact purpose or requirements. Some tools are better for only network devices while others are better from a cloud monitoring or APM monitoring perspective. You can check...
What do you like most about LogicMonitor?
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 ...
What is your experience regarding pricing and costs for LogicMonitor?
I researched the pricing of LogicMonitor, and it costs around ten dollars per device per month, which is somewhat expensive compared to other products. Some monitoring tools such as Zabbix are free...
Ask a question
Earn 20 points
 

Comparisons

 

Overview

 

Sample Customers

Kayak, Zendesk, Ted Baker, Trulia, Sophos, iVision, TekLinks, Siemens
Citrix, Amdocs, Sysaid, Hexaware, Effibar, Revtrak, Taptica
Find out what your peers are saying about LogicMonitor vs. Loom Systems and other solutions. Updated: March 2026.
885,311 professionals have used our research since 2012.