Amazon CloudWatch Reviews

AWS CloudWatch is perfectly suited for deployments where there are a lot of EC2 instances you need to control and where you need to scale in new EC2 instances depending on users or network load, you can take advantage of multiple integrations AWS CloudWatch have to improve your application platform performance.

If you need to collect and act on metrics, which you should no matter what it is that you do, then CloudWatch will make a great fit. If you're after fancy analysis and charts, then there are better alternatives out there.

CloudWatch is one of the best services provided by AWS. With the help of CloudWatch, we can monitor all of our active features hired to AWS. CloudWatch checks EC2 instances, Custom Dashboards for our files as many other instances. Made our workflow way better and faster. Planning to acquire more services from Amazon.

Basically, any monitoring needs for an application would be a good fit for using CloudWatch.

Starting with AWS Cloud, you should always incorporate CloudWatch, together with CloudTrail. The two together gives you a lot of insight into your cloud environment and allow you to create (security) automation scenarios.

Amazon CloudWatch is well-suited for companies with a large enough user base to require monitoring of apps/access in a single user-centric interface. The tool works well when you're concerned about latency and need to ensure that resources are optimized.

Amazon CloudWatch allows us to scale our Fargate instances when utilization goes high. This allows us to provision a minimal amount of servers, then when traffic gets high we know that we won't be throttled.

Amazon CloudWatch logs allowed us to stream massive amounts of logs off of devices without hitting any throttling, and then to stream those into S3 or ELK as needed for analysis.

CloudWatch is useful when you need to aggregate information/logs from various AWS resources. If you are interested in application logs, it is less suited for that. For basic alerting and display of AWS metrics over time, the metric graphs are suitable. Overall, if you are looking to track a handful of metrics or log options, it can be a decent solution.

If you have a large cloud estate and need proactive monitoring, dashboards, and alerting then it makes sense to use CloudWatch as its obviously native to AWS. CloudWatch is well suited to anyone that wants to see into their data, their traffic, or their system health. It's the eyes and ears of AWS. It really is best for any scenario where you are hosting infrastructure with AWS and want to keep an eye on it.

Ideal for monitoring AWS services and workloads. We have several of our websites entirely hosted on AWS and we're able to get a Grafana dashboard of all the relevant metrics from CloudFront, S3, EC2, RDS, and Elastic Beanstalk. This can be set up within the hour or templated on your code for infrastructure (we do this with terraform & cloud formation). By design, it isn't suited for non-AWS workloads.

If your company has lots of AWS services or uses part of the AWS services, you should also set up CloudWatch. It is a great tool to monitor your resources' health status. It provides specific details about your resources' status. It can alert you when some of the services go down.

For companies who do not use AWS, CloudWatch is less appropriate to use.

CloudWatch is highly recommended for monitoring EC2 services. It provides easy setup, straight forward alarm creation, easy to read monitoring.
It is great for scalability/cost. We know when to increase an EC2 instance or when it can be scaled down. I do have a concern on the documentation. I would say it is not for AWS beginners and to actually talk to support can be costly.

Amazon CloudWatch is best for monitoring your AWS infrastructure. When using other services, such as Lambda, you rely on Cloud Watch to provide all of the logging functionality for the functions. Other than writing custom Lambda functions to trigger autoscaling rules, using CloudWatch Events to trigger scaling policies is amazing.

If most of the applications are cloud hosted on the Amazon infrastructure, then using CloudWatch will aide a lot in terms of actively monitoring performance. We had been experiencing a severe bottleneck with our student portal application under high loads. With using Amazon CloudWatch we were able to identify the problem areas and make tweaks accordingly.

Nothing better than AWS CloudWatch on AWS for event recording and alarms. It can also be used for cost monitoring. Logs can be retained for long terms. Logs can be ingested into ELK or Splunk using a Lambda or some other mean, then dashboards can be generated. These are very useful features if your organization has 100s of APIs or microservices where they need a unified view, monitoring, and analytics.

You can easily set up rules to call AWS lambda on time. It's good for notification on time.

To monitor all cloud environments. To integrate with other monitoring platforms such as SolarWinds and Nagios.

Amazon CloudWatch is well suited to monitor applications and helps you know the resource utilization.

Anyone using AWS to host any of their infrastructure should be leveraging CloudWatch for notifications, alerts, alarms, auto-scaling, metrics gathering and historical lookback, and performance analysis.

It is a great tool for infrastructure monitoring. Very beneficial to monitor any web or cloud services.

It is well suited for organizations already using a number of Amazon services, as most of these will integrate very nicely with CloudWatch. If you have detailed log retention requirements, it's quite nice as well since they make it easy to configure retention and export data to S3. The tooling for metric filters and dashboards are very customizable and sufficient for general monitoring but the UX is not the most friendly. If your organization spends a lot of time on business intelligence and performance tracking, you may want to consider a more targeted 3rd-party service.

Well suited if:

• Your organization is married to the AWS ecosystem
• You tech stack is reliant on third-party services
• You use Splunk as your log aggregator (integrates well)
• You prefer to be proactive about health of your tech stack
  

Not particularly suited if:

• You don't use AWS
• You like to fly by the seat of your pants

If you are using other AWS products, including EC2, ECS, or Lambda, using CloudWatch is an easy decision. You will get log aggregation and instrumentation out-of-the-box. The lack of log search features may be a sticking point, though your organization does not have to use CloudWatch exclusively. If your platform does not rely on AWS products, CloudWatch should not be considered.

If you're just starting out with smaller applications in the AWS cloud, then AWS cloudwatch is the right tool. When your company starts growing, along with your software becoming more mature, you may end up piping your logs to another system in order to do more analytics on it and gather better insights.

Amazon CloudWatch is well suited for anyone that's using AWS and wants to see into their data, their traffic, or their system health. It's the eyes and ears of AWS. It really is best for any scenario where you are hosting infrastructure with AWS and want to keep an eye on it.