New Relic Reviews

A typical use case with New Relic, it’s an APM tool. We basically put the agent in, the agent discovers, and then we feed it onto predefined monitors with a controlled baseline. That baseline will then feed the problems that New Relic is detecting into PagerDuty. PagerDuty is our incident management tool. PagerDuty has something called Event Orchestration.

The incident that comes down from New Relic has a payload. We look at the payload, the attributes, and define rules in Event Orchestration. Let’s say the team wants to implement suppressions on alerts, some mutations, delays. They want to actually cross-engage a different team. So there are a lot of use cases that come about once we get the incident into PagerDuty from New Relic. New Relic obviously has the conditional baseline, which can be adjusted as we go along. So, that’s basically a staple activity that we perform with New Relic. Among other advanced use cases, which will take me a bit to explain here.

It’s like any other APM tool. One of the most outstanding features of any APM tool is the anomaly detection part. If there is logic that is going to detect the anomaly, with a predefined baseline that the system will produce over a period of time, for instance, a week, then keep adjusting it as you go along. That is one of the most useful cases of any APM tool that I feel.

One of the things that our enterprise actually had a challenge with was the licensing structure for New Relic. I remember there are two things that I feel are different in New Relic from Dynatrace. You have a user model version, and you wanted your clients to be on user model version two. But that’s not easy. You have to build that user structure from scratch. That was one of the downers we felt in Nutanix. And the other thing was the licensing.

The licensing structure was slightly different from Dynatrace. Dynatrace gave us a better deal, to be honest. Apart from that, I don’t feel they’re two different tools. These are the same tools.

I have been using it for about four years. 

I would rate the stability a nine out of ten. It is stable. Everyone uses SaaS platform. It never went out. There was no unplanned outage, at least that I experienced, apart from the regular maintenance windows or predefined windows by the vendor itself. 

So, it has been stable product.

It’s easily scalable because you deploy your agent. Our enterprise used to have a starter kit. The starter kit was basically an initialization of deploying the agents against our OpenShift. We had Kubernetes running under OpenShift. So there was a starter kit that deployed it. I didn’t feel anything really difficult with the implementation of the starter kit. So it was pretty okay.

I would rate the scalability a nine out of ten because nothing is perfect.

We regularly used to meet with the success manager, and there were technical people as well. We had at least once a month office hours with them. And then on an ad hoc basis, if we needed them, we used to engage them.

I have used Dyntrace, GCP and Prometheus. Dynatrace has a little bit more edge, not from the product technicality point of view, but purely from the way I think the licensing scheme is modeled. The product behaves a little more easily compared to New Relic.

The initial setup is easy and straightforward. 

Dynatrace is a little more complicated than New Relic, but New Relic was easier to deal with.

I would rate my experience with the initial setup an eight out of ten, with ten being easy and one being difficult. It is not that difficult to setup.

The licensing model was more expensive compared to competitors because of the way they were defining their user structure; there was full-stack observability and less than full-stack observability. 

There’s no advantage to having anything less than full stack observability because once you get people on board with an APM tool, they would like to know as much as possible about what the agent can discover. 

If the agent is able to discover and you’re not giving anybody full-stack observability, it’s like you’re treating your product like Lego. The more you buy, the more expensive it gets. If you want to make it into any bigger construction, you gotta pay more. So that was a downer.

Overall, I would rate it a seven out of ten because of the licensing issue. 

At this point, Dynatrace is doing better than New Relic.

We use New Relic APM for application monitoring, so if the application goes down, we do the root-cause analysis of why it went down. Was it the database? Was it the middle tier? We try to find out where it is and determine why the component went down.

We also use New Relic APM for its self-healing mechanism, which helps us determine the application's needs if it goes down. What data does it require? What was missing? Was the application able to send an email or a text alert?

We also have contractors responsible for the upkeep of the application. We have service-level agreements with these vendors, so we try to figure out how to incentivize or disincentivize the vendor. We try to measure their KPIs and SLAs, so New Relic APM tells us the uptime for the application for a month, a quarter, and a year.

These are our use cases for the solution.

What I like best about New Relic APM is its user interface because it's simple.

The tool lets us view what caused issues, especially in the cloud, where so many things could go wrong.

The most valuable feature of New Relic APM is end-to-end monitoring.

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.

I've been using New Relic APM, on and off, for about ten years.

