New Relic Reviews

We use New Relic APM to gather performance monitoring metrics such as thread count, CPU, response time, JVMs, and DB connectivity. New Relic APM is an observability tool.

To me, the most valuable feature of New Relic APM is the traceability, mainly based on the time travel method, so you get the overall response time, which is pretty helpful for developers and ADR techs looking into issues on a deeper level.

New Relic APM is a very good, tailor-made solution.

Documentation could be improved in New Relic APM, so users would have more clarity on configuring the dashboard. If New Relic gave better guidelines, users would find it easier to understand the metrics and features of New Relic APM.

Another area for improvement is integration with Kubernetes. Currently, the process isn't user-friendly. It's challenging and lacks documentation for users to understand how to integrate New Relic APM with Kubernetes quickly. With multiple levels of Kubernetes dockers and other DBs on different clouds, it's tricky to gather all into New Relic APM on a single dashboard.

What I'd like to see in the next version of New Relic APM is a single dashboard where you can easily view which applications fall under specific APMs. If there's a search feature where you can type in a keyword to find out if an APM is related to a particular application, that would be great.

I've been using New Relic APM for four years now.

New Relic APM is a stable solution, and I've never seen any outages from it.

New Relic APM is a scalable solution.

Support for New Relic APM is up to the mark, mainly because I belong to a big organization with dedicated email and Slack support. The support team gives clarifications about usability and configurations. I'm giving New Relic APM support a five on a scale of one to five.

My company also uses AppDynamics and Datadog for some of the applications, but those will be moved entirely to New Relic APM, as the tool is very user-friendly and has no lags. AppDynamics, on the other hand, has some delay, and you have to inject some methods in writing applications to gather the metrics. Performance-wise, New Relic APM is better and doesn't cause a high response time compared to other solutions.

Other teams handle the installation and configuration for New Relic APM.

I'm unaware of how much the license for New Relic APM costs.

My company is currently using New Relic APM.

Over a thousand people from different teams use New Relic APM within the company. My company currently has two hundred to three hundred applications, so even if New Relic APM is used occasionally, because of the number of applications it's being used on, usage of the tool could result in almost daily usage.

As New Relic APM is user-friendly, it's a tool I can recommend to others, but before making the purchase, you should utilize the free trial version, and also look at the sample dashboards provided by New Relic, which you can show to the customers to better explain how the dashboards look and what New Relic APM is used for.

My rating for New Relic APM is eight out of ten, as there's always space for improvement.

My company is a customer of New Relic APM.

We use New Relic APM to monitor our public cloud-hosted application and infrastructure.

Not so far. Although, we haven't really got a very mature system of defining our application processes from end-to-end and certainly not our client-centric impact.

I'm reasonably satisfied. We haven't run the rule over it too much because it hasn't been a massive investment.

It has been quite valuable to demonstrate how we can change our views for our services due to their service. It has proved value so far.

We don't have any problems with this solution.

The configuration isn't terrible when compared with other products.

It does everything we wanted it to do. We haven't been too critical in our thinking about where it can improve.

There really is nothing that stands out with New Relic. With the insight, I think it will be found lacking for its report aggregation capabilities. How granular I could go down at looking at certain data, especially related to the operations, is limited.

The API integrations that they have for us to automate our configuration was fine, but I think for some of these tools, it was over-engineering for us to try and automate any of that. So, we just use the user interfaces.

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

We are using the latest version.

It's a stable solution. We have not encountered any issues. We're not plugging too much traffic into it. We're not reporting on it heavily. It's not feeding into our service management processes heavily. So we haven't seen anything.

We have not yet explored the scalability, it's too early for us.

There are approximately 15 of us using it altogether. We are called infrastructure engineers, who are third line infrastructure support and architecture people. 

Some of the lead developers have access, but there are 15 of us and we are all pretty similar.

We have not contacted technical support.

We have two custom in-house processes that do our application data flow monitoring. We have manually and in a custom nature, built out a performance monitoring platform in Splunk using our knowledge of the system over the years.

I have used App Dynamics in the past with another company. There really is nothing that stands out with New Relic. It is similar to AppDynamics and Dynatrace.

The initial setup was straightforward. 

I don't think any of these tools are tools that anyone can pick up and install. 

I wouldn't say it was any more difficult to configure than some of the other solutions. It is definitely not more difficult to configure than AppDynamics. 

The price was one of the reasons we chose this solution. It's reasonably priced. It's cheaper than the likes of AppDynamics and Dynatrace, based on how our subscription is.

We looked at Datadog initially and found the initial setup to be far more complex than what we found in New Relic. 

Our proof of concept has been successful.

Getting an order in and reporting is an industry in itself, don't think it can solve the problems it's not trying to solve. It is an application performance monitoring tool. Don't try and make it anything else.

The big problem with Splunk for us is that it can do everything. The thing that's nice about New Relic is it doesn't try and do everything, it does what it does. So far, it does it to satisfaction, but don't try and fill multiple holes in your toolchain with it. It's good at what it does.

