CloudWatch by a Simple Engineer
Updated May 29, 2020
CloudWatch by a Simple Engineer
Score 9 out of 10
Vetted Review
Verified User
Overall Satisfaction with Amazon CloudWatch
A few years back we migrated all of our local VM's to AWS. This includes robust VM's that host our Oracle, Mysql, Jenkins, and other development boxes. We also host our web-services which our customers use to receive our data. CloudWatch helps us monitor and alert our dev-ops and development team of any health concerns on those ec2 instances. We also can tell when we need to scale up an instance or even scale down, saving money in the process.
- Gives a well-reported status on your system health, usages, and traffic.
- The ability to place monitors on any or all of our instances while triggering alarms on certain events.
- Easy to set up and create alarms.
- The interface is really well designed.
- Its limitation on only Amazon resources.
- Cost is higher.
- Lack of ability to create graphs on distinct counts and histograms which can make it hard quickly identify specific IP addresses that have a high request volume in a certain period. We have worked around this but a feature on the dashboard would be nice.
- Scalability. Saving us cost when we can downgrade underperforming instances.
- Great monitoring and peace of mine without always having to check logs to any services failure.
- Support cost is high. It would be nicer if documentation would be easier to follow.
Currently, we only tried and used Cloud Watch, but for AWS it is perfect. Since this is an Amazon product monitoring Amazon services, integration is great. If we decide in the future to move away from AWS, we would reconsider changing alarm monitoring. AWS can be costly compared to the competition.