New Relic Reviews

Since I'm a performance engineer, I typically use New Relic day-to-day for investigating any performance bottlenecks identified during our performance testing of any application. I look at the results, identify the root cause behind performance issues, and create dashboards to monitor the observability perspective of the tool for production as well as the QA environment.

New Relic helps me every day because whenever we face any issue, the very first thing we do is check the dashboard we have created. We browse through the dashboard to look into different aspects including CPU, memory, logs, and different transactions. Once we identify what might be the reason, we either directly go into those metrics in detail to look for the root cause or look into transactions to identify if a performance bottleneck exists, then at what layer or step it has occurred and what is causing that performance issue. Once we identify that, it is very easy to look into the code for that particular method or area to pinpoint the root cause, inform the developers about the issue, and identify possible solutions for it.

I have been using New Relic extensively for performance engineering troubleshooting and root cause analysis for our large-scale SaaS environment, which has become one of the primary tools we heavily rely on during our performance testing and production issues investigations. I appreciate New Relic's ability to provide end-to-end visibility across the entire application stack, and its APM capabilities are particularly useful for our day-to-day tasks by identifying slow transactions, bottleneck methods, external service dependencies, database performance issues, and error hotspots. We frequently use transaction traces, distributed tracing, thread profiling, database analysis, and external call breakdowns to pinpoint where the response time is being spent. With our Kubernetes workloads moving to containerized environments, the Kubernetes monitoring capabilities that New Relic provides are valuable as they allow us to correlate application performance with pod-level metrics, resource utilization, deployments, and infrastructure behavior, helping reduce the time required to identify performance bottlenecks. The integration we have seen between APM, Kubernetes monitoring, logs, and distributed tracing provides a much more complete picture than using disconnected tools. The NRQL feature allows us and our team tremendous flexibility to build custom dashboards, perform deep analysis, and answer specific questions that may not be available through standard views. The dashboarding capabilities we rely on are powerful, allowing both engineers and leadership to view performance trends and operational metrics meaningfully. Leadership is not technical, so being able to create that dashboard helps, and for engineers, alerts can be automatically triggered without needing developers or QA engineers to investigate further. If there's nothing wrong, they are happy that all is well, and if there is an issue, alerts are triggered, prompting them to go to New Relic to identify the cause and analyze the issue.

The best feature of New Relic is the effectiveness of the observability platform. The combination of APM, distributed tracing, Kubernetes monitoring, logs, database visibility, profiling, and analytics capability significantly reduces our troubleshooting time, and those are the features I appreciate about New Relic.

I think we utilize all of the features available due to our architecture, where we must go through everything. There is a sequence in how we go through these features: first, we look at the dashboard for a holistic overview, then check the transactions to identify degraded ones, move to traces to find the cause of slowness, and might have to go into logs, database queries, external calls, or distributed tracing.

While I appreciate many aspects of New Relic, I believe the product could improve in some areas—specifically, some advanced capabilities can have a learning curve for new users, and the licensing and consumption model can be difficult to predict, particularly in environments generating large volumes of telemetry data. Organizations may need to invest time in proper instrumentation and dashboard design, as we did, to reach the current stage we are now.

The licensing and consumption model can be unpredictable due to dependency on telemetry data, making it challenging for environments generating large volumes to estimate costs. Organizations need to invest time to explore New Relic's extensive functionality and properly instrument features to realize their full impact. Additionally, designing dashboards is not straightforward; users need to create their NRQL queries before they can fully understand the value.

Regarding the user interface, I have noticed changes in past years, with some features we appreciated in previous versions and others in new ones. One issue we have reported is the text overlaying on dashboards when editing, which makes it challenging to navigate. Another issue is that some users experience blurred text, requiring a system restart and login to rectify.

I have been using New Relic for more than eight years now.

Before using New Relic, we used Grafana, Splunk, VividCortex, and Opster to monitor and observe each layer, requiring different tools for each, which slowed us down. With New Relic, we can visualize all underlying systems architecture and metrics in one place, which helps us correlate issues faster and easier, allowing us to save almost seven to eight hours of analysis time previously spent on multiple systems and tools.

New Relic is deployed in our organization as a private cloud or possibly hybrid cloud, as it can function both ways.

I advise that New Relic is the best APM tool available, providing everything you need to pinpoint root causes for performance bottlenecks and serving as an effective observability tool for production telemetry metrics. There are open-source tools that are easier to use but have limitations, whereas New Relic offers a wide variety of useful features for performance engineers, SREs, and leadership. While it is costly, the valuable data and time saved justify the investment, so I encourage others to give it a try.

