We performed a comparison between Amazon CloudWatch and Azure Cost Management based on real PeerSpot user reviews.
Find out what your peers are saying about Splunk, Datadog, Wazuh and others in Log Management."Amazon CloudWatch's best feature stems from its ability to monitor app performance."
"Monitoring time and ensuring ease in it is the most valuable feature."
"The most valuable feature of Amazon CloudWatch is the monitoring and UI."
"We use Amazon CloudWatch for logging."
"The most valuable features of Amazon CloudWatch are metrics, dashboards, alarms, logs, events, logs insight, and application insights."
"We have found the pricing to be reasonable."
"It's a very simple logging system."
"The detection is the most valuable feature."
"The tool helps with budgeting and reporting. It notifies us whenever we cross the threshold."
"It is easy to log in, and everything is graphical so that you can build on the published resources."
"The tool is very stable."
"The most valuable feature of Azure Cost Management is its way of segregating accounts based on resources."
"The most valuable feature of Azure Cost Management is cost optimization."
"The product provides visibility into what we are consuming."
"The cost analysis and exportability are the most valuable features of the solution."
"It is a fully scalable product with the potential to enhance our application and increase our servers. All cloud-based solutions are fully scalable."
"The technical support must be improved."
"It's not an advanced way of monitoring."
"I would like to monitor inbound and outbound transfer. I would also like to control the traffic for load balancing."
"The product's configuration has some challenges. The solution needs to be more user-friendly."
"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 configuration capabilities could be better."
"The solution should provide human-readable metrics."
"CloudWatch's scalability could be improved."
"The policy-based remediation is probably the biggest area where Azure is lacking and that's why we sell a lot of our technology to our customers."
"We would like to see more flexibility added to this solution, such as being able to compare reservations, or compare costs across multiple financial years and report on the reasons for deviation in spend."
"If it worked better with other cloud providers it would be better."
"It would be nice if they could introduce connections to other clouds. It would be good to connect to AWS and Oracle cloud."
"The dashboard could be improved."
"The solution's technical support should be faster, more knowledgeable, and customer-friendly."
"Cost Management could always provide more details. The more information, the better. They just need to build on what they have now."
"Stability is an area in the solution that lacks in certain areas. So, it needs to be improved."
Amazon CloudWatch is ranked 12th in Log Management with 40 reviews while Azure Cost Management is ranked 2nd in Cloud Cost Management with 41 reviews. Amazon CloudWatch is rated 8.0, while Azure Cost Management 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 Azure Cost Management writes "A good, but limited cost information solution with strong analytics but requiring more flexibility in its reporting functionality". Amazon CloudWatch is most compared with Zabbix, Datadog, Google Cloud's operations suite (formerly Stackdriver), Dynatrace and VMware Aria Operations for Applications, whereas Azure Cost Management is most compared with IBM Turbonomic, VMware Aria Cost powered by CloudHealth, AWS Savings Plans, Cloudability and Nutanix Cloud Manager (NCM).
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.
