Try our new research platform with insights from 80,000+ expert users

Elastic Observability 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

Elastic Observability
Ranking in IT Infrastructure Monitoring
11th
Average Rating
8.0
Reviews Sentiment
6.8
Number of Reviews
27
Ranking in other categories
Application Performance Monitoring (APM) and Observability (7th), Log Management (16th), Container Monitoring (4th), Cloud Monitoring Software (6th)
Loom Systems
Ranking in IT Infrastructure Monitoring
63rd
Average Rating
8.0
Reviews Sentiment
6.9
Number of Reviews
4
Ranking in other categories
Anomaly Detection Tools (2nd)
 

Mindshare comparison

As of August 2025, in the IT Infrastructure Monitoring category, the mindshare of Elastic Observability is 3.3%, down from 4.9% compared to the previous year. The mindshare of Loom Systems is 0.3%, up from 0.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
IT Infrastructure Monitoring
 

Featured Reviews

Adelina Craciun - PeerSpot reviewer
Customization enables tailored monitoring and alerting across departments
The possibility to customize it has been quite useful. Whatever the other departments want to dream up, we implement. Whatever they want to monitor, the granularity of it, the changes in the threshold, and the anomalies that they want reported all require some development. So far, every single request has been fulfilled.
Keerthi Kumar Sangaraju - PeerSpot reviewer
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

"Machine learning is the most valuable feature of this solution."
"I found Elk to be excellent for log analytics, security analytics, application code-level analytics, collaboration with DevOps teams, CI/CD, microservices, and Kubernetes, specifically cloud-native or cloud-specific tasks."
"The solution has been stable in our usage."
"It is very stable, and I would rate it ten out of ten based on my interaction with it."
"We use AppDynamics and Elastic. The reason why we're using Elastic APM is because of the license count. It's very favorable compared to AppDynamics. It's inexpensive; it's economical."
"It is a powerful tool that allows users to collect and transform logs as needed, enabling flexible visualization and analysis."
"The architecture and system's stability are simple."
"We can view and connect different sources to the dashboard using it."
"The solution is absolutely scalable. If an organization needs to expand it out they definitely can."
"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."
"The RFS portion of the solution is the product's most valuable feature."
"You can develop your own apps within Loom, and they can be configured very simply."
 

Cons

"The auto-discovery isn't nearly as good. That's a big portion of it. When you drop the agent onto the JVM and you're trying to figure things out, having to go through and manually do all that is cumbersome."
"If we had some pre-defined templates for observability that we could start using right away after deploying it – instead of having to build or to change some of the dashboards – that would be helpful."
"I am familiar with Azure Monitor, which I find more user-friendly compared to Elastic, which is a very technical tool."
"The cost must be made more transparent."
"The price is the only issue in the solution. It can be made better and cheaper."
"One example is the inability to monitor very old databases with the newest version."
"Elastic Observability is difficult to use. There are only three options for customization but this can be difficult for our use case. We do not have other options to choose the metrics shown, such as CPU or memory usage."
"The interface could be improved."
"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. 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."
 

Pricing and Cost Advice

"So far, there are just the standard licensing fees. Several of the components are embedded in the license or are even open source. They're even free depending on what you use, which makes it even more appealing to someone that is discussing pricing of the solution."
"Since we are a huge company, Elastic Observability is an affordable solution for us."
"Pricing is one of those situations where the more you use it, the more you pay."
"Users have to pay for some features, like the alerts on different channels, because they are unavailable in different source versions."
"One needs to pay for the licenses, and it is an annual subscription model right now."
"There are two types: cloud and SaaS. They charge based on data ingestion, ingest rate, hard retention, and warm retention. I believe it costs around $25,000 annually to ingest 30GB of data daily. That is the SaaS version. There is also a self-managed license where the customer manages their own infrastructure on-prem. In such cases, there are three license tiers that respectively cost $5,000 annually per node, $7,000 per node, and $12,500 per node."
"We have been using the open-source version."
"The product’s pricing needs improvement."
Information not available
report
Use our free recommendation engine to learn which IT Infrastructure Monitoring solutions are best for your needs.
865,384 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
18%
Computer Software Company
15%
Manufacturing Company
8%
Government
6%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What do you like most about Elastic Observability?
Elastic Observability significantly improves incident response time by providing quick access to logs and data across various sources. For instance, searching for specific keywords in logs spanning...
What is your experience regarding pricing and costs for Elastic Observability?
The license for Elastic Observability is the same as for other uses; you pay for Elastic, and you can use it for various cases. Observability is actually cheaper compared to logs because you're not...
What needs improvement with Elastic Observability?
I think they are working on the AI-based features, which are currently in technical preview. The only challenging aspect for new users is often writing the query language. Basic searching is very e...
Ask a question
Earn 20 points
 

Overview

 

Sample Customers

PSCU, Entel, VITAS, Mimecast, Barrett Steel, Butterfield Bank
Citrix, Amdocs, Sysaid, Hexaware, Effibar, Revtrak, Taptica
Find out what your peers are saying about Elastic Observability vs. Loom Systems and other solutions. Updated: July 2025.
865,384 professionals have used our research since 2012.