I would rate New Relic an eight out of ten. We utilize nearly 70 to 80 percent of its features, so eight seems appropriate given the ease with which users can work and instrument New Relic.

I choose eight out of ten as we are yet to explore 20 percent of New Relic features, and the ease of creating alerts, dashboards, and instrumentation often requires expertise. Live tracing of a transaction would enhance the platform, allowing us to trace transaction data flow with an architectural diagram to visualize time spent, which would elevate my rating to a 9 or 10.

The time savings initially amounted to seven to eight hours per person per week, and increased to almost 24 hours after creating dashboards with automated alerting systems in place. Now, we can directly get alerts during our tests and have a holistic view of the architecture's performance, enabling us to quickly identify any bottlenecks. Since we save time, we can create better dashboards and invest more time in harnessing other areas of the applications we test. My overall rating for New Relic is eight out of ten.

I have around one to two years of experience using New Relic to make it much more optimal for one of the applications while working with Oracle.

My main use case for New Relic is to generally see when the response time or the payload is increasing for the API calls and for which particular region, so that is the main reason we are using it for optimization.

For those things, let us say we have some core regions in the US, such as East America. If we think a certain payload or a certain API is taking two to three minutes of time, which we do not usually expect, we just see what the number of repeat use cases is happening over there, create a proxy server, store the data locally, and try to get that response time increased.

The best features New Relic offers in my experience is that it serves as a single point where we can see all the API functionality, cross-check the payloads, and understand at what time our API is up or when it usually fails, all in a single place.

Having everything in one place has helped me and my team by saving our time and making troubleshooting easier. If we receive any Jira tickets stating that a particular request is taking time or the user is facing glitches, we can simply log in to our New Relic application and review the use case scenarios, determining what frequent calls are made for the API and threshold values set.

New Relic has positively impacted our organization by allowing us to spot complaints before clients jump into a call, as we can suspect and fix issues early. This makes clients happy and reduces the number of ticket counts, showcasing its positive impact.

Since using New Relic, time saved has improved by almost 50% due to the integration of Copilots and AI, and the ticket count reduction has surpassed 75%, allowing us to efficiently address similar issues.

There are certain scenarios where I feel additional functionalities could enhance New Relic, such as gaining more data about calls. For example, it could indicate API failures by implementing AIs that suggest optimizations based on payloads and server requests.

Regarding user interface and design, I believe the current UI is straightforward and effective, allowing users to easily gather conceptual data.

I have almost full-stack experience totaling six to seven years, and it remains the same.

New Relic is considered stable and can be integrated into existing projects.

I do not have much information on scalability as I have not explored that aspect extensively.

My experience with customer support for New Relic has been positive. We faced a glitch in a previous project and received a response quickly, within three to four working days, which was helpful for addressing technical issues.

Positive

We did not use any other solutions before New Relic. It was the only one we found after researching and deemed it had good functionality.

I do not have specific metrics regarding return on investment since those metrics are managed at the management level. However, I can share that the ease of functionality for developers has improved and the reduction in ticket counts by 50 to 70% has eased the workload.

I do not have much exposure to pricing, setup cost, and licensing details, as we have a dedicated team handling that aspect.

Apart from New Relic, we do have other similar software, but I emphatically choose New Relic because of the ease of functionality and the comprehensive documentation, making it easy to incorporate into applications.

There are many alternatives such as DataDog, Dynatrace, and Splunk Observability, but after our research, we concluded that New Relic would be a better match for our projects.

If building a good application that is live and in use, and suspecting certain APIs might take longer response times, I would advise using New Relic for centralized monitoring of all calls and payloads.

New Relic has everything necessary, and I would love to see agentic AIs integrated into it in the future to enable users of varying experience levels to access extensive data easily. My overall rating for this product is 9.

On-premises

My main use case for New Relic is monitoring the app performances from dashboards and tracing the API calls. For app performance, I monitor the four golden signals, the throughput, error rate, and the Apdex score. For tracing, I try to find out where there is latency and from which source the latency is coming, whether it is the network or the database call.

The best features New Relic offers are end-to-end tracing of any calls and custom dashboards. Those features stand out for me in my daily work because, as an SRE and DevOps engineer, when I need to debug or find the root cause, especially when multiple teams are involved, end-to-end tracing is useful to identify the correct team and engage them further. Custom dashboards are useful to showcase high-level metrics to the leadership.

In multiple cases, I use New Relic to debug and find the root cause, especially where network calls are involved. It is also useful for alerting when the throughput is dropping or the error rate is spiking. Time is saved in debugging and finding root causes.

