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

• Monitor traffic rates and server usage on real time
• Helps engineers to dive deep into an issue and guides them to the root cause
• Provides high-level system health status of different components (ie. Server capacity, RPM, page load time, error rate..)
• Near real time reporting
• Links with deployment so easy to understand if an issue has occurred after a particular release

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

• It would be helpful if use cases for particularly a Windows installation, were provided to help determine which set of configuration files would be the one a group would want to control. I.e. potentially with a department trying to do DevOps, it's difficult to determine which team needs to have responsibility for what at times. The reason I mention this, is New Relic seems to in many ways be a tool that's useful for DevOps-related processes and staff.
• On the main New Relic One site, sometimes a refresh option is available for new features. It would be helpful to see what the new features are in advance before trying this out. Particularly if doing a demo or a working season with another team.
• I'm not aware of a page or specific site which describes/summarizes all of the different NR Products and their features.
• Sometimes it's tricky to determine which product to use to accomplish a task.

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

• Gives us great visibility into what our services are doing at all times.
• Alerts us quickly when there is a problem so we can address it with alacrity.
• Gives us extremely customizable options in regards to how we want to track, store, and materialize our data.

Read full review