We performed a comparison between Amazon CloudWatch and Google Cloud's operations suite (formerly Stackdriver) based on real PeerSpot user reviews.
Find out in this report how the two Log Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The most valuable feature of Amazon CloudWatch is reliability."
"It is a stable solution...I rate the technical support a ten out of ten."
"The product helps us collect and store various metrics to set test alarms."
"The monitoring features are valuable."
"The monitoring feature is valuable."
"The detection is the most valuable feature."
"The solution offers very detailed metrics for their services."
"We have found the pricing to be reasonable."
"The cloud login enables us to get our logs from the different platforms that we currently use."
"Our company has a corporate account for Google Cloud and so our systems and clusters integrate really well."
"It's easy to use."
"Provides visibility into the performance uptime."
"The most valuable feature is the multi-cloud integration, where there is support for both GCP and AWS."
"I like the monitoring feature."
"The features that I have found most valuable are its graphs - if I need any statistics, in Kubernetes or Kong level or VPN level, I can quickly get the reports."
"We find the solution to be stable."
More Google Cloud's operations suite (formerly Stackdriver) Pros →
"There is room for improvement in the pricing, because they have a premium version, but it's not really a premium version. It's just an enhanced monitoring version, and it can be a bit expensive depending on your usage."
"Amazon CloudWatch's pricing needs improvement."
"There's a learning curve with Amazon CloudWatch since we have to learn to write the queries to extract the keys and logs."
"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 graphical interface has room for improvement. CloudWatch only gives you a breakdown of what's wrong. However, it would be nice if it could automatically remedy the problems it identifies. You should be able to configure it so that when a specific condition arises, it will take a predefined action."
"There is room for improvement in terms of stability."
"The solution could benefit from a price decrease."
"For monitoring applications or for APM, CloudWatch has some limitations. You cannot monitor application performance from CloudWatch, and you have to go for a third-party tool."
"While we are satisfied with the overall performance, in certain cases we must add additional metrics and additional tools like Grafana and Dynatrace."
"Lacking sufficient operations documentation."
"The product provides minimal metrics that are insufficient."
"If I want to track any round-trip or breakdowns of my response times, I'm not able to get it. My request goes through various levels of the Google Cloud Platform (GCP) and comes back to my client machine. Suppose that my request has taken 10 seconds overall, so if I want to break it down, to see where the delay is happening within my architecture, I am not able to find that out using Stackdriver."
"This solution could be improved if it offered the ability to analyze charts, such as a solution like Kibana."
"It is difficult to estimate in advance how much something is going to cost."
"It could be even more automated."
"It could be more stable."
More Google Cloud's operations suite (formerly Stackdriver) Cons →
More Google Cloud's operations suite (formerly Stackdriver) Pricing and Cost Advice →
Amazon CloudWatch is ranked 12th in Log Management with 40 reviews while Google Cloud's operations suite (formerly Stackdriver) is ranked 26th in Log Management with 9 reviews. Amazon CloudWatch is rated 8.0, while Google Cloud's operations suite (formerly Stackdriver) is rated 7.8. The top reviewer of Amazon CloudWatch writes "Instantaneous response when monitoring logs and KPIs". On the other hand, the top reviewer of Google Cloud's operations suite (formerly Stackdriver) writes "Good logging and tracing but does need more profiling capabilities". Amazon CloudWatch is most compared with Zabbix, Datadog, Dynatrace, SolarWinds NPM and Nagios XI, whereas Google Cloud's operations suite (formerly Stackdriver) is most compared with AWS X-Ray, Datadog, Azure Monitor, New Relic and Grafana. See our Amazon CloudWatch vs. Google Cloud's operations suite (formerly Stackdriver) report.
See our list of best Log Management vendors and best Cloud Monitoring Software vendors.
We monitor all Log Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.