New Relic Reviews

My main use case for New Relic is monitoring all the servers which are hosted in my environment. The agents installed on the servers keep sending the details to the dashboard. Whenever the server is not available or online, we immediately receive an alert to our email indicating that the host is not available along with the reasons. This helps us to come to know whether the server is actually unavailable or not, and enables us to take necessary action. Apart from that, CPU utilization, disk utilization, and everything else is monitored by New Relic. If any threshold value is crossed, we immediately receive an alert and take the needed action for those situations.

Real-time monitoring is the best feature New Relic offers. What stands out to me about the real-time monitoring is the speed of the alert being the major aspect. When a server goes offline, we immediately receive an alert. The dashboard is very much interactive and we receive all the information from there. Monitoring is a crucial thing for every work, and New Relic is doing a very good job in this part. We are getting real-time alerts, and many of the issues are being resolved with timely alerts helping a lot to remediate those things. If something happened and we got to know about it lately, so much disruption would happen. New Relic is helping a lot in these scenarios.

I would not say downtime decreased, but whenever a server goes down, we are able to take immediate actions in those scenarios. That helped a lot. I would not say the downtime is reduced, but the time period during which the server goes down has decreased so much. That helped a lot.

In the dashboard, if they could show a little more metrics regarding the application and related things, that would be how New Relic could be improved. Currently, there are things showing from the server level and application level, but it can be improved. That is what I felt.

Regarding user interface, I do not feel much concern, but for some kind of issues when we are trying to get support from the New Relic team, their SLA seems to be long. They are taking seven to ten working days for resolving some kind of scenario or issue. That is a bit difficult for us. If they could improve the customer support by reducing their SLA within three to five days, if they could remediate everything, that will be so much helpful.

When it comes to the customer support part, I felt they need to be a little more improved on that part. The support overall is good, but they can improve. That is the reason I have given it eight out of ten.

For the last four years, I have been using New Relic in my current organization.

New Relic is stable.

It is very much scalable.

When it comes to the customer support part, I felt they need to be a little more improved on that part. The support overall is good, but they can improve. That is the reason I have given it eight out of ten.

Positive

Previously we were using a tool called Eggplant monitoring tool. There were a lot of issues with that. That is how we decided to change the monitoring in my environment, and a lot of research happened before New Relic came into the picture.

There is return on investment because since we reduced the downtime, we can definitely save a lot of money within that period. The tool also helps the employees in their work.

There were options like Dynatrace and SolarWinds that we explored, but New Relic is the closest one which aligns with our needs and uses.

Monitoring is a crucial thing for every work, and New Relic is doing a very good job in this part. The major concern from my side is that they should be a little more faster with the resolution part regarding customer support.

It is a great platform for monitoring. If you have a lot of servers in your environment and you need real-time monitoring, I would definitely suggest New Relic. It is a great tool to explore.

We are just consumers of this tool and do not have any other relationship with this vendor. I have given this review an overall rating of eight out of ten.

Our day-to-day use case is to look at our application performance and our overall Apdex scores, and we do take care of our page load times and we look at overall trends of traffic spikes, our page visits, and what not. We monitor our CPU utilization and our performance of our new components and page time loads, and we take these graphs seriously and we act accordingly. We monitor a lot of other important key metrics from New Relic, including our error rate and our production performance.

We have deployed our new microservices, and we have continuous monitoring on New Relic to take care of the application and the service performance and the traffic metrics from New Relic. We have configured some custom dashboards and we have some third-party integration of New Relic with Opsgenie as an event dispatcher. We do have custom notifications for on-call support, and our Slack support, so these custom dashboards and custom metrics make our job easy to monitor our new services and performance of the new services.

We rely on New Relic dashboards for a lot of other key events, especially when there is a marketing campaign or when we know that our application traffic will spike. We monitor our CPU utilization and our error rate so keenly from New Relic. We will increase some of the thresholds and we will have some custom metrics to capture this new feature or new expected market spike, creating specific brand metrics accordingly.

