New Relic Reviews

• On-demand profiling – This gives us the ability to execute a thread profiler on demand and get a very in depth view of call costs
• ApDex/Error monitoring – As a dev-ops solution, this is a great tool because we’re able to help predict issues before the end-user starts notifying us. We can set thresholds that are based on our metrics

We are now able to quickly identify how our product behaves in production. Before New Relic APM, we would push a build, and try to dig through a plethora of information (event logs, error messages, customer feedback, etc) to find problem spots. Instead, we now publish and can see all the key stats (apdex, response time, error rate, etc.) and quickly drill into what’s causing an issue.

More configurability through the dashboard, for example, being able to ignore transactions without the need to update the config or code.

I've been using it for two years and alongside Insights for one year.

No issues encountered.

No issues encountered.

No issues encountered.

Really high. While we’ve never had any major issue, the ticket I’ve opened have received responses within a couple hours with quality answers.

We didn’t use any other solutions prior to this.

It was straightforward. On each of our servers, we installed the agent, added our key to a config, and then within minute we were seeing metrics on our site.

In-house. Always start with your development or QA environment. While we had no issues, it’s best to take a dry run, and get a feel for how the app affects performance to see if the data is what you’re looking for.

I have no hard numbers detailing how much we get back for what we pay. However, as a dev-ops tool, it has been priceless. We are now able to pinpoint issues much quicker and can significantly reduce our downtime.

We did evaluate one additional tool but the install and integration was significantly more cumbersome. The core reason we chose New Relic was the ease of us and the quality of the metrics it gave us. Within hours of demoing the product, we were already learning more about our application than we expected.

Our primary use case for the solution is notification, customization, and everything from New Relic. Before adding a monitoring tool to New Relic APM, we need to add a subscription and specify the target we want to add, and this is a blank dashboard where we have to select, step by step, which modelling we want to understand. The solution is very similar to Azure monitor.

The new release is very valuable because it is well integrated.

We have been using the solution for approximately two years.

The solution is stable.

The scalability is good but can be improved.

The initial setup is straightforward. It is easy to track and easy to follow. It's somewhat like creating a graph where drag and drop features.

I rate the solution an eight out of ten. The solution is good, but the scalability can be improved.

We are using New Relic APM to monitor our production application and to get some insight into performance.

The most valuable feature is the ability to receive in-depth information about applications. It can detect a lot of important information.

The solution could improve by having more network monitoring features, such as for all the infrastructure.

I have been using New Relic APM for approximately six months.

The stability has been fine.

The solution is scalable. We had a lot of infrastructure at the beginning and it worked well.

The support could improve because they are not very fast and the information was not very accurate.

I would rate the technical support a three out of five.

The installation is straightforward, and it only took approximately one month.

Our office did the implementation of the solution.

The price of the solution could be less expensive. You have to pay a lot for each user. There is an additional cost for extra features.

My advice to others is this solution is working fine for me and it might most likely be for you too.

I rate New Relic APM a nine out of ten.

We used it more heavily before Synthetics came, but it’s kind of like Synthetics, but used domestically.

It allows us to perform threshold testing to see how quickly transactions are getting out to customers, providing us with data such as response time and adequacy.

Our software does significant data queries, so we throttle performance according to region just to keep the application up. Now we can open it up completely because of New Relic tools.

Ability to quickly identify different browser usage performance issues across our application functions. Again saves time in coding to enhance the end user experience.

It enables us to fine-tune our application quicker. It's also better if we find issues in our application than if our customers find it.

It also prevents performance issues because we're able to see potential issues before they cause real problems.

I can't recommend any improvements to Browser. I really can’t find anything that I don’t like about these apps.

Deployment was very simple.

We've encountered no issues with stability.

Scaling has not been a problem.

I've not had to use technical support.

We had no problems setting it up.

The way some transactions are recorded, you can dig through and see what’s going on with the request, how many times you’re making a certain call. That’s the biggest part – almost like application profiling.

We get greater insight into what our application is doing once it’s in production. We can identify issues faster, and being able to identify issues before they become a big problems is an improvement. We use it in load testing to identify inefficient query patterns.

At times some of the data can be opaque. Some of the aggregates over time tend to become more vague, so you lose resolution. Greater resolution going further back in time would be nice. If I start going back a month or two, the resolution is a lot lower, which is kind of challenging and makes it harder to do in-depth historical analysis.

