New Relic Reviews

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 main purpose we are using New Relic is to enable application backend and frontend performance monitoring. We enable synthetic monitoring for the application team and for the business owners of the applications. Additionally, we
on-host integration for different DBs, SQL, and Oracle.

The most valuable feature of New Relic is its ease of use.

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.

I have been using New Relic for approximately two years.

New Relic is a highly stable solution.

New Relic is scalable. I have not seen an issue with the scalability. We have over 600 applications and a very high number of users using the solution and there has not ever been a performance issue.

I have contacted the support from New Relic when things do not work as expected or when some framework is not supported. Some of the support agents do not get back to us for weeks, but others do answer more quickly. The support could improve.

I rate the support from New Relic a five out of ten.

Neutral

I have used AppDynamics previously and New Relic is easier to use and user-friendly. 

I have also used Dyatrace and prefer New Relic because of its license and usability. However, if I look at the features I then would choose Dynatrace, it has more features.

The initial setup of New Relic is easy. I do not have to use the documentation a lot of the time because it has a guided installation method. We have automated a lot of the tasks needed with other tools such as Ansible and ServerNow catalog tasks.

The deployment of 20 or 30 servers without automation would take a lot of time. There are many different agents and components. There are other solutions that are not as difficult, such as Dynatrace. However, they only have one module.

This solution required a license and it is better than some other competitors.

My advice to new users of this solution is it's easy to use and look for the most secure features.

I rate New Relic an eight out of ten.

I gave my rating because the solution provides simplicity and the license is one of the best compared to other tools.

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.

Positive

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.

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.

The New Relic APM basically helps us understand how the application is functioning at a very in-depth level. The APM helps us bring in observability, which is the next part of monitoring. It tells us about every database query, long-running query, website response time, page load times, and everything in very good detail that normal, basic monitoring cannot provide. APM is really important to every organization out there.

It brings value in three places. One is code detection and resolution. You can pinpoint and identify where the issue lies within the application. 

The second thing is performance monitoring, which actually gives you performance in terms of actual signs. When a user logs into a particular website, what kind of performance that user actually sees, we can see that as well.

It also gives metrics. All that session data as well we get helps us come to know if a user was frustrated when using the site or if they were happy, or what the emotion was.

The solution offers good code detection and resolution.

It offers helpful user metrics so we can learn more about the user experience. 

It has good performance monitoring. 

One thing that Data Dog provides, which is the RUM, Real User Monitoring, is something that could be useful in this solution. Data Dog captures the entire session and then provides it as a video player path, which gives more insight into what the user was doing. It's pretty impressive. New Relic does that, yet it only captures using a couple of screenshots, which is not very detailed since you are unable to see the entire user flow. That is one thing that New Relic can actually improve upon.

We have a few different teams on the solution right now, including an admins team, and an SRI team, and they depend on this solution very much.

I'm also familiar with Datadog, which offers excellent RUM in comparison to New Relic. 

I don't have any details in relation to ROI at this time. 

The solution is around $5,000 to $6,000. Everything is included. We only pay for the data that is ingested. You can use all the features and the APM and not have to pay extra. YOu just pay for what you use. 

I'd rate the solution nine out of ten.

We recently purchased the Splunk SAM module and are exploring whether it is worth integrating the ITSM module. We are deciding if we can have a proper platform or if we should go with features that New Relic offers.

The synthetics, alerts, and native inbuilt capabilities for monitoring the cloud with the New Relic agents have been helpful.

We had some issues with the New Relic platform showing the sample traces because we want the entire traces to be listed as we are capturing some end-to-end metrics. So we thought it was not just the sample data we needed but the details of every transaction that goes through to the application. The New Relic team is helping fix this, and they have an option we are using in the meantime.

The thing missing from these platforms is connectivity. All the solutions work well with the cloud solutions, but the connectivity between legacy and newer cloud applications is not great. In addition, none of these tools can do end-to-end traceability across the different applications.

We have been using this solution for about four years.

It is a stable solution.

Regarding scalability, we recently extended our contract with New Relic for the next two years.

Regarding support, I think they have a pretty good support team. We have a current issue, and their technical team is on it. They're re-platforming, and there are a lot of alerting modules, so they advised of a bug. We hadn't faced an issue in four years where an existing functionality broke, and this was the first time. They're supporting us around the clock to get it fixed. The support team is also open to feedback. For example, we were building automation solutions and recommended that New Relic have native integration with AWS, so they added an event bridge integration with the AWS platform. So the alerting triggered from New Relic can be sent as an event to the AWS so we can complete our ops, like self-remediation and auto-healing. It's the feedback we provided that supported them in building the product that we needed.

We were using Dynatrace before, and then we switched to New Relic.

We got professional services from New Relic to help with the setup, and they were very helpful. In 2018, we went with their professional services, and their pricing was better at the time and comparatively lower than Dynatrace's. We were shelling out almost a million dollars per year for Dynatrace, but we saved some money once we moved to New Relic. Their professional services were about 60K when we used their support. I recently moved to a new team after a long time, and we have weekly connects with the New Relic team, and there has been a complete restructuring of the teams. So previously, the professional services were topnotch, but it is not as good now.

We feel it's a little bit pricey compared to Splunk. We haven't explored Dynatrace because we have invested so much in New Relic. New Relic changed its pricing model. Initially, we planned to put it into all the systems, but with all the pricing and strategy, we decided to refrain from monitoring. It costs about 600k to 700K per year.

I rate this solution an eight out of ten. Regarding advice, compared to Dynatrace, Dynatrace is adopting a lot more than New Relic. The problem is we are invested so much in New Relic. We are still trying to decide if New Relic is good for our company or if we should move to Dynatrace or SignalFx. I am not the best person to make that conclusion.

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.

We use New Relic for collecting the metrics on microservices and databases.

New Relic's dashboard is nice, and it's reliable. It's also compatible with many services, especially Java and the Python ecosystem.

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.

We have used New Relic APM for more than a year. 

I rate New Relic eight out of 10 for stability. 

I rate New Relic eight out of 10 for scalability. We have around 150 users, including nine or 10 DevOps people acting as admins. 

I previously used AppDynamics. I liked it a lot. Since the acquisition, we've mostly used New Relic. I prefer AppDynamics because I'm familiar with it, and it's easy to use. I don't remember the specifics about features, but I liked the overall feel of AppDynamics.

The initial setup isn't complex. I haven't deployed it, but my colleagues say it is easy.

The return on investment is definitely good. You need an APM in any development setup if you plan to deploy multiple services. It's a fundamental part of the process. I can't compare the ROI to New Relic's competitors, but you need an APM. 

I think the price is reasonable compared to AppDynamics. I don't know the license costs, but most of my startups are using New Relic. Those startups are sensitive about prices, so it's affordable. 

I rate New Relic APM seven out of 10. I would rate it eight as a solution for startups. If you want to implement something quickly and easily, New Relic should be your first choice. However, I would pick Dynatrace to explore deeper aspects of special transactions and distributed setups.