New Relic Reviews

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.

Our company uses the solution for time series analysis. 

The solution is good for sending alerts, drawing graphs about system usage, and creating plug-ins. 

The solution should include more detailed reports for SQL database requests. 

I have been using the solution for three years. 

The solution is very stable and working fine. 

The solution is scalable and has been used for both small and big projects that scaled over time with no issues. 

Technical support is knowledgeable, responds quickly, and provides good assistance.

I rate support a ten out of ten. 

Positive

We migrated from AppNeta because the solution is more stable and cost effective. 

The setup is easy and plug-ins can be written for any differences required. 

I rate setup a ten out of ten. 

We implement the solution in-house for customers and offer both on-premises and cloud options. 

I prefer the on-premises option because I like to configure and set things up rather than using ready-to-go options. 

The solution does not require ongoing maintenance because it works fine and runs with no troubles. 

The solution is less expensive than AppNeta. 

There were some benefits to using AppNeta. It provided more detailed stats and graphs for hosting products. If you need more specific digitalization based on system stats, you might want to go with AppNeta. For our use cases, it was less stable and more expensive than the solution. 

The solution is an excellent product for time series and operation analyses. It is a good and stable solution, has a good price, includes good usability features, and includes good support. 

I rate the solution a ten out of ten. 

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.

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.

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.

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.