New Relic can be improved by providing auto-completion of New Relic Query Language queries. Custom dashboards may have more templates so that I can drag and drop and create my own monitoring dashboards.

I chose a rating of 8 out of 10 because the UI requires me to dig in and find the needed traces, and it can be more user-friendly.

I have been using New Relic for more than seven years.

New Relic is stable.

New Relic's scalability is good, and I can scale easily using the agents installed in my infrastructure.

The customer support for New Relic is excellent.

Positive

I did not previously use a different solution.

I have a long-standing relationship with New Relic, so dedicated sales teams engage with my leadership team and we finalize the costs.

Before choosing New Relic, I evaluated other options, specifically Datadog and Splunk.

At the team level, New Relic is a good observability tool. My advice for others looking into using New Relic is that it is a great tool for monitoring your application, querying your logs, and visualizing various parameters. I would rate this product an 8 out of 10.

Public Cloud

Amazon Web Services (AWS)

New Relic is primarily used for log monitoring, where queries on the logs provide insights and create log-based metrics for all alerting-related requirements. The focus is mainly on alerting and dashboards.

New Relic helped with the mean time to detection, the MTDD metric tracked for applications. For the platform, the detection capability enabled a reduction from around 20 to 30 minutes down to three minutes. This has been really helpful in terms of detecting issues as well as helping to triage and troubleshoot issues faster, creating a positive impact on the organization.

One of the best features that New Relic offers is the user interface, which is much easier to use compared to other products such as Datadog or Splunk. The team management and alert configuration process is also fairly straightforward. New Relic is very useful for teams that don't have much of a dedicated DevOps team but want to have observability for their platform, and it's an easy way to get started.

One of the main UI features is the ability to see a particular frequency, such as an error or a high amount of logs at a particular timestamp, and easily filter that via the graph as well as the timestamps that can be configured. This is relatively easy to use compared to other products.

New Relic is priced on the higher side. Because of the pricing model, organizations have experienced uncontrolled costs and were not able to afford New Relic, which resulted in moving to open-source solutions such as Grafana and Loki. This pricing structure has been the main pain point experienced with New Relic.

New Relic has been used for the past two years.

One of the metrics that helped as a return on investment was the ability to detect issues faster and troubleshoot more quickly, which in turn helped to achieve a much better service level agreement with customers.

Pricing is primarily an area of concern. The overall rating for New Relic is eight out of ten.

Public Cloud

Amazon Web Services (AWS)

Our main focus is APM-related functionality, so we were looking for a convenient way to get all the details, as some of them are missing from New Relic and Grafana. Currently, we are working with Site24x7, where we are getting the information we are looking for in our comfort zone.

We used the Docker container as the agent in our server, which was split into one agent to collect the client's logs and metrics to see the web vitals, and another metric to collect the server metrics and APM-related traces.

The main benefit we found was the Error Inbox, and having all features available at a single point was very useful for us. The API functionality allows us to get hit counts from external sources, such as APIs or databases, and everything is mapped very clearly. We can overview which components are experiencing response delays, which ones are getting correct responses, and identify any unknown external APIs inside the application. We can investigate why we are getting 400 responses and similar issues.

I reviewed another observability tool, DataDog, and we moved away from New Relic because the pricing was not convenient and didn't fit our budget. With DataDog, some of the APM features we were looking for were not available, so we discontinued using both solutions.

Grafana is helpful, but it requires significant work in adding agents and configuring applications and server metrics. We implemented open-source Grafana, which wasn't convenient regarding APM, and most of the logs and traces related to APM were not what we needed, so we moved to Site24x7.

The Grafana Open Source implementation was done through their vendor. While they provided certain features, when compared to Grafana Cloud, the customized Open Source version wasn't really convenient for us. The only helpful aspect was that we could get server metrics on Grafana Open Source from our servers.

I have been working with New Relic for approximately six months.

New Relic was stable enough, and there were no downtimes or issues.

New Relic offers 400 GB per month free, but that quota was completely used within two weeks for a single server. We have substantial data in our server as our company is a trading financial company. For a single server, it takes around one and a half to two weeks to reach the limit. Additionally, we need to store logs for over five years based on SEBI regulations.

I didn't seek any support help from New Relic, but when I tried to get information regarding the plans, the response was delayed for a week. Other than that, everything was fine.

Positive

We reviewed Grafana and moved to another observability tool. We also evaluated DataDog, but we ultimately moved away from New Relic because the pricing wasn't convenient and didn't fit our budget. We are now using Site24x7 in production.

Implementing the New Relic agent is quite simple, and we were very comfortable with New Relic overall. However, it wasn't convenient based on our budget, which is why we discontinued using it.