New Relic offers custom dashboards and incident and alerting management with third parties like Slack and Jira, and it also has an AI or ML-based anomaly detection system where we can smartly identify whether there are predicted error rates for specific services or components of the UI.

We rely mostly on incident and alerting integrations and custom dashboards, while the AI and ML-based anomaly detection is a one-time configuration that handles events in a generic manner to predict the next incoming trends of errors or unexpected traffic spikes. These custom dashboards are specifically created for our application segment, and we heavily rely on creating multiple queries or custom queries for these metrics. For incident and alerting, we update metrics and the incident response team to quickly resolve issues based on our specific use case.

New Relic has positively impacted our organization by reducing errors, improving performance, and saving time. It has been an awesome tool for identifying errors on time, and even though it does not directly change our code, we use New Relic to identify errors ahead of any other application performance monitoring tool. We continuously improve performance by monitoring metrics, dashboards, error rates, and custom metrics.

For our end-to-end use case, New Relic is completely satisfactory, and we extensively rely on its features for our day-to-day life. I would like to have more AI and ML-based suggestions and algorithms from New Relic, and while the New Relic dashboards and UI are customizable, they can sometimes lead to a clumsy behavior. A smart AI assistance to organize our dashboards and explain features and functionalities can be a wish-to-have feature to help us leverage what New Relic offers.

As I mentioned earlier regarding wish-to-have features, New Relic can improve by incorporating more AI insights. When there is a component or UI customization, having a smart AI agent to guide users on customizing New Relic would significantly ease the process. This helps users who possess a technology-specific skill set and might find a learning curve overwhelming when using complex applications like New Relic or other performance-related tools.

I have been using New Relic for more than three to four years now, and we use New Relic extensively as our daily visit for our coffee time. We will be monitoring the dashboards and we have some of the integrations with Slack and then our teams and then our mailing systems. We extensively use New Relic to monitor our application performance, degradations, and then our Apdex scores.

New Relic is completely stable in our environment, and we have not experienced any issues internally regarding logging or lags with the service.

New Relic is completely scalable for our use case. We currently use New Relic for tens of thousands of developers and hundreds of teams within our organization, and we have not encountered any scalability issues, maintaining isolated application sections along with custom dashboards accessed by specific teams.

Customer support from New Relic is very good, and we rarely need to create support tickets. Our dedicated team engages directly with New Relic support to address any issues, whether related to internal downtimes or external factors like Cloudflare or AWS downtimes.

Positive

Prior to New Relic, we were using Sumo Logic, which we found to be outdated and frustrating, particularly in its environment segmentation and log analysis time. The integration experiences with New Relic greatly surpass those of Sumo Logic, providing us with a modern and effective application monitoring solution with enhanced dashboard visualization capabilities.

There is a definite return on investment for New Relic, as we would not have invested in building its infrastructure if there were no returns. We track metrics related to our integrations with New Relic internally in Jira, using story points to measure how much New Relic reduces our application monitoring overhead. While we do not have a dedicated resource solely for New Relic, our full-stack developers share responsibilities on multiple fronts, including working with New Relic.

Regarding pricing, setup cost, and licensing, these aspects are managed at our organizational level, so it is not just my individual use case contributing to the costs. However, considering the features New Relic offers, the pricing or cost setup has not been a blocker for our budget.

Before choosing New Relic, we evaluated options including Splunk and other performance monitoring solutions. However, New Relic stood out as an exceptional tool, and we made a seamless transition from our previous alerting system to unify all teams under New Relic without hesitation.

For our faster incident response, we almost respond to an incident in no time thanks to thresholds and alerting metrics being properly in place. We have immediate responses upon finding incidents, and for reduced downtime, we take these metrics seriously to dig deep for root causes. Regarding improved user experience, we experiment with our application features using A/B testing, which helps us monitor trends and user interactions effectively. For example, we created a revamped website with modern components and ran a 50/50 A/B test on traffic, gaining insights on user preferences between the new and old design, which we tracked through New Relic.

