New Relic Reviews

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.

I used New Relic Insights to create dashboards, to receive some metrics regarding performance, and alerts regarding any kind of issues with the performance. Additionally, we used it for SQL and Oracle to receive metrics related to performance, such as CPU and memory.

Depending on the type of dashboards we wait for some time and then we build alerts in New Relic Insights for the metrics to prevent issues.

There are times when you restart the engines and the servers have a unique ID for the host and you need to remove the server. It is difficult because some are on-premise and others are production hosts. Having downtime is not very good when updating. However, it is not a constant issue.

I have used New Relic Insights within the last 12 months.

We have some performance issues with the servers. Sometimes the server is consuming a lot of CPU or memory, and New Relic Insights fails. They don't receive any information from the server or to the dashboard.

The solution is scalable, and it is easy because all the documentation is available.

There were approximately 11 people using this solution in my organization.

I have not contacted support. There is a lot of documentation available and you can search it globally. You can find a lot of the content on various topics regarding your issue.

The installation was simple. We don't need to use a user interface to install it. We can use two or three commands in the PowerShell or three or two commands in the batch. One device can take 10 minutes, and 100 devices can take one hour depending on many factors.

The script takes the information for the device from the system information but if you are using an interface, such as a wizard, you need to modify files and put all the information regarding the devices and environment, such as the license and hostname. All the information should be put in there. It is very easy.

To set up the metrics, you need to build the dashboard and after that, when you add a new device, it's automatically added.

To receive all the metrics for each system regarding its application, the user in the interface for all the dashboards can type the hostname and can see all the tools in that host, it is a very powerful view. You can modify some of the parameters to fit your needs.

One person can do the implementation. However, depending on how many devices you have it could require a little more work. There are third-party scripts that are available to install New Relic Insights across all devices.

In AWS or Azure, we have a root command that can select multiple devices making the process easier.

There was zero maintenance needed for New Relic Insights, it automatically updates.

My advice to those wanting to implement this solution is for them to create a test environment and try different operating systems, such as Windows and Linux. Test different applications in both environments to see what fits the use case best.

I rate New Relic Insights an eight out of ten.

It helps us keep our customers happy, that’s the bottom line. When it responds the way they expect, they’re happy.

It shows us where the bottlenecks are in our code. It was great to reveal where our code was insufficient or needs to be refactored. The most important thing is that it tells us where the latency in throughput and response time are.

What we have we’re happy with, but we’re still evaluating.

Very stable. Never had any issues.

Very extensible. Support and QA can look at the parts they care about and that allows for feedback and communication across the teams. It’s been great for our support team.

Never had to contact them.

We knew that we were going to move into SaaS, and these are the kinds of tools we’re going to need to get there.

Very straightforward. In this day and age, that’s what you expect from a service like that. Being able to set my alerts and the thresholds for those alerts is very intuitive.

We look at what it produces – I don’t look at cost. We look at what you can get from the product. If it’s the right tool, it doesn’t matter what it costs because you’re going to get it back many-fold from your productivity.

New Relic was it. We looked at other things we could put together ourselves, but they weren’t the full package. Something like this is all-inclusive; it’s a one-step.

We look for their reputation, how many people are using the solution. When your peers talk about it, you know that’s something you should consider. Knowing also who their customers are and how long they’ve been around is important.

The ease of use, the information you can get out of it from the very little things you do – you get so much out of it. It’s very intuitive. You don’t have to read a manual – you just use it.

We've been able to automate a lot of our interactions with it. Also, it has the ability to monitor random URLs not tied to the one pinger per application (though it costs extra).

I think that there have been some questionable product enhancements. Over a year ago, New Relic rolled out a new navigation that really disrupted our workflow. It added many more clicks and was surprisingly frustrating. Luckily, that was mostly reverted, but more recently, around six months ago, they redesigned the error reporting page. This is another example of a tool that worked fine, but which is now very hard to use.

About six months to a year ago, we invested a lot of time automating a lot of our interactions with New Relic. However, their API couldn't do a lot of things, and even getting a list of errors was impossible without scrubbing every application/server manually and checking health conditions yourself. This seems very basic. While they have made a new API version, we've had difficulty with that as well. 

Additionally, I'm told that they will deprecate completely the old API, which now means I need to reimplement everything that was working in this new version.

It's been a stable product. We haven't had any issues with instability.

It's scaled for our needs. We haven't had any issues with scalability.

Cost is significant with a lot of extras. For instance, another big negative point is the inability to monitor random URLs not tied to the one pinger per application. They've added it which is great, but now it costs extra for using it in any real capacity.

The most valuable feature is the transparency into how applications are running. That’s huge because we previously didn’t have it and we had no idea what was going on. Now, we can see exactly what’s going on and are able to understand what code paths are running. That stuff is hugely beneficial to us.

The biggest thing is being able to give our customers a world-class experience. As we’re in media, this means things like hockey results, election results, favorite TV shows, etc. We’re able to cover all our bases to make sure our customers get what they love.

When I look at APM now, it’s very web-centric, but we have certain infrastructure components that are very service-based which take data from one area to another. With APM, it’s a little difficult to fit into that. So, what I’d like to see is the ability for the dashboard to be customized where it can display collection jobs and how they break out one by one.

It also needs some web UI tweaks. It’ll be interesting to see where it evolves with the “analytics everywhere” theme and incorporation of all the other items.

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.

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

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

It’s easy to use, has a low barrier of entry, you can craft custom instrumentations, and craft your own metrics to get your own details out of it.

• 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.