New Relic Reviews

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. 

We use the solution to ensure the applications perform at the accepted performance level. The application must not have any bugs or problems. It must also have no bottlenecks in the volume of the transactions. We use the tool before we deploy an application to production and during the first part of the deployment to ensure that the application will perform properly.

The product allows the developer to see the actual problems in the applications. It shows which part of the code and which part of the software component or architecture is having a problem. It's easy to resolve the issues and pinpoint the bottlenecks in the application.

The solution must provide better support for Azure Web Apps service. The solution does not completely support the architecture of Azure Web Apps.

I have been using the solution since 2018.

I rate the tool’s stability a ten out of ten.

The tool is pretty scalable. We did not have any problem using it on multiple nodes or instances. We have a report server. The report server would have more than two instances. Sometimes, the application node would have more than two instances, one database, and a proxy. The tool can handle 12 or 16 instances at the same time in one single application.

Our largest customers had around 800,000 users. The task of monitoring the tool and identifying the issues depends on the specific assignments that the technical person receives. One person does the deployment and configuration.

The setup is straightforward. We have complete and concise instructions on enabling the APM on a particular application platform. We work on different application stacks. New Relic has different instructions for different types of technology stacks. We follow their instruction.

For job applications, JAR files need to be installed. The APM provides it. For other applications, we have to put the necessary IP address or domain links on the application. Then, New Relic automatically scans the specified server, and it appears on the New Relic console. The solution is cloud-based.

The product ensures that the applications have the expected speed and performance. It can handle large volumes of users and transactions. It also identifies the bugs in the applications. Once the users access the applications, the tool can detect any problems. The product can easily identify whether the issue is on the client side, the application side, or at the database level.

We highly recommend the solution for people who want to deploy large applications or applications with a lot of users. It will provide them with the necessary information to ensure the application performs as expected. We enable New Relic for the first three to six months. Once all the problems have been identified, we turn it off.

Then, we turn it on again on a particular period to see if problems can still be identified for that particular cycle. The applications we work on follow a particular cycle of operations. So, we normally turn on New Relic when we need to do a large volume of processing or complex processing on the applications.

Overall, I rate the tool a ten 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.

The primary use case is for synthetic monitoring of all the APIs. It helps to detect if any APIs are failing before a customer detects an issue.

The solution was deployed on cloud.

There were 15 people using this solution. They worked on the configurations and setting alerts for new environments and customers. The solution was used on a daily basis.

At my previous organization, they were planning to replace New Relic with Google Apigee. That was only to be done in conjunction with the cloud migration from the in-house hosted apps.

One valuable feature is that the synthetic alert stays open until the issue is resolved. You can actually monitor whether your system is back up.

I would like the ability to set up certain dummy accounts and do the actual things that the customer is doing, without impacting the production environment. Only the read APIs are called from New Relic, not the write APIs. If we had a test account to do the write part of it, it would give us better monitoring. For example, if we are selecting the data for an existing account, we can do that part of the monitoring with New Relic.

When we see failures and slowness, I would like there to be an option to do a deep dive into a collection of metrics to show the bottlenecks. It would be helpful if it didn't just state the problem, but indicate the areas to look at for a deeper resolution of the problem.

I have used this solution for three years.

It's mostly stable.

It was scalable.

Technical support is responsive, but you need to create a support ticket with the right priority, which is based on certain questions that they ask. If it's created with the right priority, they will respond. If your ticket is created with a lower priority, they will respond on the next business day.

I would rate technical support as five out of five.

I have also used AppDynamics to show us the time that the APIs were at a certain level, like the database level or application level. I think New Relic has started implementing the ability to trace transactions to that level, but I don't know if that feature was well developed because I didn't use it a lot in New Relic. 

In Apigee, for example, they monitor a certain percentage of the transactions to show where the bottlenecks are.

The supportability in AppDynamics is good.

Setup was pretty smooth. I wasn't involved in initial setup, but for newer customers and installations, setup wasn't very cumbersome.

Initial setup was done by New Relic, but we did later installations ourselves.

The pricing is fine.

I would rate this solution as nine out of ten. 

