Amazon CloudWatch Reviews

We are primarily using the solution to monitor some of the instances that we have on Amazon for our testing development. It is also the go-to solution used by our organization to track logs and organize metrics across all applications deployed on Amazon Web Services

We are able to, on a real-time basis, understand the capacity utilization and the latency aspects, and, to that extent, we can now know the productivity of the tests and if the development team has increased them in any way. The tool provides an easy integration to monitor and aggregate metrics for any deployment on AWS cloud.

The solution works well as part of an overall Amazon ecosystem.

The solution is easy to set up.

The solution gives us very good real-time data.

Ability to aggregate performance metrics.

Getting  real time alerts on AWS environment.

The drill-down aspect on the dashboard of the solution needs improvement. We get a very good high-level overview, but when we drill down, it becomes a little less clear. We have given this feedback to AWS as well and hope they will improve this in the future. It could also do a much better job of monitoring performance when core AWS services are not used. 

I've been using the solution for about three and a half years now.

The solution is very stable. We haven't had issues with bugs, glitches, or crashes.

The solution scales quite well.

It's the infrastructure team that is using the solution at our organization. It's a team of about seven or eight people and they are using it to monitor the performance of the cloud instances to address any degradation.

The solution is currently being used in 100% of the Amazon instances that we are leveraging. Unless we increase the number of instances on Amazon, we are not planning to scale this product beyond what we are using. We are already using it to the maximum.

Amazon's technical support is a tiered support system. In our case, we have somebody who's available to us and they call us to assist if we need them to.

We didn't previously use a different solution. We've only ever used Amazon.

The solution's initial setup was fairly simple and straightforward. 

The deployment took less than a week. Once we started, our first task was to understand the solution and how we could best leverage it for our environment. Once we had that configured, we then started working towards deploying it.

We worked directly with Amazon. We didn't work with an integrator or reseller.

We have monthly licensing costs. The licenses are probably in the vicinity of about $300 - $350/month.

There are no other costs or hidden fees beyond the licensing.

We didn't evaluate any other solutions. This is because this was the product that was native to Amazon and so this, we knew, would suit us. There was no need for us to look at another product at that time we set this solution up.

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. 

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.

We can set CPU thresholds using the solution.

The technical support must be improved.

I have been using the solution for more than two years.

The tool is very stable.

We have more than 600 customers hosted in the AWS environment.

Recently, we faced a payment issue in AWS. Our payments were not happening through the default account. My organization contacted the support team. Sometimes, we get good support. Sometimes, we do not get good support.

We have the complete documentation to set up AWS. We use Confluence for our documents. The steps to set up AWS are clearly mentioned in the documentation.

The solution charges $0.09 for 1GB of data we store in AWS.

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

We use it for testing environments.

There is room for improvement in terms of stability. 

I have been using this solution for two years. 

I would rate the stability an eight out of ten. 

I would rate the scalability a ten out of ten.

The initial setup is easy. 

I deployed the solution myself. We need cloud architects and engineers for the deployment and maintenance of the solution.

Overall, I would rate the solution a ten out of ten. I would definitely recommend using the solution.

We use the solution for monitoring the traffic. We analyze any suspicious traffic detected by AWS.

The monitoring feature is valuable. AWS provides a detailed document of how CloudWatch works and how we can integrate and utilize it. We get a summary of all the logs explained in the documentation.

The product should provide more features.

I have been using the solution for one and a half years.

I rate the tool’s stability a nine out of ten.

I rate the tool’s scalability a nine out of ten. Almost 100 people from three to four teams use the solution in our organization.

We have reached out to the support team a few times. The technical support is very good. Sometimes, we don’t even have to reach out to the team. If they detect any issue, they email us about it.

Positive

The initial setup was quite easy.

I have seen an ROI on the solution.

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.

We are using Amazon CloudWatch for all of our data monitoring.

The most valuable feature of Amazon CloudWatch is reliability.

When customers want to see the CPU or memory utilization there is a cost. This should be free to see the utilization.

I have been using Amazon CloudWatch for approximately three years.

If the servers are running then the solution is good. It is a separate service on the cloud.

The solution is scalable.

All of our technical staff are using the solution. We have a large organization with many branches.

I rate the scalability of Amazon CloudWatch 

I have not used the support but I have heard from a colleague they are excellent.

We were previously using the AppDynamics machine agent and it saved money by using Amazon CloudWatch.

There is no setup for Amazon CloudWatch. It is on the cloud and all that is required is a migration.

The price of Amazon CloudWatch is reasonable. When the rate of data collection is done the price will increase. The price is less than other solutions.

This is a native Amazon Cloud solution and I would recommend it for monitoring.

I rate Amazon CloudWatch a nine out of ten.

The solution is used for monitoring systems and for protection. For example, there are ransomware attacks and other threats that need to be secured.

The most valuable feature of Amazon CloudWatch is intrusion prevention.

The solution could benefit from a price decrease.

I have used Amazon CloudWatch within the last 12 months.

The solution is stable.

We have approximately 10 people using Amazon CloudWatch in my organization.

I have not used the support from Amazon CloudWatch.

We used assistance for the implementation of the solution.

The solution is expensive.

I rate Amazon CloudWatch a seven out of ten.

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.

I have found the memory metrics and the CPU metrics valuable.

Amazon CloudWatch has a user-friendly interface.

I would like to monitor inbound and outbound transfer. I would also like to control the traffic for load balancing.

It would be good to see the transfer inbound per EP or per load balancing. This is a useful metric to have another review of your solution. It can also provide information on from where the clients enter and how they consume our data and solution.

I've been using Amazon CloudWatch for the past four years.

It is a stable solution.

It's scalable.

The initial setup is straightforward.

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.

The portability that we have in Amazon is great. It's very different than the other solutions on offer.

The solution is easy to use. I find it quite enjoyable.

The portability of the Datadog is much more flexible for us. The client does not need to have Amazon services for the entire life of the project, unfortunately. They can change. But for Amazon to move over to Google Cloud, for example, that it's very important for the client. They are not investing in a particular single cloud service.

The panel should be better. Datalog's is much more visual.

The configuration capabilities could be better. We've found it to be quite good on Datalog, for example. They should emulate that.

I also have experience with Datalog. I find there a lot more positive aspects of that over this solution.

As an implementor, I can implement the solution for our clients.

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.