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 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.
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.
Head of API at a marketing services firm with 11-50 employees
Real User
Top 20
Dec 20, 2024
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.
IT Manager at a consultancy with 10,001+ employees
MSP
Top 20
Sep 5, 2024
It helps prevent issues but does not cause losses. The error messages and deep insights may help us find the root cause and resolve the issue. It could be bit better. We are looking at sorting the error loss by date, keyword, or something similar and grouping the logs with some keywords, like error.
Business Development Manager at a tech services company with 11-50 employees
Real User
Top 5
Aug 5, 2024
The product's initial setup phase is not straightforward to manage if you have no experience with installations, making it an area that can be improved.
New Relic is very slow, and the app is a bit frustrating to use, which is something that has been happening a lot in the past year. During the last six months, I have noticed that it has become extremely laggy. The irony stems from the fact that a tool used for performance measurement itself has so many performance issues. I think it has also become too crowded with too many features. I have been using New Relic for ten years, and over a period of time, it has added a lot of new tools and new profiles, which are great, but now the tool has become too crowded. Around 80 percent of the time, I use the tool only for basic use cases, which were all there even ten years ago. The tool has definitely improved the interface, which is good, but apart from the basic features that I need, there are all these features in the tool that crowd the tool's entire user interface, which becomes complex. I like Sentry because its main interface for error reporting and handling has always been very clean and focused while not being crowded with too many things, but I don't know about the solution's future. With New Relic, the tool seems crowded when it comes to its interface, which has too many features.
Documentation is one of the biggest things that I have a problem with since its documentation is not clear sometimes. Logging right now is something I want to improve. So, every log that you have has to have an issue. So logging needs to be probably set right. I would like to see more logging capabilities in the solution. If they can accept logs, they just can't report. So, I guess reporting on logging is something I want to see in the future.
The initial setup can be made easier. Like Mixpanel, New Relic can also have a step-by-step guide for the setup process. It needs slight improvements to be made in the user experience.
I would like for this solution to improve the automatic configurations of workloads and capabilities. In the next release, I'd like to see a better pricing structure.
One thing I'd like to see in any APM, especially New Relic, is the ability to use distributed transactions. When one microservice calls another, it calls another database and microservice. The entire data visualization layer will not be able to correlate from one microservice from end to end and return on that path. Distributed transactions would be a great addition that would make life simpler. Unfortunately, no APM has that end-to-end capability. When I say "distributed transactions," I'm not only talking about the database level. It needs more and better visualization of communications across various microservices and integration with logs.
New Relic APM is a good tool, and it has a database of failures, but it could use a list of customer-specific failures. For example, if my application went down last year, it should figure out why it went down and what the root cause is through artificial intelligence and machine learning. New Relic APM should be able to give my company advanced analytics through AI. The tool has a self-healing mechanism, advanced analytics, and the ability to send alerts, but in the next release, I'd like more improvement on that front, including better AI and machine learning.
Marketing Executive at a financial services firm with 10,001+ employees
Real User
Nov 29, 2022
There were some settings we had issues with. For example, a certain setting to change the time zone. If we change the time zone, it will take 24 hours to reflect the time zone and make the changes. It'll be great if the settings once we change them, reflect the change at least after one hour. That would be helpful so that we don't need to wait for one complete day to see the changes.
Senior Associate Consultant at a tech services company with 10,001+ employees
MSP
Oct 12, 2022
New Relic does enable frontend performance monitoring by default. However, when we are troubleshooting the issue, New Relic is not able to trace back to the service where the issue is. Other solutions, such as Dynatrace are better. Dynatrace provides security vulnerabilities for all applications and this is where New Relic lacks. Additionally, there should be more use cases for automation. From the application team's perspective, they should be able to identify the issue before it occurs. This is the main feature that any monitoring tool should have. New Relic was not able to trace back to the original method of the transactions where the issue occurred. This area needs to be improved.
Cloud Consultant at a tech services company with 201-500 employees
Consultant
Dec 28, 2021
There are times when you restart the engines and the servers have a unique ID for the host and you need to remove the server. It is difficult because some are on-premise and others are production hosts. Having downtime is not very good when updating. However, it is not a constant issue.
New Relic offers real-time application monitoring and insight into performance bottlenecks. Its customizable dashboards and APM integration provide efficient operational support, while server performance alerts ensure quick issue detection.New Relic provides comprehensive monitoring of application performance, tracking bottlenecks across databases and front-end components. Users employ it for server and infrastructure monitoring, as well as analyzing key metrics such as CPU and memory usage....
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 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.
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.
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.
It helps prevent issues but does not cause losses. The error messages and deep insights may help us find the root cause and resolve the issue. It could be bit better. We are looking at sorting the error loss by date, keyword, or something similar and grouping the logs with some keywords, like error.
There is room for improvement in the stability.
The product's initial setup phase is not straightforward to manage if you have no experience with installations, making it an area that can be improved.
New Relic is very slow, and the app is a bit frustrating to use, which is something that has been happening a lot in the past year. During the last six months, I have noticed that it has become extremely laggy. The irony stems from the fact that a tool used for performance measurement itself has so many performance issues. I think it has also become too crowded with too many features. I have been using New Relic for ten years, and over a period of time, it has added a lot of new tools and new profiles, which are great, but now the tool has become too crowded. Around 80 percent of the time, I use the tool only for basic use cases, which were all there even ten years ago. The tool has definitely improved the interface, which is good, but apart from the basic features that I need, there are all these features in the tool that crowd the tool's entire user interface, which becomes complex. I like Sentry because its main interface for error reporting and handling has always been very clean and focused while not being crowded with too many things, but I don't know about the solution's future. With New Relic, the tool seems crowded when it comes to its interface, which has too many features.
The solution must provide better support for Azure Web Apps service. The solution does not completely support the architecture of Azure Web Apps.
The solution needs to have staging.
Documentation is one of the biggest things that I have a problem with since its documentation is not clear sometimes. Logging right now is something I want to improve. So, every log that you have has to have an issue. So logging needs to be probably set right. I would like to see more logging capabilities in the solution. If they can accept logs, they just can't report. So, I guess reporting on logging is something I want to see in the future.
The initial setup can be made easier. Like Mixpanel, New Relic can also have a step-by-step guide for the setup process. It needs slight improvements to be made in the user experience.
I would like for this solution to improve the automatic configurations of workloads and capabilities. In the next release, I'd like to see a better pricing structure.
The price could improve.
Some AIOps are missing in New Relic APS, and I would like to see more features in this area.
One thing I'd like to see in any APM, especially New Relic, is the ability to use distributed transactions. When one microservice calls another, it calls another database and microservice. The entire data visualization layer will not be able to correlate from one microservice from end to end and return on that path. Distributed transactions would be a great addition that would make life simpler. Unfortunately, no APM has that end-to-end capability. When I say "distributed transactions," I'm not only talking about the database level. It needs more and better visualization of communications across various microservices and integration with logs.
New Relic APM is a good tool, and it has a database of failures, but it could use a list of customer-specific failures. For example, if my application went down last year, it should figure out why it went down and what the root cause is through artificial intelligence and machine learning. New Relic APM should be able to give my company advanced analytics through AI. The tool has a self-healing mechanism, advanced analytics, and the ability to send alerts, but in the next release, I'd like more improvement on that front, including better AI and machine learning.
There were some settings we had issues with. For example, a certain setting to change the time zone. If we change the time zone, it will take 24 hours to reflect the time zone and make the changes. It'll be great if the settings once we change them, reflect the change at least after one hour. That would be helpful so that we don't need to wait for one complete day to see the changes.
The solution should include more detailed reports for SQL database requests.
New Relic does enable frontend performance monitoring by default. However, when we are troubleshooting the issue, New Relic is not able to trace back to the service where the issue is. Other solutions, such as Dynatrace are better. Dynatrace provides security vulnerabilities for all applications and this is where New Relic lacks. Additionally, there should be more use cases for automation. From the application team's perspective, they should be able to identify the issue before it occurs. This is the main feature that any monitoring tool should have. New Relic was not able to trace back to the original method of the transactions where the issue occurred. This area needs to be improved.
The solution only supports the cloud platform and not on-premises. Therefore, they should assess supporting the licensing on-premises as well.
There are times when you restart the engines and the servers have a unique ID for the host and you need to remove the server. It is difficult because some are on-premise and others are production hosts. Having downtime is not very good when updating. However, it is not a constant issue.