TrustRadius
Amazon CloudWatch is a native AWS monitoring tool for AWS programs. It provides data collection and resource monitoring capabilities.As with most other Amazon services, Amazon CloudWatch is user-friendly and learned with relative ease, but consider alternativesAmazon CloudWatch is used by Econometric Studios to develop systems for viewing how programs and apps are performing. It is used by certain individuals within the organization. The program is helpful in that it allows a single place for IT professionals to monitor activity.,Perhaps the most useful aspect of CloudWatch is its all-in-one user interface. Makes it easier to manage. CloudWatch also appears to never have downtime. The third advantage of CloudWatch is that it integrates nicely with other Amazon products.,The data collection could be made easier to access and manipulate. Although the program is made for professional IT managers, the program could be made more useful for other analysts. The logs data is cool but requires some effort for taking action.,9,CloudWatch is liked by the IT guys, in that it makes their job easier. Whether that actually is a positive ROI is debatable. It doesn't seem like it. CloudWatch could have a positive ROI in the sense that IT professionals consider it an integral tool to streamline their management of IT resources. Cloud is not a positive ROI in the sense that it doesn't appear to have saved any money on the personnel or software side.,Cloudability, Azure Active Directory, ParkMyCloud and Nutanix,Azure Active Directory, ParkMyCloud, CloudabilityCloudWatch for the winWe 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.,10,It frees up developer time from needing to create/monitor a logging solution. It allows for quick alerting when resources are in a bad state. We are able to quickly see what is going on with an alert with data in one place.,Sumo Logic, PagerDuty, JenkinsCapable logging of AWS metrics and eventsAmazon 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.,9,CloudWatch Metrics gave us the opportunity to analyze our server performance and try to track down times where our customer experience could be affected. CloudWatch logs facilitated an understanding of what was happening with various AWS systems (for example, CloudFormation and determining what occurred when launching new stacks, etc.). CloudWatch Alarms provided some rudimentary alerting capabilities before we moved on to a different solution.,PagerDuty, PaperTrail and Sumo Logic,PagerDuty, Sumo Logic, SolarWinds PapertrailEasy to implement & cost effectiveAmazon Cloudwatch is used specifically for our AWS workloads (providing detailed monitoring of multiple services from EC2, Application Load Balancers, RDS, Elasticsearch As a Service, etc). Cloudwatch API allows us to visualize the monitoring with free open source solutions such as Grafana, which are then used within our NOC across the business. The ease of use and implementation of CloudWatch metrics reduces the implementation time of monitoring and is also very cost effective, as you only pay for what you use.,CloudWatch API allows integration into multiple monitoring solutions, such as SolarWinds Orion, Site24x7, and Grafana just to name a few we use. It's cost-effective and you only pay for what you use. Easy implementation, just a few lines which you can rinse and repeat when provisioning workloads from code or a few tick boxes when doing ad-hoc.,Memory metrics on EC2 are not available on CloudWatch. Depending on workloads if we need visibility on memory metrics we use Solarwinds Orion with the agent installed. For scalable workloads, this involves customization of images being used. Visualization out of the box. But this can easily be addressed with other solutions such as Grafana. By design, this is only used for AWS workloads so depending on your environment cannot be used as an all in one solution for your monitoring.,10,Cloudwatch costs are below 0.5% of our AWS spend providing a very cost effective monitoring tool. We're able to integrate Cloudwatch metrics into our existing monitoring solutions (Site24x7/Solarwinds/ Grafana)—all for free! Due to no memory metrics, we do have to install agents on some workloads.,Site24x7, AlertSite and Solarwinds Web Performance Monitor,Dell EMC SC Series (Compellent), Dell PowerEdge R, Atlassian ConfluenceGreat Monitoring Tool for AWS ApplicationsAmazon CloudWatch is now used by our whole department of enterprise architecture. It provides a solution for monitoring, alerting, and auditing our services on AWS. It solves problems such as not being informed of unhealthy services so we can take action as quickly as possible. The dashboard is a great tool to have to monitor all the resources you have.,Real-time monitoring. Unhealthy resources reports and alerts. Clear dashboard.,Only used with AWS resources Not cloud agnostic Have to pay much for detailed report.,10,Improved our ability to monitor resources. Shortened our response time to unhealthy services. Helps us keep a high in-service rate, so we can deliver stable service.,,Google BigQuery, Amazon DynamoDB, Google Cloud Datastore, BigTable, Azure DevOps (formerly VSTS), Google Data StudioCloudWatch by a Simple EngineerA 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.,8,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.,,Amazon Cloud Drive, Amazon Elastic Compute Cloud (EC2), Amazon S3 (Simple Storage Service)AWS CloudWatch ReviewWe are using Amazon CloudWatch to monitor our AWS infrastructure. This includes networking flow logs to application logs. Using the Events feature in Amazon CloudWatch allows us to trigger auto-scaling rules for our auto-scaling groups, to spin up and spin down hosts. This provides us a dynamic infrastructure that can adjust for the requests coming in.,Events. Flowlogs. Monitoring.,The price is too high for stored logs. Not everything is integrated into Cloud Watch. Different interfaces per region.,8,There's a lower cost to trigger ASG using CloudWatch Events. Serverless implementation. It's a managed solution.,Elasticsearch, Datadog and New Relic,Puppet Enterprise (formerly Puppet Data Center Automation), Nagios, AWS LambdaBest monitoring application offered by AmazonIn my previous position at a public university, we had various applications that were deployed on the Amazon cloud infrastructure. The student portal and course registration applications were the most widely accessed websites in our portfolio. They were also the most critical in terms of business continuity for the university. We started using Amazon Cloudwatch to aggregate all our application logs for performance monitoring and security alerts. It was used by the product development department mainly.,Amazon Cloudwatch integrates with all the Amazon deployment infrastructure and provides monitoring capabilities at each step of the pipeline. Individual dashboards can be configured to do performance monitoring. Alerts can be configured for different performance indicators that can be very useful for event mitigation.,Presently the application expects scripting experience in order to configure individual scripts for handling performance monitoring and alerts. The documentation is not at par for an enterprise offering and hence it makes the learning curve even steeper.,8,It's a fully managed service that makes it ideal for developers and integration teams to easily monitor application performance and setup custom alerts when any degradation happens.,Amazon DynamoDB, Amazon Elastic Compute Cloud (EC2), Amazon S3 (Simple Storage Service)Change CronJob with CloudWatchWe use CloudWatch on a couple of projects. Usually for changing CronJob functions, for watch logs and to debug AWS Lambda functions. It is easy to set up CloudWatch to call some AWS Lambda functions.,You can call the AWS Lambda function at a certain time. You can debug the AWS Lambda function.,Filter and Search can be better from the site.,10,Easier to adjust than Cron Job. Save time in setting watch logs or debugs.,AWS Lambda, AWS CodePipeline, Amazon DynamoDB and Amazon Pinpoint,AWS Lambda, Amazon DynamoDB, AWS CodePipelineCloudWatch is a useful tool for monitoring AWS infrastructureAmazon Cloudwatch has been useful for aggregating metrics around our cloud 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.,Set up alarms to alert teams and is a useful monitoring tool. Integration into other products. Dashboards.,It takes time to get a hang of the tool. The graph metrics and view could be improved.,8,Has helped consolidate AWS alerting into one place and saved us on a handful of occasions. Expensive,BeyondTrust PowerBroker, PowerBroker Password Safe, Splunk EnterpriseAmazon CloudWatch ReviewWe have multiple web applications running in production and we were looking for the right tool to monitor them. Since most of our applications run in AWS, we considered Amazon CloudWatch to monitor our web applications and know the performance and optimize resource utilization. Logs and metrics are very useful to review.,Logs Metrics Alerts,The dashboard needs some improvements to read.,8,Improved our application maintenance.,Amazon Elastic Compute Cloud (EC2), Amazon Relational Database ServiceCloudWatch is an excellent tool for an AWS hosted infrastructureWe use CloudWatch across the entire organization to monitor the performance of our infrastructure as well as alerts on issues and problems.,CloudWatch integrates flawlessly with any AWS object like load balancers, EC2 instances, target groups, etc. CloudWatch is extremely easy to create graphs and charts with. Creating Dashboards on CloudWatch is as simple as dragging and dropping selected charts.,It is not always easy to understand what metric type one should use with CloudWatch metrics. Averages, sums, min, max, etc. are not always readily apparent and CloudWatch does not stop you from creating useless metrics. CloudWatch cannot show milliseconds, it will instead show numbers in 'e' notation. Many of the standard metrics provided by AWS into cloudwatch cannot see below 1 minute intervals.,9,CloudWatch has helped us reduce time to issue resolution. CloudWatch has helped us allow non-technical users to monitor and have insight into the infrastructure. CloudWatch helps us determine how best to scale and size our infrastructure.,Nagios and New Relic,Ansible, Docker, SwarmExcellent Monitoring!!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.,8,Easy monitoring of infrastructure allowed us to focus on other important things and leave this to CloudWatch to monitor. Lot of automation and customization is possible. Overall positive impact.,Trello and Microsoft Azure,Oracle Analytics Cloud, Bentley ProjectWise, ADP Streamline Payroll, Oracle API ManagerAmazon CloudWatch - Perfect when melded with other monitoring platformsWe 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.,7,The cost is low in terms of what you get and what it provides. Containers and workloads are now monitored and we can see how the computed levels are increasing, which allows us to make adjustments before we have complaints. The proactive element of CloudWatch allows us to address issues before they arise.,Nagios, Datadog and SolarWinds Server & Application Monitor,Nagios, DatadogDon't Skip Proactive Server(less)-side MonitoringWe 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,10,It saves time pouring through log files, providing us non-engineers with a nice clean, intuitive interface It helps us maximize "up-time" by allowing us to stay ahead of third-party service downtime,AWS Lambda, Amazon Redshift, Amazon Relational Database ServiceAWS CloudWatch: a must for your cloud AWS infrastructureMost 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.,9,CloudWatch is a great tool for cloud infrastructure monitoring and alerting. Currently, there is no good alternative in AWS. For an SRE organization, it has great value and ROI. Just imagine that you can set 10-second or 30-second period alarms on your EC2 infrastructure and it would raise alarm for CPU or memory utilization or if the service is not responding. This kind of service is a must-have for engineering organizations.,Elasticsearch, Splunk Enterprise and Enterprise Fluentd,Elasticsearch, Splunk Enterprise, Enterprise Fluentd, New Relic, DatadogSimple Log Aggregation and Metrics Out-of-the-BoxOur 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.,8,CloudWatch is integrated with other AWS products out-of-the-box; our engineers do not need to configure and maintain log aggregation services and can focus on our product. Allowing engineers to focus on building competitive advantages instead of infrastructure is a huge boon. It is easy for our engineers to build alerts with CloudWatch; we know when services break and can respond before our customers discover the problem. CloudWatch can be inexpensive, particularly if your business is required to retain logs for years.,New Relic, Datadog, PaperTrail, Loggly and Nagios,New Relic, PaperTrail, Zoom, PyCharm, IntelliJ IDEA, Visual Studio IDECloudWatch - Flexible Log Management At A Great Price PointWe 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.,7,We were able to set up log streaming, retention, and simple downtime alerts within a few hours, having no prior experience with CloudWatch, freeing up our engineers to focus on more important business goals. CloudWatch log groups have made it relatively easy to detect and diagnose issues in production by allowing us to aggregate logs across servers, correlate failures, isolate misbehaving servers, etc. Thanks to CloudWatch, we are generally able to identify, understand and mitigate most production fires within 10-15 minutes. Choosing CloudWatch to manage log aggregation has saved us quite a bit of time and money over the past year. Generally, 3rd-party log aggregation solutions tend to get quite expensive unless you self-host, in which case you typically need to spend a fair amount of time setting up, maintaining, and monitoring these services.,Loggly, Graylog, PaperTrail and New Relic APM,Docker, New Relic APM, Threat StackNecessary if you are in the AWS cloudWe 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.,7,Looking at logs is necessary for software development. Cloudwatch provides what our users need to get the job done It won't directly affect the bottom line but less time spent on support issues means less wasted money.,Splunk Cloud and Sumo Logic,JIRA Software, Splunk Enterprise, OktaA great tool to get insights into your AWS infrastructure.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.,5,Cheap Part of AWS/Cloudformation/Terraform already.,,Amazon Elastic Compute Cloud (EC2), Amazon Elastic MapReduce, Amazon Aurora, Amazon S3 (Simple Storage Service)Amazon CloudWatch is an essential tool for governing your system-wide resources and app managementAt 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.,9,Pro: We've reduced the cost of salaried employees need to run in-house servers by close to 50%. Pro: We've reduced down time of any servers substantially. Con: It's not quite automated and its usage requires training.,,HipChat, TrelloCloudWatch is a great almost-free monitoring solution if you are on AWSWe 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.,9,Very positive ROI, we are able to pre-empt production issues via alerting CloudWatch is low cost and allows us to get enterprise level monitoring CloudWatch allows us to get visibility into all of our workloads and see how traffic is increasing or decreasing and make product level decisions,New Relic and Nagios,Amazon Elastic Compute Cloud (EC2), Amazon Relational Database Service, Amazon S3 (Simple Storage Service)Easy to set upWe 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,8,Better experience to end user
Unspecified
Amazon CloudWatch
72 Ratings
Score 8.4 out of 101
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>TRScore