I would suggest that teams interested in New Relic start by learning about application performance monitoring systems. To effectively utilize all New Relic features, understanding the purpose and integration of New Relic within your system is essential. With a solid foundation of why New Relic is needed, users will observe rather than merely look at system data, while being patient to learn and configure these systems effectively. I have given this review a rating of nine out of ten.

We mostly used to do creation of dashboards and creating alerts as per the conditions and setting up some NRQL queries, or New Relic Query Language, to make different kinds of conditions and policies to receive alerts whenever we receive any error or spike in request time, response time, etc.

New Relic's NRQL query language is what I appreciate most because it is similar to SQL queries. We are able to check the exact timestamps whenever we need to find the logs and can find out proper errors without any complication in the queries. Secondly, their alerts and condition settings are valuable because there are direct links and direct openings for alerts and condition entities where we can check whatever alerts we created. We can check the conditions and understand how this alert got triggered. Additionally, I appreciate the dashboard view, where we can create whatever dashboards we needed.

New Relic must be integrated with real multiple platforms. For example, Elasticsearch has some capabilities where you can collaborate it properly with AWS services also, similar to how CloudWatch works. There are some differentiations between CloudWatch and New Relic—CloudWatch does not have the dashboard, but New Relic does. CloudWatch does not provide proper logs, but New Relic can provide them. However, I need New Relic to have a real direct connection with any type of cloud that an organization uses. We can do this with Prometheus and Grafana, so I was looking for the same integration with New Relic as well.

New Relic can do better with integration with the multiple clouds. This is not happening right now properly, or it might be my organization is not using it correctly. But right now there is no such kind of proper integration directly with the cloud services so we are able to fetch the real-time logs at the same time.

Additionally, it was a little expensive for my organization because at the time of review, I tried to connect with the marketing team. They told me that it is a real, real a little bit expensive as per the data ingestion and usage. Furthermore, alert policies sometimes take time for new users to understand. Some of the things in NRQL—because I am using it for more than five years, I am very familiar with it—but for new users who are new to New Relic, there is a little difficulty with that.

I have been using New Relic for more than five years in my career.

Sometimes it works real slow, but I think it depends on the organization to organization usage. Because we mostly use it for organizational purposes rather than for personal work, but to be honest, the experience of New Relic is a little slow as compared to the other applications. New Relic lags sometimes. It has not crashed in my work experience.

Adding more stuff into New Relic to handle is not an issue. New Relic is highly scalable and its build quality is very easy for handling to startup, enterprise, scale up, and workloads. It is also suitable for cloud native architectures, SaaS, or software as a service, and for high volume data ingestion also. NRQL is also very quite easy for scaling. If we need to query huge data efficiently using NRQL language, we are able to filter it by the exact timestamps and pod information as well as post region, versions, and services. New Relic is highly scalable compared to the other applications.

To be honest, till now we did not get any such kind of big outage which makes us directly contact to the customer care support team. What happened in my scenario was about two to three years ago when I was working for the application support, and we needed some kind of thing where actually my teammate was trying to ask a new thing to add in New Relic. He needed support, and he did not face any kind of issue. Over the call bridge he made, there was no such kind of issue. They are very polite and helped him out.

Positive

I basically tried to use Site24x7, which is quite good. And Amazon CloudWatch also. Because Site24x7 gives us mostly full monitoring for the applications, infra, and other network kind of things. And it is a little simpler setup as compared to New Relic. And for CloudWatch, it is a part of Amazon AWS web services. So it gives us AWS native monitoring for logs and metrics and the alarms.

I prefer most of the time New Relic, but sometimes if New Relic goes kind of slow or laggy, instead of that, sometimes I use AWS CloudWatch, to be honest.

