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

Elastic Search vs Loom Systems comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

Elastic Search
Average Rating
8.2
Reviews Sentiment
6.7
Number of Reviews
65
Ranking in other categories
Indexing and Search (1st), Cloud Data Integration (12th), Search as a Service (1st), Vector Databases (1st)
Loom Systems
Average Rating
8.0
Number of Reviews
4
Ranking in other categories
IT Infrastructure Monitoring (66th), Anomaly Detection Tools (2nd)
 

Mindshare comparison

Elastic Search and Loom Systems aren’t in the same category and serve different purposes. Elastic Search is designed for Indexing and Search and holds a mindshare of 28.1%, up 25.1% compared to last year.
Loom Systems, on the other hand, focuses on IT Infrastructure Monitoring, holds 0.2% mindshare, up 0.2% since last year.
Indexing and Search
IT Infrastructure Monitoring
 

Featured Reviews

Saurav Kumar - PeerSpot reviewer
Provides us with the capability to execute multiple queries according to our requirements
Logsign provides us with the capability to execute multiple queries according to our requirements. The indexing is very high, making it effective for storing and retrieving logs. The real-time analytics with Elastic benefits us due to the huge traffic volume in our organization, which reaches up to 60,000 requests per second. With logs of approximately 25 GB per day, manually analyzing traffic behavior, payloads, headers, user agents, and other details is impractical.
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

"The AI-based attribute tagging is a valuable feature."
"It provides deep visibility into your cloud and distributed applications, from microservices to serverless architectures. It quickly identifies and resolves the root causes of issues, like gaining visibility into all the cloud-based and on-prem applications."
"The most valuable feature of Elastic Enterprise Search is the Discovery option for the visualization of logs on a GPU instead of on the server."
"Logsign provides us with the capability to execute multiple queries according to our requirements. The indexing is very high, making it effective for storing and retrieving logs. The real-time analytics with Elastic benefits us due to the huge traffic volume in our organization, which reaches up to 60,000 requests per second. With logs of approximately 25 GB per day, manually analyzing traffic behavior, payloads, headers, user agents, and other details is impractical."
"The solution offers good stability."
"The solution is stable and reliable."
"The most valuable feature of Elastic Enterprise Search is user behavior analysis."
"I appreciate that Elastic Enterprise Search is easy to use and that we have people on our team who are able to manage it effectively."
"You can develop your own apps within Loom, and they can be configured very simply."
"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."
 

Cons

"Technical support should be faster."
"There is another solution I'm testing which has a 500 record limit when you do a search on Elastic Enterprise Search. That's the only area in which I'm not sure whether it's a limitation on our end in terms of knowledge or a technical limitation from Elastic Enterprise Search. There is another solution we are looking at that rides on Elastic Enterprise Search. And the limit is for any sort of records that you're doing or data analysis you're trying to do, you can only extract 500 records at a time. I know the open-source nature has a lot of limitations, Otherwise, Elastic Enterprise Search is a fantastic solution and I'd recommend it to anyone."
"Elastic Enterprise Search could improve its SSL integration easier. We should not need to go to the back-end servers to do configuration, we should be able to do it on the GUI."
"There are some features lacking in ELK Elasticsearch."
"We see the need for some improvements with Elasticsearch. We would like the Elasticsearch package to include training lessons for our staff."
"They're making changes in their architecture too frequently."
"Performance improvement could come from skipping background refresh on search idle shards (which is already being addressed in the upcoming seventh version)."
"The documentation regarding customization could be better."
"The reporting is a bit weak. They should work to improve this aspect of the product."
"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 discovery and mapping still takes a lot of human intervention, it's quite resource heavy,"
 

Pricing and Cost Advice

"We are using the Community Edition because Elasticsearch's licensing model is not flexible or suitable for us. They ask for an annual subscription. We also got the development consultancy from Elasticsearch for 60 days or something like that, but they were just trying to do the same trick. That's why we didn't purchase it. We are just using the Community Edition."
"The cost varies based on factors like usage volume, network load, data storage size, and service utilization. If your usage isn't too extensive, the cost will be lower."
"The pricing structure depends on the scalability steps."
"To access all the features available you require both the open source license and the production license."
"we are using a licensed version of the product."
"It can move from $10,000 US Dollars per year to any price based on how powerful you need the searches to be and the capacity in terms of storage and process."
"This is a free, open source software (FOSS) tool, which means no cost on the front-end. There are no free lunches in this world though. Technical skill to implement and support are costly on the back-end with ELK, whether you train/hire internally or go for premium services from Elastic."
"The solution is affordable."
Information not available
report
Use our free recommendation engine to learn which Indexing and Search solutions are best for your needs.
824,067 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
19%
Financial Services Firm
15%
Manufacturing Company
8%
Government
7%
Financial Services Firm
23%
Computer Software Company
16%
Real Estate/Law Firm
8%
Media Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What do you like most about ELK Elasticsearch?
Logsign provides us with the capability to execute multiple queries according to our requirements. The indexing is very high, making it effective for storing and retrieving logs. The real-time anal...
What is your experience regarding pricing and costs for ELK Elasticsearch?
I am not directly involved with pricing or setup costs. While I know a portion is open-source, a paid version might be necessary.
What needs improvement with ELK Elasticsearch?
An improvement would be to have an interface that allows easier navigation and tracing of logs. The current system requires manually inputting dates to verify alerts. A visual timeline that pinpoin...
Ask a question
Earn 20 points
 

Comparisons

No data available
 

Also Known As

Elastic Enterprise Search, Swiftype, Elastic Cloud
No data available
 

Overview

 

Sample Customers

T-Mobile, Adobe, Booking.com, BMW, Telegraph Media Group, Cisco, Karbon, Deezer, NORBr, Labelbox, Fingerprint, Relativity, NHS Hospital, Met Office, Proximus, Go1, Mentat, Bluestone Analytics, Humanz, Hutch, Auchan, Sitecore, Linklaters, Socren, Infotrack, Pfizer, Engadget, Airbus, Grab, Vimeo, Ticketmaster, Asana, Twilio, Blizzard, Comcast, RWE and many others.
Citrix, Amdocs, Sysaid, Hexaware, Effibar, Revtrak, Taptica
Find out what your peers are saying about Elastic Search vs. Loom Systems and other solutions. Updated: January 2022.
824,067 professionals have used our research since 2012.