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

Amazon OpenSearch Service vs Logz.io comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive SummaryUpdated on Feb 22, 2026

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

Amazon OpenSearch Service
Ranking in Log Management
15th
Average Rating
7.6
Reviews Sentiment
6.7
Number of Reviews
13
Ranking in other categories
Application Performance Monitoring (APM) and Observability (23rd), Search as a Service (3rd)
Logz.io
Ranking in Log Management
28th
Average Rating
8.2
Reviews Sentiment
6.8
Number of Reviews
10
Ranking in other categories
Security Information and Event Management (SIEM) (33rd)
 

Mindshare comparison

As of October 2026, in the Log Management category, the mindshare of Amazon OpenSearch Service is 1.3%, down from 2.8% compared to the previous year. The mindshare of Logz.io is 1.2%, up from 0.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Log Management Mindshare Distribution
ProductMindshare (%)
Amazon OpenSearch Service1.3%
Logz.io1.2%
Other97.5%
Log Management
 

Featured Reviews

Md. Shahariar Hossen - PeerSpot reviewer
Senior Software Engineer at Cefalo
Event tracking has become smoother and data analytics provide clear insights for user actions
Amazon OpenSearch Service is not providing the processing feature directly. From Amazon OpenSearch Service, we are actually maintaining the AWS SQS, the queue service, which is responsible for providing information about what data has to be modified. So using that SQS, we're actually providing it, but we're not directly using Amazon OpenSearch Service for keeping data to other data pipeline thing. So far we didn't use it for any machine learning purposes, but in future, we have plans to extend or implement this feature. Since AWS itself is secure and Amazon OpenSearch Service is a part of this entire ecosystem, it becomes much easier for security purposes. From the validation point of view, Amazon OpenSearch Service itself provides easy to communicate APIs and up-to-date documents, which is much beneficial. For example, if I'm missing anything, I can directly go and check the documentation. That is actually much easier. I would rate it as really good so far. It's much faster. For our local machine, we can also use a kind of replica of Amazon OpenSearch Service just for development purposes. That is another good feature. I would say for the encryption thing and also the user access control management, it's much faster. For some of these hashing algorithms, it also worked really well so far. To be honest, I didn't find any places where it can be improved. However, I think they could provide more abstraction. For example, still for searching, we have to write down the queries in a specific manner, such as for a specific JSON structure or in a specific way. Otherwise, they don't provide us the actual results. For at least this purpose, I think abstraction could be a bit easier or a bit improved. Other than that, right now there is the age of AI, so some kind of prompting could also work, but I'm not sure how it could be integrated. As a user, lower prices or reasonable pricing is always better. Those can be improved as well. However, it is good that most of the services including Amazon OpenSearch Service actually provide pay as you go pricing. So if there were a bit lower version or a bit less payment methodology, it might be much better.
Arkajyoti Misra - PeerSpot reviewer
Associate Director at Husk Power Systems
AI-driven observability has reduced investigation time and now improves uptime and customer trust
As for improvements needed in Logz.io, I think cost or pricing is always a consideration, especially since I come from a startup and an Indian company, making us look for products that provide better value for money. Compared to the market, their pricing appears decent but might need reevaluation as we scale further to remain competitive. The main concern for me is pricing, as feature-wise, I believe Logz.io is on par with other tools available in the market; however, it is not as widely discussed. Their features align with offerings from Elastic Stack and other prominent tools, including functionalities available from Prometheus or Grafana, providing centralized logging and other capabilities in the UI, so while the product direction is solid, improved pricing would immensely benefit us. I believe we have covered almost everything regarding improvements needed for Logz.io.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The initial set up is very easy...We really appreciate Amazon!"
"The most valuable features of Amazon Elasticsearch are ease of use, native JSON, and efficiency. Additionally, handles many use cases and search grammar was useful."
"It enables us to efficiently search and retrieve our event data, offering us a versatile approach to locate specific information within these logs."
"AWS has now made our life easy."
"This service already sorts data like vectors. They have classified the storage pre-defined."
"Our customers have seen tangible benefits from Amazon OpenSearch Service, especially in terms of their applications running smoothly, so they do get a return on investment."
"It's actually easier to collaborate since it is already deployed in the AWS cloud itself."
"The customer service is excellent, rated nine out of ten."
"Our team doesn't spend time setting up, managing, and tuning a logging platform, which frees them up to spend time on higher value pieces of work and allows our people to focus on the high-value business change work."
"I can't imagine how I ever worked without it before."
"InsightOne is the main reason why we use LogMeIn. This is mostly because of log data that we are pushing tools and logs in general."
"The query mechanism for response codes and application health is valuable."
"It is massively useful and great for testing. We can just go, find logs, and attach them easily. It has a very quick lookup. Whereas, before we would have to go, dig around, and find the server that the logs were connected to, then go to the server, download the log, and attach it. Now, we can just go straight to this solution, type in the log ID and server ID, and obtain the information that we want."
"The other nice thing about Logz.io is their team. When it comes to onboarding, their support is incredibly proactive. They bring the brand experience from a customer services perspective because their team is always there to help you refine filters and tweak dashboards. That is really a useful thing to have. Their engagement is really supportive."
"We use the product for log collection and monitoring."
"Logz.io has impacted our organization very positively."
 

