Loggly vs New Relic: What are the differences?
What is Loggly? Log Management, Simplified in the Cloud. The world's most popular cloud-based log management service delivers application intelligence.
What is New Relic? 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.
Loggly and New Relic are primarily classified as "Log Management" and "Performance Monitoring" tools respectively.
Some of the features offered by Loggly are:
- See what your application is doing during development
- Catch exceptions and track execution flow
- Graph and report on the number of errors generated
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
"Centralized log management" is the top reason why over 35 developers like Loggly, while over 411 developers mention "Easy setup" as the leading cause for choosing New Relic.
Airbnb, Spotify, and LinkedIn are some of the popular companies that use New Relic, whereas Loggly is used by AdRoll, Engine Yard Cloud, and Heroku. New Relic has a broader approval, being mentioned in 3143 company stacks & 566 developers stacks; compared to Loggly, which is listed in 95 company stacks and 15 developer stacks.
What is Loggly?
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
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.
We log things of importance to loggly. It's a nice one-stop place to search into errors, exceptions, and expectations.