Skip to main content
TrustRadius
Amazon CloudWatch

Amazon CloudWatch

Overview

What is Amazon CloudWatch?

Amazon CloudWatch is a native AWS monitoring tool for AWS programs. It provides data collection and resource monitoring capabilities.

Read more
Recent Reviews

A must-have!

9 out of 10
October 23, 2019
We use AWS to sync a lot of files that all the users need. It's a very good tool to keep track of everything, including notifications and …
Continue reading
Read all reviews
Return to navigation

Pricing

View all pricing

Canaries

$0.0012

On Premise
per canary run

Logs - Analyze (Logs Insights queries)

$0.005

On Premise
per GB of data scanned

Over 1,000,000 Metrics

$0.02

On Premise
per month

Entry-level set up fee?

  • No setup fee
For the latest information on pricing, visithttps://aws.amazon.com/cloudwatch/prici…

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services
Return to navigation

Product Demos

AWS Container Day - Amazon Cloudwatch (Container Insights)

YouTube
Return to navigation

Product Details

What is Amazon CloudWatch?

Amazon CloudWatch is a native AWS monitoring and observability service built for DevOps engineers, developers, site reliability engineers (SREs), and IT managers. CloudWatch provides users with data and actionable insights to monitor applications, respond to system-wide performance changes, optimize resource utilization, and get a unified view of operational health. CloudWatch collects monitoring and operational data in the form of logs, metrics, and events, providing users with a unified view of AWS resources, applications, and services that run on AWS and on-premises servers. CloudWatch can be used to detect anomalous behavior in environments, set alarms, visualize logs and metrics side by side, take automated actions, troubleshoot issues, and discover insights to keep your applications running smoothly. With Amazon CloudWatch, there is no up-front commitment or minimum fee; users simply pay for what they use.

Amazon CloudWatch Screenshots

Screenshot of How Amazon CloudWatch works - high-level overviewScreenshot of CloudWatch Application MonitoringScreenshot of CloudWatch ServiceLens and Contributor Insights - expedite resolution timeScreenshot of Improve Observability with Amazon CloudWatchScreenshot of Visual overview of Amazon CloudWatch

Amazon CloudWatch Videos

Amazon CloudWatch: Complete Visibility of Your Cloud Resources and Applications
Governance with AWS

Amazon CloudWatch Competitors

Amazon CloudWatch Technical Details

Deployment TypesOn-premise
Operating SystemsWindows, Linux, Mac
Mobile ApplicationNo
Supported CountriesAmericas, Europe, Middle East, Africa, Asia Pacific

Frequently Asked Questions

Amazon CloudWatch is a native AWS monitoring tool for AWS programs. It provides data collection and resource monitoring capabilities.

Datadog, Azure Monitor, and Splunk IT Essentials are common alternatives for Amazon CloudWatch.

Reviewers rate Support Rating highest, with a score of 8.4.

