CloudCheckr vs New Relic

• Detailed Best Practices. It's important to align your cloud to industry best practices for security and cost—it just performs better if it's used the way it's meant to be used. AWS is very flexible, and that's great when you have special requirements, but you've got to at least know when you're using something in a non-standard way so you can think through the implications.
• Cost Reduction. Some recommendations are almost impossible to make at least for our setup, but many, many others are easy. We only have to log into CloudCheckr every few months and make a few changes for it to more than pay for itself.
• Right-Sizing. This is related to the other points, but for some reason is separate from their cost module. The metrics it's able to pull only tell half the story, so it's good to verify it's sizing recommendations before making changes. But it does show you what instances to focus on first, and even if you choose a slightly different size to move it to, it does clearly indicate it's current size isn't appropriate. And this works both ways, if the size is too big, you can save some cash by making it smaller, but if it's too small, you want to be sure to scale up before you run into performance problems.

Read full review

• New Relic lets you drill down into the nitty-gritty of your application, breaking down requests however far you want in order to inspect the performance of your application throughout the request lifecycle.
• New Relic offers many integrations with other services and technologies, making it easy to get it set up and start using it.
• New Relic offers many views and types of visualizations to help you understand what's going on in as much detail as you want to know.

Read full review

• CloudCheckr features have a tendency to break without warning. Functionality in place for months could suddenly stop working.
• CloudCheckr support often delays work on support tickets for fixing broken application functionality.
• The CloudCheckr platform and documentation website often crash or experience performance degradation.
• CloudCheckr cost reporting is often impacted by faulty code or broken report functionality. This can contribute to a low level of confidence in CloudCheckr's ability to deliver accurate cost reporting.

Read full review

• Cloud-centric / OS-centric. There is no/limited ability to query metrics with an agent installed.
• Insights-based queries (dashboards and alerts) are limited to 1000 (soon to be 2000) records and that doesn't work for enterprise scale.
• NRQL is awesome -- except when it isn't. The replacement QL is more robust but is significantly more complex to learn.
• No agent management tools in the platform. And, yes, you will want agent management tools after the first dozen or so deployments.

Read full review

• CloudCheckr has allowed us to increase resell margins as an MSP.
• CloudCheckr has made us aware of cost savings opportunities that exceed the price of the platform itself.
• CloudCheckr has given us additional visibility that has allowed us to manage and understand cloud computing costs.

Read full review

• New Relic helps us detect defects before our customers do.
• New Relic helps us prioritize performance improvements. Engineers don't need to spend time measuring the latency of transactions themselves.
• New Relic helps us notify the appropriate people rapidly when there are problems.

Read full review