We compared Amazon CloudWatch and LogRhythm SIEM based on our users' reviews in five categories. We reviewed all of the data and you can find the conclusion below.
Features: Amazon CloudWatch users liked the solution’s simplicity, intuitive interface, and ability to handle large workloads. Users also praised CloudWatch’s comprehensive monitoring and alerts. Users praised LogRhythm SIEM for its user-friendly centralized dashboard, strong integration capabilities, and event-filtering capabilities. Some reviews mentioned that Amazon CloudWatch could improve performance and dashboard visualization through. Others noted that the solution lacked compatibility with some databases. LogRhythm SIEM has the potential to improve its SOAR and NDR features, platform stability, and MDI integration. LogRhythm users requested expanded log storage, better load balancing, and streamlined search capabilities.
Service and Support: Customers generally have positive opinions about Amazon's customer service. They commended the support team for its availability and timely issue resolution. LogRhythm SIEM was generally praised for its helpful and knowledgeable support, although there have been occasional delays and knowledge problems.
Ease of Deployment: Amazon CloudWatch is generally described as easy to set up. LogRhythm SIEM's setup is considered to be straightforward. However, it is more time-consuming and complex for enterprise deployments involving multiple components or vendors, and users often require assistance from professional services or LogRhythm-certified engineers.
Pricing: Amazon CloudWatch offers a flexible pricing structure based on usage and processing, without any separate licensing cost. Some users said that scaling up can be costly due to the need for additional storage space. LogRhythm SIEM’s license typically includes all elements. However, enterprise customers may encounter complexities related to additional features and add-ons.
ROI: Amazon CloudWatch offers a return on investment by minimizing the need for manual monitoring. LogRhythm SIEM has proven to be highly valuable, delivering a significant ROI by reducing the mean time to detect and respond.
"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."
"Our team finds it overall quite useful."
"The alarms are one thing I love about AWS CloudWatch. It has alerts that notify us when resource use is approaching the limit."
"The most valuable features of Amazon CloudWatch are metrics, dashboards, alarms, logs, events, logs insight, and application insights."
"Amazon CloudWatch is a cheap and easy-to-use solution."
"The solution offers very detailed metrics for their services."
"The most valuable feature of Amazon CloudWatch is the monitoring and UI."
"The most valuable feature of Amazon CloudWatch is collecting the logs from Lambda."
"We have NetFlow information going into it, so we can examine a lot of traffic patterns and anomalies, especially if something stands out and is not the baseline. This helps a lot."
"Compliance reporting is another great feature of this product. It has built in reports right out of the box."
"We use this solution to examine disparate log sources and provide a cohesive method to search for anomalous behavior."
"We have to be able to show the evidence, and LogRhythm does a great job of putting it forward and making it easy to create reports with nice looking dashboards, which show off what we are doing as a security program."
"It seems like it will scale easily with the way our environment is set up."
"When it comes to dealing with support, all my interactions have been great. Everyone has known what they're doing and have been quick to respond. They seem to always know the answer. I haven't stumped anybody yet."
"I would rate the product a ten out of ten. The solution is very user-friendly and straightforward. The tool's report customization is interesting."
"The ability to investigate a particular period of time where you can analyze logs is its most valuable feature."
"What would make Amazon CloudWatch better is if it includes more on-site checks, particularly status checks on the CPU, network input/output, etc. It would also be helpful if there's built-in swap space, disk, and memory monitoring in Amazon CloudWatch because, at the moment, my team has to configure it manually through a shell script."
"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 monitoring part and GUI are areas in Amazon CloudWatch that have shortcomings currently and can be considered for improvements in the future."
"There could be further enhancements through CloudWatch's partnerships."
"The solution could benefit from a price decrease."
"The solution's pricing is a bit higher."
"The product's configuration has some challenges. The solution needs to be more user-friendly."
"The configuration capabilities could be better."
"Move it to Linux. I would like to see it get off the SQL Server."
"Better integration with different services is needed, as there are quite a few platforms that we use that don't integrate very smoothly with LogRhythm."
"When we had version 7.2.6, there were a lot of issues deploying that version and with the indexing. The indexer was unstable. So, we were not able to use the platform when we were on that version until we were able to upgrade to 7.3.4."
"We do about 750 million a day and some days we do 715 million. Some days we do 820 million or 1.2 billion. But there's no way to drill in and find out: "Where did I get 400,000 extra logs today?" What was going on in my environment that I was able to absorb that peak? I have no way to identify it without running reports, which will produce a long-running PDF that I have to somehow compare to another long-running PDF... I would like to see like profiling behavior awareness around systems like they've been gunned to do around users with UEBA."
"I would like to see support added for Exchange 2016, and CheckPoint OPSec Lea."
"Appliance-based setups can sometimes pose scalability issues"
"I would probably look for more things to go into the web console that is currently on the fat client."
"I think they probably need to, because a lot of companies are having this cloud-first strategy, where anything that's new has to go into the cloud for some reason."
Amazon CloudWatch is ranked 12th in Log Management with 40 reviews while LogRhythm SIEM is ranked 7th in Log Management with 166 reviews. Amazon CloudWatch is rated 8.0, while LogRhythm SIEM is rated 8.4. The top reviewer of Amazon CloudWatch writes "Instantaneous response when monitoring logs and KPIs". On the other hand, the top reviewer of LogRhythm SIEM writes "The solution reduced our investigation time from days to hours and assists in managing our workflows". Amazon CloudWatch is most compared with Zabbix, Datadog, Google Cloud's operations suite (formerly Stackdriver), Dynatrace and SolarWinds NPM, whereas LogRhythm SIEM is most compared with IBM Security QRadar, Splunk Enterprise Security, Microsoft Sentinel, Wazuh and LogRhythm Axon. See our Amazon CloudWatch vs. LogRhythm SIEM 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.