The most common users of Amazon CloudWatch are from Enterprises (1,001+ employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(167)

Attribute Ratings

Reviews

(26-38 of 38)
Companies can't remove reviews or game the system. Here's why
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We use CloudWatch to monitor logs of cloud services and other infrastructure. Mostly being used by our development and engineering departments. It gives us a good idea about the health of infrastructure and helps us prioritize maintenance activities.
  • Easy integration with other services.
  • Seamless Configuration.
  • Variety of matrix, graphs and dashboards.
  • Support to third party libraries.
  • User Interface can be improved.
  • High cost of implementation.
  • No Phone notifications.
It is a great tool for infrastructure monitoring. Very beneficial to monitor any web or cloud services.
David Tanner | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
We use Amazon CloudWatch across IT to trigger alerts, handle scaling, and for logging.
  • We are able to capture all of our Lambda logs through CloudWatch and ship them off to another provider for analysis.
  • The alerting features allow us to scale certain services when needed so we don't have to do it manually, or over provision.
  • Monitoring resource utilization allows us to see what is going on in our RDS services, so we can test optimizations and fixes.
  • The auto refresh feature could use some work so that it doesn't kick you back to the main dashboard.
  • The search features aren't as well developed as other areas in the AWS console.
  • It would be nice to be able to create a custom dashboard of multiple widgets like resource stats and alarms on one page.
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.
Kevin Van Heusen | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Amazon Cloudwatch has been useful for aggregating metrics around our Amazon server environment, as well as a way to set up alerts based on various criteria for those environments. In addition to alerting and metrics, Cloudwatch has a logging facility to aggregate logs from various Amazon sources. It has given us a good view of our AWS infrastructure.
  • Solid support for posting data from a variety of AWS services to CloudWatch logs.
  • Can setup alarms alert teams when certain resources hit a particular metric threshold.
  • CloudWatch Metric view allows for custom graphs based on whatever AWS criteria you would need.
  • Alerting could be beefed up, the options in terms of notification of alerts are pretty slim.
  • The usability of the Metric graph view could be improved, it can be tricky to find the metrics of interest and setup graphs.
  • The CloudWatch log view is pretty basic, the search options could stand to be more fleshed out.
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.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Most of my organization's cloud platform runs on AWS. So as part of that, we use CloudWatch for collecting and monitoring logs for the infrastructure. CloudWatch helps collects monitoring data in the form of logs and events and provides one unified view of AWS resources and services that run on AWS. We use it for monitoring logs and events, raising alarms if any part of our infrastructure has any issues and also ingests CloudWatch logs into ELK system for detailed log analysis and monitoring.
  • We use CloudWatch for collecting and monitoring logs for the AWS infrastructure.
  • CloudWatch events and alarms are configured for all our infrastructure running on AWS. Like Ec2, ECS, AWS Lambda, RDS. We can track auto-scaling at the service level (ECS) and instance level (EC2 and ECS).
  • CloudWatch helps collects monitoring data in the form of logs and events and provides one unified view of AWS resources and services that run on AWS.
  • We use it for monitoring logs and events, raising alarms if our infrastructure has any issues and also CloudWatch logs into ELK system for detailed log analysis and monitoring.
  • AWS Lambda's cold and warm boot times can also be registered using it.
  • CloudWatch could provide better log analytics using a better log parsing and log indexing. Like what is provided in ELK or Splunk.
  • Better dashboarding can be provided. Currently the dashboarding is very rudimentary.
  • No good customizable log indexing is available.
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.
Rob Bates | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
Incentivized
We use CloudWatch to monitor all of our cloud estates. We also integrate Cloudwatch into our main monitoring platform (SolarWinds) which allows us to pull the CloudWatch metrics down into SolarWinds. This is used specifically by our IT department, and our devs tend to use the native dashboard with CloudWatch. Overall it gives us visibility into our instances running in AWS and also provides us with alerting, which we also integrate into Slack.
  • Allows integration into non-native products (SolarWinds, Nagios, etc).
  • Proactive monitoring and recommendations.
  • Alerting and dashboards.
  • There is only a limited amount of credits available each month when pulling metrics into other applications. We have had to use larger polling intervals as a result.
  • Unable to export alert data into 3rd party data warehouses for record keeping.
  • Learning curve is slightly steep and there isn't much automation in terms of setting alerts up.
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.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Our engineering team uses CloudWatch to collect logs and monitor our back-end infrastructure and services. We use AWS ECS, Lambda, API Gateway, SageMaker and Step Functions; CloudWatch collects logs for these products out-of-the-box. It is easy to configure log retention policies; e.g., after three months, we can move logs to S3 infrequent-access or Glacier to save money. CloudWatch's log search in the console lacks many of the search features you would find in PaperTrail or Log.ly, but I find it is serviceable. Searching JSON-lines logs in the console might be an unpleasant experience. Similarly, CloudWatch metrics are provided out-of-the-box for all of the AWS products we use; it is easy to create alarms for these metrics and integrate them with PagerDuty.
  • Integration with other AWS products is CloudWatch's greatest feature. CloudWatch logs and metrics are provided out-of-the-box for ECS, Lambda, Sagemaker, and most other AWS products. Log aggregation and instrumentation are difficult to configure and manage; it is great to defer that work to AWS.
  • Configuring log retention policies is simple with AWS. If your business is required to retain logs for years, being able to automatically move old logs to S3 IA or Glacier with a few clicks is convenient.
  • Configuring alerts from metrics is simple, and it is easy to integrate alerts with PagerDuty or email.
  • The console's log search lacks many of the features you would find in PaperTrail or Log.ly. Regex search is either not supported, or very difficult to find.
  • It can be difficult to understand how the CloudWatch bill breaks down by log group.
  • The date/time picker in the console could be easier to use.
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.
Kyle Reichelt | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
We use Amazon Cloudwatch in a variety of ways, from monitoring the performance and validation success/failures of our ETL (extract, transform, and load) processes, our Lambda Services, our EC2 instances, our RDS instances, as well as our Redshift instance. Certainly we're using Amazon Cloudwatch to monitor day-to-day server-side activities, but the really impressive capabilities lie in its ability to both diagnose issue, as well as to trigger automated remediation.
  • Lambda process monitoring, particularly useful when you're relying on third-party services.
  • Active monitoring RDS (set thresholds so we know before a database runs out of space)
  • Auto-requisitioning of additional resources
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
Brian Dentino | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
Incentivized
We use Amazon CloudWatch to aggregate and retain logs across all of the different services that make up our infrastructure. It is primarily used across our engineering and dev ops departments. Using CloudWatch logs allows us to address compliance issues associated with log retention because it is very easy to configure an expiration (if any) for log files. We also use CloudWatch metrics to monitor important KPIs and performance metrics for our business.
  • 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.
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.
Score 7 out of 10
Vetted Review
Verified User
Incentivized
We manage hundreds of virtualized machines in the AWS cloud, so we need a place to look up logs from all of these machines. We use cloudwatch in debugging production issues and tracking trending data. Devs use it in our dev environment to debug new code.
  • 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.
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.
Score 5 out of 10
Vetted Review
Verified User
Incentivized
Cloudwatch is a great way to get information about all your hardware in Amazon Web Service. It allows you to know the state and health of all of your infrastructure and you can alert, graph, and monitor the health and state of every piece. It solved the issue of not knowing the state of your system.
  • Monitor
  • Alert
  • Visibility
  • Amazon-only
  • cumbersome compared to other solutions
  • not 100% customizable.
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.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
We use CloudWatch to monitor all of our production infrastructure. We need visibility into how our servers, databases and AWS resources are behaving and CloudWatch provides realtime dashboards to get information. We also use alerts on cloudwatch so that the system is proactively monitoring for our recommended levels of CPU usage, or storage usage, and alerts us when alarms break. This allows us to run our operations without having all eyes on glass 24x7. Recently we have been using CloudWatch Logs to send application logs to CloudWatch for later processing and debugging.
  • Infrastructure monitoring
  • Infrastructure alerting
  • Dashboarding
  • 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.
CloudWatch is a great low-cost solution for infrastructure monitoring and alerting if you are an AWS customer. You basically get it for free and requires little setup. If you are not on AWS, you can't enjoy the benefits of CloudWatch, so if you are running multi-cloud, need to think about how you will monitor all of your resources and assets.
March 20, 2017

Easy to set up

Score 8 out of 10
Vetted Review
Verified User
Incentivized
We used it in our web app for improved response time for video streaming. Our web servers are already in EC2.
  • Easy to set up
  • Pay per use
  • Better performance
  • IPv6 support
  • No free support
It is more beneficial if web servers are in EC2
Score 9 out of 10
Vetted Review
Verified User
Incentivized

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.
It's well suited where you rely on cloud services to run mission critical applications. I think it'd be less suitable in a scenario where the information you store on your servers is what your customers expect you to manage directly.
Return to navigation