New Relic Reviews

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.

Our use cases were varied. We had front-facing applications, message brokers, API gateways, legacy applications running on RPC, and platforms. We used New Relic for instrumentation, and we discovered different metrics using it.

New Relic is an APM tool, similar to Dynatrace or Datadog. It uses an agent to discover metrics based on browser, mobile, and custom matrices. We can also develop synthetic monitoring. It has helped us in exploring the metrics.

The best feature of New Relic is its simple look and feel, making it easier to use than other tools.

One thing New Relic needs to improve is the user data schema. It wanted us to move from version one to version two, but that was difficult because we wanted to do single sign-on, and it couldn't support our Ping Identity platform. That's something New Relic needs to work on.

Another issue I have with New Relic is its suite licenses. It has a two-tier system: the full-stack observability, which requires a suite license, and the free version, which doesn't offer any peer review capabilities. It needs to change because having a suite license for a user who can only view the post-stack, not even the curated view, is a big no-no. Dynatrace or SAP don't have this issue.

I should point out one more thing about New Relic. We use it with OpenShift, and one of the issues we faced was that New Relic required root access, which was a concern because no admin in the world would give any third-party vendor root access. However, they seem to have corrected this in the next version. 

I have been using New Relic for three years. We're using version 8.0.

It has its limitations, but it is a stable solution. 

It is a cloud-based solution, so the platforms automatically scale. 

We struggled with the support. 

We are currently using Dynatrace. We have moved away from New Relic because of its shortcomings – the user data schema. They had two versions, and we couldn't group different entities under version one. For example, our enterprise applications are numerous, including activation, OSS, BSS applications, and so forth.

It is an expensive solution. The licensing scheme is based on users having to have full stack observability, and there is no free version for non-seat license users to access what they want to see. I believe it's an expensive tool. They were not like that a couple of years back. Their new licensing scheme is based on full-stack capabilities; many clients would not like it. I would rate the licensing model a four out of ten. It is a very poor licensing scheme. 

It works well, and it has a very good look and feel to it. However, it also has its limitations. So some clients may like it. That's why they will be willing to pay more for New Relic compared to any other API. It's fine.

Overall, I would rate the solution an eight out of ten. 

If we receive errors or exceptions, or we need to check the load we use New Relic.

The most valuable features of New Relic are the reports and ease of use.

The price could improve.

I have been using New Relic for approximately one year.

I rate the stability of New Relic a nine out of ten.

We have approximately five managers using this solution.

I rate the scalability of New Relic a nine out of ten.

I have not used the support from the vendor.

We are mainly using Tomcat, but we use New Relic simultaneously. New Relic works as well Tomcat.

We have a team that does the deployment of the solution.

The price of New Relic could improve. It is expensive.

I rate the price of New Relic a six out of ten.

We have not evaluated other solutions.

One administrator can handle the maintenance on the weekends.

I would recommend this solution to others.

I rate New Relic a nine out of ten.

New Relic APM is an application monitoring tool.

There are many valuable features in New Relic APM. We developed some software applications and we are able to monitor the errors very easily. Their log security retention is very good.

New Relic APM could improve error debugging and the correlation with the logs. We are receiving some alerts or alarms but we need to correlate with the error log, but it is difficult if it is more than seven months retention period, it is hard to trace. We need this especially for getting historical information. 

Within short periods of monitoring, we do not have a problem it is only when it crosses the retention period that we are not able to correlate the errors with the log.

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

New Relic APM is stable. In the last two years, we have not faced any stability issues. If the vendor is having a maintenance issue they will notify us in advance.

I rate the stability of New Relic APM a six out of ten.

They are a costly solution and the stability should be better for the price.

The scalability of New Relic APM is good.

There are two types of users, one is the basic user which is free and has limitations. We have approximately 40 basic users. The second type of user is pro which does not have the limitations of the basic user. We have 10 pro users.

The support from New Relic APM is good. We create a ticket, and immediately after we have the support. 

I rate the support from New Relic APM a five out of five.

We were using another solution previously. New Relic APM was picked by the organization because they preferred it, and this is why we switched. New Relic APM is easier to configure.

