New Relic Reviews

I use New Relic for the creation of dashboards, alerts, and any type of observability resources that are relevant for my company.

The most valuable features of New Relic are the ease of creating dashboards and its integration capabilities with many external tools. It enhances operational response by providing analytics and alerts that help us address issues quicker. 

Using New Relic speeds up troubleshooting and resolution, giving us a clearer picture of where issues are, thus saving time and effort.

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.

I have been using New Relic for one year.

I find New Relic to be a stable tool. It is reliable in the aspects that I use.

While responsive, customer service does not always provide straightforward solutions immediately. Issues that could be solved quickly sometimes take longer because they go around in circles. However, they are helpful when direct interaction is initiated.

Neutral

The setup is easy for the part I'm responsible for. However, since I do not manage the complete product setup, I cannot comment on the entire process.

For our part, New Relic has provided value by speeding up issue troubleshooting and resolution, allowing for more efficient use of time.

I rate New Relic seven out of ten. 

For those looking to use New Relic, it is more suited for networking and infrastructure monitoring rather than application performance monitoring, integration, or API log handling.

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.

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.

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

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.