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

Amazon OpenSearch Service vs Mezmo comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Aug 11, 2025

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 Application Performance Monitoring (APM) and Observability
24th
Ranking in Log Management
20th
Average Rating
7.6
Reviews Sentiment
7.2
Number of Reviews
12
Ranking in other categories
Search as a Service (3rd)
Mezmo
Ranking in Application Performance Monitoring (APM) and Observability
74th
Ranking in Log Management
50th
Average Rating
9.0
Number of Reviews
2
Ranking in other categories
Observability Pipeline Software (7th)
 

Mindshare comparison

As of October 2025, in the Application Performance Monitoring (APM) and Observability category, the mindshare of Amazon OpenSearch Service is 2.0%, up from 0.6% compared to the previous year. The mindshare of Mezmo is 0.3%, up from 0.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Performance Monitoring (APM) and Observability Market Share Distribution
ProductMarket Share (%)
Amazon OpenSearch Service2.0%
Mezmo0.3%
Other97.7%
Application Performance Monitoring (APM) and Observability
 

Featured Reviews

Johnny Suleiman - PeerSpot reviewer
Scalability is a key feature as it allows easy scaling of the platform without downtime
OpenSearch is used as a search engine for specific logs, mainly in e-commerce and monitoring the logs themselves. It is very valuable for e-commerce, enabling data analysis on application logs and customer behavior, and can be integrated with other services, including AI and machine learning…
TO
It consolidates all logs into one place and provides required features and functionalities
Every once in a while, our IBM cloud operational implementation gets behind. Sometimes, when we have a customer event, we do not get access to the latest logs for about 30 minutes, particularly for the sites that are heavily utilized. This is clearly not good. It is impossible to do RCA when you can't look at the logs that pertain to the time period in which the event occurred. It could be more of an operational problem than a feature problem. I don't have visibility about whether it is a LogDNA issue or just an operational issue.

Quotes from Members

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

Pros

"They have the good documentation in the help text and that is the reason the Amazon is the perfect solution in the current market."
"The business analytics capabilities are the most important feature it provides."
"Regarding valuable features of the solution, we found with the process, which we have used in both cases where we used the solution that while you're seeing the streaming of data, you can analyze in the initial phase what sort of data you are streaming and whether it is valuable."
"Amazon OpenSearch Service provides a managed database solution, so we don't need to manage everything ourselves."
"In case there is a failure, Elastic manages everything well, and there no major downtime."
"This service already sorts data like vectors. They have classified the storage pre-defined."
"It's a good log management platform. In terms of infrastructure management, it's good."
"The stability of the product is good."
"The solution aggregates all event streams, so that if there are any issues, it's all in the same interface."
"LogDNA consolidates all logs into one place, which is super valuable."
 

Cons

"The configuration should be more straightforward because we had to select a lot of things."
"They can enhance data visualization."
"There is a problem with the database. Amazon only provides the hosting to run our applications bias, but there is no option to manage the database within the Elasticsearch product."
"In terms of data handling capabilities with Amazon OpenSearch Service, they can be complex and managing data in comparison to other SIM solutions is a major drawback, as it is very hard to handle the data."
"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 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."
"The price is fair yet leans towards the expensive side. I'd rate it five out of ten with respect to capabilities vs. cost."
"Every once in a while, our IBM cloud operational implementation gets behind. Sometimes, when we have a customer event, we do not get access to the latest logs for about 30 minutes, particularly for the sites that are heavily utilized. This is clearly not good. It is impossible to RCA when you can't look at the logs that pertain to the time period in which the event occurred. It could be more of an operational problem than a feature problem. I don't have visibility about whether it is a LogDNA issue or just an operational issue."
"No ability to encapsulate a query or a filter, and communicate or share that among the team."
 

Pricing and Cost Advice

"Compared to other cloud platforms, it is manageable and not very expensive."
"There is a community edition available and the price of the commercial offering is reasonable."
"You only pay for what you use."
"The solution is not expensive, but priced averagely, I will say."
Information not available
report
Use our free recommendation engine to learn which Application Performance Monitoring (APM) and Observability solutions are best for your needs.
868,787 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Computer Software Company
12%
Manufacturing Company
9%
Government
8%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business7
Midsize Enterprise2
Large Enterprise2
No data available
 

Questions from the Community

What do you like most about Amazon OpenSearch Service?
We retrieve historical data with just a click of a button to move it from cold to hot or warm because it's already stored in the backend storage
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?
In terms of data handling capabilities with Amazon OpenSearch Service, they can be complex and managing data in comparison to other SIM solutions is a major drawback, as it is very hard to handle t...
Ask a question
Earn 20 points
 

Also Known As

Amazon Elasticsearch Service
LogDNA
 

Overview

 

Sample Customers

VIDCOIN, Wyng, Yellow New Zealand, zipMoney, Cimri, Siemens, Unbabel
Instacart, Asics, Lime, Salesforce
Find out what your peers are saying about Amazon OpenSearch Service vs. Mezmo and other solutions. Updated: September 2025.
868,787 professionals have used our research since 2012.