Amazon CloudWatch vs. Apache CloudStack

Cloud watch is great and essential if you decide to invest in AWS and have any need to monitor the health of all aspects of your VPC resources, or at the organizational level (multiple accounts). Another benefit of the service is constant upgrades at no additional costs; the software evolves to develop modules and interface improvements. For first-time users in AWS, this is going to take a bit to understand, so the learning curve to this metrics environment can seem overwhelming at first glance/use.

Incentivized

Whether our clients are VPS hosting providers or operate private cloud infrastructure for their internal enterprise requirements, CloudStack provides solutions in an easy to implement and operate way that is simple to provide training for. The learning curve for our customesr adopting CloudStack for the management of their cloud infrastructure is shallow, enabling our clients to come up to speed quickly without having to outsource their administrative functions any longer than necessary

• It provides lot many out of the box dashboard to observe the health and usage of your cloud deployments. Few examples are CPU usage, Disk read/write, Network in/out etc.
• It is possible to stream CloudWatch log data to Amazon Elasticsearch to process them almost real time.
• If you have setup your code pipeline and wants to see the status, CloudWatch really helps. It can trigger lambda function when certain cloudWatch event happens and lambda can store the data to S3 or Athena which Quicksight can represent.

Incentivized

• Low-cost solution
• Open-source
• Engaged community
• Solid documentation
• Is a very reliable tool for orchestration with good usability

Incentivized

• 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.

Incentivized

• Sometimes you can find undocumented bugs that can compromise the entire infrastructure.
• [If] you don't have an official support channel, you have try to find out the source of the problem by yourself.
• Volume size limitation. Other players allow you to create volumes up to 64TB while ACS allows only 2TB volumes

Support is effective, and we were able to get any problems that we couldn't get solved through community discussion forums solved for us by the AWS support team. For example, we were assisted in one instance where we were not sure about the best metrics to use in order to optimize an auto-scaling group on EC2. The support team was able to look at our metrics and give a useful recommendation on which metrics to use.

Incentivized

I believe that CloudWatch is a better solution to use with AWS services and resources in terms of cost and ease of integration with AWS infrastructure services. But keep in mind that Elasticsearch is better at aggregating application-level metrics. We chose CloudWatch because of its capabilities to integrate and monitor AWS services in almost real-time.

Incentivized

The University, my first large implementation, had a big issue with 149 small data centers spread on São Paulo State, this data centers costs to university were very high, the consolidation idea in two data centers were awesome, but were worried with the management, so we adopted ACS to management of all 576 physical hosts. Now a days the university is delivering IaaS for all staff, students, teachers and researchers, they are using these resources to delivery services to their clients and have a great results in research area

• 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.

Incentivized

• Low-cost solution (free and open-source)
• More than 2000 users using it simultaneously
• Stable and reliable
• Up and running since 2012

Incentivized