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

Amazon CloudWatch vs Honeycomb.io comparison

 

Comparison Buyer's Guide

Executive Summary

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 CloudWatch
Ranking in Application Performance Monitoring (APM) and Observability
13th
Average Rating
8.0
Reviews Sentiment
7.2
Number of Reviews
46
Ranking in other categories
Log Management (14th), Cloud Monitoring Software (10th)
Honeycomb.io
Ranking in Application Performance Monitoring (APM) and Observability
25th
Average Rating
8.6
Reviews Sentiment
7.0
Number of Reviews
2
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of April 2025, in the Application Performance Monitoring (APM) and Observability category, the mindshare of Amazon CloudWatch is 1.6%, up from 1.1% compared to the previous year. The mindshare of Honeycomb.io is 1.7%, up from 1.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Performance Monitoring (APM) and Observability
 

Featured Reviews

Rasanpreet Singh - PeerSpot reviewer
Reliable AWS monitoring and logging
The choice of logging solution should always be determined by the specific business requirements. It is crucial to align the logging strategy with what type of logs are needed and how they should be used. There are instances where we require custom solutions to retrieve logs, especially application logs that may not be easily accessible through CloudWatch or similar services. When we heavily rely on AWS native services, CloudWatch is indeed a robust choice. However, in certain scenarios, we might need integration capabilities with other tools, and if they can incorporate such features, it would enhance overall logging capabilities. I would rate it eight out of ten.
Diego Gomes De Lima - PeerSpot reviewer
Easy to use and the dashboard is very intuitive
We faced some OpenTelemetry metrics lost between the communication from the service and the Honeycomb.io. I can't say if this is a Honeycomb.io issue or if there are some limitations in OpenTelemetry. Alerts are very helpful in Honeycomb.io, but we don't usually merge because we can compare queries with queries for making alerts. We can make alerts based on static numbers, which may block us from building alerts that could be generic enough or could be serviced.

Quotes from Members

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

Pros

"Amazon CloudWatch is a cheap and easy-to-use solution."
"The most valuable part is the metrics part, which is really good."
"Setting up this product was easy. I found data analytics as its most valuable feature."
"You can automate actions or use AWS functionalities like auto-scaling, where you can configure the metrics to add more nodes if the threshold is exceeded."
"The initial setup is easy."
"The most valuable feature of Amazon CloudWatch is intrusion prevention."
"Amazon CloudWatch's best feature stems from its ability to monitor app performance."
"We can create events and alerts. We use the information to dive down into the infrastructure performance."
"The solution's most valuable features are the queries for the OpenTelemetry events and all the tracing."
"The solution's initial setup process was straightforward since we were getting enough support from Honeycomb.io's team."
 

Cons

"The solution's pricing is a bit higher."
"When customers want to see the CPU or memory utilization there is a cost. This should be free to see the utilization."
"There's a learning curve with Amazon CloudWatch since we have to learn to write the queries to extract the keys and logs."
"The dashboard and the UI could improve in Amazon CloudWatch. Additionally, they should focus on visibility inside the servers with AI and machine learning integrations. This would allow users who are using the solution to see what is happening within the system better."
"The solution should provide human-readable metrics."
"I found several areas for improvement in Amazon CloudWatch. First is that it's tough to track issues and find out where it's going wrong. The process takes longer. For example, if I get an exception error, I read the logs, search, go to AWS Cloud, then to the groups to find the keyword to determine what's wrong. Another area for improvement in Amazon CloudWatch is that it's slow in terms of log streaming. It requires an entire twenty-four hours for scanning, rather than just one hour. This issue can be solved with Elasticsearch streaming with Kibana, but it requires a lot of development effort and integration with Kibana or Splunk, and this also means I need a separate developer and software technical stack to do the indexing and streaming to Kibana. It's a manual effort that you need to do properly, so log streaming should be improved in Amazon CloudWatch. The AWS support person should also have a better understanding of the logs in Amazon CloudWatch. What I'd like added to the solution is a more advanced search function, particularly one that can tell you more information or special information. Right now, the search function is difficult to use because it only gives you limited data. For example, I got an error message saying that the policy wasn't created. I only know the amount the customer paid for the policy, the mobile number, and the customer name, but if I use those details, the information won't show up on the logs. I need to enter more details, so that's the type of fuzzy matching Amazon CloudWatch won't provide. If this type of search functionality is provided, it will be very helpful for businesses and companies that provide professional services to customers, like ours."
"The product’s documentation must be improved."
"Better reporting is always something needed. That could be an answer to just about anything. But you always want better reporting, better dashboards, things that are just more dynamic and more accessible."
"We can make alerts based on static numbers, which may block us from building alerts that could be generic enough or could be serviced."
"The process of log scraping gets delayed on Honeycomb.io. At times, it gives false alerts to the application team."
 

Pricing and Cost Advice

"It’s an open-source solution."
"What's were using is the free service of Amazon CloudWatch, so they're not charging us. As for hidden fees, we're not aware of them because we're using what our clients provided us."
"The pricing can be considered reasonable, especially when already operating on a cloud platform."
"Amazon CloudWatch has very cheap pricing, and it hardly costs my company $25-$30 a month for fifty systems, so it's pretty affordable."
"The price is okay for me."
"Its pricing is reasonable. It is sometimes tricky, but it is reasonable as compared to others."
"The product's cost is relatively inexpensive."
"The pricing is average."
Information not available
report
Use our free recommendation engine to learn which Application Performance Monitoring (APM) and Observability solutions are best for your needs.
847,646 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
17%
Financial Services Firm
17%
Manufacturing Company
8%
University
5%
Computer Software Company
16%
Financial Services Firm
15%
Manufacturing Company
9%
Comms Service Provider
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for Amazon CloudWatch?
Amazon CloudWatch charges more for custom metrics as well as for changes in the timeline, which I see as a disadvantage given the price.
What needs improvement with Amazon CloudWatch?
Amazon CloudWatch charges extra for custom metrics, which is a significant disadvantage. Another aspect that needs improvement is the look and feel of custom dashboards, which currently do not matc...
What do you like most about Honeycomb.io?
The solution's initial setup process was straightforward since we were getting enough support from Honeycomb.io's team.
What needs improvement with Honeycomb.io?
We faced some OpenTelemetry metrics lost between the communication from the service and the Honeycomb.io. I can't say if this is a Honeycomb.io issue or if there are some limitations in OpenTelemet...
What is your primary use case for Honeycomb.io?
The solution is mainly used for stack observability. It observes service behavior or any kind of failure that may be happening. The tool is also related to research. My company is working more on t...
 

Comparisons

 

Overview

 

Sample Customers

AirAsia, Airbnb, Aircel, APUS, Avazu, Casa & Video, Futbol Club Barcelona (FCBarcelona), National Taiwan University, redBus
Clover Health, Eaze, Intercom, Fender
Find out what your peers are saying about Amazon CloudWatch vs. Honeycomb.io and other solutions. Updated: April 2025.
847,646 professionals have used our research since 2012.