Amazon CloudWatch Reviews

<a href='https://www.trustradius.com/static/about-trustradius-scoring#question3' target='_blank' rel='nofollow noopener noreferrer'>Customer Verified: Read more.</a>
Amazon CloudWatch
72 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 8.4 out of 101

Do you work for this company?

Show Filters 
Hide Filters 
Filter 72 vetted Amazon CloudWatch reviews and ratings
Clear all filters
Overall Rating
Reviewer's Company Size
Last Updated
By Topic
Industry
Department
Experience
Job Type
Role

Reviews (1-23 of 23)

Companies can't remove reviews or game the system. Here's why.
Thomas Young profile photo
Score 9 out of 10
Vetted Review
Verified User
Review Source
Amazon CloudWatch is used by Econometric Studios to develop systems for viewing how programs and apps are performing. It is used by certain individuals within the organization. The program is helpful in that it allows a single place for IT professionals to monitor activity.
  • Perhaps the most useful aspect of CloudWatch is its all-in-one user interface. Makes it easier to manage.
  • CloudWatch also appears to never have downtime.
  • The third advantage of CloudWatch is that it integrates nicely with other Amazon products.
  • The data collection could be made easier to access and manipulate.
  • Although the program is made for professional IT managers, the program could be made more useful for other analysts.
  • The logs data is cool but requires some effort for taking action.
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.
Read Thomas Young's full review
David Tanner profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source
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.
Read David Tanner's full review
Kevin Van Heusen profile photo
Score 9 out of 10
Vetted Review
Verified User
Review Source
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.
Read Kevin Van Heusen's full review
No photo available
Score 10 out of 10
Vetted Review
Verified User
Review Source
Amazon Cloudwatch is used specifically for our AWS workloads (providing detailed monitoring of multiple services from EC2, Application Load Balancers, RDS, Elasticsearch As a Service, etc). Cloudwatch API allows us to visualize the monitoring with free open source solutions such as Grafana, which are then used within our NOC across the business. The ease of use and implementation of CloudWatch metrics reduces the implementation time of monitoring and is also very cost effective, as you only pay for what you use.
  • CloudWatch API allows integration into multiple monitoring solutions, such as SolarWinds Orion, Site24x7, and Grafana just to name a few we use.
  • It's cost-effective and you only pay for what you use.
  • Easy implementation, just a few lines which you can rinse and repeat when provisioning workloads from code or a few tick boxes when doing ad-hoc.
  • Memory metrics on EC2 are not available on CloudWatch. Depending on workloads if we need visibility on memory metrics we use Solarwinds Orion with the agent installed. For scalable workloads, this involves customization of images being used.
  • Visualization out of the box. But this can easily be addressed with other solutions such as Grafana.
  • By design, this is only used for AWS workloads so depending on your environment cannot be used as an all in one solution for your monitoring.
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.
Read this authenticated review
No photo available
Score 10 out of 10
Vetted Review
Verified User
Review Source
Amazon CloudWatch is now used by our whole department of enterprise architecture. It provides a solution for monitoring, alerting, and auditing our services on AWS. It solves problems such as not being informed of unhealthy services so we can take action as quickly as possible. The dashboard is a great tool to have to monitor all the resources you have.
  • Real-time monitoring.
  • Unhealthy resources reports and alerts.
  • Clear dashboard.
  • Only used with AWS resources
  • Not cloud agnostic
  • Have to pay much for detailed report.
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.
Read this authenticated review
No photo available
Score 8 out of 10
Vetted Review
Verified User
Review Source
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.
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.
Read this authenticated review
No photo available
Score 8 out of 10
Vetted Review
Verified User
Review Source
We are using Amazon CloudWatch to monitor our AWS infrastructure. This includes networking flow logs to application logs. Using the Events feature in Amazon CloudWatch allows us to trigger auto-scaling rules for our auto-scaling groups, to spin up and spin down hosts. This provides us a dynamic infrastructure that can adjust for the requests coming in.
  • Events.
  • Flowlogs.
  • Monitoring.
  • The price is too high for stored logs.
  • Not everything is integrated into Cloud Watch.
  • Different interfaces per region.
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.
Read this authenticated review
No photo available
Score 8 out of 10
Vetted Review
Verified User
Review Source
In my previous position at a public university, we had various applications that were deployed on the Amazon cloud infrastructure. The student portal and course registration applications were the most widely accessed websites in our portfolio. They were also the most critical in terms of business continuity for the university. We started using Amazon Cloudwatch to aggregate all our application logs for performance monitoring and security alerts. It was used by the product development department mainly.
  • Amazon Cloudwatch integrates with all the Amazon deployment infrastructure and provides monitoring capabilities at each step of the pipeline.
  • Individual dashboards can be configured to do performance monitoring.
  • Alerts can be configured for different performance indicators that can be very useful for event mitigation.
  • Presently the application expects scripting experience in order to configure individual scripts for handling performance monitoring and alerts.
  • The documentation is not at par for an enterprise offering and hence it makes the learning curve even steeper.
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.
Read this authenticated review
No photo available
Score 10 out of 10
Vetted Review
Verified User
Review Source
We use CloudWatch on a couple of projects. Usually for changing CronJob functions, for watch logs and to debug AWS Lambda functions. It is easy to set up CloudWatch to call some AWS Lambda functions.
  • Filter and Search can be better from the site.
