We compared Amazon CloudWatch and LogicMonitor 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. LogicMonitor stands out for its seamless integration with external applications, personalized dashboards, and efficient AIOps functionality.
Room for improvement: Some reviews mentioned that Amazon CloudWatch could improve performance and dashboard visualization. Others noted that the solution lacked compatibility with some databases. LogicMonitor users have requested better dashboards, customizable alerts, and more automation. Some also suggested improvements in the solution’s AI 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. LogicMonitor's support team is praised for being helpful, knowledgeable, and responsive. The solution also offers learning resources and ample information to help users navigate and customize the platform.
Ease of Deployment: Amazon CloudWatch is generally described as easy to set up. LogicMonitor's initial setup is generally regarded as effortless. Users appreciated the vendor’s help during onboarding and the solution’s extensive documentation.
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. LogicMonitor’s licensing model is based on the size of the environment. It is seen as a high-end solution with a high price tag and may be too costly for smaller organizations.
ROI: Amazon CloudWatch offers a return on investment by minimizing the need for manual monitoring. LogicMonitor users have seen an ROI in the form of increased visibility and shorter resolution times.
Comparison Results: Reviewers say that Amazon CloudWatch is a simple, intuitive solution that can handle large workloads, but some mentioned dashboard visualization and customizability as areas for improvement. LogicMonitor is a premium solution geared toward large enterprises, featuring smooth integration and advanced AIOps features. Users praised LogicMonitor for its painless setup process and excellent support, but some noted that the solution’s steep price tag might put it out of the range of smaller businesses and that it could improve dashboards and AI capabilities.
"The most valuable feature of Amazon CloudWatch is intrusion prevention."
"The detection is the most valuable feature."
"The most valuable feature of Amazon CloudWatch is collecting the logs from Lambda."
"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."
"It's a very simple logging system."
"Setting up this product was easy. I found data analytics as its most valuable feature."
"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."
"The product can be integrated with AWS very easily."
"LogicMonitor helps us prevent potential downtime. It's pretty good. It generates low-level warnings that aren't necessarily preemptive but can still alert us to issues we should investigate. These warnings allow us to correlate data and identify areas where we should take action, even if the issues aren't critical."
"The alerting would be number one in my book. The thresholds for getting alerts for different criteria are pretty well-thought-out. We don't get many false positives or negatives on the alerting side. If we do get an email alert or some similar alert, we know that it is something that has to be looked at."
"The solution’s overall reporting capabilities are pretty powerful compared to ones that I have used previously. It seems like it has a lot of customizations that you can put in, but some of the out-of-the-box reports are useful too, like user logon duration and website latency. Those type of things have been helpful and don't require a lot of, if any, changes to get useful content out of them. They have also been pretty easy to implement and use."
"Having a full team at LogicMonitor for support is super helpful as they are available all the time to answer any questions you may have."
"It's the depth of data that it gathers that I find really useful because there's nothing worse, when you're trying to find information about something or dig deeper into something, than hitting the bottom of the information really quickly and not having enough information to work with. With LogicMonitor, there is a load of information to dig through. It's a really good solution for that."
"The initial setup is very simple."
"The most valuable feature of LogicMonitor is the infrastructure monitoring capability."
"I really appreciate the reporting function because it allows me to create dashboards that will be emailed to me during the morning so that I have a complete overview of my client's health, within a specific time frame."
"The solution's integration could be easier for laypersons."
"The product's configuration has some challenges. The solution needs to be more user-friendly."
"It's not an advanced way of monitoring."
"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."
"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."
"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."
"CloudWatch's scalability could be improved."
"Automated remediation of issues has room for improvement. I don't know how best to handle it, but I know that they're kind of working on it. I know there are some resources that can do automated remediation. I would like them to improve this area so it could be completely hands-free, where it detects an issue, such as, if a CPU is running high. There are ways to do it even now, but it's a bit more involved."
"There are some very specific things that need improvement in LogicMonitor. One is the lack of formatting for customized alerts, particularly the delivery of them to our email channel. We'd also like to see further customization of dashboards. Finally, something that is specific to us as an MSP that uses LogicMonitor, is white-labeling or skinning of the product, so we can make it look more customer-focused for our customers."
"One of the areas that I sometimes find confusing is the way that the data is presented. For example, a couple of weeks back I was looking at bandwidth utilization. That's quite a difficult thing to present, but they should try to dumb down how the data is presented and simplify what they're presenting."
"Role-based permissions could be better and updating modules could be smoother."
"The topology mapping is all based on the dynamic discovery of devices that could talk to each other. There is no real manual way that you can set up a join between two devices to say, "This is how this network is actually set up." For example, if you have a device, and you're only pinning that device and not getting any real intelligent information from it, then it can't appear on the map with other devices. Or if it can appear, then it won't show you which devices are actually joined to it."
"LogicMonitor can easily easy to pull data from one item at a time. I have yet to find a good way to get LogicMonitor to show me all the WAN devices and how they're doing in terms of capacity."
"The process of upgrading some of the collectors has been a little bit confusing. I need to understand that better."
"We would like to see more functionality around mapping of topologies, in terms of networks. An improvement that we would like to see is added functionality to get more detail out of mapping. For example, if the LogicMonitor Collector identifies a connection between two network endpoints, it would be great to actually see which ports are connecting the two endpoints together. That functionality is something we greatly desire. It would actually make our documentation more dynamic in the sense that we wouldn't need to manually document. If this is something that the platform could provide, then this would be a great asset."
Amazon CloudWatch is ranked 9th in Cloud Monitoring Software with 40 reviews while LogicMonitor is ranked 13th in Cloud Monitoring Software with 25 reviews. Amazon CloudWatch is rated 8.0, while LogicMonitor is rated 9.0. The top reviewer of Amazon CloudWatch writes "Instantaneous response when monitoring logs and KPIs". On the other hand, the top reviewer of LogicMonitor writes "We went from nothing to full visibility across our internal and external estates of equipment". Amazon CloudWatch is most compared with Zabbix, Datadog, Google Cloud's operations suite (formerly Stackdriver), Dynatrace and SolarWinds NPM, whereas LogicMonitor is most compared with ScienceLogic, SolarWinds NPM, Zabbix, OpsRamp and SCOM. See our Amazon CloudWatch vs. LogicMonitor report.
See our list of best Cloud Monitoring Software vendors.
We monitor all Cloud Monitoring Software 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.
