What advice do you have for others considering Amazon CloudWatch?

Before setting up any alarms or monitoring, it is advisable to review the documentation to know how to effectively monitor your applications for different use cases. I'd rate the solution eight out of ten.

I would definitely recommend CloudWatch if your applications are running in AWS. If your applications are in a different environment or cloud, I am not sure I would recommend it. I'd rate the solution six out of ten.

I will recommend the product to others. CloudWatch brings in a lot of value. It enables live monitoring. We have ten engineers in our technical team. The tool is self-sufficient. It does not require much maintenance. We enable it, ensure the logs are pushed to the third-party tools, and monitor them. It does not require any deployment process. We are more aligned with Amazon’s services when building our products. It is suitable for our business purposes. Overall, I rate the product a nine out of ten.

I will recommend the tool to others. Overall, I rate the solution an eight out of ten.

We don't need to update or do any maintenance on Amazon CloudWatch. The solution has more features available, like metrics. Amazon CloudWatch provides a wide range of metrics for AWS resources, including EC2 and all AWS services. Users can create a custom dashboard to visualize and monitor metrics from various AWS services on a single screen on the dashboard. This helps in checking the health and performance of the application and resources. Amazon CloudWatch logs allow users to monitor and install log files from the application. The solution's alarms allow users to set thresholds on metrics. Overall, I rate the solution ten out of ten.

Leveraging CloudWatch is advantageous due to its seamless integration with cloud services, making it a valuable asset for monitoring and gaining insights into the platform's performance. Overall, I would rate it eight out of ten.

Overall, I rate Amazon CloudWatch a six out of ten.

We use AWS for our infrastructure. Overall, I rate the product a six out of ten.

I would rate this solution ten out of ten.

CloudWatch has good features and tools. No matter how many people are on the security team, CloudWatch monitors the performance of your gateway resources daily, including CPU utilization and network traffic. If you are new to monitoring, CloudWatch is good because it helps you monitor your environment and your logs and captures and generates logs by applications and resources. I rate CloudWatch an eight out of ten.

I would say to someone who wants to use it, read the recommendations thoroughly before you start using it. Overall, I would rate the solution a ten out of ten.

If someone wants to use the product. It depends on whether the company can use another tool. If so, I recommend AWS, which, too, has a monitoring tool. However, it may still be too expensive for a small company. I recommend using CloudWatch for a small company if they don’t have money. Overall, I rate the solution an eight out of ten.

People who want to use the solution can follow the AWS documentation for configuring the product. Overall, I rate the solution a nine out of ten.

I have not used the solution extensively, but it's not user-friendly, and we have to learn the queries and then type. If you can write custom queries or learn to write them, you can do many things with Amazon CloudWatch. Rapid7 is cheap and more user-friendly as compared to Amazon CloudWatch. However, Amazon CloudWatch is more stable as compared to Rapid7. Overall, I rate Amazon CloudWatch a nine out of ten.

If someone is utilizing a limited set of services on Amazon AWS and their application is hosted on Docker or Kubernetes products, they may choose to use an alternative monitoring tool instead of relying on Amazon CloudWatch. However, the developers of Amazon CloudWatch are continually improving the tool, and adding features to address any issues that are not currently available on the cloud version will eventually be incorporated into Amazon CloudWatch. If the infrastructure and the software services are relatively simple I would recommend this solution. The Amazon CloudWatch agent can provide additional metrics, but for those seeking a more visually appealing and understandable approach, different tools may be more suitable. I rate Amazon CloudWatch an eight out of ten. I rated the solution an eight out of ten because of its user-friendly interface and the presence of a helpful single dashboard. This solution also offers unique tools, like application insights, which rely on artificial intelligence. This means that regardless of the traffic or type of users accessing our server, the insights provided are based on AI technology. The role of application insights is expected to grow significantly in the coming years as the solution continues to incorporate AI into its functionality. For example, it can provide information on how much memory was occupied by your machine at a particular time.

Most of my customers are using Datadog. I rate Amazon CloudWatch a six out of ten.

Since it is a cloud solution, we are likely on the latest version, although I don’t know the exact version number. This is a basic version that you can start using right away, and there's nothing too technical to think about or to know. You can implement it right away and then try to scale up or advance on the monitoring. I would rate the product eight out of ten.

I rate AWS CloudWatch nine out of 10. It gives me an idea about my resources through logs, metrics, etc. I recommend it. It's easy to understand, with graphs showing the services running on your applications and the resources they're consuming. You can also track your billings, and identify the services consuming too many resources and terminate instances if necessary.

I would recommend they have an understanding of the basics of AWS before you start configuring. I would rate Amazon CloudWatch a nine out of ten.

Amazon CloudWatch is a web-based tool, so there's no version control for it, so you could say it's always the latest version provided by Amazon. It's deployed on the cloud. Almost everyone from the technical team within my company uses Amazon CloudWatch, so that's five to six people in total. One to two people is enough to handle the deployment and maintenance of Amazon CloudWatch because it's a one-time process. Once it's done, you don't need to change it in a way, so one to two people would be fine. As Amazon CloudWatch is an essential tool for my company, usage of it will gradually increase with new projects or instances because of the basic infrastructure monitoring and similar features it provides; however, there's no plan to expand in terms of doing more with Amazon CloudWatch. My advice to others looking into implementing Amazon CloudWatch is that Amazon has pretty sufficient documentation on installing the tool and configuring the alerts. Still, it would be better to have a script deployed through Lambda to create alarms or use the Amazon SSM Agent to create the alarms instead of manually doing it. I'd rate Amazon CloudWatch as eight out of ten because it does whatever it promises, and it's a good tool for monitoring and alerting.

