New Relic Reviews

I would use New Relic on every new Rails application I build. I can see how useful it is and I've been doing that for years now. When you have multiple applications and want to understand what is going all between all of them, New Relic is also a great choice. You can "tag" the request and New Relic will create a map for you.

New Relic is appropriate for large enterprise organizations with large teams and in house data centers. For smaller businesses, or where cloud computing is heavily used, or where you have a specific language that is your sole focus, I believe there are more modern tools that will give better insights into specific platforms. New Relic, in my opinion, is the HP Openview of app performance. It covers a broad spectrum, but depth is lacking.

New Relic is a perfect choice if your use case allows for sending metrics from your servers or consumer end-devices. It will enable you to monitor your databases, queues, virtual machines or virtually any other infrastructure components. It will not work well if your customers restrict their data from being transferred to the cloud service providers.

New Relic gets you 80% of the way there when it comes to application monitoring and performance tooling. It is easy to set up with a simple gem install, and gives you actionable information right out of the box. For application platforms where their integration is robust and widely used (like Rails), this is especially true.

Well suited for monitoring our Acquia website. We have not tried it on any other internet-facing service.

Probably overkill for any internal sites or servers as it monitors too many parameters and may be cumbersome to manage. The management interface is too cluttered and cannot be customized to only monitor deployed agents. Maybe I do not know how to do that.

If you have full-fledged web application such as a website then New Relic is very good. But for small companies the price might be high. If you have backend servers which are connected to the Android and IOS apps then New Relic might not be good, there are some other alternatives such as Mixpanels.

For detailed performance monitoring, as well as quick setup of services, New Relic does an amazing job. It also does a great job of easily "guiding" you into problematic database calls. If you're looking for specific event tracking, such as how many times a page is viewed, or how many times a user clicks a certain button, New Relic is less suited for that even though there are ways of implementing it.

If you're concerned about the performance of your application, or you'd like a powerful tool to assist with debugging certain issues and analyzing your function calls, this is one of the best tools available anywhere. If you just need general application monitoring or uptime monitoring, this is overkill.

New Relic is great for profiling most web applications and determining what is wrong with them and if they are performing well. It is less appropriate for desktop applications, technically you could integrate with New Relic but there are most likely better options out there for that use case. New Relic also has support for profiling mobile apps but it is not as comprehensive as their web support.

Step transactions and Web URL sequence monitoring is more difficult than it could be. Having a recorder process would take this tool to the next level. That said, the console is so easy to use that there is hardly any training required to access data you need to find or view.

When you need automated alerts and good traffic data, New Relic is a great tool. You definitely get what you pay for, and while New Relic is priced competitively, it gives a lot more than the free or cheaper solutions.

If some issue happens with an application I go directly to New Relic's dashboard where I can see immediately what happened and therefore quickly fix the problem. You can see how different layers of your application perform there and immediately identify in some cases where the problem arises from.

New Relic is very well suited to identify performance bottlenecks and identify areas where there's room for improvement in your application. It narrows down the time and resource consumption to a method-level which makes it much simpler for developers to implement performance enhancements and apply fixes more practically than out in the wild.

Well suited for bootstrapping an APM program.

I think the biggest factor here is price. If you can get by with something cheaper, then great. Other people do basic up/down monitoring, and New Relic's biggest strength seems to be APM. But if downtime is money lost, reputation, etc, then you really need to consider two factors. One, of course, is the application's status, but it's also quite valuable to have historical data and the right tools to identify the issue and get the application healthy again. A cheaper tool might tell you the health of the application, but if it doesn't help you quickly fix any problems, it's only half of what you need. New Relic is worth the extra cost for us, as it gives us much more data to work with so we can address issues quickly.

Do you need to monitor OS-based workloads? Do you have a mix of on-prem and Cloud instances? Do you need to have a converged view to see your OS, application, real-user monitoring (REUM), Synthetics, and other time-series data? New Relic is the platform that can deliver on those requirements.

Their technical support one of the best engagements we have had with a vendor. Exemplary in every way!

New Relic is a great choice for monitoring the performance of your back-end. New Relic integrates with PagerDuty and supports many common web frameworks out-of-the-box. Error traces and transaction monitoring are valuable tools for detecting problems and prioritizing improvements. The thread profiler has helped us to understand some defects that were tricky to reproduce. The service maps it generates are useful.

Great dashboarding capabilities. Can build out reports of any level of complexity.

After my experience, I found New Relic well suited if you have a critical online service or product and also a dedicated team to mantain and improve it over time. New Relic gives you a lot of interesting data to help you make technical and customer related decisions. One of our services is a web application where users can buy services between them, and it's critical for us to keep all services up and running without errors.

New Relic Insights is well suited for smaller web development teams who do not have the resources to hire a dedicated web server manager. It is also great for teams who deploy code often and need a debugging and monitoring tool. New Relic can save valuable troubleshooting time and frustration by providing excellent insights at all times.

New Relic works great if you are doing any sort of custom development and run a production web app. I’m not sure however how good the Docker support is because I haven’t used New Relic for that. I have also found that if you use almost exclusively SaaS providers and don’t do custom development there may be more economical options.

If you have a product which is used by at least 1 customer or you plan to sell more you have to improve. That's why you are going to fix and improve each day. But where to start or in which order / priority? This means you need an APM tool for it. That tool is one of the best and probably what it is cut out for!

New Relic is well suited to monitor production and non production applications. I use New Relic frequently and it's well suited to analyze issues. It provides so many details that issues are easy to identify and it saves a lot of time. I used to struggle to go through logs before using New Relic. Insights, APM, alerts, ping etc., are great features.

New Relic is relevant to all web properties. They have a robust, flexible platform.

Well suited for:

• Application performance monitoring
• Database performance monitoring
• Alerts and Custom Alerts
• Thread level data and graphs for drilling down on request/response to view averages, metrics over time etc.
• SQL query analysis
• Error monitoring and alerting