My advice is to have a project plan in terms of what you want to monitor. You can monitor various micro-services, but you probably want to restrict the monitoring to what exactly impacts the customers. Have a plan for implementation, the components you want to monitor first, the components you want to monitor later, and an automation strategy for synthetic monitoring. For example, for the right APIs, think about whether you can have monitoring using synthetic accounts.

We used New Relic APM for monitoring our data.

The synthetic alert is the most valuable feature in New Relic APM. I also like the time travel feature and find traceability useful in the solution.

New Relic APM also has good response times.

In the pro licensing model of the solution, my company used the data analysis feature more and took care of more complex workloads that my team could easily track. Data analysis is another feature of New Relic APM which I found helpful.

The UX/UI design of New Relic APM could be improved. The solution currently has some slow pages in terms of loading and viewing the pages, for example, the reports. The reports and other pages take a long time to load, so if that area could be improved, especially when looking for data, it would enhance New Relic APM.

I started using New Relic APM around March of this year, 2022, until June, so my experience with it is almost a year.

New Relic APM is a very stable solution.

You can scale New Relic APM, but I expected it to be more scalable.

If you contact New Relic APM technical support during office hours, then the team is responsive, but sometimes, it's delayed, especially when you contact support during offline hours. New Relic APM support is limited, so I'd rate this area as three out of five.

I used Dynatrace before using New Relic APM, but that was in my past organization. I switched to New Relic APM because I moved to another organization. I also use Datadog, but mostly, it's New Relic APM that I'm using.

In my current organization, I did some POCs, but not effectively, so I've only used New Relic APM and no other solutions, at least in the organization I belong to now.

I used to handle the New Relic APM setup process more for algorithms, mainly writing algorithms to define the rules for better tracking. I focused on the time travel, traceability, and other valuable features of the solution, primarily monitoring and not the initial setup for New Relic APM because the IT team took care of that process.

On the part I handled, the process was seamless, and there was nothing complex about it, but it could be because I asked for help from the IT team. The process was average. It wasn't very smooth and wasn't very complex either, so neutral.

The initial setup for New Relic APM, which was done by the IT team, took more than a day.

The IT department took care of deploying New Relic APM. The implementation was in-house, and New Relic gave my company a server similar to a one-of-a-kind setup tool that you can install within half a day.

The IT department handles New Relic APM licensing, but the solution is priced reasonably. I'm actively using the mobile monitoring function of New Relic APM, and it's one of the best products for me because it's economical, so anyone can easily pick it over other solutions and use it. It has basic features.

My company went for the New Relic APM sixty-day free trial, so there was a limitation to the number of people that could use the product. It only allowed twenty-one users maximum.

New Relic presented New Relic APM pricing and packages very well. For example, there's silver and platinum, and each package was easy and more economical than other tools. In this context, I'd recommend New Relic APM because of its reasonable price and package.

My company initially used the standard New Relic APM package, and by the end of the month, it moved to the pro model, which had low, flexible pricing.

I was into this Dynatrace, a monitoring tool in my previous organization, but not now.

I'm now using New Relic APM at an organizational level rather than a personal level.

New Relic APM has an on-premise deployment; though my company planned to deploy it on the cloud, it wasn't successful, so another solution for cloud deployment is now being tested from AWS.

As New Relic APM is one of the best solutions in the market, my rating for it is eight out of ten. I didn't give it a ten because of the support, reporting, and UI/UX that need improvement.

I'd recommend the solution even to startups or novices planning to do some monitoring, and in the future, New Relic APM could compete with similar tools used by the experts.

At the moment, nine people, mostly software engineers, use New Relic APM within my organization. The software engineers get the alerts from the product.

New Relic APM requires maintenance by a minimum of three resources, and it would depend on the requirements, tools, and features. For example, my company currently uses three New Relic APM platforms, web, mobile, and desktop.

My company is just a user, not a partner of New Relic APM.

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 solution is an APM monitoring tool.

We will be monitoring all kinds of server details, including how the application is handling things and any threat count, as well as if there are any network utilization failures or problems with DNA instance ports.

The transaction summary is great. It's very helpful for reporting. 

The initial setup was not that difficult. 

It's stable.

The pricing is pretty good. 

The solution is scalable. 

There were some settings we had issues with. For example, a certain setting to change the time zone. If we change the time zone, it will take 24 hours to reflect the time zone and make the changes. It'll be great if the settings once we change them, reflect the change at least after one hour. That would be helpful so that we don't need to wait for one complete day to see the changes.

