New Relic vs. Sentry

New - relic is well suited if you want to analyse the performance of your services and you want to improve it. Integration with multiple services with same account gives a clear picture of flow of your APIs if you have micro-service architecture. New-relic is less appropriate when you want to do logging of your system. As it does not emits every single calls

Incentivized

Great for standard web application performance monitoring, analytics and error reporting. Shows line level code errors, gives insight into performance issues (plugins, API issues, etc.). Automation and scheduled scanning in production gives client visibility into 'after deployment' value. Also lets a relatively small number of developers keep tabs on a handful of different site/applications without needing a bunch of tools. The UI is pretty complicated and can be overwhelming for new users. Documentation could be better for the learning curve,

Incentivized

• gives us an monitoring of all our underlying servers and also we can configure some alerts upon them like CPU and memory alerts.
• Kubernetes cluster monitoring with new relic for EKS gives us and minute details of our cluster utilisation like node usage, pods memory request and limits
• Network traceability for each and every request with response time analysis is great we can trace which component is responsible for generating response delay
• log managements of the logs the infrastructure is generating we can view logs through there only

Incentivized

• Great web interface. Lots of data available in a really clean format, with filtering options and more.
• Per-user exception tracking. User is complaining about something being broken? Look up their account ID in Sentry and you can see if they've run into any exceptions (with device information included, of course).
• Source map uploading. Took a little while to figure this out but now we have our deploy script upload sourcemaps to Sentry on each deployment, meaning we get to see stack traces that aren't obfuscated!
• Very generous free tier – 10,000 events per month. We're nowhere near that yet.

Incentivized

• I would like to see sort of simulator inside the user interface, that way we can send requests directly from it to test some configuration instead of setting up a test environment in our end.
• It would be nice if the data ingestion can be filtered by APM's. That way we can know which application is ingested most data.
• It would be nice if we could ingest logs (apache, system logs, and other logs) and correlate them with the APM.

Incentivized

• Alert Configuration. Would be really helpful to have multiple logical groupings within the "If" section of a single configurable alert.
• Alert Copying. Being able to copy an alert from one project to another would be super beneficial.
• Alert Tags. Better UI around how we select which tags are getting sent with each alert instead of a tiny text box.

Incentivized

The only issue that we have had with New Relic is that the price might be a little expensive for smaller companies. The amount of data you store in New Relic impacts the cost, and can get away from you if you don't work closely with the vendor. Overall though the application is top notch.

Incentivized

As an engineer, New Relic has been very quick and easy for me to pick up/install/use. It has been less easy for some of the less technical-minded folks in our organization and their UI still is inconsistent multiple years after refactoring their platform to be New Relic One.

Incentivized

Never observed an outage

Incentivized

there are times where browser cache will cause issues that require you to clear your browser before continuing.

Incentivized

There are times I feel that the initial support is lacking. And in some cases the automated responses of not hearing anything are annoying if the reason why there has been no movement is because we are still waiting to hear back from NR support. So, i think they should loose the automation as it can seem disingenuous

Incentivized

It's better to start by implementing New Relic in one project and test everything. Try to follow best recommended practices and read all the official documentation. Everything seems well tested. Then, start by installing agents to the rest of your projects and keep a close look to all logs and metrics New Relic gives you.

New Relic is the most full-featured offering that we've found, and is incredibly easy to start using with a PHP app. The New Relic agent is installed as a PHP extension so it is able to monitor and track the performance of any PHP app being run by the web server. Other tools required the installation and setup of a PHP dependency at the application level.

Incentivized

We used Rollbar but didn't like the configuration its not easy. And also doesn't support wide features like Sentry although its a cheaper option but doesn't have the dash-boarding like Sentry and its was not easy to integrate webhooks for different purposes. Somehow many people in company where not able to understand Rollbar dashboard who were very much used to Sentry.

Incentivized

Agent deployment is easily integrated into our workflow. Adding the agent to new servers is quick and painless

Incentivized

• Less time debugging issues or letting issues go unknown
• We know of issues before our customers
• One common tool for logs, apm, infrastructure, and most alerting. Makes for easier developer experience.
• Cost is expensive and is one of highest engineering spends

Incentivized

• It helped stabilize our system in the beginning
• We had to take it down later due to internal reasons and majorly because of cost-cutting process
• If someone has a unstable system and have no way to figure out what to do, can use sentry at least temporarily along with some other APM to fix their system faster

Incentivized