We had some pretty informed opinions on what it was going to do. We knew where it wanted us to get, and so far it has cost the amount we wanted it to cost and done everything that we wanted it to do.

I would rate New Relic APM a ten out of ten.

The primary use case is monitoring.

It gives insights to non-technical people about what technical issues are most important, how much it impacts customers, and potentially, where we should be targeting our development teams when they have time.

It has in-depth analysis using developer code for someone whose not traditionally a developer.

They could improve the education process and how people understand that these tools are very technical. I understand everything very quickly and where it all comes in because I grew up with the product, but right now if someone was to pick it up from day one, it is a very steep learning curve.

The monitoring is only as good as the alerts that it produces. By having it set up fine grain alerting, it is a bit of a pain. They already have all these other companies that use their system, so they should easily be able do alerts based on deviations that we don't need to program on a per instance or artifact basis.

It has been stable for all our work lines.

So far, I haven't hit any scaling issues with them, and the environments that I have come from have thousands of servers being monitored.

Their technical support has been pretty good.

It was quite hard to integrate, if you weren't technically skilled. 

A lot of people who consume this product may not be technically skilled, but if you are, it is easy to use. From this perspective, it is really good, but this is an important aspect as well.

This was recently implemented at the current place that I work. Previously, without a monitoring solution, a developer could potentially spend a day working on a feature or a bug to try and resolve and issue. Now, a lot of the times, with monitoring put in place, we can understand if a customer is actually hitting this bug, and how often they are hitting it, and how much frustration they are dealing with on a day-by-day basis, then reprioritize our tasks. It gives our developers that insight, or it gives less skilled engineers or less technical leads the ability to ramp up quickly on what that particular bug is, so we can easily scale out. So, the cost of solving that problem isn't just reliant on a tech lead understands the system or built the system. Anyone can find the issue, including associates, and the amount of time they spend debugging has been reduced by a lot.

They gave us aggressive discounts when they were brought in for the first time, but they have also kept them for the year-on-year renewals, which has been absolutely fine. Thus, we haven't looked to change.

The pricing and licensing are good if you have an account manager and a partner manager who are looking to help out. 

We also evaluated AppDynamics and Dynatrace. 

We chose New Relic because they have a slightly different pricing model. We were aggressively negotiating price, which means they gave us a pretty good price. Since then, they have continued upholding that same level of customer service, discounts, and partner level. So, it has been really nice working with them.

You definitely need this product if you want scale and stability.

It fulfills what it's designed to do. Their constant iteration of features means it will always keep us well-informed about that particular requirement about the software.

We are also using New Relic with PagerDuty and Slack. They integrate pretty seamlessly. A couple of button pushes, and it was done.

We are using the SaaS version.

We have our current parameters and our current dashboards. Our main purpose is to continue to migrate and get the same metrics in New Relic. We will prepare another secondary dashboard between the parameters. And we will do a lot of monitoring on it as it is mainly used for monitoring purposes.

The monitoring so far has been good and we are happy with it. 

I haven't come across any features that are lacking. 

I've only used the solution for two or three months. 

It's very stable. We have currently around 150 GB of data that we are going to analyze. Almost each and every day around 75 to 80 GB is analyzed. We haven't had issues with the volume or with bugs or glitches. 

The solution scales well. 

London mostly handles any troubleshooting. I don't have to worry about reaching out to technical support. we do have the documentation we can reference, however, if we do need assistance. 

I've used Stackdriver in the past. However, it doesn't work well, with, for example, virtual machines.

The initial setup was done by our London team. I wasn't involved in the process and don't have any real details about how it went. 

I'm not sure if any ongoing maintenance is needed.

While it's my understanding that our in-house London team handled the implementation, I can't say if they needed help or recruited consultants or integrators to assist in the process. 

While we do pay for the solution on a monthly basis, I can't speak to the exact cost of the product. There might also be some additional costs on top of the licensing, however, I can't say with certainty. 

I'd recommend companies try it out and see if they like it. 

I would rate the solution eight out of ten. We've been happy with it so far. 

We use it for application performance monitoring.

Its most valuable feature is application performance monitoring.

It gives me a complete x-ray of the application to understand where the bottlenecks are, then improve and fix issues.

We send through all our real-time transactions through it, and it is very stable. 

The scalability is very good. We have a large real-time environment for processing payments.

Their technical support is pretty good and responsive. We have a real good relationship with them.

The integration and configuration of New Relic was straightforward and easy.

It works well with the AWS platform that we are using. The integration with AWS was straightforward and easy.

We have seen ROI.

Comparatively, the pricing is expensive.

I zeroed in on New Relic. I was looking for a cloud native product at the time that I was looking for a solution, and two years ago, it was one of the leading products. It was quick to market, and we wanted to implement something quickly. It provided all the features which were required, and we didn't have to do our own installs within our data center.