I just wanted to mention that if I don't have to go for the CloudWatch because sometimes we are not able to fetch the logs properly at the particular period of time and sometimes as per the new users also, if they are not able to share this log or the specific timestamp they need. So I go further with the Prometheus and Grafana because they are cloud native systems, plus they include the excellence with the Kubernetes.

When we did deployment a long time ago, there was no such kind of issue with New Relic at that time of deployment because we were easily able to set it up. If we want logs and trace enablement, it is really very easy, and the same applies to log forwarding also, creating a dashboard or we need a default dashboard also.

We mostly do this with one person, but in the shadow we need only one person to guide them or if anybody needs a support. It depends on the type of deployment, meaning how much things you have to deploy. Sometimes if it is going to take a real big time, so we require to take a shadow support for us. One person can do it easily.

New Relic is quite good, not so much fast, but quite good. Overall for everything, I would rate this product a nine. My overall review rating for this product is 9.

My main use case for New Relic is for the visualization of performance tests. I use New Relic for visualizing performance tests to understand whether the system I'm working on works as expected under a heavy load, and this is mostly related to Kafka systems. I usually send a lot of events via a Kafka topic to the system and check how many pods are available of the services, how many partitions are in use, and CPU usage.

Beyond my main use case, I also use New Relic as an investigation tool during incidents. It is very helpful when I need to examine how some services behaved based on CPU usage and memory, which is quite helpful, especially when looking into a deep understanding of what is occurring. For example, our services are Java-based, and I need to examine how some of the Java memory areas were occupied, and New Relic provides that information.

In my opinion, the best features New Relic offers include its quite universal query language, which I can use quite easily and have good visualization based on that query.

What I appreciate most about the universal query language and its visualization is mostly for understandability. The query language is quite understandable, and the problems mostly lie in understanding what data I need to pick up, not about how I need to query that data. Understanding how that works is very simple, especially regarding the query language for time series and the time frame I need to examine. The query language is quite easy to understand.

New Relic has positively impacted my organization regarding my main area of interest, which is performance tests, and by using New Relic, I received a lot of information to improve my systems. It is very helpful for incident investigation.

When considering how New Relic can be improved, the only thing that could be a bit confusing is that there are many things in New Relic, and sometimes I need to know where to find some visualization and some data that is flowing to New Relic from my system. It is not obvious for newcomers to understand where to find that data and where to look for it.

The needed improvements are mostly an issue for the company that uses New Relic. Whenever I create a new dashboard or other items, I need to document what I have done and put it into documentation. I believe that documenting is all that newcomers need.

I have been working in my current field for about five years.

New Relic is stable based on my experience, as I have not seen any problems with the UI. However, there could be problems or hiccups with the integration with Java-based services and microservices. I have seen logs indicating that the service is not able to send the metric or custom metric to New Relic, but that is mostly due to some internal infrastructure specifics.

New Relic's scalability is good based on my experience, and it can handle my organization's needs as they grow.

I have not interacted with customer support for New Relic because I did not have a chance to do so, as there were no problems with New Relic.

Before using New Relic, I used a combination of Grafana and a relational database, but that was an ad hoc solution for me to visualize the data that was not in New Relic. Mostly, I use New Relic if it is possible.

I have a separate team for New Relic configuration and maintenance, so I do not know those details.

I have a separate team for New Relic configuration and maintenance, so I do not know those details.

I do not know whether my organization has seen a return on investment from using New Relic, but it has definitely shortened the time of incident investigation.

Regarding my experience with pricing, setup cost, and licensing for New Relic, I have the same answer. I have a separate team for handling New Relic, so I do not know the details of the deployment, pricing, and buying.

I cannot answer whether my organization evaluated other options before choosing New Relic, but I am sure they chose based on several options.

I do not have anything else to add about the features, as that covers everything I wanted to discuss about New Relic.

