New Relic vs Runscope: What are the differences?
Developers describe New Relic 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. On the other hand, Runscope is detailed as "API Performance Monitoring". Keep tabs on all aspects of your API's performance with uptime monitoring, integration testing, logging and real-time monitoring.
New Relic can be classified as a tool in the "Performance Monitoring" category, while Runscope is grouped under "API Tools".
Some of the features offered by New Relic are:
- Performance Data Retention
- Real-User Response Time, Throughput, & Breakdown by Layer
- App Response Time, Throughput, & Breakdown by Component
On the other hand, Runscope provides the following key features:
- Runscope Radar: Automatically monitor your APIs from around the globe. Integrates with PagerDuty, New Relic Insights, Keen IO, HipChat, Slack and more. Test complete API workflows with powerful assertions and notifications.
- Runscope Metrics: API performance and usage reports.
- Runscope API Traffic Inspector: Log and view API calls from any language or framework to any API to solve integration problems.
"Easy setup" is the primary reason why developers consider New Relic over the competitors, whereas "Great features" was stated as the key factor in picking Runscope.
According to the StackShare community, New Relic has a broader approval, being mentioned in 3142 company stacks & 578 developers stacks; compared to Runscope, which is listed in 38 company stacks and 7 developer stacks.
What is New Relic?
What is Runscope?
Want advice about which of these to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Runscope?
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
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.
Just like we care about errors, we care about metrics - especially around performance. You'd be crazy not to use it - and not surprisingly, it's a one-click add-on in Heroku.
Used Runscope for monitoring API uptime and data validation in context of the Harald beacon platform.