New Relic Reviews

We were using New Relic to build performance, application monitoring, security aspects, infrastructure, exporting from databases, lower-performance tips, and trying to identify deadlocks.

Yes. However we dropped due to not able to achieve RoI due to high cost

The most valuable feature is application monitoring.

The main reason we switched away from New Relic is that the cost is too high. They should bring the pricing down to be more competitive.

I would like to see the capacity planning improved.

The security standard and compliance are areas that should be improved.

We had been using New Relic APM for a few years and have now switched to DataDog.

There is no question about this product's stability. It is very good and I would continue to use it, but the price has caused the organization to move on to the DataDog solution.

New Relic is a scalable solution. I have between 10 and 15 large customers who use it.

I have never been in contact with technical support. I am comfortable with using the product.

We have switched away from New Relic and have begun to use DataDog.

This is a cloud-based solution that doesn't need to be installed.

This is an expensive tool.

This is one of the best tools that I have used. I have recommended it to customers in the past and would continue to do so. In summary, this is a very good product and the only real problem is that the cost is on the higher side.

I would rate this solution an eight out of ten.

We primarily use the solution to optimize web pages and to track user behavior.

The solution's most valuable aspects are that it tracks java better and operates very efficiently.

The solution does not provide input on how the page performs in a big group. It just says that the page performance is bad, but it does not say what can be done to improve it. If they could provide some insight or guidance on how to make improvements, that would be a big help.

The solution could adjust the pricing to make the costs more reasonable.

I've been using the solution for three months.

The solution is quite stable.

The solution is scalable. We have about 15 people using it currently. They're mostly developers and managers and we all use the product daily.

The solution offers 24/7 support and they are quite efficient.

We didn't previously use a different solution.

The initial setup is very straightforward. Deployment took about a week. It doesn't require more than three people to deploy and maintain the solution.

We had a vendor partner assist us with the implementation.

The solution is quite expensive. It costs around $5,000 a month. There aren't any additional costs above that.

There were other options that were considered, but I was not a part of the decision making process.

The solution is a cloud-based software.

I'd rate the solution six out of ten.

I use the product for monitoring many types of metrics, e.g., availability and comparing numbers in relation to products. I evaluate the response time of servers and the product to determine the health of the servers.

Sometimes, I monitor the user's time of response and use this information to improve the number of servers on the back-end. Or, I can use it to change my back log for front-end developers and improve their response times. It's very important in this case because I can improve the experience of the final user.

Time of response for back-end and front-end (user) requests.

There is a picture which goes to your browser and it monitors requests from other users. However, it's impossible to use now because the price is very high. The feature is very nice, but I tried it during the trial period, and the current price makes it impossible to use.

The infrastructure of New Relic is very stable, and it works well.

We are using AWS Cloud, and I integrated New Relic with our software, was very simple. It is easy to use the New Relic product, and it is not a hard connection between AWS Cloud and it.

The return of investment is very good.

New Relic browsers are very expensive.

I recommend using the free version of New Relic. If you like the free version and understand its importance for your company, you can move to the trial. Then, you can migrate to the paid version.

I have tried other competitors of New Relic, but the other competitors which I tried were not good. On the other hand, the competitors are cheaper than New Relic.

We chose New Relic because it has all the attributes which we are using to monitor the health of servers.

I use other type of software for database, e.g., MongoDB and GraphQL. It is easy to integrate New Relic with these third-party softwares. I don't spend more than one or two days for integration, as it's very fast. It can monitor our codes and third-party codes in these softwares.

The website is much more responsive because we are able to quickly pinpoint the worst pages – we can be really targeted with where we put our resources. In a lot of areas, one page takes one minute, the next can be ten, then some take one, some take 30 seconds. You have to decide at what point you want to focus, this allows us to find the pages that are really painful for users, and fix those and make them a lot better.

It’s absolutely the ability to get a really specific read of what is taking up time. For example, if a webpage takes two minutes to load it tells you why it’s taking so long.

