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

Amazon CloudWatch vs Logz.io 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 Log Management
16th
Average Rating
8.0
Reviews Sentiment
7.2
Number of Reviews
47
Ranking in other categories
Application Performance Monitoring (APM) and Observability (13th), Cloud Monitoring Software (11th)
Logz.io
Ranking in Log Management
32nd
Average Rating
8.2
Reviews Sentiment
7.5
Number of Reviews
8
Ranking in other categories
Security Information and Event Management (SIEM) (40th)
 

Mindshare comparison

As of October 2025, in the Log Management category, the mindshare of Amazon CloudWatch is 2.1%, up from 1.3% compared to the previous year. The mindshare of Logz.io is 0.5%, up from 0.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Log Management Market Share Distribution
ProductMarket Share (%)
Amazon CloudWatch2.1%
Logz.io0.5%
Other97.4%
Log Management
 

Featured Reviews

Rahul Kundu - PeerSpot reviewer
Proactively address issues with seamless monitoring while enhancing custom metrics functionality
We use CloudWatch for monitoring and logging. It helps us monitor our applications' performance, particularly in ensuring that every API hit returns a response within four seconds, which is our SLA. We also monitor invocation errors in Lambda and use CloudWatch alerts to notify us of any issues…
Derrick Brockel - PeerSpot reviewer
The solution is a consistent logging platform that provides excellent query mechanisms
We can query a lot of data points and build dashboards. The vendor is good at adjusting their models. Most companies want us to forecast our yearly use and pay it upfront on day one. With Logz.io, we commit to use 14 TB in a year. However, they measure us every month and give us a monthly bill. Depending on our monthly usage, we pay for 14 TB divided by 12 months or a little extra. It's a little bit more like AWS. Other solutions do not do it. They want their money upfront. We really like the dashboards. We have 36 sub-accounts. Each sub-account is an app, and we could put restrictions on that app. Previously, there were capacity restrictions on the sub-accounts. If we have a sub-account of 1 TB and use only 100 GB, we waste 900 GB that day. We could not share it between sub-accounts. Now, they provide an overhead volume. We do a reserve, and any sub-account could use anything over the reserve. It utilizes our footprint better.

Quotes from Members

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

Pros

"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."
"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 most valuable feature of Amazon CloudWatch is collecting the logs from Lambda."
"The solution effectively monitors golden signals like CPU, page requests, and queues."
"CloudWatch immediately hooks up and connects to the KPIs and all the metrics."
"Our team finds it overall quite useful."
"We have found the pricing to be reasonable."
"The tool is simple to setup where it is just plug and play. The tool is reliable and we never had any performance issues."
"It is massively useful and great for testing. We can just go, find logs, and attach them easily. It has a very quick lookup. Whereas, before we would have to go, dig around, and find the server that the logs were connected to, then go to the server, download the log, and attach it. Now, we can just go straight to this solution, type in the log ID and server ID, and obtain the information that we want."
"InsightOne is the main reason why we use LogMeIn. This is mostly because of log data that we are pushing tools and logs in general."
"The visualizations in Kibana are the most valuable feature. It's much more convenient to have a visualization of logs. We can see status really clearly and very fast, with just a couple of clicks."
"The other nice thing about Logz.io is their team. When it comes to onboarding, their support is incredibly proactive. They bring the brand experience from a customer services perspective because their team is always there to help you refine filters and tweak dashboards. That is really a useful thing to have. Their engagement is really supportive."
"We use the tool to track the dev and production environment."
"We use the product for log collection and monitoring."
"The query mechanism for response codes and application health is valuable."
 

Cons

"The integration with third-party tools must be made easier."
"The product should provide more features."
"The technical support must be improved."
"It's not very intuitive. It doesn't have drag-and-drop functionality to trigger actions from notifications."
"The product's configuration has some challenges. The solution needs to be more user-friendly."
"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."
"Incorporating a straightforward method or a plug-and-play solution for integrating these databases with our systems, facilitating smooth data transfer, and enabling the creation of dashboards for monitoring and analysis would be beneficial."
"I would like granularity on alerting so we can get tentative alerts and major alerts, then break it down between the two."
"I would like them to improve how they manage releases. Some of our integrations integrate specifically with set versions. Logz.io occasionally releases an update that might break that integration. On one occasion, we found out a little bit too late, then we had to roll it back."
"When it comes to reducing our troubleshooting time, it depends. When there are no bugs in Logz.io, it reduces troubleshooting by 5 to 10 percent. When there are bugs, it increases our troubleshooting time by 200 percent or more."
"Capacity planning could be a little bit of a struggle."
"The solution needs to expand its access control and make it accessible through API."
"The solution needs to improve its data retention. It should be greater than seven days. The product needs to improve its documentation as well."
"The price can be cheaper and they should have better monitoring."
"The product needs improvement from a filtering perspective."
 

Pricing and Cost Advice

"It’s an open-source solution."
"The pricing model is pay-as-you-go so you have to be mindful of usage to manage costs."
"It is a free-of-charge service."
"The price is okay for me."
"Amazon CloudWatch is a cheap solution."
"The product's cost is relatively inexpensive."
"Amazon CloudWatch has very cheap pricing, and it hardly costs my company $25-$30 a month for fifty systems, so it's pretty affordable."
"I consider it as a medium-priced solution."
"You pay for what you need, and that is a good model. They are also quite happy to talk to you about your uses and your use case. They will even go as far as suggesting things that you don't need to do in order to save you money. At one point, I was quite surprised at how cheap it could be if we wanted it to be or how much they would help us manage our costs."
"The product is a little expensive."
"The product's pricing is cheaper than other solutions."
"At the time it was set up, we thought Logz.io was very reasonable for what we were getting in terms of how much time and hosting costs it was saving us, because you don't have to run the servers for it anymore."
"The tool is an open source product."
report
Use our free recommendation engine to learn which Log Management solutions are best for your needs.
868,787 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
17%
Computer Software Company
12%
Manufacturing Company
10%
University
4%
Computer Software Company
14%
Financial Services Firm
11%
Comms Service Provider
11%
Manufacturing Company
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business17
Midsize Enterprise8
Large Enterprise24
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise1
Large Enterprise6
 

Questions from the Community

What is your experience regarding pricing and costs for Amazon CloudWatch?
Overall, the pricing of Amazon CloudWatch is very expensive.
What needs improvement with Amazon CloudWatch?
Apart from traceability of network resources, Amazon CloudWatch needs to be more interoperable with other tools because many companies are starting to use AI-based dashboards. When using third-part...
What do you like most about Logz.io?
The query mechanism for response codes and application health is valuable.
What is your experience regarding pricing and costs for Logz.io?
The product is a little expensive. We're pushing 17 TB. It costs us one and a half million dollars a year.
What needs improvement with Logz.io?
Capacity planning could be a little bit of a struggle. The product must add some AI capabilities to learn from previous behaviors. Instead of us setting thresholds, the tool should learn the thresh...
 

Comparisons

 

Also Known As

No data available
Logz
 

Overview

 

Sample Customers

AirAsia, Airbnb, Aircel, APUS, Avazu, Casa & Video, Futbol Club Barcelona (FCBarcelona), National Taiwan University, redBus
Dish Network, The Economist, Forbes, Holler, Kenshoo, OneSpan, Siemens, Sisense, Unity, ZipRecruiter
Find out what your peers are saying about Amazon CloudWatch vs. Logz.io and other solutions. Updated: September 2025.
868,787 professionals have used our research since 2012.