I'm a solution architect who works for a service-based company, so I have different clients. I provide software development services for architecture support for multiple global insurance companies and the bank financial sector. Some companies use Amazon CloudWatch, and I've worked on that solution. I've also provided Azure Managed Grafana services for one of the clients. There's no particular version for Amazon CloudWatch, but whatever the latest version is, that's what I'd be configuring. I don't focus too much on the version of the solution. It's on AWS Cloud. My company runs almost forty to fifty projects, mostly using AWS and Amazon CloudWatch, so at least thirty to forty people use the solution. What I would advise anyone looking into using Amazon CloudWatch is to go for it especially when you're on the AWS environment. To be frank, I've only used Amazon CloudWatch, so I'm recommending it because I've never faced any major challenge with it. I haven't found any new software that's as user-friendly as Amazon CloudWatch. I did have a few problems with it such as log storing, log back up, and log searching, and if I see any other tool that's better than Amazon CloudWatch, then I'll put that up for discussion, but right now, other people also recommend the solution and I know it, so I'm going ahead with Amazon CloudWatch. I'm looking at other solutions in the market, but I'm not comfortable, and I haven't even done a POC with other solutions yet. I'd compare Amazon CloudWatch with my old style of reading the logs as a developer, and I would rate the solution as seven out of ten. Amazon CloudWatch benefits me by streaming all the logs together, and this means that across all the services, I can search for specific transactions. The solution also has a single dashboard that shows me all services via log steaming. My company is a service provider, partner, and manager of AWS.

The solution is pretty good because it automatically comes and works well with AWS. Before you use any product from AWS, think about whether it is supported or how it will interface. I suggest using the solution with one product at a time and then transitioning to important interfaces. If you find you can't configure the solution with Redshift for example, and are struggling to build your S3 even though both use S3, then you may have to find another monitoring solution. It makes sense to follow Amazon's best practices. They advise not to use certain monitoring components alone but to use them as an integral part of your system. Monitor your ecosystem and think of a high-level picture of it rather than just determining that CloudWatch must be a part of Redshift. This solution is just one part of an entire system. I would rate the solution a nine out of ten.

We're an enterprise group. We may have a partnership with Amazon. I'm not sure. We mainly use the public cloud. We also have hybrid setups. I'd rate the solution an eight out of ten. It does what it does and it does well. However, the UI could always be better.

I'd recommend the solution. Whoever is using Amazon services has to consider using CloudWatch as a bundled solution so that the systems are properly monitored and notified. If anybody is using any other Amazon services, they definitely should consider using CloudWatch. That's my recommendation. I'd rate the solution nine out of ten. It's a robust service.

Take the time to learn the solution in-depth because Amazon CloudWatch has a lot of features. That way, you will be able to know how to use all of the features. On a scale from one to ten, I would rate this solution at eight.

We're using Amazon CloudWatch. Our clients are using different monitoring services. Some are using Prometheus, while some are using Nagios, but in our platform overall, all the services are located in AWS only. I have no advice for people looking into using Amazon CloudWatch, but in our case, all our services are running on the AWS platform, so initially we thought of using all their cloud-based native services to save on admin and infrastructure costs, including other connectivities. That was our plan initially, but now client requirements have been more demanding. The client wants a real-time monitoring solution which is something we are unable to get from the product, so we are looking for a new solution like Datadog, or New Relic, or Prometheus. My rating for Amazon CloudWatch is a seven out of ten. I'm a consumer and I'm working in a company like Accenture. It's a service-based organization. It's a MNC (multinational corporation), so it's global and we have multiple clients. These multiple clients have different strategies and they want their applications to be set up in the Cloud. I'm the AWS architect, so I do the solutions and provide solutions for them, e.g. cost optimization, infrastructure optimization, etc. What clients find most challenging thing in the Cloud is monitoring, so we are looking for a centralized monitoring solution where we can get everything in a single window, but we want a service that's similar to Amazon CloudWatch. We collect data and we need to analyze that log and analyze the metrics, so we create a refined monitoring data, then we publish it by using the Amazon QuickSight dashboard. There are three different services we have to use, so instead of using all these different services, we want to use only one service: a centralized monitoring service to meet all our needs. This is what we are looking to have in the future.

I would recommend it depending on what a customer wants to achieve or what is the requirement for monitoring. I would rate Amazon CloudWatch a six out of 10.

I'm an implementor, not a user. We are not a partner. I'm not sure which version of the solution is currently used, as it depends on the client's environment. I'd rate the solution at a seven out of ten. I personally have a lot of EC2 stations on Amazon and I have a lot of computing credits on Amazon. I really enjoy using Amazon.

It's a good product. It does what it says it's going to do. In the beginning, you've got to really focus on your optimization, and have somebody who understands it from the beginning. That was a part of the implementation, to be able to do the maintenance and be effective at it. I would rate it an eight out of ten because overall it's really good. I'm sure they're going to add more features and more things over time, but it's a pretty complete product for the most part. Again, some of the learning pieces could be better, the reporting could be better. It's not perfect, but it's not bad. It's pretty good.

I don't check the version we use, so I'm unsure if we're using the latest one or not. Since it's a cloud application, I assume it's always the most up-to-date option. Since Cloudwatch isn't a free service, I'd advise other organizations to really know what they want to monitor to avoid extra costs. I'd rate the solution eight out of ten. If the solution revised its pricing and simplified its portfolio of monitoring services I'd rate it higher.

We're not using the latest version of the solution. We might be using the latest version minus one. I would advise other users that they need to understand the solution and what it is capable of doing. From there, they should build out their use case and try to see if the solution will fit into it. It's a good idea to do a POC. Unless you do a technical evaluation and a proof of concept, you will not be 100% thorough in your preparations before implementing any kind of solution. I'd rate the solution eight out of ten.