They instrument up from the bottom to the top – every piece of code - they have a very perfect read of what’s being done, and how long it’s taking. And, a super nice way of presenting that.

It gives you amazing statistics, but doesn’t give you enough information about what to do with the statistics. The sales people need to be on board on this end.

There were no issues.

From a point of view of showing you what to do fine but in terms of showing you what to do with the data infuriatingly unhelpful. Very friendly and available however.

There was no solution in place previously.

We implemented in-house.

It was able to really effectively find the problem and solve it – it sped up the pages considerably.

The monthly cost os $1000 per server per month, but it could be even more. We pay about $250 for the server, and then New Relic wants over $1000 to give us statistics on those servers.

The alternative is to do UNIX profiling. Basically, you do it piecemeal, and amongst those piecemeal solutions is also browser profiling, and it’s really hard to justify. We thought about it, as if you’re a relatively small company New Relic is expensive, but it's way better than that. The price point is an issue so we turn it on and off when we need it. Not a great solution for a start-up.

Application monitoring. The fact that we can trace a request through all the layers of the application (gateway-app server-database (persistent and caching layers)) and trace all the steps in between, is invaluable to us!

We can monitor our performance easily using the metrics, Apex, that New Relic have devised. This is a weighted number (0 to 1) which gives us a clear unobtrusive insight into our performance. Therefore, by leveraging the API, we can integrate the current performance metrics of our entire stack into our wall-boards and internal reporting.

With the recent introduction of Docker integration we're seeing increased metric collection, but are also missing a few minor metrics and deployment setups.

We've been using it for over five years now.

In a regular and normal usage, deploying the agent (either PHP, NodeJS or the server agent) is very simple and intuitive. We do however run into issues integrating the PHP agent into the Dokku deployments, but we have been working with the Dokku/Heroku/New Relic support staff to fix this.

It is fairly stable. There have been issues in the past where stability was not fully reliable, but all problems were quickly resolved and we personally haven't had any data loss issues of any kind.

We haven't seen any issue that affect us personally.

It's a big 10/10. The engagement of the customer service either via tickets or the public forum is excellent.

After building our initial integration with our framework several years ago the technical support engineer provided us with great insight and it really was a two way street of communication: we provided ideas that were implemented and they also gave us insight into optimal integration points.

We've tried various other tools over the years, but after giving New Relic a try, we haven't looked back.

The initial set-up was at the time the most straightforward and easy as imaginable. This really pushed us over the edge of giving it a go and loving it from day one.

We did it ourselves, and it's easy.

Since it's an application monitoring platform the actual ROI is a lot harder to calculate than other services directly related to the business. We do however see an increased focus on performance and therefore have a good ROI. It's also due to the fact that there are ways to keep the costs of New Relic down and still have the benefits.

Just try it out and install it on a couple of systems. You could go "all in" and have the full license and instalment on everything, but certainly during start-up, you could leverage a couple of instalments and still have insights, if it's installed into core parts of your set-up

Can't remember which platforms were out there. Soon after we started with New Relic, AppDynamics went live, and much later Server Density added APM. They both seem like worth competitors, but as previously mentioned: we have no reason to switch yet.

Just give it a go and see how it goes.