The initial setup of New Relic APM is simple.

The price of New Relic APM could be less expensive. We are using the New Relic APM pro account and it is more costly. When compared to competitors the solution's pricing should be much more realistic.

I rate the price of New Relic APM a one out of five.

We evaluated other solutions, such as Dynatrace and Datadog. When comparing New Relic APM to other monitoring tools, it's not complex and is similar in features.

I rate New Relic APM a six 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.

We use New Relic for monitoring and alerts. 

We detect issues using dashboards that we built on New Relic. For example, if our drivers are taking too long to get rides, we usually detect the problem using New Relic dashboards.

The user experience with dashboards and the machine learning features are its most valuable features. The dashboards are useful for BI and fraud detection, if implemented the right way.

The APIs could be better. I would also like more APIs and features to integrate with streaming solutions, like Kinesis or Kafka.

The stability is good. Because it is calibrated for SaaS, it is transparent for us.

The scalability is good because it is SaaS.

The technical support is good.

The integration and configuration was good for our containers and LAN disks.

The detection piece of it brings us a big return on investment.

Splunk and Dynatrace are the alternatives in the market. New Relic is the solution that our company purchased.

I have used another product at my company called Dynatrace. Though, I think New Relic is better because its dashboard is more intuitive for users. I use Dynatrace at my company because we have a partnership with them.

New Relic is the best choice because the product has good dashboards, scalability, and environments.

The most valuable features to us are--

• Measuring performance from the applications point view against the view of the customer's browser,
• Being able to troubleshoot issues due to an app or network issue, and
• The error rate is helpful in finding issues in the server pool.

It helps us troubleshoot issues quicker, and when we're using it for performance analysis, several items can boil to the top. We can look at what's going on and what's slow and causing problems, instead of looking in general at which queries or operations are causing slowness.

I can't think of much to improve. We're very used to the way it looks and the traces. It's much better than it used to be, but perhaps the retention on some of the old problem traces would be an improvement. I think they run out after a relatively short amount of time and being able to look back and spot check some of them. If we have a problem today, it would be nice to look at back at the traces by, say, a week or a month even if there wasn't a problem then, so we can compare whether it's relatively slow or it suddenly become slow.

But I think the data layout is great as everything you need is at the top and we can able to drill down further and further to individual server,s or into the error rate and individual transactions.

The code is great. We don't have any issues, and I think that's the majority of New Relic customers. You have issues with your first customers, fix the issues, and then leave it alone until the next issue comes along.

Our track record is the same, we used it, troubleshot it, and then the developers fixed it.

I think we're finding more and more ways to use it. Because of plug-ins, we are pushing as much information in front of the app to the developers. I think too many companies end up with too many tools, but with New Relic, we want to keep in front of our developers all the time.

We've had to contact tech support several times, and each time they've been great. Their one-time survey call is good.

We've been using AppDynamics alongside New Relic. We had issues finding some problems, so we brought in AppDynamics and were able to dive further in, but after about six months, New Relic traces we're exactly as in-depth and usable. We were pretty confident with New Relic, and brought AppDynamics in to dive deeper, but their interface was Flash, which was slow and not nice.

Everything else about New Relic was nice. We could put different pieces of data in front of the developers, which is nice. They don't have as much information as we do in Ops from our other tools, but they get just the right amount of information to see where the bottlenecks are.

It was quick and simple. Always, whenever we look at a product, including ours, we've got in the back of our heads, what's the mean time to pretty graph? How quick is it to get data in front of you and that's usable? Within minutes we were able to get the information, and the first hour was great with New Relic.

When we're looking at new products, we look at whether the product works, how it works. Doing tests that are long enough is hard as no one wants to spend the time doing it, so I try to make sure that it won't take more than 14 days to set up correctly. If it's important enough, then the trials will be done.

It is one of the things that helps DevOps work in our organization and has helped stop finger pointing. It gives both sides enough info to help point us in the right direction of finding where an issue is. It gives us the insight into production to developers that operations doesn't want developers to have, and it allows them to use it all the time.

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.