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

Akamai mPulse vs Amazon CloudWatch comparison

Why PeerSpot?
 

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

Akamai mPulse
Ranking in Application Performance Monitoring (APM) and Observability
64th
Average Rating
6.6
Reviews Sentiment
5.5
Number of Reviews
6
Ranking in other categories
No ranking in other categories
Amazon CloudWatch
Ranking in Application Performance Monitoring (APM) and Observability
24th
Average Rating
8.0
Reviews Sentiment
7.2
Number of Reviews
49
Ranking in other categories
Log Management (19th), Cloud Monitoring Software (14th)
 

Mindshare comparison

As of October 2026, in the Application Performance Monitoring (APM) and Observability category, the mindshare of Akamai mPulse is 0.6%, up from 0.5% compared to the previous year. The mindshare of Amazon CloudWatch is 1.0%, down from 1.7% 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.0%
Akamai mPulse0.6%
Other98.4%
Application Performance Monitoring (APM) and Observability
 

Featured Reviews

Arivu Arumugam - PeerSpot reviewer
Staff Engineer at a financial services firm with 10,001+ employees
Lacking in regard to observation of the entire platform but does dynamic injections from within
There is little that's unique about mPulse but since the solution is part of Akamai, you can do dynamic injections from within the product which is a great feature. the UI is quite good. It offers a basic set of features but nothing unique other than that as part of Akamai, you can do dynamic injections.
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.

Quotes from Members

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

Pros

"There's a good relationship between the price and the licences."
"There is little that's unique about mPulse but since the solution is part of Akamai, you can do dynamic injections from within the product which is a great feature."
"It provides a great overview for management regarding user experience."
"It’s a very good product for performance tracking, I haven’t used many others, so I can’t comment on a competitive level."
"The most valuable feature is the solutions overall performance. It is very efficient and accurate for our usage."
"It provides real-time monitoring for performance and availability of specific portions of the website without a significant data overhead."
"We are a worldwide company and we need to have a solution with good performance which the solution is providing us with; it has helped our company."
"Enables dynamic injections from within the product which is great."
"The most valuable feature of Amazon CloudWatch is collecting the logs from Lambda."
"It is very easy to use; as a monitoring tool, whenever your system experiences issues, it will notify you and is directly linked to your service."
"We use Amazon CloudWatch for logging."
"We can create events and alerts. We use the information to dive down into the infrastructure performance."
"Every time we get an alarm or have an incident, CloudWatch is always there. We use it not only for resources we've spun up in the cloud, but also for some of our on-premises resources."
"The solution offers very detailed metrics for their services."
"We have found the pricing to be reasonable."
"CloudWatch provides essential monitoring capabilities that integrate seamlessly with other AWS services."
 

Cons

"It needs a more intuitive GUI and more customization options."
"In the next release, I would like to see the possibility of sharing the metric from this solution with other solutions."
"The end-to-end distributor tracing connectivity isn't there."
"They work very well, only thing is they need more time to improve and fix all the issues."
"The solution didn't help us much and that's the reason we never used mPulse on a full scale and why we chose to go with Dynatrace."
"Scalability to larger volume of data seems to be hit or miss."
"There could be further enhancements through CloudWatch's partnerships."
"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."
"What would make Amazon CloudWatch better is if it includes more on-site checks, particularly status checks on the CPU, network input/output, etc. It would also be helpful if there's built-in swap space, disk, and memory monitoring in Amazon CloudWatch because, at the moment, my team has to configure it manually through a shell script."
"There is room for improvement in terms of stability."
"Amazon CloudWatch has all the data, but to see what is happening, you need some third-party tool."
"Right now, in relation to monitoring services, there are too many services and too many metrics per service."
"Maybe Amazon Web Services can improve by providing a library for CloudWatch with some useful features."
"It is hard to configure; it is not a straightforward tool."
 

Pricing and Cost Advice

Information not available
"It is a free-of-charge service."
"The product's cost is relatively inexpensive."
"I consider it as a medium-priced solution."
"The solution is expensive."
"The price is okay for me."
"We have monthly licensing costs. The licenses are probably in the vicinity of about $300 - $350/month."
"The pricing can be considered reasonable, especially when already operating on a cloud platform."
"Amazon CloudWatch is a cheap solution."
report
Use our free recommendation engine to learn which Application Performance Monitoring (APM) and Observability solutions are best for your needs.
915,341 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
11%
Financial Services Firm
11%
Construction Company
10%
Outsourcing Company
6%
Financial Services Firm
13%
Manufacturing Company
10%
Outsourcing Company
8%
Comms Service Provider
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business1
Large Enterprise6
By reviewers
Company SizeCount
Small Business17
Midsize Enterprise8
Large Enterprise26
 

Questions from the Community

Ask a question
Earn 20 points
What is your experience regarding pricing and costs for Amazon CloudWatch?
The experience with pricing, setup cost, and licensing for Amazon CloudWatch has been positive. It was very easy to set up because it is built into AWS and does not require separate licensing, bein...
What needs improvement with Amazon CloudWatch?
For improvements, I think Amazon CloudWatch could enhance certain areas, particularly regarding pricing structure. I wish to see simpler pricing, more intuitive dashboards, easier log queries for b...
What is your primary use case for Amazon CloudWatch?
My main use case for Amazon CloudWatch is the monitoring and analytics of the application servers. I basically use Amazon CloudWatch to monitor the microservices and AWS infrastructure, helping me ...
 

Also Known As

SOASTA mPulse
No data available
 

Overview

 

Sample Customers

Nordstrom, Gatwick, DirecTV, MSN, SquareSpace, SAP, Lenovo, Hallmark, myspace, Intuit, Kentucky Derby, Toys "R" Us, Netflix, Newsweek, The Washington Post, Lowe's, Nike, REI, Apple, Sears, Verizon, Wendy's, Huawei
AirAsia, Airbnb, Aircel, APUS, Avazu, Casa & Video, Futbol Club Barcelona (FCBarcelona), National Taiwan University, redBus
Find out what your peers are saying about Akamai mPulse vs. Amazon CloudWatch and other solutions. Updated: September 2026.
915,341 professionals have used our research since 2012.