Give it a shot. See if it meets your use case.

I have used the on-premise and AWS versions. The versions are very similar.

• Mostly monitoring
• Analytics
• Troubleshooting
• PagerDuty

• It visualizes metrics well and tracks our incoming requests, providing a lot of detail which is useful for troubleshooting. 
• It can track cross-application, knowing when you go from one application to another, like a request stop. 
• It's very visually appealing and useful.

It is a one stop shop and integrates with PagerDuty seamlessly. The solution is pretty self-contained.

We would like to receive more AWS-specific details from the New Relic Dashboard, like EC2 health.

I haven't seen any problems with it.

Scalability is good. We are using it at an enterprise level and have 20 companies in our corporation.

It has a good presence on the Internet, in terms of support and community. Answers are out there and easy enough to find.

The AWS integration was seamless for us. It was implementing stuff that other people have done so many times before, and the team which headed it up knew what they were doing. From my understanding, there was very minimal configuration. Maybe there was more on the New Relic side, but as far as feeding it, it was pretty easy.

We were also looking at CloudWatch and a homegrown performance-type solution.

We chose New Relic because it is all-inclusive. It has everything right there.

I just starting using it, but the product is pretty impressive.

We are hosting it through AWS.

The primary use case of the solution is to monitor, log, and investigate incidents.

The most valuable features are the dashboards and tracing.

It is complex to use and it can be improved by simplifying it by making it more user-friendly. I would like to see the option to group alert conditions added.

I have been using the solution for two years.

The solution is stable.

The solution is scalable.

The support team helped to resolve any issues I had.

The setup is moderate. 

I give the solution an eight out of ten.

I suggest anyone interested in using the solution should learn the query language first. It is a serious tool and requires a lot of time invested in order to understand how it works.

It monitors all of our services that are running. It also monitors our infrastructure. Therefore, we use it for monitoring, identifying when services go down, or when they are outside of what we would consider normal operations.

We have been able to proactively identify failures before they happen. As an example of something in the last week, we had an instance where a volume was filling up on one of our VMs, so we set up a basic alert that if it got to a certain point, it would send me an email. This way, my support team or I could take some action on it and execute a run look. This has prevented failures from occurring in our production environment.

The alerts that it provides is one of the most common things that we use. As an example, when a service isn't performing how we anticipated it, either I receive an email or my support team receives an email, then we can take action on it.

It is complicated, especially in how you interpret the data that it provides. For someone who works in it every day, I can figure out what I want. For the general, every day developer who uses it once a month, there is large learning curve to figure out exactly the information that they want from it. If it had a bit more canned, out-of-the-box features, especially some of the reporting features, that would be more useful.

Sometimes, it is difficult to work through and figure out. Some things are difficult to work through which is why I haven't done them yet, because it will take me six hours to figure out how to set them up, e.g., the dashboard. How I want it to look and how the developers might want to interpret that data, but I don't have six hours to go figure this out, and it takes a long time to do this stuff.

They have this alerting capability where I can set up an alert policy, then within that alert policy, I can set up as many alerts as I want. I can set up one or I can set up a 1000. I would like a feature where I can turn off alerting at a policy level. Thus, when a policy is inactive, I can shut down all of my alerts within the policy. Right now, I have to go through them manually and deactivate each one that I don't want to use.

I have never seen it be down or unavailable. So, the stability is good.

I've never had an issue with scalability. They have been able to scale and handle everything that we've sent them.

I have used their online support. I don't think I've ever had a phone call from anyone, but I've definitely exchanged some emails with their online support forums, which has worked out well.

We used to use AppDynamics, which is one of their big competitors. I don't exactly know why the switch. We were told to go to New Relic. I think a lot of it had to do with the cost. Possibly, they found New Relic to be a cheaper alternative to AppDynamics.

The configuration and installation were good. New Relic has some very good documentation. Everything in their API is some of the best that I have seen. It wasn't without issues because it's a piece of technology, and we had to figure out how to use it, but everything has worked well.

The issues were working through the documentation and figuring out exactly how to implement on some of the technology.

I did all the configuration, so there is a portion where we install an agent on our infrastructure and on our web services that run. I did all of that configuration. They gave me the account ID and the license to go with it, and I configured that in some of their config files, then I knew exactly where to send the logs to, etc.

Corporate handled the licensing and the purchasing of it, then they gave me a license key. However they configured it is how we use it.

If you are looking to evaluate New Relic, compared it to other products, it is very powerful in terms of what it can do. However, it is a complicated to interpret some of the data which is provided with it. There is a trade off if you want to implement this product versus implementing something that is simpler and out-of-the-box, but not obtaining as much depth in what you can learn.

It has some advanced plugins for EngineX, which is a web balancer that we use. So, we do integrate with these, which is a little bit outside of their normal realm. There is also an Apache one that we use. The integration is good. Once you figure out how to install it and read through the documentation, it works as anticipated.