Azure Application Insights vs New Relic: What are the differences?
Developers describe Azure Application Insights as "It is an extensible Application Performance Management (APM) service for web developers". It is use to monitor your live web application. It will automatically detect performance anomalies. It includes powerful analytics tools to help you diagnose issues and to understand what users actually do with your app. 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.
Azure Application Insights and New Relic belong to "Performance Monitoring" category of the tech stack.
Airbnb, Spotify, and StackShare are some of the popular companies that use New Relic, whereas Azure Application Insights is used by Poq, Nexosis, and Shyft. New Relic has a broader approval, being mentioned in 3142 company stacks & 579 developers stacks; compared to Azure Application Insights, which is listed in 8 company stacks and 4 developer stacks.
What is Azure Application Insights?
What is New Relic?
Want advice about which of these to choose?Ask the StackShare community!
Why do developers choose Azure Application Insights?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Azure Application Insights?
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 Azure Application Insights?
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.