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
8.8
Reviews Sentiment
6.9
Number of Reviews
49
Ranking in other categories
Application Performance Monitoring (APM) and Observability (9th), Network Monitoring Software (6th), Container Monitoring (4th), Cloud Monitoring Software (5th), AIOps (6th)
Loom Systems
Ranking in IT Infrastructure Monitoring
65th
Average Rating
8.0
Reviews Sentiment
6.9
Number of Reviews
4
Ranking in other categories
Anomaly Detection Tools (4th)
 

Mindshare comparison

As of August 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.3% 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

"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 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."
"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."
"LogicMonitor basically gives you the ability to monitor the infrastructure side of your application ecosystem."
"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."
"One of the key reasons for going for it was the knowledge of the things that they put in the product."
"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."
"Because we are now a structured managed services organization using one common platform for observability, we have seen significant benefits from using LogicMonitor."
"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."
"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."
"The RFS portion of the solution is the product's most valuable feature."
"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 solution is absolutely scalable."
 

Cons

"This is one thing that is a pain and flaw with LogicMonitor."
"The process of upgrading some of the collectors has been a little bit confusing. I need to understand that better."
"The APM part is somewhat lacking; they have made some attempts, but it is very rudimentary and I would not even categorize it as a solution to be honest."
"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."
"We only use plain monitoring and do not use cloud monitoring such as Office 365 because it is too expensive."
"Delayed detection is a significant issue. Because of high load on the infrastructure, sometimes I will not find the alert immediately."
"LogicMonitor can effortlessly pull data from one item at a time. I have yet to find an excellent way to get LogicMonitor to show me all the WAN devices and how they're doing in terms of capacity."
"LogicMonitor should always improve AI because we are always striving for real intelligence."
"The reporting is a bit weak. They should work to improve this aspect of the product."
"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 reporting is a bit weak."
"What's lacking in Loom Systems is the level of priority for each incident."
"The change management within the solution needs to be improved. There needs to be more process automation."
"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."
 

Pricing and Cost Advice

"We pay for the enterprise tech support."
"The licensing side of things with LogicMonitor, is quite simple. It is one license per device. Recently, you have additional licenses with things, like LM Cloud, which does confuse things a bit. Because it's very hard to estimate how many licenses you're going to need until you're monitoring it, so it's quite hard through that process to give a customer price to say, "This is how much this services will cost.""
"It definitely pays for itself in the amount of time we're not spending with false errors or things that we haven't quite dealt with monitoring. It has been good cost-wise."
"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."
"It can handle scaling. It is like any other cloud service. There is a cost associated with scaling, so we currently don't monitor all of our environments. We monitor just the customer-facing production environments. It would be nice if we could monitor our dominant environments, but we will have to pay a lot more due to the scaling issue. So, there's a balance there between what we would like and what we are willing to pay for."
"The tool's pricing falls into the middle range."
"We've had customers who have reduced their costs by not having multiple platforms for monitoring. That said, especially with super-large environments, the cost model for LogicMonitor is the one area where we run into issues."
"In terms of pricing, I would rate LogicMonitor four out of five."
Information not available
report
Use our free recommendation engine to learn which IT Infrastructure Monitoring solutions are best for your needs.
908,800 professionals have used our research since 2012.
 

Top Industries

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

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise13
Large Enterprise31
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 is your experience regarding pricing and costs for LogicMonitor?
My experience with pricing, setup cost, and licensing is that the licensing model has changed and is very confusing as it currently stands and overly complicated.
What needs improvement with LogicMonitor?
I do see negatives and areas for improvement in LogicMonitor. Obviously, there is always space for improvement. First of all, I believe the commercial aspects require improvement. At the moment, if...
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: August 2026.
908,800 professionals have used our research since 2012.