New Relic APM is a very stable tool.

New Relic APM is a scalable tool.

My company has dedicated customer support for New Relic APM, and I found the support available and always helpful. I'd rate customer support as nine out of ten.

Positive

We used Splunk, AppDynamics, and Datadog, apart from New Relic APM, but New Relic APM was the best in terms of MVP (Minimum Viable Product).

I wouldn't say that the initial setup for New Relic APM is easy, but it's comparable to other tools because of the comprehensive documentation you can use as a guide. My company also has very knowledgeable engineers who set up the tool.

It took about six weeks to deploy New Relic APM completely.

We implemented New Relic APM through our in-house team.

We've seen ROI from New Relic APM, so we renewed it last September.

We're paying for the New Relic APM license annually.

We evaluated several tools, such as AppDynamics and Datadog, where we did demos and test runs.

My organization uses many application performance management solutions, such as AppDynamics, New Relic APM, Splunk, and Datadog. I'm the CTO for the state of Hawaii, and across the board, different departments use different APM tools.

I'm using the latest version of New Relic APM, but I cannot recall the exact version.

My company has a dozen engineers using and monitoring New Relic APM.

I'd tell anyone planning to use New Relic APM that it has to fit what you have. For example, most of my company's payload is in AWS, and the tool has adopters and features that CloudWatch cannot provide. Still, New Relic APM can, so you should do a demo or trial run first and see if it's a tool that'll help you with end-to-end monitoring. New Relic APM is working well for my company, so an excellent way to start is to do a trial run to see how the tool works out for your current applications.

My rating for the tool is nine out of ten because my experience with it has been great. New Relic also worked closely with my company and has always been upfront on what's available and what's not.

My company is a New Relic APM customer.

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.

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.

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.

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.

I have been working with New Relic for over one and a half years.

New Relic is highly stable. I have never experienced an outage or any misbehavior with this solution.

New Relic offers high scalability. It is quite flexible and can scale according to our needs.

The technical support team for New Relic is good. I would rate them a nine out of ten.

Positive

Before New Relic, we did not use any specific solution for observability. We used normal monitoring tools.

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.

The deployment typically requires two to three tier-one or tier-two team members from the technical team.

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.

We evaluated several other options like Datadog. However, after comparing prices and support, we chose New Relic.

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.

We use New Relic APM. We use New Relic synthetic monitors to monitor around 3,600 websites that we host for clients. We also use a scripted browser to automate some of the scripting browser tests that we run. The APM is there and we use basic monitoring with all the metrics, et cetera.

One of the best features is that New Relic only has a very straightforward pricing model. They only charge for the data that is ingested. All the features that they provide are completely free of cost. You can use any tool that they provide, and you just pay for the data that is ingested.

The initial setup is straightforward. 

It's stable.

New features are added often.

It's scalable. 

Technical support is helpful and adheres to the SLA.

Their pricing model, in terms of user management, is that you pay for every user. They don't have an opportunity to share the dashboard with the public. If you want to share it with stakeholders or people outside the organization who just want to have a look at a couple of metrics, you can't do that without onboarding them to the product itself.

I've been using the solution for more than three years. 

They often keep introducing new features. That said, as far as the stability of the product itself is concerned, it's a very stable product. There are no bugs or glitches. It doesn't crash or freeze. 

It is scalable. We have a scalable infrastructure. Their API calls and everything help us scale the monitoring and the use of New Relic itself. We scale the solution according to our requirements.

The developers use it to test and look at the logs, and the SRE team uses it for reliability. 

We have another system admins team that reuses it for monitoring of services that are running. Even our stakeholders use it for various dashboards and look at the SLA reports and other stuff. The user base is not very large, yet we have different teams who use New Relic in different ways.

Technical support was very helpful. They are very prompt, and they reply within the SLA time limit. It's pretty good.

Positive

The product is pretty straightforward with every product that is out there - even with Datadog. New data integrations are seamless. The initial setup is pretty simple and straightforward.

I'm not sure how long the deployment takes. 

It's easy to maintain. We integrate it with our CI/CD pipeline, so any changes go through the same process. We don't have a dedicated team to maintain it.

The payment structure is great. Users are only charged for data ingested.

We spend somewhere around $5,000 to $6,000 per month with an annual recommitment of maybe $60,000. These are just ballpark figures. Licensing is handled by the finance team and the vendor management team.