Alongside APM, we're using New Relic servers, plugins, and pretty much everything else except Insights, Synthetics, or the mobile product.

Pretty stable. Sometimes the charts will fail to load or there are some random errors. But because of the way we use APM, there’s no significant impact.

Our use doesn’t really push the limits of New Relic, but it looks like it will scale just fine.

It was already in production when I joined the company.

I don’t see us being able to operate without New Relic. It’s important to collect a lot of metrics, but it’s more important to identify the ones that are essential to your business purposes. Know which data are really important and what you should keep an eye on.

Just to show the response time of the app, and how much time each request spends in the tiers. Database is a tenth of a second, web takes two-tenths, and Ruby takes one-tenth.

I can tell you that there are two use cases. One is to look at how we are performing on average over time. So, assuming the systems are healthy and we look at the last month, the average response time is very good at telling us that. Let's say I add capacity, I can see it trend downwards. The other use case is pinpoint key problems happening right now. Uber called and they are saying that their Freshdesk isn’t working. We look in and can see clearly that only the database is taking 27 times longer than it should, and it helps us solve acute broken things.

It helps with current broken things and help us understand what is happening on our system overall.

It just gives us an idea for how fast were running. That cuts down to it -- how fast we're running, and if there is slowness, where it's coming from. It's really fast at telling us.

I would say that the user interface is maybe a little bit overly complicated. But I don’t have any specific way to improve it. I would say that what’s not commonly used, that are rarely used, should be less conspicuous and buried behind. Like your iPhone has one or two buttons -- if you need settings you can dig down to that stuff, but you don’t want that in your face when you take a call. Similarly, when you are in New Relic there are all these things that I need to sift through mentally. I just want to see how fast the apps are responding. You can’t change that.

I want to see the potential for Docker statistics or container statistics. Like if we start running containers, will it be able to track data for a given container. If one container serves one purpose, we need to track how many requests per day, when does the usage peek, how much does it vary week to week. And then that needs to be organized per container.

Finally, there's lot of noise on the front page that I don’t want to see. If it is customizable then it isn't obvious. Another nuance is that it always shows the wrong throughput for the most recent five minutes, and it's always wrong. The system is wrong for the most recent five minutes. They show wrong data and that changes after the five minutes is up.

We've had it for more than two years.

10/10 - it's very stable. It went down, maybe, once.

Super scalable. For us it scales for what we need. Scale means does it work as well if you have three nodes or 500, and it does. It doesn't break when you scale it up.

I don’t know. Never had a problem. Never had an issue with it. Really simple, like your microwave. Does it well so I never needed support.

This has always been our solution since we started.

We looked for a product that gives the data in a way that is easy to visualize, is reliable, and is simple.

• Custom instrumentation/events. We use this tool are additional analytics and debugging.
• With limited code, we can create and report on custom metrics or events in real-time. This allows us to quickly identify success rates of our efforts.

Joining datasets. Currently, it’s only possible to pull data from a single event type. It would be nice to do more of a SQL-like join, for example, CheckOut events with ItemsAddedToCartEvent.

I've been using it for one year, and alongside their APM, which I've been using for two years.

No issues encountered.

No issues encountered.

No issues encountered.

Really high. While we’ve never had any major issue, the ticket I’ve opened have received responses within a couple hours with quality answers.

We didn’t use any other solutions prior to this.

It was straightforward. On each of our servers, we installed the agent, added our key to a config, and then within minutes we were seeing metrics on our site.

In-house. Always start with your development or QA environment. While we had no issues, it’s best to take a dry run, and get a feel for how the app affects performance to see if the data is what you’re looking for.

I have no hard numbers detailing how much we get back for what we pay. However, as a dev-ops tool, it has been priceless. We are now able to pinpoint issues much quicker and can significantly reduce our downtime.

We did evaluate one additional tool but the install and integration was significantly more cumbersome.

The core reason we chose New Relic was the ease of us and the quality of the metrics it gave us. Within hours of demo-ing the product, we were already learning more about our application than we expected.

New Relic APM can improve the information when we dig deeper to check a problem. There should be more detailed information provided.

I have been using New Relic APM for approximately six years.

The stability of New Relic APM is very good.

The scalability of New Relic APM is good. We have not had any issue with scalability when we use different types of loads, it worked very well.

The technical support from New Relic APM is very good.

The ROI from using New Relic APM is good.

I rate New Relic APM an eight out of ten.