New Relic Reviews

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.

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.

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.

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.

Before joining the FinTech sector, I worked in the insurance tech space as an application support and implementation engineer.

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.

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.

Public Cloud

Amazon Web Services (AWS)

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

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

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

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

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

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

New Relic is stable.

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

The customer support for New Relic is excellent.

Positive

I did not previously use a different solution.

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

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

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

Public Cloud

Amazon Web Services (AWS)

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

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

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

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

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

New Relic has been used for the past two years.

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

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

Public Cloud

Amazon Web Services (AWS)

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

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

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

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

New Relic is stable and reliable for me.

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

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

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

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

Private Cloud

Other

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

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

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

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

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

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

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

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

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

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

New Relic is stable.

New Relic has handled changes in the environment very well.

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

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

We did not evaluate other options.

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

I have worked with New Relic for approximately three to four years.

The best features in New Relic include its numerous API integrations and a good source of support. The support is excellent, and they provide blogs and forums. There is something called NRQL, New Relic Query Language, which can be used to query many things and retrieve data. Using API calls allows you to automate and pull a dashboard out of it, making manipulation easily done. These are some things I have done with New Relic as an end customer.

It reduces the operational overhead. Your data is monitored end to end, which could be directly linked with the SLA and SLO. That is the main thing.

New Relic can be improved by incorporating an automated incident analysis solution. They have comprehensive enterprise data, and based on that, they could generate and forecast things. They can predict anomalies, and even though anomaly prediction is already there, it can be improved.

Using real-time data, if there are any malicious patterns or something happening, they can identify those. They really need to stream the data and have something important running, such as predicting or identifying any suspicious activity. If they could develop these features, it would be very beneficial.

In my opinion, New Relic is a stable solution.

I would rate the technical support from New Relic as nine out of ten.

Positive

The initial setup of New Relic is pretty easy. It is very well documented.

The deployment of New Relic was done in-house.

I am not sure about ROI as I have not gone over that. However, it reduces the operational overhead. Your data is monitored end to end, which could be directly linked with the SLA and SLO. That is the main thing.

I have experience with various Amazon solutions, but I am not really involved in the data-related role. My scope is that I work within some specific services. In my organization, I am part of an engineering team where I work only with these specific things. I love to explore these things, but I do not have much hands-on experience, and I am not a subject matter expert.

I have worked with Zabbix and Grafana. Grafana is a visualization tool that allows you to ingest existing data and visualize it while taking a report out of it. It is a great monitoring dashboard tool. Currently, in my company, they are using other solutions DataDog and New Relic. However, I would choose Grafana. It is open-source, and the enterprise edition is also available. The open-source version is more than enough for an enterprise to have their data visualized.

New Relic is suitable for banking domains, investment brokerage products, or anything related to high-security data. Organizations might use New Relic because they want their data stored and they want the support. It works as a whole monitoring solution, including logging, monitoring, and application profiling tools. It has a good set of API for managing alerts, and many automations can be done in New Relic. It is an enterprise solution that requires payment.

I rate New Relic eight out of ten.

On-premises

Amazon Web Services (AWS)

My main use case for New Relic is to monitor application health on a daily basis. Starting with my day, I go to the dashboards to check how the application health is and any alerts already triggered for the application, whether it concerns disk, memory, CPU, or how the applications are running. Recently, we had a slow query running for the application, which was really the bottleneck as it took a long time for the application to respond, and we found it out by using New Relic to identify the slow query, which really helped me.

To troubleshoot and resolve the slow query issue once New Relic points it out, I generally go to the Application Performance Monitoring, which is APM, and then I check in APM for the query where there are different tabs, including one for the database. After that, I go and check the database, which shows what query is taking how much time. Since we are using Java applications, we can see how much time the queries take. We are also using some Cassandra for caching purposes, which can show that query. I checked with the developer about a simple select query that took a long time, and after I spoke with them, they fine-tuned that query, resolving the issue. New Relic proved really helpful in finding out the slow query.

New Relic is easy to use even for someone with no knowledge; by seeing the dashboard, they can easily find out the application's health and notice what is happening. This is a significant advantage compared to other APM monitoring tools, and another aspect I appreciate is its good alerting mechanism, which can throw alerts and can be configured with PagerDuty or Slack, allowing easy checks on triggers and troubleshooting using New Relic.

The best features New Relic offers include APM, which stands out most prominently, along with Synthetic monitoring, which also really helps. Infrastructure can be checked too, but since our organization is using these modules, through APM, I can see the heap memory, application CPU, and memory, which are crucial from the application's perspective. Multiple alerts can also be configured using APM, making it extremely interesting.

Synthetic monitoring is similar to a mix of APM and other tools. I can create multiple dashboards using Synthetics, allowing me to view synthetic monitoring in a single shot, which gives good confidence in checking my day-to-day work.

New Relic features customized monitoring, which allows us to customize and distribute dashboards, and it really helps us. New Relic has positively impacted my organization by providing faster detection capabilities, allowing us to easily find issues, which is the best advantage. We can also improve application performance by finding the actual root cause of issues, which I find really beneficial.

Regarding faster detection and improved performance, there are instances where, when the application specifies its heap memory around 20 GB, and it tries to reach about 90%, New Relic immediately detects the heap memory alert, sends it over Slack, and even calls us using Slack. This lets us easily detect the issue and delve into what Java is causing that high heap memory usage, allowing us to investigate further.

New Relic can get pricey for larger organizations.

Specifically, it's the pricing for larger scale deployments that could be improved.

I have been working in my current field for almost six years, and I have been using New Relic for almost five years.

New Relic is 100% stable in my experience.

The scalability of New Relic is very high, as I have never seen any downtime issues or similar problems.

I have reached out to customer support multiple times for various cases, particularly for customization such as creating dashboards, and my experience has been good.

Positive

I would advise others looking into using New Relic that it is friendly, easy to use, and distributed, with NRQL queries that you can easily write to check for issues.

New Relic is a very good product in the market compared to others; it is really helpful for beginners as they learn about this product, and it proves beneficial when performing longevity tests to find latency issues, making it very interesting to identify where actual latencies occur, resulting in it being an excellent product from my perspective.

On a scale of 1-10, I rate New Relic a 10 out of 10.

Hybrid Cloud

Google

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

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

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

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

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

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

I have been using New Relic for three years.

New Relic is very stable.

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

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

Positive

I have not previously used a different solution.

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

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

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

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

Hybrid Cloud

Other

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

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

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

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

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

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

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

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

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

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

Positive

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

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

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

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

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

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

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

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

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

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

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

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

I have been using New Relic for one year.

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

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

Neutral

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

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

I rate New Relic seven out of ten. 

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

Other