New Relic Reviews

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.

I'm working with a banking client. Apart from a uniform monitoring platform experience, they are looking for a solution that is scalable and also ready for cloud services monitoring and container-based workloads.

NewRelic provides a one-stop shop monitoring solution for organizations that are looking for 360 degree monitoring solution. Application, Infrastructure, Network, Database, Enduser monitoring, Mobile everything under one roof. Apart from that, as per Gartner Magic quadrant, NewRelic is among the top leaders.

The one thing that I like the most is the tight integration between different layers like APM, Infrastructure, Logging etc.. I don't have to go to a different UI to view different metrics. Secondly, health maps and service maps helps to evaluate the overall health of all the applications and any dependencies.

With Insights, I can create some powerful impactful dashboard that gives organization the business value they expect from the data collected from different data sources 

The solution needs some sort of improvement on the synthetic monitoring site.

The product has good documentation for Linux, however, their documentation for Windows is lacking substantially. It's something they need to develop and mature over time.

It would be great if it had out of the box integration with AWS, GCP, and other clouds. For example, if I'm using BigQuery in GCP, I want the data that I am executing in BigQuery to be reflected in New Relic. 

I'm working for a client where I'm proposing NewRelic solution to them. They have been looking for an intelligent monitoring solution that can provide a uniform monitoring platform experience to monitor application performance, infrastructure, end-user experience where NewRelic is the best fit.

The solution is quite stable. We don't have any issues there. There aren't bugs or glitches. It doesn't crash. It's reliable.

The solution is both scalable and fast. We have no complaints about it at all in that regard.

It's multitenant on the cloud which helps make it very easy to expand as needed.

I've found technical support to be pretty good. They accept the new feature ideas quite readily and their SLA is also very good.

I kind of have worked on different tools, but then no one has provided a unified solution. I've worked on ELK, Sumologic for centralize logging specifically. I've also worked with Splunk.

AppDynamics also provides these features, but I have not explored AppDynamics so much.

The solution is straightforward to set up. It's not a complex implementation. They are more compatible on Linux side of things, however. 

They need to provide more documentation for Windows. For example, I was trying the New Relic logs feature yesterday, and they have very good documentation for Linux, and can explain quite well how to do log forwarding on Linux. Then, for Windows, they do not have that specific documentation. I was stuck and I haven't worked on it today due to this lack of documentation. 

The pricing is reasonable. APM is a bit on the higher side, however, their service offering is quite good.

The solution is more mature than a lot of options on the market. If a company is looking for something that offers a unified scalable solution where they can monitor everything in one place, then NewRelic is definitely the option they should look out for.

I'd rate the solution eight out of ten.

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. 

We use New Relic to generate log management, like the different kinds of logs and alarms, and automate the same easily.

The versatility of the solution is its most valuable feature. It offers features like user behavior and user experience monitoring besides log management in one suite. When comparing it with other tools, other tools are primarily focused on only the management or only user behavior, but New Relic has both features.

The initial setup can be made easier. Like Mixpanel, New Relic can also have a step-by-step guide for the setup process. It needs slight improvements to be made in the user experience.

I have been using New Relic for two to three months.

It is a stable solution. I rate it eight out of ten.

It is a scalable solution. I rate it eight out of ten.

The initial setup was simple, but it can be made easier. I rate it seven out of ten. I did not deploy it a hundred percent because I was testing it out. The solution was deployed on the cloud.

I will recommend the solution, especially for a large product. So that one can have complete monitoring from the front-end tool and back-end server side.

I rate the overall product 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.

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 do have a couple of applications for one of our customers. We are involved in performance testing and engineering of those applications. We use New Relic in multiple areas. It's used to monitor infrastructure in this use case. We capture the metrics around the utilizations on the infrastructure. 

We do also identify bottlenecks of the services or the calls, which are causing high response times. 

Those are two key areas where we have been using New Relic. We have been able to identify calls that are causing a lot of performance issues in the overall application, and then that, in turn, helps us to see what can be tuned to bring the performance to a better state.

It's a build-down feature, so you have the option to drill down when a call is being received. It further drills down the method level and shows which particular method or hit is actually causing the performance issue.

It's a common feature for all APM tools. That is the key benefit of any APM tool - it helps you to understand and get to the bottom of the issue or the root cause at the earliest possible time.

The solution offers good documentation. 

It's pretty easy to set up.

Real-user monitoring would be helpful as it would help me to really understand the client-side performance of the application. Maybe for whatever reason, we have not got to explore a similar kind of feature in New Relic.

I've been working with the solution for a year.

The stability is good. There are no bugs or glitches. It doesn't crash or freeze. 

The solution is scalable. The deployment is not done by us; however, when we have to add new services or new components, it is pretty easy. The turnaround is also pretty quick.

Our team just accesses the client's New Relic tool. It's typically just used by performance testers and engineers. It also sometimes gets used by architects as well the development team. From our side, we have three people working on the solution. 

