We performed a comparison between Amazon CloudWatch and Grafana Loki 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 collecting the logs from Lambda."
"Most of it's around optimizing utilization, their cloud utilization. They're making sure that they're getting the most out of their in-cloud environments and their instances. Making sure that there's no strange behavior in the environment."
"The monitoring feature is valuable."
"You can enable alarms and metrics, and it has robust integration with AWS services. You can also trigger events. For example, if the CPU utilization is above 80%, it can launch a new instance for you."
"Monitoring time and ensuring ease in it is the most valuable feature."
"The most valuable feature of Amazon CloudWatch is the monitoring and UI."
"The solution gives us very good real-time data."
"The alarms are one thing I love about AWS CloudWatch. It has alerts that notify us when resource use is approaching the limit."
"The best feature of Grafana Loki is that it integrates well with our other tool."
"The log collection feature is good and the solution is easily understandable. v"
"The most valuable features of the solution stem from the fact that it is an open-source tool that is stable and flexible."
"Loki also utilizes the same service discovery mechanism as used by Prometheus. So, whatever labeled metadata you see in Prometheus, you have the exact same metadata in the Loki system. Given this level of intricacy and the attempt to address these challenges, I firmly believe that Loki deserves praise for the work."
"The most valuable feature of the solution is the tool's GUI. The solution's GUI is very user-friendly."
"The most valuable feature is the capability to set up alerts, which becomes necessary when we need to receive notifications for specific events."
"The effectiveness of filters is pivotal for optimizing the search process and extracting the specific information we need from the extensive log data."
"The solution's stability has never been a problem. Stability-wise, I rate the solution a nine to ten out of ten."
"The drill-down aspect on the dashboard of the solution needs improvement. We get a very good high-level overview, but when we drill down, it becomes a little less clear. We have given this feedback to AWS as well and hope they will improve this in the future."
"When customers want to see the CPU or memory utilization there is a cost. This should be free to see the utilization."
"I think something that can be improved are the alerts and alerting mechanism based on no rejects. We want to have it more flexible and that is one of the key things that is required."
"It is hard to configure; it is not a straightforward tool."
"CloudWatch doesn’t monitor disk throughput by default."
"The configuration capabilities could be better."
"This product lacks some features: real-time data stream monitoring, application performance monitoring, mobile app monitoring, and live dashboards. Its workflows also need improvement."
"Better reporting is always something needed. That could be an answer to just about anything. But you always want better reporting, better dashboards, things that are just more dynamic and more accessible."
"My main concern is the recommended production-grade setup. They suggest using tools like Tanka or Jsonnet. They should simplify the process to increase adoption."
"The correlation of requests is not simple in Grafana Loki and can be improved."
"We had a well-structured dashboard with a functional query. However, an issue arose when the Kubernetes pod restarted. The statistics from our Grafana query would reset, dropping to zero and starting anew. This was particularly noticeable with linear graphs, which are expected to show consistent growth."
"In Grafana Loki, the creation of metrics is not so easy, making it an area that could be made easier."
"The solution's scalability depends on the team managing the Grafana instance."
"The Docker container partition feature needs improvement as they do not reuse the space and goes into a pending state."
"We encountered certain limitations when it came to alerting, particularly when dealing with specific data sources."
"There is a need for some change in the alerting types of the product. In short, a few changes in the alert area are needed due to minor shortcomings."
Amazon CloudWatch is ranked 12th in Log Management with 40 reviews while Grafana Loki is ranked 13th in Log Management with 12 reviews. Amazon CloudWatch is rated 8.0, while Grafana Loki is rated 8.0. The top reviewer of Amazon CloudWatch writes "Instantaneous response when monitoring logs and KPIs". On the other hand, the top reviewer of Grafana Loki writes "Effective for Logging, recovery from node failures is fast and single UI supports metrics, logs, and even tracing". Amazon CloudWatch is most compared with Zabbix, Datadog, Google Cloud's operations suite (formerly Stackdriver), Dynatrace and SolarWinds NPM, whereas Grafana Loki is most compared with Graylog, Wazuh, syslog-ng, Splunk Enterprise Security and Fortinet FortiAnalyzer. See our Amazon CloudWatch vs. Grafana Loki report.
See our list of best Log Management 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.
