Sold by
New Relic APM, Logs + Infrastructure Monitoring (PAYG with Free Tier)
New Relic's observability platform provides engineers with full visibility into the performance of their AWS cloud services. Get unlimited access to New Relic, including Application Performance Monitoring, Infrastructure, DEM, Serverless, Logs, AIOps, Events, Alerts, and more.
Reviews (616)
Ravindra N.
End-to-End Observability That Makes Troubleshooting Faster
Reviewed on Jul 01, 2026
Review provided by G2
What do you like best about the product?
What I like most about New Relic is its end-to-end application performance monitoring and real-time observability. It provides a unified view of application health, making it easier to detect, investigate, and resolve performance issues. Comprehensive Application Performance Monitoring (APM). Real-time monitoring of applications, infrastructure, and services. Distributed tracing for identifying bottlenecks across microservices. Custom dashboards and alerts for proactive monitoring. Detailed error analytics and performance insights. The most valuable feature is distributed tracing. It helps track requests across multiple services, making it much easier to identify the root cause of latency or application failures in complex environments. The biggest benefit is faster troubleshooting. Instead of manually correlating logs and metrics from different systems, New Relic provides the visibility needed to diagnose issues quickly, improve application performance, and maintain a better user experience.
What do you dislike about the product?
The biggest challenge is balancing observability with cost. As applications scale and generate more logs, metrics, and traces, it's important to optimize what is collected to keep costs under control. Creating advanced dashboards and custom queries may require additional expertise. Managing data retention and ingestion costs requires careful planning. Some alerts need fine-tuning to avoid unnecessary notifications.
What problems is the product solving and how is that benefiting you?
New Relic solves the problem of limited visibility into application performance and system health. Instead of relying on separate tools for logs, metrics, and performance monitoring, it provides a unified platform to monitor applications, infrastructure, and user experience. Detects performance bottlenecks and application issues in real time. Centralizes metrics, traces, logs, and error data in one platform. Helps identify the root cause of production incidents faster. Provides proactive alerts to minimize downtime. Monitors APIs, databases, infrastructure, and application performance from a single dashboard. In my day-to-day work as an SDET, I use New Relic to monitor application performance after deployments, investigate API latency, analyze errors, and validate system stability. Having end-to-end visibility into application behavior helps me collaborate more effectively with developers and operations teams. The biggest benefit is faster incident resolution. By correlating performance metrics, traces, and errors in one place, New Relic reduces troubleshooting time, improves application reliability, and helps deliver a better experience for end users.
Ramkumar H.
New Relic: Unified, Real‑Time Observability That Turns Multi‑Service Chaos into Clarity
Reviewed on Jun 30, 2026
Review provided by G2
What do you like best about the product?
The best thing about New Relic, in my view as an observability‑focused AI, is its ability to turn chaotic, multi‑service systems into something you can actually reason about. The platform gives you a single, correlated, queryable source of truth across APM, logs, infra, browser, mobile, synthetics, and custom telemetry, and that changes how teams troubleshoot, optimize, and ship.
New Relic’s strongest advantage is unified, real‑time observability that lets you see exactly where a problem starts, how it propagates, and what to fix first.
New Relic’s strongest advantage is unified, real‑time observability that lets you see exactly where a problem starts, how it propagates, and what to fix first.
What do you dislike about the product?
Signal noise — Alerts can get overwhelming if not tuned well. Out oft hebox policies often fire too frequently, and correlation doesn’t always group incidents the way you expect. Steep learning curve — NRQL is powerful, but not intuitive for beginners. Querying events vs metrics vs logs requires mental overhead. UI complexity — The interface is feature rich, but sometimes cluttered. Finding the exact trace, entity, or dashboard can take more clicks than necessary.
What problems is the product solving and how is that benefiting you?
New Relic solves the core observability problems that make modern systems hard to understand, and that directly benefits you in practice by making debugging, performance tuning, and NVF exam preparation dramatically easier.
Fragmented telemetry — In most systems, logs live in one place, metrics in another, traces somewhere else. New Relic unifies them so you can correlate everything instantly.
Fragmented telemetry — In most systems, logs live in one place, metrics in another, traces somewhere else. New Relic unifies them so you can correlate everything instantly.
Qazim Adedigba
Monitoring has improved uptime and incident response but still needs better cost and access control
Reviewed on Jun 30, 2026
Review from a verified AWS customer
What is our primary use case?
As an Application Monitoring Engineer, my primary responsibilities include ensuring the uptime of services, managing infrastructure, and monitoring transactions. I use New Relic to set up incidents, SLO, and SLI for early issue detection and efficient monitoring tasks. I frequently utilize dashboards, alerting, and New Relic Query Language (NRQL) as they form the core of my operations. Dashboards help me monitor important services at a glance, while alerting allows me to manage issues without needing to be at my workstation constantly. With NRQL, I can efficiently query services and infrastructure to address problems using specific keywords.
New Relic enables preemptive action through synthetic monitoring and supports setting SLOs and error budgets, leading to effective alerting and reporting on application performance. Regarding customer interactions, New Relic significantly reduced the back-and-forth that might have occurred during incident resolution, as demonstrated by a recent case where I quickly identified network issues impacting a team member's service.
What is most valuable?
As an Application Monitoring Engineer, two of the most important aspects for me are the dashboard and alerting features of New Relic. They allow me to view issues quickly and customize what I want to see, aiding in interpretation and reporting. The dashboard's clarity and flexibility mean I do not need to delve deep into logs, as I can identify issues at a glance, filter by errors, and configure alerts to manage my time effectively without being overwhelmed by noise.
New Relic positively impacts my organization by simplifying issue detection, allowing us to focus on what is important and avoid unnecessary searches. Its reporting, tracing, logging, integration, querying, and alerting features make incident investigation smoother, allowing for a reduced mean time to detect and resolve issues. The user interface is easy to navigate, enabling efficient operation from any device.
What needs improvement?
I find New Relic to be somewhat expensive. Our team shares logins, contrasting with other applications where individual team accounts are standard. Pricing is a primary concern since New Relic can be costly, and sometimes it can be slow when dealing with large datasets, especially during critical incidents where rapid data access is essential.
Customization for some dashboards, particularly for Java applications, often feels cumbersome, requiring extensive learning to manage issues such as Java heap problems effectively. An AI feature that simplifies customization could significantly enhance usability.
For how long have I used the solution?
I have been in the tech for more than four years, and as an Application Monitoring Engineer, I have worked for over two years in my current role. I have been using New Relic for that duration as well.
Which solution did I use previously and why did I switch?
Before joining the FinTech sector, I worked in the insurance tech space as an application support and implementation engineer.
Which other solutions did I evaluate?
It is challenging to pick the best feature because while Grafana is good for dashboards, New Relic serves as a one-stop shop for various functionalities. I recommend New Relic as a worthwhile tool due to its capabilities in enhancing uptime and facilitating faster issue resolution; however, I also note that the cost should be a consideration.
What other advice do I have?
I started using New Relic when I joined my current team, as effective monitoring requires the right tools to know what to do at the right time. With New Relic, I set up incidents, SLO, and SLI to catch issues early, utilizing dashboards and alerting, making my monitoring tasks efficient since I joined.
Metrics indicate that New Relic improves both my mean time to detect and mean time to resolve issues, resulting in faster incident resolution. As a service is down, alerts prompt immediate action, allowing me to isolate problems swiftly, enhancing uptime and customer satisfaction while reducing engineer fatigue.
Our team experiences challenges with limited shared logins, causing interruptions during troubleshooting. A more secure login structure would enhance usability and performance, potentially earning a higher rating.
I find that reporting and scheduling reports are essential aspects I am using regularly, where weekly reports detail our application availability for executives to review. The platform also facilitates collaboration with engineers, enabling us to quickly share observations about issues in applications or services, thus minimizing the need for prolonged discussions.
I rate New Relic a seven out of ten primarily due to its cost.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
RohitSharma1
Unified observability has reduced troubleshooting time and provides end-to-end performance insights
Reviewed on Jun 04, 2026
Review from a verified AWS customer
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using New Relic for more than eight years now.
Which solution did I use previously and why did I switch?
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.
What other advice do I have?
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.
HemantKumar7
Monitoring has improved Java microservices and enables proactive issue detection and alerting
Reviewed on May 12, 2026
Review from a verified AWS customer
What is our primary use case?
We use Java microservices, so we capture the events with the help of New Relic. Based on that, we add the alerting part inside New Relic.
We have enabled the New Relic Java agent inside our microservices, which observes the metrics from the microservice. We have created the dashboard inside New Relic, which captures the metrics and plots the weekly data inside New Relic. We can also add a timeframe in New Relic to observe the past trends and current analysis.
This is our main use case. We can observe the response time, Apdex score, error percentage, database queries, and web transactions inside New Relic.
How has it helped my organization?
New Relic has a great impact on our organization because without logging into the database and any other tool, you can directly capture the long-running queries and which APIs are taking a lot of time. You can filter them inside New Relic. You can also create custom dashboards inside New Relic, and based on your use case, you can create that particular dashboard. You can also set alerting based on the past trends of those metrics.
All of these metrics improve because we can say without any major outage, if we get the Apdex score alert or either response time or whatever alert we have set up inside New Relic, we timely get the alert. We can also proactively get the alert and proactively fix those things. Instead of getting a production down, you can analyze those things based on New Relic trends. You can fix and respond proactively without any minimal damage.
What is most valuable?
In my experience, New Relic is one of the best APM tools. You can monitor your API's response. You can filter the APIs based on the response it is taking, and you can monitor the response times based on the multiple APMs related to respective environments. You can observe the Apdex score inside New Relic. In one single window, you can look for the multiple metrics, which is really useful for production.
You can also monitor heap parameters and memory of the JVM inside New Relic. You can also integrate it with your incident management tool so that based on the alert you have set up inside New Relic, you can get the alert over your incident management tool.
What needs improvement?
Sometimes the UI feels like it is not that much user-friendly for any new user who is using New Relic. The user interface could be more user-friendly for someone who is new to New Relic.
For alerting and dashboards, I still think there is some tuning and a user-friendly experience required because while creating, it is something complex.
There are some changes required from the UI side. If someone is new, the UI is not that overwhelming from the new user experience perspective.
For how long have I used the solution?
I have been using New Relic for the last five years.
What do I think about the stability of the solution?
In my experience, New Relic is very much stable.
What do I think about the scalability of the solution?
New Relic is very much scalable for our organization.
How are customer service and support?
We have excellent customer support with New Relic.
Which solution did I use previously and why did I switch?
From the start we are using New Relic and did not previously use a different solution.
How was the initial setup?
I think there is nothing to improve in New Relic. It is having the best features. As we talk about setup, you can set it up very easily. It captures from the observability side, if we talk about it, metrics, logs, and you can visualize a dashboard based on those metrics. You can also integrate it with your incident management tool. So I think there is nothing required for the improvement as of now.
What was our ROI?
I have seen a return on investment because if you timely monitor the things and fix those things, and there is no such production outage, your production is running smoothly and there is no outage, that means you are saving. You are definitely getting ROI on whatever you are investing because if your production is down, then there is a loss of revenue from the customer side. It is a great tool to get ROI.
What's my experience with pricing, setup cost, and licensing?
As we talk about pricing, it is not that much cheaper. It totally depends on your ingestion, how much ingestion it is taking. So, it is totally dependent on that.
Which other solutions did I evaluate?
We have tried Signoz and OTel, but they will not work for us because these are open-source, and you need to perform lots of tuning. Of course, New Relic is not open-source, and there are lots of features in New Relic. That is why we go for New Relic.
What other advice do I have?
If someone is trying to monitor their applications which are built with Java, you should definitely go for New Relic because there are lots of features inside New Relic. You can integrate New Relic with cloud providers, and you can also integrate your incident management tools. If you are observing and capturing something, you can also set up alerting, and you can directly integrate it with your incident management tool. There are lots of integrations in New Relic, so you do not need to worry about it. Based on a single screen, you can capture multiple metrics including response time, Apdex, throughput, and you can track your APIs which are slow over time. You can also monitor your CPU, memory utilization, and apart from it, you can also visualize your logs and errors inside your microservices. You can also monitor database queries which are taking a lot of time. There are lots of things inside New Relic. I have given this review a rating of 9 out of 10.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Real Estate
Easy-to-Use Metrics and a Clean Interface
Reviewed on Apr 29, 2026
Review provided by G2
What do you like best about the product?
I like the easy to use metrics and user interface.
What do you dislike about the product?
The costs can add up unless the project is shared across web assets which requires more configuration.
What problems is the product solving and how is that benefiting you?
Easy to use dashboard for monitoring metrics across our web properties. Also useful to trace inefficiencies or errors in our stack.
Sabina K.
New Relic Unlocks Powerful Insights with Versatile Dashboards and Browser Monitoring
Reviewed on Apr 29, 2026
Review provided by G2
What do you like best about the product?
The way we monitor our application and analyze performance issues has improved enormously since introducing New Relic, as we get new insights that were hidden from us previously. Its versatile dashboards allow team members to select the metrics that are relevant to their area of focus. Moreover, the browser monitoring capability has proven to be a useful as it has helped us to discover frontend performance issues that had a detrimental effect on user retention.
What do you dislike about the product?
The pricing structure is volatile and easily scales with high volumes of publication/population rates, which can make budgeting complex. The API also has some advanced functionality only available with the higher-end plans, which feels restrictive for teams with limited enterprise budgets.
What problems is the product solving and how is that benefiting you?
New Relic has addressed the issue of monitoring silos by bringing together our application, infrastructure and user experience monitoring in one place. This has allowed our team to diagnose incidents quicker, which in turn means that we can fix problems quicker, providing our users with a better product.
amit y.
Clear, Fast Application Performance Visibility with New Relic
Reviewed on Mar 14, 2026
Review provided by G2
What do you like best about the product?
What I like most about New Relic is how quickly it gives clear visibility into application performance. I’ve used it to monitor Node.js and Python services, and integrating the APM agent was pretty straightforward both in regular deployments and containerized environments. The transaction traces and error insights make it easy to spot slow endpoints or bottlenecks. I also like the dashboards and alerts, which help keep track of application health without much effort. Overall, it makes debugging and performance monitoring much easier for engineering teams.
What do you dislike about the product?
One area that could be improved is the pricing model, especially as telemetry and log ingestion grow. In larger environments it can become difficult to predict costs. The UI is also very feature-rich, which is great, but it can take some time for new users to navigate and find the right views or queries. Some simpler onboarding guides or curated dashboards for common use cases would make it easier for teams getting started with the platform.
What problems is the product solving and how is that benefiting you?
New Relic helps us quickly understand what’s happening inside our applications in production. While working with Node.js and Python services, it made it much easier to identify slow endpoints, failing transactions, and database bottlenecks through APM traces. Instead of relying only on logs, we could see performance issues in real time and debug them faster. This helped reduce troubleshooting time and improved overall application reliability for our teams.
reviewer2805771
Intelligent monitoring has reduced incident toil and has automated root cause analysis
Reviewed on Mar 02, 2026
Review from a verified AWS customer
What is our primary use case?
My day-to-day activities in New Relic include infrastructure monitoring, APM monitoring, browser monitoring, and database monitoring. In cloud environments, I monitor multiple clouds like AWS, GCP, and Azure. The features I use inside New Relic include alerts, service levels, parsing rules, dashboards, workloads, and muting rules.
Recently, I received an alert for a login failure in my application, so I went to New Relic and checked where the issue was. Since we have set up complete distributed tracing of that particular journey and introduced custom correlation IDs for all the journeys, whenever we get any error or transaction, we obtain that particular correlation ID for that transaction. That correlation ID is unique for all transactions, so when I got that login error during my recent troubleshooting, I checked the alert in New Relic to understand why it was triggered. We discovered an internal server issue by examining the logs in New Relic and troubleshooted that issue effectively.
The main use cases with New Relic include browser monitoring and cloud services monitoring. In cloud services monitoring, we are using Lambda functions from AWS, and from Azure, we are using APIM, app gateway, and Azure functions. We use New Relic to monitor those particular resources to identify where we are encountering issues and what challenges we face. The recent features that New Relic has launched, including AI agent integration, are very helpful for faster troubleshooting, allowing us to easily diagnose the root cause of any incidents. I am looking forward to that particular feature in the future.
What is most valuable?
The features that performed very well include custom visualization in New Relic, which allows me to create a dashboard tailored to our specific needs. There are no restrictions on charts, and by using React, I can easily create those types of dashboards. New Relic has also introduced a good feature for Agentic AI integration, and they have launched the One App integration. This integration allows different types of applications within a cluster to be included in the form of APM. Additionally, a new feature launched troubleshoots issues automatically; for example, when I received an alert for my EC2 machine usage reaching ninety percent, I got a notification in my Slack channel, and by giving a thumbs up, New Relic's SRE agent connects with the AWS Bedrock agent to troubleshoot automatically and scale up the EC2 machine without manual intervention. These features of New Relic stand out significantly.
The AI integration helps us in different ways, particularly in root cause analysis (RCA). I was using the AI RCA feature in New Relic's incident tab, which provides a button to generate RCA by checking details of past events related to that particular incident. This allows me to easily identify issues and troubleshoot them. For instance, after integrating my EC2 machine with New Relic, I received an alert at two a.m. for memory usage reaching eighty percent. After receiving that alert in my notification channel, I enabled the AI agent to provide a complete RCA and solution for the issue. Once I approved the suggested solution, the AI agent automatically scaled up my EC2, allowing me to troubleshoot the issue efficiently without further intervention. Using these New Relic features significantly reduces our mean time to detect (MTDD) and mean time to resolution (MTTR).
Other features include the custom visualization capability, which allows us to better visualize our data. The default dashboards in New Relic have a limited number of widget types, so for specific visualizations such as spider maps, I cannot create that with the default widgets. Thus, the custom visualization feature is very helpful for that. New Relic has recently launched NR Lens, which allows querying data from different sources; previously, New Relic only provided access to data within their database (NRDB), but now we can query data from platforms such as Google Sheets. Integrating various platforms with New Relic simplifies the data querying process, and there are excellent Agentic integrations with notification channels such as ServiceNow, enabling easy communication with New Relic AI. These are powerful features of New Relic.
What needs improvement?
I have noticed discrepancies between New Relic's documentation and Terraform resources. For example, there have been instances where new features launched in the New Relic UI have not been updated in the Terraform provider. Improving the synchronization between the UI and Terraform would be very beneficial for us.
I would also point out that the query section within the UI has slowed down in response times over the past few months. Previously, querying anything in New Relic provided quicker results, so reducing the time taken to provide query results would be helpful for everyone.
For how long have I used the solution?
I have been using New Relic for three plus years.
What do I think about the stability of the solution?
New Relic is stable.
What do I think about the scalability of the solution?
Regarding New Relic's scalability, it excels at the enterprise level for cloud integrations that can utilize tags. However, for other integrations such as APM or Kubernetes, it is less scalable as each application requires its own agent for integration.
How are customer service and support?
The customer support experience was good, with faster troubleshooting provided by New Relic's support team.
Which solution did I use previously and why did I switch?
What was our ROI?
We observe a return on investment with New Relic. Previously, we needed more manpower to troubleshoot issues and determine exact RCAs, which consumed both time and money. After implementing New Relic, we have decreased staffing requirements while saving time and money.
Which other solutions did I evaluate?
I evaluated other options, including Datadog, Dynatrace, Coralogix, Grafana, Prometheus, Azure Monitor, and AWS CloudWatch.
What other advice do I have?
Compared to other observability competitors, New Relic offers better pricing for their features, and the user interface is user-friendly.
Using New Relic, we can showcase business KPIs data and compare it with trends from the last month or year. We can easily check whether our business performance is declining, stable, or improving, as well as the revenue generated from our website. New Relic allows us to analyze this data efficiently if we are sending it to their platform. Additionally, it has a wide range of integrations with third-party platforms, major clouds, and multiple backend languages.
My advice for others considering New Relic is to focus on cost, as it is competitive compared to other options. I would also recommend the excellent features New Relic provides within this price range, such as the Agentic AI feature, SRE agent capabilities, custom dashboards, and custom visualization, which help in proactivity regarding alerts and awareness of potential issues. I would rate my overall experience with New Relic a nine out of ten.
Victor Trainee
Monitoring large scale applications has improved troubleshooting and reduced downtime
Reviewed on Feb 05, 2026
Review provided by PeerSpot
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I work in my current field of software engineering for one year and five months.
What do I think about the stability of the solution?
New Relic is stable and reliable for me.
What do I think about the scalability of the solution?
New Relic has good scalability and can handle my growing needs.
Which solution did I use previously and why did I switch?
Which other solutions did I evaluate?
I evaluated other options before choosing New Relic, including Datadog, Grafana, and OpenTelemetry.
What other advice do I have?
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.