Instrumental vs New Relic: What are the differences?
Developers describe Instrumental as "Visualize any aspect of your application performance, measure production code in real-time, and share with your entire team". Instrumental is a real-time application and server monitoring platform. With over a million datapoints processed every second, we're one of the highest scale monitoring services. On the other hand, New Relic is detailed as "SaaS Application Performance Management for Ruby, PHP, .Net, Java, Python, and Node.js Apps". New Relic is the all-in-one web application performance tool that lets you see performance from the end user experience, through servers, and down to the line of application code.
Instrumental and New Relic can be categorized as "Performance Monitoring" tools.
Some of the features offered by Instrumental are:
- Application monitoring - we accept any volume of arbitrary data, making it easy to set up graphs to measure the performance of your application in real time
- Server monitoring - Ruby apps can use our instrumental tools gem to monitor information like CPU statistics, memory usage, disk space, and all the other things you'll need to monitor your servers. Language support - Ruby is supported using a custom library, and all other languages are supported with our Statsd backend
- RESTful API - upon authentication, data is collected and returned in strict JSON format
On the other hand, New Relic provides the following key features:
- Performance Data Retention
- Real-User Response Time, Throughput, & Breakdown by Layer
- App Response Time, Throughput, & Breakdown by Component
"Best, fastest, and easiest-to-use Interface" is the top reason why over 2 developers like Instrumental, while over 411 developers mention "Easy setup" as the leading cause for choosing New Relic.
What is Instrumental?
What is New Relic?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Instrumental?
Sign up to add, upvote and see more consMake informed product decisions
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Instrumental?
Sign up to get full access to all the tool integrationsMake informed product decisions
Free Heroku add-on. Not particularly useful for us. Rails profilers tend to do a better job at the app level. And I can never really figure out what’s going on with Heroku by looking at New Relic. I don’t know if we’re just not using New Relic correctly or if it really does just suck for our use case. But I guess some insight is better than none.
How do you know what parts of the workflow need improvement? Measure it. With New Relic in place, we have graphs of our API performance and can directly see if a server or zone is causing trouble, and the impact of our changes. There’s no comparison between a real-time performance graph and “Strange, the site seems slow, I should tail the logs”.
We monitor and troubleshoot our app's performance using New Relic, which gives us a great view into each type of request that hits our servers. It also gives us a nice weekly summary of error rates and response times so that we know how well we've done in the past week.
I'm trying to wring more instrumentation out of New Relic as it pertains to Rack, but for the time being, New Relic is monitoring/alerting uptime and some basic performance metrics.