Amazon CloudWatch vs. SolarWinds Hybrid Cloud Observability

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

- For small teams serving big organizations - it's a really simple tool to install and set up relatively quickly. - the new installer is also great - I don't have to understand what modules need to be installed; it's all streamlined. - The HCO Licensing allows you to run the Additional polling engines at a scale where the previous licensing model didn't. We can deploy APEs in locations now, which would not have been worth the investment in previously as there weren't enough devices in that location/region to spend the $$$$ on an APE License.

Incentivized

• 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

• Automated dependency mapping is a big hit.
• High availability is extremely simple to implement.
• Simple to use and drill into issues.
• Analysis of growth patterns driving the recommendation engine.

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

• Orion maps needs to be able to map to groups like atlas can by name
• web tool set integration, atm this needs to be removed from the server to install Observability

Incentivized

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

Solarwinds has the best overlap of the two others I've mentioned - the other two tools (Datadog and Dynatrace) are great in their own way but Solarwinds is just good at everything; if I had to pick one tool of the above, it would be Solarwinds for the compatibility and ease of use, the other tools are more focused on being great at certain things while Solarwinds is the jack of all trades.

Incentivized

• 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

• Provided the opportunity to offboard a number of monitoring tools that are no longer required.

Incentivized