- Managing log retention periods is very simple with CloudWatch, and can be configured on a per-group basis.
- Monitoring host performance is very easy when coupled with the CloudWatch Agent on an EC2 instance. A simple installation and configuration replaces an entire 3rd-party host monitoring stack.
- CloudWatch is flexible enough for not just host monitoring, but application monitoring as well. It's easy to pipe local logs up to CloudWatch and extract structured data in order to monitor and set alerts on custom app metrics.
- Unfortunately, the CloudWatch dashboard does not provide the ability to create histograms of discrete counts. This makes it difficult to, for instance, use CloudWatch to quickly identify specific IP addresses that have a high request volume in a certain period.
- The UX for creating a custom metric from a CloudWatch log group is somewhat confusing. Every time I need to create a new metric I find myself fumbling around the interface for a few minutes while I try to remember how to do it.
- The alerting options for CloudWatch are not as extensive as are available with some 3rd-party services.
- The ability to create dashboards off of metrics
- Setting alarms when things go wrong so we get alerts
- Its integrations with other AWS products.
- If you have to ever dig manually through logs to try to find something it can be a little overwhelming. The user interface could use some work
- I would like the ability to create more customizable dashboards.
- The way log streams are used feels very counterintuitive.
Review: "Amazon CloudWatch is an essential tool for governing your system-wide resources and app management"
At my organization, we use AWS (Amazon Web Services) to spin up new server instances for any business critical applications we require. This is known as containerization. Instead of purchasing new computers we buy more RAM and then have the capacity to spin up or shut down an almost limitless array of servers on an as-needed basis.
Not long ago companies needed to physically install servers on-site. Hardware would need to be upgraded, administrated and repaired. Also if these servers contained sensitive data, they would need to be secured from hacking or fire and theft.
Today we let Amazon host all of our data in the cloud. They are at least partially responsible for guarding our data from theft and fire. Our organization instantly recognized the benefit of being able to administrate our AWS server instances via Amazon CloudWatch. If you rely on AWS in any way, you need to use Amazon CloudWatch.
- Application Performance Management.
- Error Management.
- Utilization Management.
- The interface is clunky.
- The context sensitive help could be written more clearly.
- I wish there were more options for arranging the dashboard interface to my specific needs.
- Infrastructure monitoring
- Infrastructure alerting
- Building cloudwatch dashboards can be cumbersome. You have to navigate through various screens to get the metrics you want to add.
- Exporting alarm / alerting data is not available for further post-processing or analysis
- You have to build alerts and alarms yourself. CloudWatch does not give you any recommendations, so you have to know what you're doing.