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
13th
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 (16th), Container Monitoring (5th), Cloud Monitoring Software (11th)
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 Elastic Observability is 1.3%, down from 3.3% 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 (%)
Elastic Observability1.3%
Loom Systems0.5%
Other98.2%
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

"The tool's most valuable feature is centralized logging. Elastic Common Search helps us to search for the logs across the organization."
"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."
"For full stack observability, Elastic is the best tool compared with any other tool like New Relic or AppDynamics or Dynatrace."
"The ability to ensure that the data is searchable and maintainable is highly valuable for our purposes."
"The very positive features are the cost effectiveness and the range of things that you can implement."
"It is very stable, and I would rate it ten out of ten based on my interaction with it."
"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."
"The RFS portion of the solution is the product's most valuable feature."
"The solution is absolutely scalable."
"You can develop your own apps within Loom, and they can be configured very simply."
"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."
"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 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."
 

Cons

"With Elastic, you need to code and program more things compared to Dynatrace."
"Elastic APM's visualization is not that great compared to other tools. It's number of metrics is very low."
"I would have preferred built-in tools to manage the indexes on deployment for better visual representation, as the initial feedback regarding system performance and data storage was fairly primitive and lacking."
"The interface could be improved."
"One example is the inability to monitor very old databases with the newest version."
"The solution would be better if it was capable of more automation, especially in a monitoring capacity or for the response to abnormalities."
"More web features could be added to the product."
"The tool's scalability involves a more complex implementation process. It requires careful calculations to determine the number of nodes needed, the specifications of each node, and the configuration of hot, warm, and cold zones for data storage. Additionally, managing log retention policies adds further complexity. The solution's pricing also needs to be cheaper."
"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."
"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."
"What's lacking in Loom Systems is the level of priority for each incident."
"The reporting is a bit weak. They should work to improve this aspect of the product."
 

Pricing and Cost Advice

"The product’s pricing needs improvement."
"Elastic Observability's pricing could be better for small-scale users."
"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 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."
"Since we are a huge company, Elastic Observability is an affordable solution for us."
"The product is not that cheap."
"The price of Elastic Observability is expensive."
"One needs to pay for the licenses, and it is an annual subscription model right now."
Information not available
report
Use our free recommendation engine to learn which IT Infrastructure Monitoring solutions are best for your needs.
909,725 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
14%
Computer Software Company
10%
Manufacturing Company
7%
Government
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: August 2026.
909,725 professionals have used our research since 2012.