When sharing a specific example of how New Relic helped me improve my system and resolve an incident, there was an incident regarding a database when I examined the memory distribution in a Java machine. I quite easily examined the memory distribution during the time I had that incident and understood, based on what memory area of the Java Virtual Machine was heavily occupied, what I needed to do to optimize my service.

I do not have advice to give to others looking into using New Relic because advice is about how the person should use it. However, it is quite simple, and I do not think that there will be any problems with that. I would rate my overall experience with New Relic an eight out of ten.

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 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.

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.

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.

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.

I used New Relic in my previous job for about a year.

New Relic is stable.

New Relic's scalability is good.

The customer support for New Relic is good. I would rate the customer support on a scale of one to ten as a nine.

Positive

We previously used Splunk and needed to explore New Relic for synthetic monitoring, so we moved to New Relic.

We did not purchase New Relic through the AWS Marketplace.

I have seen a return on investment, specifically in terms of time saved.

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.

Before choosing New Relic, we evaluated OpenTelemetry, but we don't have the skills for using OpenTelemetry.

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.

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.

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.

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.

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.

I have been using New Relic for the last five years.

In my experience, New Relic is very much stable.

New Relic is very much scalable for our organization.

We have excellent customer support with New Relic.

From the start we are using New Relic and did not previously use a different solution.

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.

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.

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.

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.

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.

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.

My main use case for New Relic is monitoring performance. I use it to check the logs for any failure in applications, as well as checking the CPU and memory usage.

A quick, specific example of how I've used New Relic to solve an issue is with our SaaS applications. Sometimes an issue arises, and I need to look into our applications in the portal to see the errors. For instance, we have encountered an internal server error that prevents our applications from running. I then click on the errors to see more details and check the logs, including timestamps when the issue occurred. Recently, New Relic launched Log Patterns, enabling me to see different errors with patterns such as an error occurring 17 times in the last 15 minutes. I can use these attributes to filter by account services and agent names for infrastructure issues, allowing me to identify and fix the errors.

New Relic helps my team by getting alerts for high CPU usage. I need to check which server it is happening on. After identifying the server, I log in, go to the task manager, and kill the particular process that consumes excessive memory. This action results in the CPU usage coming down, and due to New Relic's alert, I effectively resolve issues, ensuring our application runs smoothly.

In my opinion, the best feature that New Relic offers is Log Patterns, as it efficiently fetches logs for each failure I encounter. This feature has proven to be extremely useful for me.

The Log Patterns feature helps me in my day-to-day work by identifying the number of times a particular issue reoccurs over a specified period, informing me of its frequency during that timeframe.

I would mention that I can use various filters in New Relic, such as filtering by infrastructure, host name, and server names. Filtration is an incredibly useful feature in New Relic as well.

New Relic has positively impacted my organization by making it easier to catch failures so I can resolve them quickly and take action. Previously, I did not receive notifications, and a person had to check constantly. Now New Relic manages this and alerts me to any issues, allowing me to take necessary actions and preserve my SLAs.

A specific outcome showing how New Relic helped my team is that downtime has decreased by around 15 to 20 percent in my current organization while using New Relic.

New Relic can be improved, particularly by enhancing the UI, which is currently a bit off. Making it more attractive and interactive for customers, similar to Grafana's UI, would be beneficial.

I have been using New Relic for around three years.

New Relic is stable in my experience.

The scalability of New Relic is really nice.

The customer support for New Relic is really good. Whenever I reach out to them, they are helpful.

I have used Grafana before New Relic in my previous organization. In my current organization, I only use New Relic.

I do not believe our organization evaluated other options before choosing New Relic. My director, who uses New Relic in another project, is impressed with this tool, so we likely opted for it because of that recommendation.

My advice for others looking into using New Relic is that it is a really useful tool. Before starting to use it, you should refer to its user guidance documents, as they are systematically created and truly helpful. I would rate this product a 9 out of 10.