Monitoring has improved Java microservices and enables proactive issue detection and alerting
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?
Easy-to-Use Metrics and a Clean Interface
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.
New Relic Unlocks Powerful Insights with Versatile Dashboards and Browser Monitoring
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.
Clear, Fast Application Performance Visibility with New Relic
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.
Intelligent monitoring has reduced incident toil and has automated root cause analysis
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?
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?
We previously used Grafana, Prometheus, and Datadog, but found them to be costly. In addition, Grafana and Prometheus do not offer the same range of features that New Relic provides, which is why we switched.
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.
Monitoring large scale applications has improved troubleshooting and reduced downtime
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?
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.
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.
End-to-End E‑commerce Monitoring That Quickly Pinpoints Checkout Friction
What do you like best about the product?
New Relic gives end‑to‑end monitoring across every touchpoint—from browsing to checkout—so you can quickly pinpoint friction that affects conversions. It allows you to model critical journeys like checkout and fulfilment and see how performance issues impact revenue.
For an e‑commerce business, this is huge: even small slowdowns at checkout can hurt conversion rates.
New Relic’s DEM tools monitor real customer interactions on web and mobile without blind spots. It provides:
Real‑user monitoring
Synthetic checks
Session replay to view exactly what users experienced
This helps diagnose issues fast and connects frontend errors with backend causes.
What do you dislike about the product?
New Relic can feel complex for newcomers. The platform is powerful, but understanding all its dashboards, APM details, and configuration options takes significant time.
Many reviewers note that onboarding requires a noticeable investment, especially for teams new to observability tools.
What problems is the product solving and how is that benefiting you?
Lack of visibility into the customer journey
Problem:
E‑commerce teams often struggle to understand exactly where users encounter friction—slow product pages, checkout failures, or payment gateway delays.
How New Relic solves it:
New Relic provides end‑to‑end visibility of critical journeys like checkout and fulfillment, showing which technical issues directly impact revenue
NewRelic Traces Make Diagnosing and Fixing Issues Fast
What do you like best about the product?
As a boots-on-the-ground feature developer, I find NewRelic very helpful for diagnosing issues, pinpointing their exact causes, and resolving them ASAP.
The application traces help you to pinpoint exactly where you need to be looking in your code, rather than fumbling around with complex logs or arcane error messages.
What do you dislike about the product?
NewRelic is a massive platform, and its interface can be a bit overwhelming. I also think the search functionality is a bit limited – you can only search on certain attributes, and sometimes they aren't what you expect.
What problems is the product solving and how is that benefiting you?
New Relic is my main tool for helping to debug production issues with our code.
Proactive monitoring has protected critical APIs and supports real‑time observability goals
What is our primary use case?
I used New Relic for instrumenting logs and designing different dashboards for a telecommunication company. During iPhone launches, I monitored all orders, how many orders were sold, what iPhone models had been sold, and the quantities. I used New Relic to keep the status of all of this information, and I also used New Relic for synthetic monitoring.
New Relic provides a really good dashboard and view, allowing me to filter by different options and different New Relic models. Everything shows how one system connects to another, how orders go to logistics, and delivery on the same screen, which really stood out to me. For synthetic monitoring, I used different APIs, both scripted and browser-based, and monitored them. Whenever any API goes down, I get notified instantly, which is a great feature.
I use New Relic for webhooks, setting up notifications using webhooks and getting notified in the Teams channel directly.
What is most valuable?
Synthetic monitoring and reactive monitoring are the best features that I found in New Relic. Using a simple Node.js script, I can monitor different APIs in production every one minute, two minutes, or five minutes. I don't have to monitor reactively but proactively, and the agent makes a call to my API every five minutes, allowing me to know when my API is down and helping with production downtime.
Proactive monitoring definitely impacts my team's workflow and production reliability. There was an instance when we had a very critical API that I monitored using proactive monitoring and synthetic monitoring, and it went down for a few minutes. I got notified in my Outlook, so I notified the dedicated team for that, and they fixed the issue even before the customer noticed, saving us a lot.
New Relic has positively impacted my organization by helping with our observability goals. We had 20-25 goals to have observability in place, and New Relic was a great tool to achieve that goal through creating dashboards, setting up synthetic monitoring, and different kinds of alerts. New Relic helped us achieve those observability goals by significantly saving downtime. Whenever an API is down, we get notified instantly and take actions, which saves us from downtime, and alerts definitely help us to take action quicker, even before the real customer notices any issues.
What needs improvement?
New Relic can be improved in a few areas. I noticed that some things can be easily done through Splunk but not through New Relic. For example, creating dashboards in Splunk allows you to instrument different kinds of data and API logs and scrape the data to create a dashboard. For New Relic, you have to use different accounts, so when tracing any API call, you have to move from one system to another, which are all in different accounts. You would need different account access to see end-to-end tracing, whereas in Splunk, you can see everything in one place.
For how long have I used the solution?
I used New Relic in my previous job for about a year.
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
New Relic's scalability is good.
How are customer service and support?
The customer support for New Relic is good. I would rate the customer support on a scale of one to ten as a nine.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
We previously used Splunk and needed to explore New Relic for synthetic monitoring, so we moved to New Relic.
How was the initial setup?
We did not purchase New Relic through the AWS Marketplace.
What was our ROI?
I have seen a return on investment, specifically in terms of time saved.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing for synthetic monitoring is that minions used to cost a lot and we cannot set an unlimited number of synthetic monitoring.
Which other solutions did I evaluate?
Before choosing New Relic, we evaluated OpenTelemetry, but we don't have the skills for using OpenTelemetry.
What other advice do I have?
New Relic is a good tool that you should utilize for monitoring your front end, back end, and different APIs. If you have any critical APIs like payment, which you cannot afford to go down, you can definitely use synthetic monitoring to monitor it and get notified in your Teams channel, Outlook, or mail. I would rate this product an eight overall.
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?
End-to-end tracing has improved root cause analysis and provides clear performance insights
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using New Relic for more than seven years.
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
New Relic's scalability is good, and I can scale easily using the agents installed in my infrastructure.
How are customer service and support?
The customer support for New Relic is excellent.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I did not previously use a different solution.
What's my experience with pricing, setup cost, and licensing?
I have a long-standing relationship with New Relic, so dedicated sales teams engage with my leadership team and we finalize the costs.
Which other solutions did I evaluate?
Before choosing New Relic, I evaluated other options, specifically Datadog and Splunk.
What other advice do I have?
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.
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)
