We performed a comparison between Amazon CloudWatch and Dynatrace based on our users’ reviews in five categories. After reading all of the collected data, you can find our 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. Dynatrace is highly regarded for its advanced AI engine and ability to identify infrastructure automatically. It also offers session replay and impressive visualization features. Some reviews mentioned that Amazon CloudWatch could improve performance and dashboard visualization through. Others noted that the solution lacked compatibility with some databases. Some Dynatrace reviewers feel the learning curve is a little steep, and the documentation could be clearer. Users say that Dynatrace should offer more security options and improve integration with other tools.
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. Users generally found Dynatrace's customer service to be helpful and available, but some said that the response times and documentation have room for improvement.
Ease of Deployment: Amazon CloudWatch is generally described as easy to set up. Dynatrace's setup is simple, efficient, and requires minimal technical configuration. It takes a few hours at most.
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. Users say Dynatrace is expensive. Some noted that the licensing model is complicated and not transparent. Some said they struggled to accurately predict the number of units needed.
ROI: Amazon CloudWatch offers a return on investment by minimizing the need for manual monitoring. Dynatrace users said the solution saved them money and reduced downtime.
"CloudWatch immediately hooks up and connects to the KPIs and all the metrics."
"What my company likes best about Amazon CloudWatch is that it's on AWS. My team also likes it for its log feature. As the solution is on AWS, it also has good pricing and resource availability, plus it's what clients choose. My company also chose AWS for Forge ECS, and at the time, there was a need for the log features provided by Amazon CloudWatch, so it's the solution my team went with."
"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."
"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 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."
"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."
"We use Amazon CloudWatch for logging."
"The most valuable feature of Amazon CloudWatch is reliability."
"We have configured the alerting so the error or the incident will go to the respective team. Then, the team can contact the user once they see that they have an issue and ask if they can them resolve the issue."
"The PurePath stuff for deep dive analysis on problems. That is massive as far as having a benefit."
"Reduced MTTR, thanks to smart problem detection and automated root cause analysis."
"It will allow us to eventually become more proactive when problems start arising. We can see them before they happen and address them before there is any impact to our customers."
"We use it for monitoring all the applications in our bank, and it works fantastically."
"By using Dynatrace Managed, we have improved customer satisfaction and have also helped internal teams and subcontractors make the application more stable."
"We like the on-premises platform and the horizontal scalability."
"I have never been more confident in a tool's scalability because I've seen how easy it is for it to deal with the .NET Applets."
"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."
"When customers want to see the CPU or memory utilization there is a cost. This should be free to see the utilization."
"I would like to monitor inbound and outbound transfer. I would also like to control the traffic for load balancing."
"The product’s documentation must be improved."
"The solution's integration could be easier for laypersons."
"There is room for improvement in terms of stability."
"Amazon CloudWatch needs improvement. The main thing is we have noticed missing logs."
"It's not an advanced way of monitoring."
"There should be more visibility for network performance monitoring. There should be more metrics for things like 5G and IoT. That would be the main thing because they've moved more to mobile performance rather than fixed networks."
"Log analytics in the classic synthetic and RUM tools would be a great addition."
"There is still a bit of redundancy in Dynatrace."
"Configuration could be simpler."
"When you're making that transition from AppMon, which is very dashboard-oriented, over to Dynatrace, which is no dashboards, there needs to be something in between so that business buys in a little bit. I would transition my dashboards over so that we don't have to recreate them, because recreating them is very difficult in Dynatrace. It's really hard to say, "Oh, the dashboards that you had on the team that you were using, you're not going to get over here." Or, "You have to re-create them all over again." People are going to ask questions about cost, who is going to do that."
"Due to the fact that you doing a lot, you have a problem with the learning curve. We're really looking for ways to make this product more accessible."
"Configuring nodes and agents should be more like plug and play."
"We're developing more and more microservices and, each time, for an AppMon license, you have to deploy it, you have to configure it, you to get charged for it. It's very time-consuming."
Amazon CloudWatch is ranked 12th in Log Management with 40 reviews while Dynatrace is ranked 4th in Log Management with 340 reviews. Amazon CloudWatch is rated 8.0, while Dynatrace is rated 8.8. The top reviewer of Amazon CloudWatch writes "Instantaneous response when monitoring logs and KPIs". On the other hand, the top reviewer of Dynatrace writes "AI identifies all the components of a response-time issue or failure, hugely benefiting our triage efforts". Amazon CloudWatch is most compared with Zabbix, Datadog, Google Cloud's operations suite (formerly Stackdriver), SolarWinds NPM and Nagios XI, whereas Dynatrace is most compared with Datadog, New Relic, AppDynamics, Splunk Enterprise Security and Azure Monitor. See our Amazon CloudWatch vs. Dynatrace 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.
