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

AWS Auto Scaling vs Mezmo 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

AWS Auto Scaling
Ranking in Application Performance Monitoring (APM) and Observability
15th
Average Rating
8.8
Reviews Sentiment
7.0
Number of Reviews
21
Ranking in other categories
No ranking in other categories
Mezmo
Ranking in Application Performance Monitoring (APM) and Observability
92nd
Average Rating
9.0
Number of Reviews
2
Ranking in other categories
Log Management (55th), Observability Pipeline Software (7th)
 

Mindshare comparison

As of June 2025, in the Application Performance Monitoring (APM) and Observability category, the mindshare of AWS Auto Scaling is 0.1%, up from 0.1% compared to the previous year. The mindshare of Mezmo is 0.1%, up from 0.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Performance Monitoring (APM) and Observability
 

Featured Reviews

Mbula Mboma - PeerSpot reviewer
Boosts deployment efficiency with seamless automatic scaling capabilities
My primary use case for Auto Scaling is mainly to deploy applications at scale Auto Scaling has made the deployment of applications more efficient, allowing us to manage traffic and maintain performance as user counts increase. Auto Scaling is a cool feature that works well and its automatic…
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

"AWS Auto Scaling is very good for managing traffic and creating new instances when necessary."
"I like the graphs provided by the tool."
"It can scale."
"Our internal business applications are hosted in AWS Auto Scaling."
"AWS Auto Scaling is very good for managing traffic and creating new instances when necessary."
"The solution helps optimize the cost of the AWS environment."
"The most valuable feature is the ability to select a minimum amount of active servers so that a new server automatically launches if one fails."
"AWS Auto Scaling is cost-effective and very useful for businesses."
"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 product’s security features need improvement."
"Setting up the configuration involves too much work for the cloud engineer."
"It is sometimes very critical to deploy on AWS since some servers are already running in the background. There are challenges for employees on how to deploy at a given time."
"The product’s pricing needs improvement."
"The setup can be a bit complex in some situations."
"The speed of the solution must be improved."
"We can have more auto scaling algorithms implemented in AWS Auto Scaling."
"The solution must improve automation."
"No ability to encapsulate a query or a filter, and communicate or share that among the team."
"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."
 

Pricing and Cost Advice

"The pricing is good. I have not had any customers that have complained about the price."
"The product is expensive."
"AWS Auto Scaling is a pay-per-use and pay-as-you-use service."
"AWS Auto Scaling is an expensive solution."
"The product has moderate pricing."
"AWS Auto Scaling's price is high."
"AWS Auto Scaling is a cheap solution."
Information not available
report
Use our free recommendation engine to learn which Application Performance Monitoring (APM) and Observability solutions are best for your needs.
855,164 professionals have used our research since 2012.
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What do you like most about AWS Auto Scaling?
The tool's most valuable feature is vertical auto-scaling, which is easy to use. However, most companies now prefer horizontal scaling. I set up the health check integration to monitor CPU usage. W...
What is your experience regarding pricing and costs for AWS Auto Scaling?
The pricing of Auto Scaling is medium range, neither high nor low.
What needs improvement with AWS Auto Scaling?
It is sometimes very critical to deploy on AWS since some servers are already running in the background. There are challenges for employees on how to deploy at a given time. It requires a downtime ...
Ask a question
Earn 20 points
 

Also Known As

AWS Auto-Scaling
LogDNA
 

Overview

 

Sample Customers

Expedia, Intuit, Royal Dutch Shell, Brooks Brothers
Instacart, Asics, Lime, Salesforce
Find out what your peers are saying about AWS Auto Scaling vs. Mezmo and other solutions. Updated: June 2025.
855,164 professionals have used our research since 2012.