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
14th
Average Rating
8.0
Reviews Sentiment
7.2
Number of Reviews
46
Ranking in other categories
Application Performance Monitoring (APM) and Observability (13th), Cloud Monitoring Software (10th)
Logz.io
Ranking in Log Management
20th
Average Rating
8.2
Reviews Sentiment
7.5
Number of Reviews
8
Ranking in other categories
Security Information and Event Management (SIEM) (24th)
 

Mindshare comparison

As of April 2025, in the Log Management category, the mindshare of Amazon CloudWatch is 1.9%, up from 1.0% compared to the previous year. The mindshare of Logz.io is 0.4%, down from 0.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Log Management
 

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.
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."
"Scheduling is a valuable feature."
"It's a very simple logging system."
"We use Amazon CloudWatch for logging."
"Amazon CloudWatch is a cheap and easy-to-use solution."
"The detection is the most valuable feature."
"It offers direct integrations with various storage providers, making it convenient to push logs from CloudWatch to these external platforms."
"The monitoring feature is valuable."
"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."
"The tool is simple to setup where it is just plug and play. The tool is reliable and we never had any performance issues."
"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."
"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."
"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."
"We use the product for log collection and monitoring."
"We use the tool to track the dev and production environment."
"The query mechanism for response codes and application health is valuable."
 

Cons

"There could be further enhancements through CloudWatch's partnerships."
"Adding conditional expressions would enhance its functionality."
"Right now, in relation to monitoring services, there are too many services and too many metrics per service."
"The product’s documentation must be improved."
"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 solution's integration could be easier for laypersons."
"We'd like the interface to be as easy as Datadog."
"I would like to monitor inbound and outbound transfer. I would also like to control the traffic for load balancing."
"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."
"The product needs improvement from a filtering perspective."
"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."
"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."
"I would like granularity on alerting so we can get tentative alerts and major alerts, then break it down between the two."
"The price can be cheaper and they should have better monitoring."
"Capacity planning could be a little bit of a struggle."
 

Pricing and Cost Advice

"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 pricing model is pay-as-you-go so you have to be mindful of usage to manage costs."
"The pricing is average."
"I consider it as a medium-priced solution."
"Its pricing is reasonable. It is sometimes tricky, but it is reasonable as compared to others."
"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."
"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."
"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."
"The tool is an open source product."
report
Use our free recommendation engine to learn which Log Management solutions are best for your needs.
845,406 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
18%
Financial Services Firm
17%
Manufacturing Company
8%
University
5%
Computer Software Company
19%
Financial Services Firm
12%
Comms Service Provider
12%
Manufacturing Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

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 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: March 2025.
845,406 professionals have used our research since 2012.