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

Amazon CloudWatch vs Mezmo comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Oct 9, 2024

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
19th
Ranking in Log Management
17th
Average Rating
8.0
Reviews Sentiment
7.1
Number of Reviews
48
Ranking in other categories
Cloud Monitoring Software (14th)
Mezmo
Ranking in Application Performance Monitoring (APM) and Observability
74th
Ranking in Log Management
57th
Average Rating
9.0
Number of Reviews
2
Ranking in other categories
Observability Pipeline Software (7th)
 

Mindshare comparison

As of May 2026, in the Application Performance Monitoring (APM) and Observability category, the mindshare of Amazon CloudWatch is 1.1%, down from 1.7% compared to the previous year. The mindshare of Mezmo is 0.5%, up from 0.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Performance Monitoring (APM) and Observability Mindshare Distribution
ProductMindshare (%)
Amazon CloudWatch1.1%
Mezmo0.5%
Other98.4%
Application Performance Monitoring (APM) and Observability
 

Featured Reviews

Azam S M - PeerSpot reviewer
Infrastructure Lead at Danat Fz LLC
Has provided reliable monitoring and alerting through extensive metric tracking and dashboard configuration
Amazon CloudWatch itself provides a lot of data. However, for visualization, we need to use third-party tools. We are in a process of integrating Grafana, Loki, and Prometheus to have better visualization on Amazon CloudWatch. We are also integrating Grafana with the application itself to get the application data and logs. Alternatively, there is AWS Kinesis and Glue where you can scrape the logs and have visualization, but a more easy option is Grafana. If you want to get a proper visual representation to see what is happening, then you need to integrate a third-party tool. Amazon CloudWatch has all the data, but to see what is happening, you need some third-party tool.
TO
President and Founder at STILLWATER SUPERCOMPUTING INC
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

"There is a clear return on investment, as you can reduce a lot of manual staff and physical staff monitoring by getting CloudWatch to do that work for you and save a lot based on that."
"The detection is the most valuable feature."
"CloudWatch provides essential monitoring capabilities that integrate seamlessly with other AWS services."
"It's stable, the performance is good, it's reliable, there are no bugs or glitches, and it doesn't crash or freeze."
"The most valuable feature of Amazon CloudWatch is intrusion prevention."
"The product can be integrated with AWS very easily."
"The solution offers very detailed metrics for their services."
"The portability that we have in Amazon is great."
"LogDNA consolidates all logs into one place, which is super valuable."
"With LogDNA, which brings all the logs together in an interleaved stream, it allows us to take a transaction and relate it to other contextual events making the gathering of evidence for auditors and our internal RCA much more productive."
"The solution aggregates all event streams, so that if there are any issues, it's all in the same interface."
"We haven't had anything yet that we couldn't do through LogDNA."
 

Cons

"The solution's auto-scaling could be improved."
"Amazon CloudWatch has all the data, but to see what is happening, you need some third-party tool."
"Improvement of SSSD logs would be beneficial."
"There could be further enhancements through CloudWatch's partnerships."
"I do not know whether or not CloudWatch can be integrated with on-prem services."
"The solution could benefit from a price decrease."
"The solution should provide human-readable metrics."
"The solution's pricing is a bit higher."
"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."
"Scalability could be improved; we are using it through the IBM cloud deployment and on some of the data centers that are very heavily used, there is a significant lag in the event stream, sometimes 10, 15 minutes behind, which makes the RCA impossible."
"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."
"No ability to encapsulate a query or a filter, and communicate or share that among the team."
 

Pricing and Cost Advice

"The price of Amazon CloudWatch is reasonable for detailed basic monitoring."
"The pricing model is pay-as-you-go so you have to be mindful of usage to manage costs."
"I consider it as a medium-priced 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."
"We have monthly licensing costs. The licenses are probably in the vicinity of about $300 - $350/month."
"The price is okay for me."
"It’s an open-source solution."
"The pricing can be considered reasonable, especially when already operating on a cloud platform."
Information not available
report
Use our free recommendation engine to learn which Application Performance Monitoring (APM) and Observability solutions are best for your needs.
893,221 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Manufacturing Company
9%
Transportation Company
8%
Computer Software Company
8%
Transportation Company
18%
Construction Company
17%
Comms Service Provider
12%
Outsourcing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business17
Midsize Enterprise9
Large Enterprise24
No data available
 

Questions from the Community

What needs improvement with Amazon CloudWatch?
Amazon CloudWatch itself provides a lot of data. However, for visualization, we need to use third-party tools. We are in a process of integrating Grafana, Loki, and Prometheus to have better visual...
What is your primary use case for Amazon CloudWatch?
Amazon CloudWatch is a very small service that AWS provides. It is a monitoring service for applications within the AWS cloud, and we can integrate external applications using the APIs or SDK. The ...
Ask a question
Earn 20 points
 

Comparisons

 

Also Known As

No data available
LogDNA
 

Overview

 

Sample Customers

AirAsia, Airbnb, Aircel, APUS, Avazu, Casa & Video, Futbol Club Barcelona (FCBarcelona), National Taiwan University, redBus
Instacart, Asics, Lime, Salesforce
Find out what your peers are saying about Amazon CloudWatch vs. Mezmo and other solutions. Updated: April 2026.
893,221 professionals have used our research since 2012.