Amazon CloudWatch vs. SolarWinds Papertrail

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

As a 3rd party endpoint, SolarWinds Papertrail did exactly what it needed to. My hesitation is on the technical aptitude of the colleague receiving the recommendation, as the overall level of command line skill/understanding would have to be high. Web applications are a great solution here, but MOST of them already provide some sort of logging output. The scenario would definitely be in the situation where logging wasn't readily available in the current solution space. IF something like SolarWinds Papertrail was needed, it's probably the de facto thing that I would recommend.

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

• Free configuration on how Papertrail will alert you
• Easy to setup with your server/application
• Very intuitive and easy to use
• Fair pricing policy/plan

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

• The CLI was a bit clunky and required some Linux-y thought to get right (obviously more designed with scripting in mind)
• Tracking logs in real time (think something like `tail`) wasn't wildly intuitive
• Accessing/searching archives required a lot of CLI-style pulling/extracting/reg-exing

Incentivized

We are definitely going to continue using Papertrail. It's been a lifesaver.

Incentivized

It's extremely easy to use. I and new colleagues have never had any issues configuring this tool or setting it up, it works almost out of the box with very simple instructions to follow to configure it to our own environment. I would highly recommend it on that ability alone.

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 honestly have never had the need to use the support team, as we have not run into any issues so far. If we did however, judging from how the tool itself works, I don't doubt that the team would provide excellent support for any issues that we may possibly run into.

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

CloudWatch, by itself, is terrible at search. CloudWatch Insights works great and has powerful search capabilities, but it's more difficult to set up alerts. Also, because Insights charges per search, you have the potential to accumulate a large bill if you need to do many searches. I like that SolarWinds Papertrail has a known monthly cost.

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

• SolarWinds Papertrail cost compared to the benefits it provides is a win.
• When the logs are flooded, and the monthly limits are reached, the failure to post new logs may be a significant drawback.
• The great search/filter capabilities is key for speedy and precise debugging of incidents that may happen during testing and operation.

Incentivized