While my understanding is they do provide technical support, I've never needed to reach out to them. I can't speak to how helpful or responsive they would be. 

I'm more familiar with the likes of Dynatrace, AppDynamics, and New Relic.

We are just getting into a scenario where we might end up using AppDynamics. Otherwise, I haven't used anything before New Relic in a similar way.

From a documentation standpoint, it is pretty straightforward to set up New Relic assets. The infrastructure isn't that complex. To be honest, we haven't been involved in setting it up from an infrastructure setup standpoint. We have more consumers from which we use a setup that has been done to identify bottlenecks.

There's no specific maintenance that's been required unless they've changed endpoints which would need to be configured. It is something that's natural. When we do changes to the application and change endpoints, we'll have to configure the right endpoint. Otherwise, from a maintenance standpoint, given it's cloud and it's a storage medium, it doesn't need any major maintenance activity.

The customer tends to handle the deployment process.

I've done some research, more towards trying to understand various features. The customer, however, decides what tool to use. I don't really have the authority to compare anything and make suggestions. 

That said, when it comes to New Relic against AppDynamics against Dynatrace, or for that matter, Datadog, there are a few which have a higher price and provide richer UI. We did not really end up seeing a very major difference except in terms of monitoring.

We are likely working with the latest version of the solution.

The product has been pretty easy, and it is quite user-friendly in terms of trying to understand it. New Relic looks more at observability as a key factor. With it, you have front-end observability and back-end observability. My suggestion to others would be to go over them and also see if they can look at getting the documentation that's available to explore New Relic and then start with it that way so that it's easier for them to get started.

The other part is once they are used to New Relic, they can also look into a bootcamp that's run by New Relic, or a workshop. If they could attend it and then go into New Relic, that would be easier. They do have certifications as well which would also validate the knowledge that they gain on New Relic. 

I'd rate the solution eight out of ten.

The service map feature is very useful.

The simplicity of the dashboard is very good. It shows the throughput latency and all of the transactions.

It offers transactions, but it does not offer an endpoint-level insight at the URL level. When we get a request, we want to know what the life cycle of that service is, and where the cycle is. This is what I am trying to locate with most of the solutions now.

I am trying to research how to find a cycle per endpoint and not at the service level.

It is very difficult to award the service level cycles at an endpoint level. It is important for us to get new insights to create better hygiene around the business use cases.

At the endpoint level, the visibility is not that great, and metrics are not available. It gives you a full view of the entire function's execution and not from the context of the URL altogether.

Also the response time, the latency contribution, and the throughput contribution are areas that need improvement. You can get the throughput contribution from New Relic, but not the latency contributions. You cannot get it at all.

These are the major limitations. When working with AppDynamics, I did not find any limitations, but the same can not be said with New Relic.

The way that it classifies the actual services is a bit ambiguous. It's not perfect. For example, I see there are certain solutions that are listed as extra services, as a dependency, and still I find that among load contribution, it tries to show that those services separately, which is confusing.

With the transactions, when it tries to show a type of "bufferHandler" from inside, it doesn't show what the nature of the request is. Especially with Microservices, it doesn't show what kind of method is present, which makes finding data very difficult. Instead, you need to go to the raw data. I think that defeats the purpose of using this tool.

The transactions do not show the time consumed by the request, from the metrics execution perspective. It was suggested that I did not know how to read it but I have done all that I could. It is very difficult to relate to and requires a lot of experience and time to read through, which it should not.

It should not be difficult to find the latency and throughput for the entire system when requested. It should not be difficult to develop the data that relates to the various types of execution.

It should have complete exposure around the endpoints.

The services-to-service dependency is fine but most of the startups have only one or two services that are all cycled. It does not provide you with a lot of help when you are showing that the two services are dependent.

What all of the dependent endpoints are and how are the cycles being formed is information that should be available in most tools, but not with New Relic and some other tools.

I have been using New Relic APM for one year, but in-depth in the last two months.

We are not using the latest version but within the year.

Almost all of the developers are using this solution in our organization. We have approximately 60 users.

It is used on a day-to-day basis.

I have not used technical support.

Previously, almost four years ago, I used AppDynamics. I think that it is a very good tool. I would rate AppDymanmics an eight out of ten.

We changed to another solution because of the cost. All of the developers loved the AppDynamics dashboard. It was very clear.

I was not a part of the team for the setup but my impression is that the documentation could have been better. It didn't make much sense. 

For beginners using New Relic, the setup can be difficult and should be simplified. 

We have a DevOps team to maintain this solution, but it doesn't require a lot of maintenance.

I think the pricing is reasonable.

There is a good bare minimum of required features for this tool, but if they are out to the in-depth analysis then finding a cross-dimensional relationship is not straightforward. It is difficult to implement.

If you are concerned about how your services behave, then New Relic shouldn't be your first choice. However, if you are considering New Relic APM, is a very affordable choice.

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

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.

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.