New Relic: the Observability Platform logo

    New Relic: the Observability Platform

    Sold by
    New Relic combines configuration monitoring and real-time health metrics with a dynamic, tag-driven approach to dashboards and alerting to easily visualize, analyze, and troubleshoot your entire AWS infrastructure including SAP.

    Ratings and reviews

    4.4
    611 ratings
    17 AWS reviews
    |
    594 external reviews
    External reviews are from G2  and PeerSpot .

    Filters

    Review type

    AWS Marketplace reviews
    External reviews
    Reviews (611)
    Manish L.

    Clear, Unified Observability with Powerful Distributed Tracing

    Reviewed on Nov 04, 2026
    Review provided by G2
    What do you like best about the product?
    It provides a clear, overall picture of what’s happening inside our applications. From a single place, we can monitor API response times, database queries, errors, server resources, and overall application performance. The distributed tracing feature is especially helpful when working across multiple services, since it makes it easier to pinpoint where requests are getting delayed. The dashboards are also quite flexible, and once everything is configured, it becomes much simpler to stay on top of production issues.
    What do you dislike about the product?
    The initial setup and configuration can take a while, especially if you’re monitoring multiple services across different environments. Because there are so many features and options, the interface can feel overwhelming for someone who’s new to observability tools, and it takes time to learn where everything is. Pricing is another concern, since data ingestion can grow quickly as application logs and traces get larger. At times there can also be too many alerts, so you end up spending extra time tuning thresholds to cut down on unnecessary notifications.
    What problems is the product solving and how is that benefiting you?
    New Relic helps us spot application performance issues and production errors before they turn into bigger problems. Previously, debugging something across multiple backend services meant manually checking different logs and servers. With New Relic, we can trace a request end to end, pinpoint slow database queries, review error rates, and quickly see which service is responsible. This cuts down debugging time and makes it easier for developers to investigate production issues without having to rely on multiple teams.
    Marco Aurelio G.

    New Relic monitoring agent

    Reviewed on Nov 04, 2026
    Review provided by G2
    What do you like best about the product?
    It was easy to install, and it’s straightforward to retrieve the logs from the server.
    What do you dislike about the product?
    It requires more resources, and it also needs an installation.
    What problems is the product solving and how is that benefiting you?
    Automating logs, monitoring, and refining alerts.
    Mohd D.

    Easy Setup, Powerful Insights, but Overwhelming for Beginners

    Reviewed on Oct 29, 2026
    Review provided by G2
    What do you like best about the product?
    I like that New Relic gives me a detailed view of my website and helps me diagnose every little bit so I can improve it. I use it to find slow SQL queries and functions, including PHP processes that take a lot of time. The interface is very good, with multiple graphs and different ways to view the data that make it easy to understand. Setup was very easy: I just added a snippet to my website, and it took about five minutes.
    What do you dislike about the product?
    I think New Relic can be overwhelming for beginners because it has so much to offer, with many tabs and so much data that it can be difficult to understand. I’d like a simple interface toggle so beginners can start with a simple view and advanced users can switch to more advanced features.
    What problems is the product solving and how is that benefiting you?
    New Relic helps me identify slow queries and functions on my website by giving me a detailed view into the processes, so I can fix them.
    Anonymous

    Easy-to-Use Monitoring with Deep Diagnostics, Despite a Crowded UI

    Reviewed on Oct 29, 2026
    Review provided by G2
    What do you like best about the product?
    I find New Relic easy to use and easy to dig deep into issues. I use it for server and application monitoring, and I value the database query explorer. The initial setup was easy.
    What do you dislike about the product?
    I sometimes find the New Relic interface too complex and overwhelming, with too many options and things on the same screen.
    What problems is the product solving and how is that benefiting you?
    New Relic makes it easy for me to monitor our infrastructure and applications.
    Sourabh G.

    A popular and feature-rich observability tool

    Reviewed on Oct 27, 2026
    Review provided by G2
    What do you like best about the product?
    It gives a clear picture of system performance, availability, and metrics. It’s a good tool for day-to-day monitoring and reporting. It also integrates well with different tools, and the query language is easy to learn.
    What do you dislike about the product?
    The pricing is a bit expensive, and it can get even higher as you add more integrations and manage a larger number of systems. Custom monitoring is also somewhat complex to set up and work with.
    What problems is the product solving and how is that benefiting you?
    Instead of manually checking multiple systems and logs, we can get a clearer picture of what’s happening from a single place. This helps us troubleshoot faster, identify issues more quickly, and ultimately provide a better experience for customers.
    Sarthak S.

    Excellent API Performance Visibility and Backend Health Monitoring

    Reviewed on Oct 27, 2026
    Review provided by G2
    What do you like best about the product?
    New Relic provides excellent visibility into API performance and backend application health. At PARK+, I used it to monitor API response times, track performance issues, and identify potential bottlenecks in the system. Its dashboards and monitoring capabilities made it easier to understand application behavior and investigate performance degradation. It is particularly useful for backend teams working with multiple APIs and services, as it helps narrow down issues and improves troubleshooting efficiency.
    What do you dislike about the product?
    The platform can take some time to get familiar with, especially when configuring dashboards, alerts, and advanced monitoring features. Depending on the volume of telemetry data, managing costs and deciding which metrics to track can also require attention. A simpler initial setup and more straightforward configuration for new users would improve the experience.
    What problems is the product solving and how is that benefiting you?
    New Relic helps monitor API performance, track response times, and identify backend application issues before they significantly affect users. At PARK+, it helped me investigate slow APIs, understand application performance, and troubleshoot production issues more efficiently. Having performance metrics and monitoring data in one place made it easier to identify bottlenecks and maintain the reliability of backend services.
    Raghavendra R.

    Detailed Performance Insights, with Room to Streamline MCP

    Reviewed on Oct 25, 2026
    Review provided by G2
    What do you like best about the product?
    I like New Relic's UI because it clearly shows, line by line, where there are problems and gives me detail about controller performance and running issues. I use it to check page- and controller-level performance, see where performance is lagging, and identify which query or code line is causing a production issue. When the UI is confusing, MCP gives me more detail, including how long a query took and how often the issue occurs. Once I understand it, New Relic is very smooth to use and takes very little time.
    What do you dislike about the product?
    I found the initial setup a little confusing, especially with multiple applications, and it needed some expert guidance. With MCP, I wish it would ask which app to check before running the tools, because otherwise it can consume a lot of tokens. Once I understood the setup, it was smooth to use.
    What problems is the product solving and how is that benefiting you?
    I use New Relic to see how long my controllers and queries take, where performance lags, and which lines have problems. Its UI gives me clear, line-by-line detail on controller performance and running issues.
    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.
    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.
    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?

    Amazon Web Services (AWS)
    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.