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

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
15th
Average Rating
8.0
Reviews Sentiment
6.8
Number of Reviews
29
Ranking in other categories
Application Performance Monitoring (APM) and Observability (11th), Log Management (15th), Container Monitoring (5th), Cloud Monitoring Software (11th)
Loom Systems
Ranking in IT Infrastructure Monitoring
64th
Average Rating
8.0
Reviews Sentiment
6.9
Number of Reviews
4
Ranking in other categories
Anomaly Detection Tools (5th)
 

Mindshare comparison

As of May 2026, in the IT Infrastructure Monitoring category, the mindshare of Elastic Observability is 1.4%, down from 3.8% 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 (%)
Elastic Observability1.4%
Loom Systems0.5%
Other98.1%
IT Infrastructure Monitoring
 

Featured Reviews

Mohammed-Abdelalim - PeerSpot reviewer
Assistant Vice President at QualityKiosk Technologies Pvt. Ltd.
Has provided powerful customization for unique monitoring needs but needs more out-of-the-box capabilities
In my opinion, the best features of Elastic Observability are their flexibility to integrate with other existing systems and the ability to build a unified monitoring tool that can integrate with existing ones and end-to-end user journeys which require a lot of customizations. The greatest feature in Elastic is the ability to customize. This is similar to my comments about customizable dashboards in Elastic because it's visible to the analyst. However, it's very great. Customizing these dashboards can meet the customer's specific use cases and specific stories that they have in their environment, their special environment that doesn't look like other environments. The dashboarding in Elastic is highly customizable to the level of logos. If the customer wants his company logo in the dashboard, it can be done.
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

"I have built a mini business intelligence system based on Elastic Observability."
"The very positive features are the cost effectiveness and the range of things that you can implement."
"In addition to the fact that we are more proactive in the detection of incident before they occur, we can on one click see the request path from the customer to the backend."
"Elastic APM has plenty of features, such as the Elastic server for Kibana and many additional plugins."
"For full stack observability, Elastic is the best tool compared with any other tool like New Relic or AppDynamics or Dynatrace."
"We can view and connect different sources to the dashboard using it."
"The solution has been stable in our usage."
"It's easy to deploy, and it's very flexible."
"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."
"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 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."
"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 absolutely scalable."
"You can develop your own apps within Loom, and they can be configured very simply."
 

Cons

"More web features could be added to the product."
"The solution needs to use more AI. Once the product onboards AI, users would more effectively be able to track endpoints for specific messages."
"Elastic Observability needs to improve the retrieval of logs and metrics from all the instances."
"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."
"One example is the inability to monitor very old databases with the newest version."
"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."
"Elastic Observability is an excellent product for monitoring and visibility, but it lacks predictive analytics."
"Elastic Observability needs to have better standardization, logging, and schema."
"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."
"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. 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, 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 reporting is a bit weak."
"The discovery and mapping still takes a lot of human intervention, it's quite resource heavy,"
"The change management within the solution needs to be improved. There needs to be more process automation."
 

Pricing and Cost Advice

"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."
"Elastic Observability's pricing could be better for small-scale users."
"Users have to pay for some features, like the alerts on different channels, because they are unavailable in different source versions."
"Since we are a huge company, Elastic Observability is an affordable solution for us."
"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."
"Elastic Observability is cheaper than other similar solutions, such as Dynatrace. Its license calculation is based on various factors like data volume and physical infrastructure, particularly related to RAM capacity."
"We have been using the open-source version."
"We will buy a premium license after POC."
Information not available
report
Use our free recommendation engine to learn which IT Infrastructure Monitoring solutions are best for your needs.
893,244 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Computer Software Company
12%
Government
7%
Manufacturing Company
7%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise4
Large Enterprise16
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for Elastic Observability?
The problem is their licensing model, which is a bit confusing. Many customers struggle to understand their total cost of ownership because Elastic licensing is not dependent on easy, quantifiable ...
What needs improvement with Elastic Observability?
After careful consideration about areas for improvement in Elastic Observability, aspects such as pricing, customization, implementation, and scalability could be improved. As a user of the system,...
What is your primary use case for Elastic Observability?
My use case for Elastic Observability is observability, as we upload our customers' data, including logs, and when there is an issue, we can analyze what went wrong.
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: April 2026.
893,244 professionals have used our research since 2012.