At the moment, I think the aspect of their product is the most useful to us: server monitoring. We actually display the status of our servers continually in our dashboard (using https://Screensaver.Ninja) because that's a critical aspect of our operation. This is only true because our most used product is not gaining new features as we are re-writing it from scratch, but while we were developing new features, their performance report on which controllers are taking the longest and which parts of the application are consuming the most resources is incredibly useful.

Very simple, using server monitoring. I saw over a period of time our disk usage increase until some servers went into yellow alert (above 70%). Then we started working on this issue without a rush because we knew we had time, and instead of increasing the size of our servers and thus having extra cost, we managed to find how to reduce our storage footprint to fit within our current servers. Constantly seeing the green status of all my servers makes me sleep well at night.

I think their dev packages for server monitoring could handle configuration a bit better. We install upgrades and patches every day and their packages seems to require manual intervention due to the configuration file more often than other packages. Since we use Puppet, it's trivial for us to deal with it, but sometimes we do have to look at the configuration file to figure out whether something really changed or not. To be fair, this hasn't happened in a while, so maybe they improved it already.

I've used it for five years over multiple projects in multiple companies.

No issues encountered.

No issues encountered.

No issues encountered.

I don't think I ever needed it, no.

I don't think I ever needed it, no.

I don't think New Relic has a lot of competition. We also use Linode to monitor our servers (but not our app).

I think this is one of the aspects in which New Relic shines. They designed the product to be easy to install and integrate, it's part of their guiding philosophy and probably what made me try it in the first place.

I implemented it myself.

We are happy with the free version, so I never properly evaluated this.

New Relic is not cheap, but I have a few colleagues that need the paid accounts, and although it hurts, generally not having New Relic hurts more.

Not really.

Just go ahead and try it.

I think the downtime alerts as well as the insight into performance killers from database queries are the most valuable feature for us.

I think that we didn’t have much insight into which things were causing the biggest performance hits, so it gave us instant feedback on incidents which may have caused users enough pain.

They have integrated alert and performance monitoring which they’re rolling out as a beta now. A lot of the features for application monitoring and uptime, and alerts for alerting the appropriate people when something goes wrong are not quite there yet.

We’ve never had any problems whatsoever.

It’s been useful as we’ve grown our user base; we haven’t had any scalability issues. We’ve done tens of thousands rather than tens of millions of transactions.

I’ve only used it a couple of times. They escalated the issues appropriately and it always seemed like someone who understood the issue jumped on the ticket, and we’ve had the issued resolved in a timely fashion.

We were previously using nothing else. We were reading through logs trying to interpret our own data, which was challenging. Someone suggested New Relic and we went with it right after; they’re the only player in town for this sort of environment.

The initial ground level setup was very easy, very intuitive, and went very quickly. Some of the more advanced features did require a lot of review of their documentation and a few support tickets to figure out.

I think documentation is probably key for us, and then support. Reputation and long-term relationship doesn’t matter so much if they have a good product. For this product we didn’t really have a viable alternative. We couldn’t find anybody else who did something similar.

We’re very satisfied with it. We had a little difficulty plugging in some more of the advanced features. It’s so big and so complex, but New Relic does invest in education.

This is the best tool for gaining insight into SaaS or cloud-based applications that we’ve seen. Unless you’re going to roll your own solution, you pretty much have to use them.

I’ve gotten our teams to use New Relic to help them craft code that properly performs right out of the gate. It complements our user-acceptance testing where we can put in performance testing right away.

We also have better transparency, we can see bottleneck in resources (need more memory, CPU, etc.), we can catch problems such as full disks before they crash our server. We never had that type of insight before. It makes our Ops teams’ lives easy because they just get emails as to potential issues.

It gives us the ability to determine when and what we need to scale, instead of just chucking machines at layers and hoping it’s right. It all goes towards giving our customers the best experience possible.

When you look at disk monitoring, it would be cool to see which folders are gobbling most space, so that when we get a full-disk alert, we can go into our servers to purge that without downloading a separate tool to see what’s contending for hard disk space.

Also, it's really well put together, but it would be nice to have more granularity for metrics displayed so that ops team can see more holistically what’s happening.

There are no stability problems. There have been slow points where data loads slowly, but it can be solved just by clicking refresh. No problems with agents crashing or not reporting data. So no reason for me to worry about its stability.

I never have to worry about not collecting data, but probably the web portion might need a little bit of work.

It’s scaled to all our needs. We have apps for on-site and in-cloud, and it’s worked well for both. There’s no problem with scalability.

We haven’t had to reach out yet, and hopefully things keep going smoothly.

I was involved for another account, but it was very straightforward, couldn’t possibly be simpler. So easy.

We looked at the ease of installation, how easy it is to get it put and running to see what’s happening on your machine.