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.
New Relic Solutions [Private Offer Only]
Carahsoft Technology Corp.External reviews
External reviews are not included in the AWS star rating for the product.
Real-time alerts have reduced server outage impact and support fast incident response
What is our primary use case?
What is most valuable?
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.
What needs improvement?
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 how long have I used the solution?
For the last four years, I have been using New Relic in my current organization.
What do I think about the stability of the solution?
New Relic is stable.
What do I think about the scalability of the solution?
It is very much scalable.
How are customer service and support?
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.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
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.
What was our ROI?
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.
Which other solutions did I evaluate?
There were options like Dynatrace and SolarWinds that we explored, but New Relic is the closest one which aligns with our needs and uses.
What other advice do I have?
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.
Improved incident detection has reduced response times and supports better customer agreements
What is our primary use case?
How has it helped my organization?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
What was our ROI?
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.
What other advice do I have?
Pricing is primarily an area of concern. The overall rating for New Relic is eight out of ten.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Has improved monitoring efficiency with robust alerting and automation features
What is our primary use case?
I have worked with New Relic for approximately three to four years.
What is most valuable?
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.
What needs improvement?
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.
What do I think about the stability of the solution?
In my opinion, New Relic is a stable solution.
How are customer service and support?
I would rate the technical support from New Relic as nine out of ten.
How would you rate customer service and support?
Positive
How was the initial setup?
The initial setup of New Relic is pretty easy. It is very well documented.
What about the implementation team?
The deployment of New Relic was done in-house.
What was our ROI?
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.
What other advice do I have?
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.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Reviewing diverse tools has streamlined error tracking with effective data analysis
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been working with New Relic for approximately six months.
What do I think about the stability of the solution?
New Relic was stable enough, and there were no downtimes or issues.
What do I think about the scalability of the solution?
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.
How are customer service and support?
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.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
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.
How was the initial setup?
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.
What about the implementation team?
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.
Which other solutions did I evaluate?
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.
What other advice do I have?
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.
Efficient network monitoring with robust APM and alerting capabilities
What is our primary use case?
I use New Relic for monitoring and observing the entire environment. It offers end-to-end monitoring and observability to predict potential impacts in the coming weeks. For instance, it can detect if two endpoints start consuming more bandwidth than usual, thereby providing more insights about potential impacts on the environment.
How has it helped my organization?
New Relic helps us maintain and shape the environment from a network perspective by providing end-to-end monitoring and observability. It offers insights into normal and peak behaviors, alerts us to any issues, and assists with remediation plans.
What is most valuable?
The APM feature is highly valuable as it can record session hosts, usage, and diagnose customer behaviors. Additionally, we can simulate user actions to assess the user experience. The alerting capabilities are also efficient, sending emails and desktop notifications, and providing remediation options.
What needs improvement?
The pricing could be improved as it is quite high relative to what is offered. The cost versus performance efficiency could be better. Apart from that, I don't need any specific improvements to the features themselves.
For how long have I used the solution?
I have been working with New Relic for over one and a half years.
What do I think about the stability of the solution?
New Relic is highly stable. I have never experienced an outage or any misbehavior with this solution.
What do I think about the scalability of the solution?
New Relic offers high scalability. It is quite flexible and can scale according to our needs.
How are customer service and support?
The technical support team for New Relic is good. I would rate them a nine out of ten.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Before New Relic, we did not use any specific solution for observability. We used normal monitoring tools.
How was the initial setup?
The initial setup of New Relic is super easy and straightforward. It involves proposing the solution to the client, activating administrative users, and customizing dashboards and alerts based on customer needs. Training and preparation made the process smooth and efficient.
What about the implementation team?
The deployment typically requires two to three tier-one or tier-two team members from the technical team.
What's my experience with pricing, setup cost, and licensing?
The pricing is relatively high. It can be quite costly compared to the performance efficiency, making it not very value for money, especially for smaller businesses.
Which other solutions did I evaluate?
We evaluated several other options like Datadog. However, after comparing prices and support, we chose New Relic.
What other advice do I have?
Do not implement New Relic until you have identified your needs and ensured that it meets your specific requirements. Proper assessment and planning are crucial.
I'd rate the solution eight out of ten.
Monitor applications, error logs, and Azure Kubernetes
What is our primary use case?
It is used to monitor applications, error logs, and Azure Kubernetes. We have used this as a self-hosted service in Kubernetes. We are not using it as an agent-based service. We self-hosted this New Relic on Kubernetes and maintained it as a service.
What is most valuable?
It can be integrated with PagerDuty and ServiceNow, which can auto-generate alerts and incidents and assign them to the concerned team. The dashboards can also be customized. We can also check the trends over the past year or so.
What needs improvement?
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.
For how long have I used the solution?
I have been using New Relic for two years.
What do I think about the stability of the solution?
I rate the stability an eight out of ten.
What do I think about the scalability of the solution?
I rate the scalability an eight out of ten.
How are customer service and support?
I haven't got any issues, so I should get support from a New Relic technical team. We hosted this on our own, and even though this is a self-hosted service, we are managing it.
How was the initial setup?
The initial setup is simple. We are using the Relic Chart deployment on Kubernetes, but it can be done in an hour and should not take longer.
What's my experience with pricing, setup cost, and licensing?
We just got a license for self-hosting and have set it up to do this.
What other advice do I have?
Some add-ons have been integrated. You can integrate with New Relic to get deeper insights into the logs.
I have worked on two monitoring tools: New Relic and OpeRant. In addition, I used Azure Monitor. It's completely different, monitoring only the infrastructure, not the applications. We need to know application insights about querying and everything, but it's more user-friendly.
Overall, I rate an eight out of ten.
Offers good ability to execute queries and analyze data
What is our primary use case?
I use the solution in my company to monitor the applications' performance and do some stress tests on the application. In our company, we use the tool to monitor the core application inside the data center. In some cases, New Relic is used to monitor users' access to the applications.
What is most valuable?
The most valuable feature of the solution is its ability to execute queries and analyze the data. For all the data, the tool has a specific function with which you can spot and mix the data or correlate the data wherever you want. It is easy to simulate and execute queries, and the availability of the data is very nice. The tool gives you a basic way to manage the data.
What needs improvement?
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.
For how long have I used the solution?
I have been using New Relic for a year. My company is in partnership with New Relic.
How are customer service and support?
I think the support of the tool is a good option. I think the support of the tool. I rate the tool's support an eight and a half out of ten.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I have experience with Catchpoint. With New Relic, you monitor the application from within. You monitor all the communication calls between the application and all the systems that the application needs to use, such as databases or servers. With Catchpoint, you can monitor user experience and how it interacts with the application, so we are monitoring from the outside, which is from the user to the application.
How was the initial setup?
For the product's initial setup phase, you need to have a background of doing installations. It is not a straightforward process, as you need to have more skills to do the tool's setup. The tool's setup phase is a little bit more complex but with the correct knowledge, it can still be very easy. You have to have some prior knowledge in installation to start with the tool's setup phase.
For the product's deployment phase, you need around 20 people because you need the people who do the installation and connections, along with the owner of the platform or the database, for which there is a need to create some access using New Relic. You have to do some configurations or partitions to install the agent. You need to have an expert on New Relic, as well as the user or the administrator of the infrastructure where the tool will be installed, so customizations can be done if needed.
The time required to deploy the solution depends on the amount of installations required and the architecture where the solution will be used. One agent can be deployed in maybe 30 minutes. Depending on whether you have everything in place and people know what they are doing, it may take 30 minutes to deploy the tool.
What was our ROI?
The tool can not be related to productivity. The product helps the development team that develops and makes changes in the applications. The tool helps a lot and provides a lot of information to the development teams so they do not have to do simulations. With all the information that New Relic provides, the development teams can just make decisions about the changes within the applications during the development. The tool offers information about the business process. With the tool, you can have all the information related to all the purchases from the marketplace and understand why the purchases were okay or why not, why the people that are logging in are not making any purchases, along with all the information related to the business process that are very helpful for the business.
What's my experience with pricing, setup cost, and licensing?
The product is neither cheap nor expensive, and I believe that it is a competitively-priced tool.
What other advice do I have?
I don't know how the alerting mechanism in New Relic has improved our company's response time. I am more into the demo part, so I am not a user of the tool.
I rate the tool a nine out of ten.
Offers a good interface that helps users quickly find bottlenecks in the area of performance
What is our primary use case?
I use the solution in my company for predominantly API response time. It is used to measure API response time.
What needs improvement?
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.
For how long have I used the solution?
I have been using New Relic for ten years. I use the solution as an end customer.
What do I think about the scalability of the solution?
It is a scalable solution. The product operates as a third-party or SaaS tool, so I believe that it has intra-scalability options.
How are customer service and support?
The technical support for the solution is very good. I rate the technical support an eight out of ten.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
My company has been using Sentry for error reporting, alerting, and monitoring.
How was the initial setup?
The product's initial setup phase was very easy.
One person can manage the product's deployment phase. Once the product is installed, it doesn't require much maintenance.
The solution is deployed on a cloud-based infrastructure.
The solution can be deployed in less than a day.
What's my experience with pricing, setup cost, and licensing?
I rate the product price a five on a scale of one to ten, where one means cheap, and ten means very expensive. I don't remember the product's exact price, but I know my company pays around 500 USD a month for two or three products.
What other advice do I have?
For monitoring purposes, I would say that the product has a good interface for quickly finding performance bottlenecks.
The tool gives a detailed audit of every piece of code, like how much percentage of time it takes, making it very easy for me to first locate the APIs that offer the poorest performance and then go deep dive into those APIs to see which part of the code base of that API is causing performance bottlenecks. Instrumentation becomes quite straightforward and easy with the tool's features.
I don't use the alerting system in New Relic.
My company uses New Relic only when we want to instrument APIs and for performance improvements, but we don't use it for error handling and error reporting since we prefer Sentry for such areas.
I rate the tool an eight out of ten.
An user-friendly solution that generates alerts whenever an anomaly is detected
What is our primary use case?
We use New Relic as an infrastructure management tool.
What is most valuable?
The tool's most valuable features were APM and core reliability. We get alerts whenever an anomaly is detected. The solution is very friendly.
What needs improvement?
The solution needs to have staging.
What do I think about the stability of the solution?
New Relic is stable.
What do I think about the scalability of the solution?
My company has around ten users for the product.
How are customer service and support?
The tool has good support. They have big communities and forums apart from the tech support.
How was the initial setup?
New Relic's deployment was easy. They had good documentation.
What's my experience with pricing, setup cost, and licensing?
The solution is cheap, but prices can go up when users grow.
What other advice do I have?
I rate the product an eight out of ten.
Easy-to-use, simple look and feel
What is our primary use case?
Our use cases were varied. We had front-facing applications, message brokers, API gateways, legacy applications running on RPC, and platforms. We used New Relic for instrumentation, and we discovered different metrics using it.
How has it helped my organization?
New Relic is an APM tool, similar to Dynatrace or Datadog. It uses an agent to discover metrics based on browser, mobile, and custom matrices. We can also develop synthetic monitoring. It has helped us in exploring the metrics.
What is most valuable?
The best feature of New Relic is its simple look and feel, making it easier to use than other tools.
What needs improvement?
One thing New Relic needs to improve is the user data schema. It wanted us to move from version one to version two, but that was difficult because we wanted to do single sign-on, and it couldn't support our Ping Identity platform. That's something New Relic needs to work on.
Another issue I have with New Relic is its suite licenses. It has a two-tier system: the full-stack observability, which requires a suite license, and the free version, which doesn't offer any peer review capabilities. It needs to change because having a suite license for a user who can only view the post-stack, not even the curated view, is a big no-no. Dynatrace or SAP don't have this issue.
I should point out one more thing about New Relic. We use it with OpenShift, and one of the issues we faced was that New Relic required root access, which was a concern because no admin in the world would give any third-party vendor root access. However, they seem to have corrected this in the next version.
For how long have I used the solution?
I have been using New Relic for three years. We're using version 8.0.
What do I think about the stability of the solution?
It has its limitations, but it is a stable solution.
What do I think about the scalability of the solution?
It is a cloud-based solution, so the platforms automatically scale.
How are customer service and support?
We struggled with the support.
Which solution did I use previously and why did I switch?
We are currently using Dynatrace. We have moved away from New Relic because of its shortcomings – the user data schema. They had two versions, and we couldn't group different entities under version one. For example, our enterprise applications are numerous, including activation, OSS, BSS applications, and so forth.
What's my experience with pricing, setup cost, and licensing?
It is an expensive solution. The licensing scheme is based on users having to have full stack observability, and there is no free version for non-seat license users to access what they want to see. I believe it's an expensive tool. They were not like that a couple of years back. Their new licensing scheme is based on full-stack capabilities; many clients would not like it. I would rate the licensing model a four out of ten. It is a very poor licensing scheme.
What other advice do I have?
It works well, and it has a very good look and feel to it. However, it also has its limitations. So some clients may like it. That's why they will be willing to pay more for New Relic compared to any other API. It's fine.
Overall, I would rate the solution an eight out of ten.