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.

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.

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.

I have been using New Relic for three plus years.

New Relic is stable.

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.

The customer support experience was good, with faster troubleshooting provided by New Relic's support team.

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.

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.

I evaluated other options, including Datadog, Dynatrace, Coralogix, Grafana, Prometheus, Azure Monitor, and AWS CloudWatch.

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.

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.

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.

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.

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.

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.