Cons

"There is the problem with the database. Amazon only provides the host to run to our applications bias, but there is no option to manage the database within the Elasticsearch product."
"As a user, lower prices or reasonable pricing is always better."
"It would be beneficial to have some level of customization available in the managed service, tailored to the specific use cases of the end users."
"I would say that, basically, the configuration part is an area with a shortcoming...Some upgradation is required on the configuration side so that we can get to use it."
"We faced documentation challenges during integration after migrating from Elasticsearch to Amazon OpenSearch Service. Better documentation on integration, query handling, and a more user-friendly UI could enhance the product."
"One glaring issue was with our mapping configuration as the system accepted the data we posted, but after a few months, when we attempted complex queries, we realized the date formatting had become problematic."
"The pricing aspect is a concern. The service is way too costly. For the past month, I used only 30 to 40 MB of data, and the cost was $500. AWS could improve pricing."
"I want to see a new feature in Amazon Elasticsearch Service that allows users to create default filters for filtered levels."
"The solution needs to improve its data retention. It should be greater than seven days. The product needs to improve its documentation as well."
"The price can be cheaper and they should have better monitoring."
"However, at this lower scale, we feel it does not deliver the expected value for the money we are paying, reiterating my concern about cost."
"I would like granularity on alerting so we can get tentative alerts and major alerts, then break it down between the two, but they do have a lot of good alerting stuff in there already."
"The product needs improvement from a filtering perspective."
"The solution needs to expand its access control and make it accessible through API."
"When it comes to reducing our troubleshooting time, it depends. When there are no bugs in Logz.io, it reduces troubleshooting by 5 to 10 percent. When there are bugs, it increases our troubleshooting time by 200 percent or more."
"Capacity planning could be a little bit of a struggle."
 

Pricing and Cost Advice

"The solution is not expensive, but priced averagely, I will say."
"Compared to other cloud platforms, it is manageable and not very expensive."
"You only pay for what you use."
"There is a community edition available and the price of the commercial offering is reasonable."
"You pay for what you need, and that is a good model. They are also quite happy to talk to you about your uses and your use case. They will even go as far as suggesting things that you don't need to do in order to save you money. At one point, I was quite surprised at how cheap it could be if we wanted it to be or how much they would help us manage our costs."
"The product is a little expensive."
"The product's pricing is cheaper than other solutions."
"The tool is an open source product."
"At the time it was set up, we thought Logz.io was very reasonable for what we were getting in terms of how much time and hosting costs it was saving us, because you don't have to run the servers for it anymore."
report
Use our free recommendation engine to learn which Log Management solutions are best for your needs.
916,197 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Manufacturing Company
10%
Computer Software Company
8%
Outsourcing Company
6%
Comms Service Provider
17%
Financial Services Firm
11%
Construction Company
10%
Manufacturing Company
10%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business7
Midsize Enterprise2
Large Enterprise4
By reviewers
Company SizeCount
Small Business5
Midsize Enterprise2
Large Enterprise7
 

Questions from the Community

What is your experience regarding pricing and costs for Amazon OpenSearch Service?
I would consider the pricing as a six based on how much data we are handling; if we handle minimal data, it's cheap, but for large data, it becomes costly. Our clients usually pay between $1,000 to...
What needs improvement with Amazon OpenSearch Service?
Amazon OpenSearch Service is not providing the processing feature directly. From Amazon OpenSearch Service, we are actually maintaining the AWS SQS, the queue service, which is responsible for prov...
What is your primary use case for Amazon OpenSearch Service?
Amazon OpenSearch Service is a user-friendly version of Elasticsearch, as per my understanding. I have been using it for our volunteer management system where around 5,000 to 6,000 users are using ...
What is your experience regarding pricing and costs for Logz.io?
Organizations that start with clear logging standards and retention policies can integrate applications, cloud resources, and Kubernetes workloads early to maximize the observability benefits. They...
What needs improvement with Logz.io?
Logz.io can be improved by adding more AI-assisted root cause analysis and by improving log retention flexibility. They can also provide additional dashboard customization options. Logz.io is a ver...
What is your primary use case for Logz.io?
We have been using Logz.io for more than one year. Our main use case for Logz.io is centralized log management and observability. We collect logs from multiple applications and infrastructure compo...
 

Also Known As

Amazon Elasticsearch Service
Logz
 

Overview

 

Sample Customers

VIDCOIN, Wyng, Yellow New Zealand, zipMoney, Cimri, Siemens, Unbabel
Dish Network, The Economist, Forbes, Holler, Kenshoo, OneSpan, Siemens, Sisense, Unity, ZipRecruiter
Find out what your peers are saying about Amazon OpenSearch Service vs. Logz.io and other solutions. Updated: September 2026.
916,197 professionals have used our research since 2012.