You can easily set up rules to call AWS lambda on time. It's good for notification on time.
Read this authenticated review
No photo available
Score 8 out of 10
Vetted Review
Verified User
Review Source
Amazon Cloudwatch has been useful for aggregating metrics around our cloud 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.
  • Set up alarms to alert teams and is a useful monitoring tool.
  • Integration into other products.
  • Dashboards.
  • It takes time to get a hang of the tool.
  • The graph metrics and view could be improved.
To monitor all cloud environments. To integrate with other monitoring platforms such as SolarWinds and Nagios.
Read this authenticated review
No photo available
Score 8 out of 10
Vetted Review
Verified User
Review Source
We have multiple web applications running in production and we were looking for the right tool to monitor them. Since most of our applications run in AWS, we considered Amazon CloudWatch to monitor our web applications and know the performance and optimize resource utilization. Logs and metrics are very useful to review.
  • Logs
  • Metrics
  • Alerts
  • The dashboard needs some improvements to read.
Amazon CloudWatch is well suited to monitor applications and helps you know the resource utilization.
Read this authenticated review
No photo available
Score 9 out of 10
Vetted Review
Verified User
Review Source
We use CloudWatch across the entire organization to monitor the performance of our infrastructure as well as alerts on issues and problems.
  • CloudWatch integrates flawlessly with any AWS object like load balancers, EC2 instances, target groups, etc.
  • CloudWatch is extremely easy to create graphs and charts with.
  • Creating Dashboards on CloudWatch is as simple as dragging and dropping selected charts.
  • It is not always easy to understand what metric type one should use with CloudWatch metrics. Averages, sums, min, max, etc. are not always readily apparent and CloudWatch does not stop you from creating useless metrics.
  • CloudWatch cannot show milliseconds, it will instead show numbers in 'e' notation.
  • Many of the standard metrics provided by AWS into cloudwatch cannot see below 1 minute intervals.
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.
Read this authenticated review
No photo available
Score 8 out of 10
Vetted Review
Verified User
Review Source
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.
Read this authenticated review
Rob Bates profile photo
Score 7 out of 10
Vetted Review
Verified User
Review Source
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.
Read Rob Bates's full review
Kyle Reichelt profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source
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
Read Kyle Reichelt's full review
No photo available
Score 9 out of 10
Vetted Review
Verified User
Review Source
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.
Read this authenticated review
No photo available
Score 8 out of 10
Vetted Review
Verified User
Review Source
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.
Read this authenticated review
Brian Dentino profile photo
Score 7 out of 10
Vetted Review
Verified User
Review Source
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.
Read Brian Dentino's full review
No photo available
Score 7 out of 10
Vetted Review
Verified User
Review Source
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.
Read this authenticated review
No photo available
Score 5 out of 10
Vetted Review
Verified User
Review Source
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.
Read this authenticated review
No photo available
Score 9 out of 10
Vetted Review
Verified User
Review Source

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.
Read this authenticated review
No photo available
Score 9 out of 10
Vetted Review
Verified User
Review Source
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.
Read this authenticated review
No photo available
March 20, 2017

Easy to set up

Score 8 out of 10
Vetted Review
Verified User
Review Source
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
Read this authenticated review

Amazon CloudWatch Scorecard Summary

About Amazon CloudWatch

Amazon CloudWatch is a native AWS monitoring tool designed for AWS resources and applications. CloudWatch centralized monitoring data onto one platform and formats it into automated log files for easy AWS monitoring. It provides a variety of metrics, including bandwidth, CPU utilization, etc. It can also automate error notifications and scale some resource allocations when various thresholds are crossed. It also possesses root cause analysis capabilities for diagnosing issues and bottlenecks. It is priced in a pay-for-what-you-use structure.

Amazon CloudWatch Technical Details

Operating Systems: Unspecified
Mobile Application:No