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

Amazon OpenSearch Service vs Honeycomb Enterprise comparison

 

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 Application Performance Monitoring (APM) and Observability
22nd
Average Rating
7.6
Reviews Sentiment
6.7
Number of Reviews
13
Ranking in other categories
Log Management (19th), Search as a Service (3rd)
Honeycomb Enterprise
Ranking in Application Performance Monitoring (APM) and Observability
18th
Average Rating
7.6
Reviews Sentiment
5.5
Number of Reviews
10
Ranking in other categories
AI Code Assistants (8th), AI Observability (18th)
 

Mindshare comparison

As of June 2026, in the Application Performance Monitoring (APM) and Observability category, the mindshare of Amazon OpenSearch Service is 1.1%, down from 2.0% compared to the previous year. The mindshare of Honeycomb Enterprise is 1.1%, down from 1.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Performance Monitoring (APM) and Observability Mindshare Distribution
ProductMindshare (%)
Honeycomb Enterprise1.1%
Amazon OpenSearch Service1.1%
Other97.8%
Application Performance Monitoring (APM) and Observability
 

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.
MukeshSharma - PeerSpot reviewer
Lead Engineer at Qualys
Tracing microservices has exposed gaps in visibility but has provided high-cardinality insights
I have used better tools, I would say. I would not say that I prefer Honeycomb Enterprise as much. I have used Dynatrace, and I found it more comprehensive, and AppDynamics and other tools. These tools can also provide good information, but I find other tools better. Most of the products, I would say, such as Dynatrace or AppDynamics or New Relic, are targeting this microservices market. I think Honeycomb Enterprise can have something very dedicated for microservices because there is an explosion in the migration from monolithic to microservices. If Honeycomb Enterprise can create a stable solution which is easy to use and which gives additional value and helps for faster debugging with microservices, they can certainly gain market share from others. Tracing is already there. I just wish that these tools are a bit less cryptic. These tools sometimes get quite cryptic for new users. The less cryptic they can be made, that can help these tools. Another thing is that for microservices, when you have multiple microservices installed, that is also required. There are tools where you install on a single microservice, but then these microservices interact with multiple microservices. That kind of picture, I have seen that in AppDynamics; they do give a picture showing that a particular request which arrived here had interaction with these other third-party services or microservices and databases. That is what we need. That is what performance engineers and SREs need to see for each request, where it spent the entire time; how many other services or databases it interacted with and what took more or less time, and if there is a sequence, it should highlight that also. Was it parallel or if, for instance, a call to service A and then a call was made to a database, or a call to service A and a database were in parallel, that kind of information.

Quotes from Members

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

Pros

"The customer service is excellent, rated nine out of ten."
"I would definitely recommend Amazon OpenSearch Service to other professionals due to its fast and reliable search capabilities."
"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 enables us to efficiently search and retrieve our event data, offering us a versatile approach to locate specific information within these logs."
"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."
"Amazon OpenSearch Service has enhanced our organization's ability to store and search large amounts of data efficiently."
"This service already sorts data like vectors. They have classified the storage pre-defined."
"It's very scalable since we used it for a really big organization and it worked."
"The solution's most valuable features are the queries for the OpenTelemetry events and all the tracing."
"Honeycomb Enterprise played a vital role in identifying the problems in the initial calls itself, which has actually saved us a lot of incidents and reduced customer complaints by almost ninety to ninety-two to ninety-three percent as per the data I have."
"The solution's initial setup process was straightforward since we were getting enough support from Honeycomb.io's team."
"The most valuable feature of Honeycomb Enterprise for me is the root cause analysis part because it helps me greatly with the response messages and derived error messages which are very clearly mentioned in Honeycomb Enterprise logs."
"From a pros perspective, Honeycomb Enterprise could be a better candidate with high cardinality; when there are too many unique values, Honeycomb Enterprise could be more beneficial there."
"Honeycomb Enterprise has positively impacted our organization by providing live alerts."
"The biggest return on investment with Honeycomb Enterprise is being able to find, if I am doing production support and something goes wrong, the exact scenario or the exact request and response and the details of that really quickly."
 

Cons

"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."
"I want to see a new feature in Amazon Elasticsearch Service that allows users to create default filters for filtered levels."
"As a user, lower prices or reasonable pricing is always better."
"The price is fair yet leans towards the expensive side. I'd rate it five out of ten with respect to capabilities vs. cost."
"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 configuration should be more straightforward because we had to select a lot of things."
"Amazon Elasticsearch can improve the bullion in the near search and the ease of integration with Kibana. Additionally, there could be more flexibility in the configuration and documentation."
"One improvement I would like to see is support for auto-scaling."
"We can make alerts based on static numbers, which may block us from building alerts that could be generic enough or could be serviced."
"On the negative side, dashboarding is not that great."
"The way Grit architecture is designed and how it works, it is and may not become an alternative choice of code security solutions."
"However, the reason it's only five is because it's lagging behind in terms of AI-compatible features."
"The process of log scraping gets delayed on Honeycomb.io. At times, it gives false alerts to the application team."
"Regarding other aspects, I cannot comment fully because we only use that particular part for tracing the particular threads as per the issues and there are multiple issues in which we have not used it."
"I have used better tools, I would say. I would not say that I prefer Honeycomb Enterprise as much."
"Honeycomb Enterprise can be improved by providing features similar to Splunk, as I currently use both services in my monitoring processes."
 

Pricing and Cost Advice

"You only pay for what you use."
"The solution is not expensive, but priced averagely, I will say."
"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."
Information not available
report
Use our free recommendation engine to learn which Application Performance Monitoring (APM) and Observability solutions are best for your needs.
900,747 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Manufacturing Company
10%
Computer Software Company
10%
Government
6%
Financial Services Firm
12%
Computer Software Company
11%
Manufacturing Company
9%
Comms Service Provider
9%
 

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 Enterprise1
Large Enterprise8
 

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 needs improvement with Honeycomb.io?
If any particular issue is going to take half an hour for root cause analysis, by just getting the error code, particular HTTP status codes or response error messages, we can pinpoint the issues wi...
What is your primary use case for Honeycomb.io?
I was using Honeycomb Enterprise for checking the logs and for application purposes when we were trying to find bugs and errors in a particular application. We used Honeycomb Enterprise for HTTP st...
What advice do you have for others considering Honeycomb.io?
I have read about Honeycomb Enterprise's query engine and the visualization part, which is very interesting. However, those decisions were made by the top leads, so I am not part of that decision. ...
 

Also Known As

Amazon Elasticsearch Service
Grit
 

Overview

 

Sample Customers

VIDCOIN, Wyng, Yellow New Zealand, zipMoney, Cimri, Siemens, Unbabel
Clover Health, Eaze, Intercom, Fender
Find out what your peers are saying about Amazon OpenSearch Service vs. Honeycomb Enterprise and other solutions. Updated: June 2026.
900,747 professionals have used our research since 2012.