The Grafana Open Source implementation wasn't done by ourselves; we worked with their vendor. They explained the features available in Grafana Open Source, and we implemented those solutions. However, compared to Grafana Cloud, the customized Open Source version wasn't really convenient for us.

The Error Inbox and consolidated features at a single point were very useful features. We could get hit counts from external sources, APIs, and databases, with clear mapping of all components. We could monitor response delays, correct responses, and identify unknown external APIs within the application.

We also reviewed DataDog as an observability tool, but we moved away from New Relic due to pricing concerns that didn't fit our budget. With DataDog, some of the APM features we were seeking weren't available, so we discontinued using both solutions.

We had everything in hand with New Relic initially. However, the pricing wasn't convenient for us, so we had to step back from using it.

I primarily focused on the data we were getting from New Relic, without exploring custom dashboards and other features. We were mainly focusing on the metrics and logs needed to trace our applications effectively.

On a scale of one to ten, I would rate New Relic an eight. It's overwhelming from my point of view, and we needed to do some organizing in our New Relic account based on our preferences.

I use New Relic to troubleshoot my applications and look at metrics and logs to solve problems in my day-to-day work. In my daily use, my application operates at a large scale, and because of this, we need to look at the metrics to check the health of the application and monitor the movements of the applications.

In my opinion, the best feature that New Relic offers is the filtering of the metrics and the logs. When we need to look at the metrics with New Relic, I can filter by the name of the application, which is very important and has helped me. With the metrics from New Relic, we can improve the performance and reduce the downtime because we can identify problems and solve them more quickly. New Relic has positively impacted my organization because it has helped improve the performance and reduce the downtime of the application.

I think New Relic can be more simple to use because for beginners it can be more difficult to use, so I think New Relic can improve in that aspect. There can be more improvements, and I think New Relic can be more useful, as it is hard for beginners.

I work in my current field of software engineering for one year and five months.

New Relic is stable and reliable for me.

New Relic has good scalability and can handle my growing needs.

I previously used Datadog before New Relic, and I switched from Datadog because I thought it was simpler to use. In my day, I use both Datadog and New Relic along with other applications.

I evaluated other options before choosing New Relic, including Datadog, Grafana, and OpenTelemetry.

One relevant metric I appreciate is the metrics of the helpful applications and the performance metrics from New Relic. My advice to others looking into using New Relic is to study and construct your metrics with good patterns. I would rate this review an 8.

Private Cloud

Other

In my day-to-day activity, I check the configurations of the pod, for example, the CPU or memory utilization of the pods that are deployed in the Kubernetes cluster, by going to New Relic and checking the CPU and memory utilization. When I want to check the application logs, I use New Relic for checking the logs.

Using New Relic, we are able to monitor the cluster. In each namespace, we can see what pods are deployed, what the deployment sets are, and every other resource that is deployed in Kubernetes, which we can monitor using New Relic.

Recently we have implemented cost optimization in each and every environment. We pulled down all the CPU and RAM utilization of the pods, and later we came to know that the majority of the resources that are deployed are over-provisioned. We took those metrics and scaled down a couple of resources for the pods.

We were able to save $1,000 per month.

The resources that are created on the Kubernetes cluster can be seen on the dashboards in New Relic dashboard, which is the best feature.

If I want to make any customization, for example, if I want to see the last six months' CPU and RAM utilization of the pod, I can create a custom dashboard and check the utilization.

By using New Relic, I can check quickly the utilization of the CPU and memory of the Kubernetes nodes and the pods.

The logs in New Relic are not showing the full logs. When I go and check the logs, they are not complete. There are some missing things in the logs, and if that can be added, that would be very good.

If someone can provide the official documentation on how to update New Relic and in case I want to increase anything, those features and documentation would be very good.

From the past three years, I have been using New Relic tool, which is used for monitoring purposes. For example, if I want to check what the CPU or memory utilization is of a particular pod, I go and check in New Relic. If there are any logs, I go and check the application logs in New Relic.

New Relic is stable.

New Relic has handled changes in the environment very well.

In case I lose any access or something, there is customer support available for me. If I drop an email to them, they will respond quickly to my email.

We were using Sumo Logic for the logs. Later, the management decided to move from Sumo Logic to New Relic.

We did not evaluate other options.

I would suggest using the dashboards in New Relic for resource utilization of Kubernetes deployments, pods, or nodes. I have rated this product an 8.

My main use case for New Relic is health monitoring and log assembly. When a site goes down, I have to look at the logs if a series of sites get down or are technically down for any failure at all. I have to make comparisons between logs on each and every server.