While we do use this solution currently. we are still debating between various products out there.

We are end-users.

I'd rate the solution eight out of ten.

The use case for this solution is the same as Azure Monitor. They have the same coverage for the use case. In the end, we switched to Azure Monitor.

It is for the application quality process and the live system support monitoring.

We like the performance of the product. It's very good, very reliable.

All features are all capable to responding to our requirements. There's no problem on this side. 

The solution can scale. 

The initial setup isn't a big deal. Our admins can handle it. 

The solution is quite expensive. 

We've been using the solution for about two years at this point. It hasn't been too long. 

It's stable. It is reliable. The performance has been good. There are no bugs or glitches. It doesn't crash or freeze. 

The solution is scalable. It's not a problem to expand as necessary. 

We have two or three users on the product right now. 

Previously, we did not use other application performance management products.

We also use Azure Monitor. They are very much the same. However, we've since moved over to Azure Monitor.

It's not as straightforward a setup as Azure Monitor. Then again, we have admins, and they were managing that part. It's not a big deal.

We have two admins that can handle deployment and maintenance. 

The price is an issue. It's quite expensive.

That said, I can't speak to the exact pricing. 

I'm not sure which version of the solution we're using and if it's the latest version or not. 

We'd recommend the product if budgeting is not a concern for a company.

I'd rate it nine out of ten. We were pretty happy with its capabilities. 

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.

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.

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.

I have been using New Relic for two years.

I rate the stability an eight out of ten.

I rate the scalability an eight out of ten.

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. 

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.

We just got a license for self-hosting and have set it up to do this.

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.

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.

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.

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.

I have been using New Relic for a year. My company is in partnership with New Relic.

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.

Positive

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.

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.

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.

The product is neither cheap nor expensive, and I believe that it is a competitively-priced tool.

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.

I use the solution in my company for predominantly API response time. It is used to measure API response time.

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.

I have been using New Relic for ten years. I use the solution as an end customer.

It is a scalable solution. The product operates as a third-party or SaaS tool, so I believe that it has intra-scalability options.

The technical support for the solution is very good. I rate the technical support an eight out of ten.

Positive

My company has been using Sentry for error reporting, alerting, and monitoring.

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.

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.

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.

Regarding use cases, we use it for app support. So basically, we use the APM module, and we also use it for monitoring.

It has helped my organization to dive deeper into the application using the APM module is very helpful. So when we're looking for problems of why an app is behaving incorrectly, we can dive deep into it using the APM module.

I would have to say the APM module is its most valuable feature.

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.

I have been using New Relic for ten years. Also, I am using the solution's latest version.

The stability of the product is high.

It is a very scalable product.

I rate the support a four out of ten. One of my biggest frustrations was related to its support.

Neutral

New Relic is deployed on the cloud. The ease or complexity of deploying the solution depends on the piece that you're deploying. The app pieces are pretty standard when the infrastructure is more complex.

I have not experienced any return on investment using the solution.

I think it's overpriced for the technical support that we get. We spent over 1,00,000 USD a year.

To those planning to use the solution, I would say to do as much setup as you can upfront with the technical support reps that helped set things up because trying to set it up later is more difficult.

I rate the support a six out of ten.

My primary use case for this solution is to see the application's performance and alert the reiteration of any performance.

The feature I found most valuable is being able to design my queries. It's easy to design a query.

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.

I have been using this solution for about six months.

My impression is that stability is pretty good. I would rate it an eight, on a scale from one to 10, with one being the worst and 10 being the best.

I would rate the scalability of this solution an eight, on a scale from one to 10, with one being the worst and 10 being the best.

I would rate the technical support of this solution an eight, on a scale from one to 10, with one being the worst and 10 being the best.

Positive

We have previously used a different solution, and we switched only because our current customer was already using it.

My impression is that the initial setup process is straightforward. The solution is SaaS so all it takes for deployment is just signing up for the service. Our model of deployment is the cloud.

We have seen the ROI.

I would rate the pricing of this solution an eight, on a scale from one to 10, with one being the worst and 10 being the best. We have a yearly license.

I would rate this solution as a whole a six, on a scale from one to 10, with one being the worst and 10 being the best.

When it comes to other people looking into this solution, I would advise making sure that if you're running into communities, to know what it does before you start using it.