Amazon CloudWatch Reviews

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.

Ultimately it gives you enterprise visibility that you don't typically have. If you don't have this or a competing product you would not have this visibility. And that allows you to take care of issues faster, and take care of issues on the fly, as opposed to having to go run reports, have engineers go through logs, and look at things, try to figure things out.

The ability to analyze is probably the most valuable feature. We also have system-wide visibility. And you have a unified operational health watch, I think those are pretty key. 

I think the biggest is with CloudWatch. It's part of the AWS interface, so again, it's all baked in. You don't have to have a third party tool, because it's a part of the platform, and having one platform, as opposed to having to use a lot of different platforms makes a huge difference. Or having to go to another third party platform.

I think the machine learning aspect of it probably does help because machine learning is not really machine learning. That needs some help. Better reporting is always something needed. That could be an answer to just about anything. But you always want better reporting, better dashboards, things that are just more dynamic and more accessible.

We don't use it ourselves. We deploy it but have been doing so for around nine months.

The stability is good. They took a lot of the best of what other people are doing, so it's pretty good.

Scalability is really good because it's baked into the platform, so that gives it a lot more capacity for scaling very quickly.

The technical support is fantastic. It's the best ever.

The setup is straightforward for what it is. It's a little of both. It's honestly like any technology, it's a little of both. It can be very straightforward, depending on the size of the client and what they currently have. If it's a very large enterprise client, it's going to be much more complex. If the size of their instance is running a hundred applications, versus a small company that may only be running 10. It's just going to be much more complex, making sure that everything is connected, running and that it's watching everything correctly. The setup becomes a little trickier.

I would say that the average deployment is probably about a month or two, just for this particular product. Our implementation strategy is pretty straightforward. We analyze what their instance currently looks like, and then we just build out a roadmap for overlaying and including CloudWatch, to make sure that it's connecting, watching, and then reporting accurately for each application. It could be anywhere from two people to five people to deploy and maintain. If it's a large deployment, it's going to be more. 

Maintenance is pretty straightforward. One person can be doing maintenance, or even a half-person, if you will. Somebody doing it part-time and doing something else. Just depending on the size and the complexity of what has to be done, and then maintained and watched over. Somebody has to be watching the reports, making sure if an alarm goes off, that somebody's dealing with it right away.

A lot of companies don't have a lot of control over their cloud instance. They want to but they don't know how to get there. That's part of what we help them with. CloudWatch helps provide that look into what's really going on and making sure that they're going to get the ROI out of it. If you don't have that, you're going to really struggle. I think there's more opportunity for visibility available than a lot of companies think there is, or know how to take advantage of.

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.

We primarily use the solution for budgeting and monitoring for abnormal behaviour.

The permanent marking is something we really appreciate in the solution.

The solution offers very detailed metrics for their services.

I haven't really thought about how the solution could be improved and I'm not sure what features are lacking.

The solution should adjust its pricing. We tend to find the costs for using it are a little high.

Right now, in relation to monitoring services, there are too many services and too many metrics per service.

I understand that it's per service but some complex acronyms, etc., make it kind of hard to understand the solution sometimes.

I've been using the solution for three years now.

The solution is very scalable. It's one of the reasons we chouse to use it.

We have about 2500 users on the solution currently within our company.

The technical support that Amazon provides is very good. We're satisfied with the level of service we get. You do have to pay for technical support, however, and the best offering is quite expensive.

Before using this solution, we had our own on-premises access.

The initial setup was straightforward. We didn't face any complexities.

The solution is a bit pricey. The solution requires you to pay for technical support, which is tiered, and certain options are quite expensive.

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 use the product to monitor resources for reporting purposes. It alerts us when we are required to scale up resources.

The product helps us collect and store various metrics to set test alarms. The metrics allow us to apply the configuration changes in our environment.

Amazon CloudWatch's pricing needs improvement.

We have been using Amazon CloudWatch for three years.

The product is very stable.

The initial setup process is easy.

The product generates a return on investment.

The product's cost is relatively inexpensive.

I rate Amazon CloudWatch an eight out of ten. I recommend the product if you want a system to monitor the resources. It provides proper metrics and manages workload efficiently. It offers features for real-time cloud monitoring. You can view the activities on the network set for a specific timeline.

Amazon CloudWatch is a cheap and easy-to-use solution. We can run custom queries on the logs with the solution. Since our whole system is in AWS, we can easily push to Amazon CloudWatch.

There's a learning curve with Amazon CloudWatch since we have to learn to write the queries to extract the keys and logs.

We have been using Amazon CloudWatch for five years.

Amazon CloudWatch is a stable solution. I rate Amazon CloudWatch a nine out of ten for stability.

Amazon CloudWatch is a scalable solution. I rate Amazon CloudWatch a nine out of ten for scalability.

Amazon CloudWatch's initial setup is easy.

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.

We use Amazon CloudWatch for logging.

The solution's pricing is a bit higher.

I have not faced any issues with the solution’s stability.

Amazon CloudWatch’s technical support is good.

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

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.

Monitoring time and ensuring ease in it is the most valuable feature. It offers three distinct signing metrics that allow for effective oversight.

Improvement of SSSD logs would be beneficial.

I have been using for a year now.

It has good stability features.

We have thirty members using it, so it is scalable.

The initial setup was easy.

The deployment process was done in fifteen minutes and it was very easy.

I would rate this solution ten out of ten.