New Relic vs Papertrail: 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, Papertrail is detailed as "Hosted log management for servers, apps, and cloud services". Papertrail helps detect, resolve, and avoid infrastructure problems using log messages. Papertrail's practicality comes from our own experience as sysadmins, developers, and entrepreneurs.
New Relic can be classified as a tool in the "Performance Monitoring" category, while Papertrail is grouped under "Log Management".
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, Papertrail provides the following key features:
- Intuitive Web-based log viewer
- Powerful command-line tools
- Long-term archive (S3)
"Easy setup" is the primary reason why developers consider New Relic over the competitors, whereas "Log search" was stated as the key factor in picking Papertrail.
Airbnb, Spotify, and LinkedIn are some of the popular companies that use New Relic, whereas Papertrail is used by Product Hunt, CodeCombat, and Baremetrics. New Relic has a broader approval, being mentioned in 3143 company stacks & 566 developers stacks; compared to Papertrail, which is listed in 244 company stacks and 46 developer stacks.
What is New Relic?
What is Papertrail?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
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
Which #APM / #Infrastructure #Monitoring solution to use?
The 2 major players in that space are New Relic and Datadog Both are very comparable in terms of pricing, capabilities (Datadog recently introduced APM as well).
In our use case, keeping the number of tools minimal was a major selection criteria.
As we were already using #NewRelic, my recommendation was to move to the pro tier so we would benefit from advanced APM features, synthetics, mobile & infrastructure monitoring. And gain 360 degree view of our infrastructure.
Few things I liked about New Relic: - Mobile App and push notificatin - Ease of setting up new alerts - Being notified via email and push notifications without requiring another alerting 3rd party solution
I've certainly seen use cases where NewRelic can also be used as an input data source for Datadog. Therefore depending on your use case, it might also be worth evaluating a joint usage of both solutions.
We currently monitor performance with the following tools:
- Heroku Metrics: our main app is Hosted on Heroku, so it is the best place to get quick server metrics like memory usage, load averages, or response times.
- Good old New Relic for detailed general metrics, including transaction times.
- Skylight for more specific Rails
Controller#actiontransaction times. Navigating those timings is much better than with New Relic, as you get a clear full breakdown of everything that happens for a given request.
Skylight offers better Rails performance insights, so why use New Relic? Because it does frontend monitoring, while Skylight doesn't. Now that we have a separate frontend app though, our frontend engineers are looking into more specialized frontend monitoring solutions.
Finally, if one of our apps go down, Pingdom alerts us on Slack and texts some of us.
Regarding Continuous Integration - we've started with something very easy to set up - CircleCI , but with time we're adding more & more complex pipelines - we use Jenkins to configure & run those. It's much more effort, but at some point we had to pay for the flexibility we expected. Our source code version control is Git (which probably doesn't require a rationale these days) and we keep repos in GitHub - since the very beginning & we never considered moving out. Our primary monitoring these days is in New Relic (Ruby & SPA apps) and AppSignal (Elixir apps) - we're considering unifying it in New Relic , but this will require some improvements in Elixir app observability. For error reporting we use Sentry (a very popular choice in this class) & we collect our distributed logs using Logentries (to avoid semi-manual handling here).
While it's not -hard- to login to your servers and check each log file it can quickly become a burden with log files kept in different locations, slightly different syntax for each and perhaps more than one server to dig through. Depending on your business you are probably not doing this everyday so the fact that you can setup Papertrail once and are then able to search through it in one location is a huge time saver in the long run. Papertrail has some competition in this space but i like the singular goal of this app and it has a good price to value comparison as well. It just works which is basically all you can ask from an app like this.
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 use Papertrail as a distributed log aggregator for nightly.zerotoherojs.com and dojo.zerotoherojs.com
I served me really well so far.
It is simple to use, intuitive, and reasonably-priced.
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.
Papertrail is sent logs via Heroku log drains, and provides centralised logging of both the web and background workers for debugging errors and spelunking into logs.
We use PaperTrail, so basically all of our instances write into SysLog entries that are shifted to PaperTrail.
we used papertrail at talenthouse for all out logging needs. elegant and simple ui. enjoyed the service.