I've been using the solution for one and a half years. 

The stability is great. It's reliable. I'd rate the stability four out of five in terms of reliability. There are no bugs or glitches. 

The scalability is good. I'd rate it five out of five. It is easy to expand. 

I've never dealt with technical support. 

There were no other tools being used previously. This was the first we were recommended, and we deployed it.

It's a straightforward setup. It's not overly difficult or complex. 

I'd rate the solution four out of five in terms of ease of setup. 

Mainly the setup was done by the box team, so they were using it for their purposes and for the log activity. I'm just part of testing team, so I'm focusing more on the reporting side. The setup was not done from my end; the DevOps team managed the process.

We have mostly one person handling the setup and it took about two to three weeks.

We have a third party that manages the maintenance. There might be four to five people maintaining everything. 

Our own team handled the initial setup. 

I'm not sure if we've seen an ROI at this point. 

I'm not aware of the exact licensing costs. My understanding is that it is affordable. I'd rate it four out of five. 

We likely py a yearly licensing fee. It's all-inclusive, and there are no extra fees. 

I did not handle any evaluations on my end. I'm not sure if the company looked at other options. 

We are customers and end-users. 

Since we're working on a cloud-based deployment, the solution is always up to date. 

I'd rate the solution nine out of ten. It's user-friendly and has many automated features. I'd recommend the solution to others. 

We use New Relic APM to monitor our public cloud-hosted application and infrastructure.

Not so far. Although, we haven't really got a very mature system of defining our application processes from end-to-end and certainly not our client-centric impact.

I'm reasonably satisfied. We haven't run the rule over it too much because it hasn't been a massive investment.

It has been quite valuable to demonstrate how we can change our views for our services due to their service. It has proved value so far.

We don't have any problems with this solution.

The configuration isn't terrible when compared with other products.

It does everything we wanted it to do. We haven't been too critical in our thinking about where it can improve.

There really is nothing that stands out with New Relic. With the insight, I think it will be found lacking for its report aggregation capabilities. How granular I could go down at looking at certain data, especially related to the operations, is limited.

The API integrations that they have for us to automate our configuration was fine, but I think for some of these tools, it was over-engineering for us to try and automate any of that. So, we just use the user interfaces.

I have been using New Relic APM for approximately two months.

We are using the latest version.

It's a stable solution. We have not encountered any issues. We're not plugging too much traffic into it. We're not reporting on it heavily. It's not feeding into our service management processes heavily. So we haven't seen anything.

We have not yet explored the scalability, it's too early for us.

There are approximately 15 of us using it altogether. We are called infrastructure engineers, who are third line infrastructure support and architecture people. 

Some of the lead developers have access, but there are 15 of us and we are all pretty similar.

We have not contacted technical support.

We have two custom in-house processes that do our application data flow monitoring. We have manually and in a custom nature, built out a performance monitoring platform in Splunk using our knowledge of the system over the years.

I have used App Dynamics in the past with another company. There really is nothing that stands out with New Relic. It is similar to AppDynamics and Dynatrace.

The initial setup was straightforward. 

I don't think any of these tools are tools that anyone can pick up and install. 

I wouldn't say it was any more difficult to configure than some of the other solutions. It is definitely not more difficult to configure than AppDynamics. 

The price was one of the reasons we chose this solution. It's reasonably priced. It's cheaper than the likes of AppDynamics and Dynatrace, based on how our subscription is.

We looked at Datadog initially and found the initial setup to be far more complex than what we found in New Relic. 

Our proof of concept has been successful.

Getting an order in and reporting is an industry in itself, don't think it can solve the problems it's not trying to solve. It is an application performance monitoring tool. Don't try and make it anything else.

The big problem with Splunk for us is that it can do everything. The thing that's nice about New Relic is it doesn't try and do everything, it does what it does. So far, it does it to satisfaction, but don't try and fill multiple holes in your toolchain with it. It's good at what it does.

We had some pretty informed opinions on what it was going to do. We knew where it wanted us to get, and so far it has cost the amount we wanted it to cost and done everything that we wanted it to do.

I would rate New Relic APM a ten out of ten.