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.
"What I found most valuable in Amazon CloudWatch is that it gives you detailed information, which I found helpful because it can even provide you with data for the past one minute, which is quite granular. That was what helped me most in terms of finding the root causes. Task automation is another valuable feature of Amazon CloudWatch."
"The monitoring feature is valuable."
"Amazon CloudWatch is a cheap and easy-to-use solution."
"Monitoring time and ensuring ease in it is the most valuable feature."
"It is a stable solution...I rate the technical support a ten out of ten."
"The most valuable feature of Amazon CloudWatch is its ease of use and logs. You do not have to go to each separate system to see the logs, such as Syslog and they are located in one dashboard GUI."
"The solution effectively monitors golden signals like CPU, page requests, and queues."
"Scheduling is a valuable feature."
"Currently, we are in the implementation phase. LogRhythm is better than QRadar from the point of view of collecting Windows events. It has a much higher view. You can enable monitoring by default."
"As a healthcare company, what we use it for is compliance, then to protect our data from exaltation."
"What I found most valuable in LogRhythm NextGen SIEM is that it's user-friendly. I also like its dashboard, which shows all the logs and information I want to see."
"As a SIEM, probably the best feature is that it can be tuned effectively. There are very few SIEMs out there that can be effectively tuned to provide you with meaningful information and not be overwhelmed."
"Their customer support is friendly and willing to help."
"The AI Engine can take an event and correlate it into something else giving us meaningful context regarding what is going on. We integrated it in with our ticketing system, so if an alarm fires, it raises a ticket in our system."
"We take in around 750 million logs a day. We have a lot of products and that would be a lot of different panes of glass that we would have to look through otherwise. By centralizing, we can triage and take steps much more quickly than if we tried to man that many interfaces that come with the products."
"It's reliable and the performance is good."
"We'd like the interface to be as easy as Datadog."
"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."
"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."
"The product’s documentation must be improved."
"It would be beneficial for CloudWatch to provide an API interface and some kind of custom configuration."
"There is room for improvement in terms of stability."
"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."
"More help and assistance with some of the open source products, everything seems to be focused on Windows versus giving some guidance and some documentation on how to use it."
"My big thing is the easability. I don't like to go to two different systems. The fat client that you have to install to configure it, then the web console which is just for reporting and analysis. These features need to collapse, and it needs to be in a single solution. Going through the web solution in the future is the way to do it, because right now, it is a bit cumbersome."
"The security playbook could be pre-defined and available to other analysts with similar security issues."
"We use Windows Event Forwarding to collect the logs from our Windows clients, and the logs get aggregated as one data source on that collector. Therefore, finding logs specific to one particular Windows system requires some creativity in how we search the SIEM."
"I would like to see case management become more independent from LogRhythm itself."
"The solution is likely not the best option for a smaller organization."
"The reporting on the dashboard should be improved from a management perspective. It would be helpful if they adjusted the colors and the presentation to make things clearer and easier to read."
"We would like to see more things out of the console into the web UI. I guess this is what they are doing in 7.4."
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 Fortinet FortiSIEM. 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.