We use CloudWatch for monitoring and logging. It helps us monitor our applications' performance, particularly in ensuring that every API hit returns a response within four seconds, which is our SLA. We also monitor invocation errors in Lambda and use CloudWatch alerts to notify us of any issues.
Developer at a tech services company with 11-50 employees
Real User
Top 10
2024-10-02T15:34:00Z
Oct 2, 2024
We use Amazon CloudWatch for monitoring applications. We use it for Synthetics and also RAM. Amazon CloudWatch has been very helpful for monitoring our applications. We have been able to create a monitoring account where we get metrics, traces, and application monitoring data in one account. One noteworthy feature is that this is free of cost.
Amazon CloudWatch is a monitoring and availability service designed to collect and check metrics and collect and monitor log files. We can set alarms, and Amazon CloudWatch allows users to gain operational insight into their application resource and services. The solution also helps users to ensure the reliability, performance, and availability of their infrastructure.
Senior Performance Architect at a tech services company with 501-1,000 employees
Real User
Top 10
2023-10-30T11:07:01Z
Oct 30, 2023
It serves as a diagnostic and profiling tool, particularly useful for dissecting the intricacies of applications, especially in scenarios like Microsoft's best applications. When a user triggers transactions through the GUI, such as purchasing tickets for events like cricket or concerts, the process involves multiple layers—starting from the front-end GUI to the back-end middle tier, microservices, and concluding with database interactions. It allows me to meticulously analyze and monitor these processes by creating and examining various logs. I can delve into the details of each stage, from API calls to network components, and server processing (involving Java Virtual Machine), and even gauge how long specific APIs or queries take to execute. This tool proves invaluable in identifying bottlenecks, such as waiting times or timeouts and understanding the performance of APIs, queries, and even the efficiency of gateways.
Principal Cloud Security Consultant at Pegasystems
Real User
Top 5
2023-10-16T12:23:41Z
Oct 16, 2023
We use the solution to set alerts. We can set up thresholds to trigger alerts if an instance in AWS reaches the threshold value. Based on the alerts, we check the issue in the instance.
When alarms are triggered, we rely on CloudWatch to check various metrics such as memory utilization and application performance. We examine all the relevant matrices during this process.
AWS Cloud Engineer/Cloud Architect at Landmark Technologies
Real User
Top 5
2023-09-15T20:07:34Z
Sep 15, 2023
CloudWatch is important because we use it to remediate automation. For example, I had to integrate GuardDuty with CloudWatch. If anything went wrong in the environment when GuardDuty had captured all the APIs, and if someone got an alarm on the server, it was basically because of CloudWatch. CloudWatch would have seen an intruder, thinking, "This is what's happening," and so on. I used the solution to monitor, collect, and store metrics from AWS solutions like EC2. Taking all these metrics from other sections, such as GuardDuty for the security department and all the security hubs, you are presented with all the views at once.
CloudWatch is used to monitor not only for the cloud but also for on-premises services. So, you could think of it as a comprehensive monitoring tool. It's just proprietary monitoring software.
We use the solution to monitor the devices on our system or infrastructure. CloudWatch notifies you when a token is used or when the VM is not working. It helps you to determine the status of your infrastructure.
Head of Engineering - Data and Machine Learning at a financial services firm with 51-200 employees
Real User
Top 10
2023-04-13T10:38:32Z
Apr 13, 2023
Whenever we launch any instances or use any service we receive default metrics from Amazon CloudWatch. It is easy to track what is happening in the services that we are using. Additionally, it provides metrics logs from servers and what is happening from the infrastructure.
Lead Technical Product Owner - AI & ML at a transportation company with 10,001+ employees
Real User
Top 5
2023-02-03T12:37:47Z
Feb 3, 2023
While we have used CloudWatch, we have not used it extensively. We should start monitoring our applications once it starts performing in production. We are not at that stage yet. However, we have implemented it. In the end, we will use it mainly to monitor our applications.
We use CloudWatch to monitor our infrastructure and resources, such as bandwidth, etc. It comes with the AWS package we use, and it's easier when all your services come from one vendor.
The primary use cases are creating a platform for customer experience and customer engagement. This is more about profiling a customer and it is more about using or basically understanding the customer's needs and wants and profiling the data and showing it to a business analyst.
We use Amazon CloudWatch for monitoring infrastructure for EC2 instances. We created CPU, memory, system, status, and disk utilization checks. Based on those checks, we created actions such as disk cleaning by running a command, integrating with Lambda, and sending email notifications. We use the basic functionalities of Amazon CloudWatch.
We're using Amazon CloudWatch to monitor the entire application instances, client application, and backend communication. We're also using the solution to monitor service availability and application development.
We use the solution to monitor our AWS resources. We used Azure extensively but a couple of years back we moved to use both Azure and AWS. Currently, we have three main use cases. Our predominant use case is monitoring our S3 which includes terabytes of data. We monitor all the buckets and containers plus who has access to them, the thresholds, and user data. We constantly watch all the KPIs and CloudWatch metrics. Our second use case is watching logs and processes for other products such as AWS tools, AWS Glue, and Redshift which includes a few terabytes of data. Our third use case is minor and with Athena. Our fourth use case is new. We just started using SageMaker for a small POC and want to complete all of our data modeling and logs. In the future, we will be using the solution with Airflow, which will become one of our biggest use cases. CloudWatch works very well with any of the AWS resources so we always monitor through it.
We're only using it for collecting the logs and forwarding it, and then in some areas, we use it for scheduling stuff and there are some new alerts that come in, and then from there, they had to trigger some Lambdas. We build the monitoring and everything on top of the Datadog.
Architect - Database Administration at Mitra Innovation
Real User
Top 5
2022-06-03T16:35:32Z
Jun 3, 2022
The majority of the use cases are monitoring of all the AWS services, which can be integrated into CloudWatch. Also, the application logs also can be integrated. Due to that, if there are multiple instances they can be monitored through CloudWatch. The monitoring can be automated as well. It has automated thresholds that can be set for alerting. Therefore, we use CloudWatch for monitoring and incident alerts.
We use it to monitor our servers, to check the memory of our servers, and to determine whether the CPU is overhead or not. We also use the alerting system to inform us when something goes wrong.
We always use whatever's the latest because that's all we have access to. Because we deploy to other companies, we do public and hybrid clouds. Some of it is hybrid, some of it would be private as well. The majority is probably hybrid, but we're deploying for customers. Most of it's around optimizing utilization, their cloud utilization. They're making sure that they're getting the most out of their in-cloud environments and their instances. Making sure that there's no strange behavior in the environment. That's really what we're trying to do. And that's what Cloud Watch really helps with, is it's making sure it's collecting, monitoring, analyzing, all the things that are going on within their instance, so that we can optimize it better. And if there are any anomalies, anything that is out of the norm, then we're able to catch it and fix it pretty quickly. The ability of it to detect anomalies, and setting dynamic alarms, and automating a lot of the actions. I think that's a huge benefit that the companies have seen.
Amazon CloudWatch is used for monitoring, tracking logs, and organizing metrics across AWS services. It detects anomalies, sets dynamic alarms, and automates actions to optimize cloud utilization, troubleshoot, and ensure service availability.
Organizations leverage Amazon CloudWatch for collecting and analyzing logs, triggering alerts, and profiling application performance. It's also employed for monitoring bandwidth, virtual machines, Lambda functions, and Kubernetes clusters. Valuable...
I use Amazon CloudWatch to check the log we have sent, ensuring it isn't blocked. That is the primary purpose.
We use CloudWatch for monitoring and logging. It helps us monitor our applications' performance, particularly in ensuring that every API hit returns a response within four seconds, which is our SLA. We also monitor invocation errors in Lambda and use CloudWatch alerts to notify us of any issues.
We use Amazon CloudWatch for monitoring applications. We use it for Synthetics and also RAM. Amazon CloudWatch has been very helpful for monitoring our applications. We have been able to create a monitoring account where we get metrics, traces, and application monitoring data in one account. One noteworthy feature is that this is free of cost.
We collect the CloudWatch logs and use them to analyze security. It helps us to monitor malicious activity.
We use the solution for monitoring CPU usage, memory usage, Lambda logs, and load balancer logs.
Amazon CloudWatch is a monitoring and availability service designed to collect and check metrics and collect and monitor log files. We can set alarms, and Amazon CloudWatch allows users to gain operational insight into their application resource and services. The solution also helps users to ensure the reliability, performance, and availability of their infrastructure.
It serves as a diagnostic and profiling tool, particularly useful for dissecting the intricacies of applications, especially in scenarios like Microsoft's best applications. When a user triggers transactions through the GUI, such as purchasing tickets for events like cricket or concerts, the process involves multiple layers—starting from the front-end GUI to the back-end middle tier, microservices, and concluding with database interactions. It allows me to meticulously analyze and monitor these processes by creating and examining various logs. I can delve into the details of each stage, from API calls to network components, and server processing (involving Java Virtual Machine), and even gauge how long specific APIs or queries take to execute. This tool proves invaluable in identifying bottlenecks, such as waiting times or timeouts and understanding the performance of APIs, queries, and even the efficiency of gateways.
We use the solution to set alerts. We can set up thresholds to trigger alerts if an instance in AWS reaches the threshold value. Based on the alerts, we check the issue in the instance.
When alarms are triggered, we rely on CloudWatch to check various metrics such as memory utilization and application performance. We examine all the relevant matrices during this process.
CloudWatch is important because we use it to remediate automation. For example, I had to integrate GuardDuty with CloudWatch. If anything went wrong in the environment when GuardDuty had captured all the APIs, and if someone got an alarm on the server, it was basically because of CloudWatch. CloudWatch would have seen an intruder, thinking, "This is what's happening," and so on. I used the solution to monitor, collect, and store metrics from AWS solutions like EC2. Taking all these metrics from other sections, such as GuardDuty for the security department and all the security hubs, you are presented with all the views at once.
CloudWatch is used to monitor not only for the cloud but also for on-premises services. So, you could think of it as a comprehensive monitoring tool. It's just proprietary monitoring software.
We use the solution to monitor the devices on our system or infrastructure. CloudWatch notifies you when a token is used or when the VM is not working. It helps you to determine the status of your infrastructure.
We use the solution for monitoring the traffic. We analyze any suspicious traffic detected by AWS.
We use the solution for monitoring purposes. We also use it for events and alerts.
We use Amazon CloudWatch in our company to mainly troubleshoot Lambda functions. Then, we use CloudWatch to set up CloudWatch Alarms.
Whenever we launch any instances or use any service we receive default metrics from Amazon CloudWatch. It is easy to track what is happening in the services that we are using. Additionally, it provides metrics logs from servers and what is happening from the infrastructure.
Amazon CloudWatch for infrastructure and serverless monitoring.
While we have used CloudWatch, we have not used it extensively. We should start monitoring our applications once it starts performing in production. We are not at that stage yet. However, we have implemented it. In the end, we will use it mainly to monitor our applications.
We use CloudWatch to monitor our infrastructure and resources, such as bandwidth, etc. It comes with the AWS package we use, and it's easier when all your services come from one vendor.
The primary use cases are creating a platform for customer experience and customer engagement. This is more about profiling a customer and it is more about using or basically understanding the customer's needs and wants and profiling the data and showing it to a business analyst.
We use Amazon CloudWatch for monitoring infrastructure for EC2 instances. We created CPU, memory, system, status, and disk utilization checks. Based on those checks, we created actions such as disk cleaning by running a command, integrating with Lambda, and sending email notifications. We use the basic functionalities of Amazon CloudWatch.
We're using Amazon CloudWatch to monitor the entire application instances, client application, and backend communication. We're also using the solution to monitor service availability and application development.
We use the solution to monitor our AWS resources. We used Azure extensively but a couple of years back we moved to use both Azure and AWS. Currently, we have three main use cases. Our predominant use case is monitoring our S3 which includes terabytes of data. We monitor all the buckets and containers plus who has access to them, the thresholds, and user data. We constantly watch all the KPIs and CloudWatch metrics. Our second use case is watching logs and processes for other products such as AWS tools, AWS Glue, and Redshift which includes a few terabytes of data. Our third use case is minor and with Athena. Our fourth use case is new. We just started using SageMaker for a small POC and want to complete all of our data modeling and logs. In the future, we will be using the solution with Airflow, which will become one of our biggest use cases. CloudWatch works very well with any of the AWS resources so we always monitor through it.
We're only using it for collecting the logs and forwarding it, and then in some areas, we use it for scheduling stuff and there are some new alerts that come in, and then from there, they had to trigger some Lambdas. We build the monitoring and everything on top of the Datadog.
The majority of the use cases are monitoring of all the AWS services, which can be integrated into CloudWatch. Also, the application logs also can be integrated. Due to that, if there are multiple instances they can be monitored through CloudWatch. The monitoring can be automated as well. It has automated thresholds that can be set for alerting. Therefore, we use CloudWatch for monitoring and incident alerts.
We use it to monitor our servers, to check the memory of our servers, and to determine whether the CPU is overhead or not. We also use the alerting system to inform us when something goes wrong.
We are kind of consultants. We maintain our customers' environment on AWS.
We always use whatever's the latest because that's all we have access to. Because we deploy to other companies, we do public and hybrid clouds. Some of it is hybrid, some of it would be private as well. The majority is probably hybrid, but we're deploying for customers. Most of it's around optimizing utilization, their cloud utilization. They're making sure that they're getting the most out of their in-cloud environments and their instances. Making sure that there's no strange behavior in the environment. That's really what we're trying to do. And that's what Cloud Watch really helps with, is it's making sure it's collecting, monitoring, analyzing, all the things that are going on within their instance, so that we can optimize it better. And if there are any anomalies, anything that is out of the norm, then we're able to catch it and fix it pretty quickly. The ability of it to detect anomalies, and setting dynamic alarms, and automating a lot of the actions. I think that's a huge benefit that the companies have seen.
We primarily use the solution for budgeting and monitoring for abnormal behaviour.
We are primarily using the solution to monitor some of the instances that we have on Amazon for our testing development.