In my opinion, the best feature New Relic offers is synthetic monitoring. What I appreciate most about synthetic monitoring in New Relic is that it is actually plug and play; it detects if there are several components of a website that are either failing or not communicating, and it gives a thorough log of what is actually happening.

I believe the metrics for the entire project in New Relic are very useful, as I do not have to add an add-on; everything is already included by default.

New Relic has positively impacted my organization by providing peace of mind to my clients, and it also gives a lot of insight to their marketing department on how users interact with their websites or how they work with them.

If New Relic could add a partnership with Cloudflare or any other vendor that can provide security on the edge, it would be even better because combining both technologies would be easier for the user or the client to have peace of mind by having the monitoring metrics along with any incident that may be happening. Therefore, you could have a more insightful and cohesive reason on why a site was either down or was attacked, allowing you to check only the logs in a certain time frame that aligns between the incident and the metric.

In terms of usability, I think the UI is acceptable, but it does not really guide you along with what you actually need. Additionally, regarding the reasons why a site is down, they do not generally give a good or wide insight into what exactly is happening, only some sort of idea of what it is, but not exactly what happened.

I have been using New Relic for three years.

New Relic is very stable.

I cannot form an opinion about New Relic's scalability, but I am quite sure that the scalability is efficient as far as our needs go.

Customer support for New Relic is impressive; they respond in less than five minutes. I would rate the customer support a ten on a scale of one to ten.

Positive

I have not previously used a different solution.

My advice to others looking into using New Relic is to trust only what New Relic can offer and not try to extend it to things it cannot do. For the price and for the services it offers, I think it is a pretty good package; there is room for add-ons, not improvement, as I believe New Relic is good for what it is but could use some additional features.

Before choosing New Relic, I evaluated CloudWatch, but the vendor insisted on using New Relic.

I appreciate that New Relic integrates with almost every single DevOps tool that I have. It is very easy to add it as a plugin for each agile process that we have for preparing any given task.

New Relic is a pretty good tool for what it is, which is monitoring and also providing insight metrics on the websites that it is added to. If New Relic could address security on the edge and if I missed it, then they should promote that more, as it would help the project significantly. I rate this review an eight overall.

Hybrid Cloud

Other

It is for APM,  Application Performance Monitoring. And server monitoring.

There are two types of teams we have in every organization. One is for DevOps, and the second one is for performance testing. Those who are using these tools, like AppDynamics, Dynatrace, or whatever tool we have on the APM side. 

These tools are used by two teams: one is the performance team, and another one is the DevOps team. So, the setup and the alert system belong to the DevOps team, not for performance. So, I don't use any alerts in AppDynamics, Dynatrace, or any of the tools. 

There is room for improvement in the stability.

I have experience with this product. 

I would rate the stability a six out of ten. It can be improved.

Scalability is not that much available with the applications.

There are around 400 to 500 end users. 

Whenever it is needed, they have provided support from the New Relic side.

Whenever they get their customers, they'll go for approval, then they will assign someone, then that person will come and understand what issue we are facing and what we require. Then they will try to resolve the issue.

I prefer AppDynamics and Dynatrace. These two tools over New Relic.

So, integration is possible with LoadRunner and other tools in New Relic.

I would rate it a six out of ten. 

I use New Relic for the creation of dashboards, alerts, and any type of observability resources that are relevant for my company.

The most valuable features of New Relic are the ease of creating dashboards and its integration capabilities with many external tools. It enhances operational response by providing analytics and alerts that help us address issues quicker. 

Using New Relic speeds up troubleshooting and resolution, giving us a clearer picture of where issues are, thus saving time and effort.

Email alert customization is limited; it cannot be tailored much, which makes the system more rigid than optimal. The handling of logs from integration tools is not as advanced compared to other tools. AI integration, including predictive analytics, is available for certain features but is not comprehensive.

I have been using New Relic for one year.

I find New Relic to be a stable tool. It is reliable in the aspects that I use.

While responsive, customer service does not always provide straightforward solutions immediately. Issues that could be solved quickly sometimes take longer because they go around in circles. However, they are helpful when direct interaction is initiated.

Neutral

The setup is easy for the part I'm responsible for. However, since I do not manage the complete product setup, I cannot comment on the entire process.

For our part, New Relic has provided value by speeding up issue troubleshooting and resolution, allowing for more efficient use of time.

I rate New Relic seven out of ten. 

For those looking to use New Relic, it is more suited for networking and infrastructure monitoring rather than application performance monitoring, integration, or API log handling.

Other