New Relic Reviews

I used it in another organization. I had a project where we were using New Relic for monitoring APIs and utilization of nodes or hosts. It was a standard implementation that involved getting the statistics and configuring New Relic agents on the application servers. The data was sniffed from the network based on the configuration and then it was saved. We were using the out-of-the-box capability of New Relic. We didn't do any customization on New Relic.

It was a good solution. My boss, who was a VP, was very happy with the system, and he didn't want to change the system because it was working well. Whenever anything went wrong, we got clear information about that on the fly. This information helped the operations team in sorting things faster. It gave clear information and a complete picture of what was happening in our system, which helped the operations team in performing the required actions.

The alert mechanism is quite accurate when something goes wrong in your system. For example, if you have hundreds of APIs on your server, and any of the APIs is not performing well, you get an alert. When there is a drop or change in the threshold value, the beauty of New Relic is that within a fraction of seconds, all the stakeholders who are configured in the New Relic system will get an alert. That's one good thing.

There is a dashboard where you can view API-wise performance. When you click specific APIs, you can get detailed statistics for the same.

One thing that we noticed was that historical information was only for a limited period, which was not helpful in certain scenarios. For example, if I want to size my system for an event for New Year or Christmas season based on the historical data, I won't be able to find the historical data. Currently, the data is limited to three months. It would be helpful if they can provide historical data for a longer duration so that we can plan our system accordingly.

It was used for more than four years.

Its stability is quite good. We don't see any issues with the stability.

We never had any challenges because our servers were scaled based on the load. When our load increased, we used to keep adding our servers to New Relic. We didn't see any challenges. It just required the agent configuration on the server. The only thing is that you have to put in more money when you are adding servers.

It was straightforward. We didn't see any complexity because the setup of New Relic on the client side or the application side is more of the agent configuration.

Once your agents are configured in the pre-prod or production environment, the feed used to be taken automatically. The only thing is you have to open the proxy to the New Relic system. If that is done, the rest is taken care of automatically. I don't see any challenge.

For the setup, we had one person from the customer IT who coordinated with the network team and got the proxy opened, and then tested connectivity between the on-premise site and New Relic data center. 

Later on, we had one person for configuration because sometimes, we also did data masking when we wanted to mask certain data. We didn't want that feed to go to the New Relic data center. We didn't want that data to be exposed. To query the system, there were queries available in the New Relic documentation, and we used to follow that. We also had a customized dashboard. We could prepare our own dashboard for our critical use cases such as payments.

I would rate it a four out of five in terms of ROI. 

If I remember it correctly, the pricing was based on the core, and the monthly subscription used to cost us $1,500 or $2,000. 

We had pre-prod and production services. Costing was different for pre-prod and production. For pre-prod, it was 40% less than the production service cost. It was a combined package. 

With our licensing, we could only query three months of data from the New Relic system. When we wanted to have the historical information, they said that it is going to be an additional licensing at an additional cost.

You have to see the costs. If you want to scale to a larger system or you want to implement New Relic for the entire enterprise, the cost is going to be high because you have to run hundreds of servers. If you take the frontend applications, mobile applications, and required servers, there will be a huge load and traffic. Dynatrace is one of the alternatives. Our last customer wanted to scale, and they found Dynatrace to be better than New Relic in terms of features and price. 

I would rate this solution a nine out of ten. It is one of the best products. The customer used it for more than four years before moving to Dynatrace. We were happy with it. The alert mechanism and other features were quite good. 

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.

We do have a couple of applications for one of our customers. We are involved in performance testing and engineering of those applications. We use New Relic in multiple areas. It's used to monitor infrastructure in this use case. We capture the metrics around the utilizations on the infrastructure. 

We do also identify bottlenecks of the services or the calls, which are causing high response times. 

Those are two key areas where we have been using New Relic. We have been able to identify calls that are causing a lot of performance issues in the overall application, and then that, in turn, helps us to see what can be tuned to bring the performance to a better state.

It's a build-down feature, so you have the option to drill down when a call is being received. It further drills down the method level and shows which particular method or hit is actually causing the performance issue.

It's a common feature for all APM tools. That is the key benefit of any APM tool - it helps you to understand and get to the bottom of the issue or the root cause at the earliest possible time.

The solution offers good documentation. 

It's pretty easy to set up.

Real-user monitoring would be helpful as it would help me to really understand the client-side performance of the application. Maybe for whatever reason, we have not got to explore a similar kind of feature in New Relic.

I've been working with the solution for a year.

The stability is good. There are no bugs or glitches. It doesn't crash or freeze. 

The solution is scalable. The deployment is not done by us; however, when we have to add new services or new components, it is pretty easy. The turnaround is also pretty quick.

Our team just accesses the client's New Relic tool. It's typically just used by performance testers and engineers. It also sometimes gets used by architects as well the development team. From our side, we have three people working on the solution. 

While my understanding is they do provide technical support, I've never needed to reach out to them. I can't speak to how helpful or responsive they would be. 

I'm more familiar with the likes of Dynatrace, AppDynamics, and New Relic.

We are just getting into a scenario where we might end up using AppDynamics. Otherwise, I haven't used anything before New Relic in a similar way.

From a documentation standpoint, it is pretty straightforward to set up New Relic assets. The infrastructure isn't that complex. To be honest, we haven't been involved in setting it up from an infrastructure setup standpoint. We have more consumers from which we use a setup that has been done to identify bottlenecks.

There's no specific maintenance that's been required unless they've changed endpoints which would need to be configured. It is something that's natural. When we do changes to the application and change endpoints, we'll have to configure the right endpoint. Otherwise, from a maintenance standpoint, given it's cloud and it's a storage medium, it doesn't need any major maintenance activity.

The customer tends to handle the deployment process.

I've done some research, more towards trying to understand various features. The customer, however, decides what tool to use. I don't really have the authority to compare anything and make suggestions. 

That said, when it comes to New Relic against AppDynamics against Dynatrace, or for that matter, Datadog, there are a few which have a higher price and provide richer UI. We did not really end up seeing a very major difference except in terms of monitoring.

We are likely working with the latest version of the solution.

The product has been pretty easy, and it is quite user-friendly in terms of trying to understand it. New Relic looks more at observability as a key factor. With it, you have front-end observability and back-end observability. My suggestion to others would be to go over them and also see if they can look at getting the documentation that's available to explore New Relic and then start with it that way so that it's easier for them to get started.

The other part is once they are used to New Relic, they can also look into a bootcamp that's run by New Relic, or a workshop. If they could attend it and then go into New Relic, that would be easier. They do have certifications as well which would also validate the knowledge that they gain on New Relic. 

I'd rate the solution eight out of ten.

The service map feature is very useful.

The simplicity of the dashboard is very good. It shows the throughput latency and all of the transactions.

It offers transactions, but it does not offer an endpoint-level insight at the URL level. When we get a request, we want to know what the life cycle of that service is, and where the cycle is. This is what I am trying to locate with most of the solutions now.

I am trying to research how to find a cycle per endpoint and not at the service level.

It is very difficult to award the service level cycles at an endpoint level. It is important for us to get new insights to create better hygiene around the business use cases.

At the endpoint level, the visibility is not that great, and metrics are not available. It gives you a full view of the entire function's execution and not from the context of the URL altogether.

Also the response time, the latency contribution, and the throughput contribution are areas that need improvement. You can get the throughput contribution from New Relic, but not the latency contributions. You cannot get it at all.

These are the major limitations. When working with AppDynamics, I did not find any limitations, but the same can not be said with New Relic.

The way that it classifies the actual services is a bit ambiguous. It's not perfect. For example, I see there are certain solutions that are listed as extra services, as a dependency, and still I find that among load contribution, it tries to show that those services separately, which is confusing.

With the transactions, when it tries to show a type of "bufferHandler" from inside, it doesn't show what the nature of the request is. Especially with Microservices, it doesn't show what kind of method is present, which makes finding data very difficult. Instead, you need to go to the raw data. I think that defeats the purpose of using this tool.

The transactions do not show the time consumed by the request, from the metrics execution perspective. It was suggested that I did not know how to read it but I have done all that I could. It is very difficult to relate to and requires a lot of experience and time to read through, which it should not.

It should not be difficult to find the latency and throughput for the entire system when requested. It should not be difficult to develop the data that relates to the various types of execution.

It should have complete exposure around the endpoints.

The services-to-service dependency is fine but most of the startups have only one or two services that are all cycled. It does not provide you with a lot of help when you are showing that the two services are dependent.

What all of the dependent endpoints are and how are the cycles being formed is information that should be available in most tools, but not with New Relic and some other tools.

I have been using New Relic APM for one year, but in-depth in the last two months.

We are not using the latest version but within the year.

Almost all of the developers are using this solution in our organization. We have approximately 60 users.

It is used on a day-to-day basis.

I have not used technical support.

Previously, almost four years ago, I used AppDynamics. I think that it is a very good tool. I would rate AppDymanmics an eight out of ten.

We changed to another solution because of the cost. All of the developers loved the AppDynamics dashboard. It was very clear.

I was not a part of the team for the setup but my impression is that the documentation could have been better. It didn't make much sense. 

For beginners using New Relic, the setup can be difficult and should be simplified. 

We have a DevOps team to maintain this solution, but it doesn't require a lot of maintenance.

I think the pricing is reasonable.

There is a good bare minimum of required features for this tool, but if they are out to the in-depth analysis then finding a cross-dimensional relationship is not straightforward. It is difficult to implement.

If you are concerned about how your services behave, then New Relic shouldn't be your first choice. However, if you are considering New Relic APM, is a very affordable choice.

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

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.

We use it to monitor servers. It's just a log in New Relic. I set the start and end times, and then I just pull down the server metrics.

It's not the New Relic APM, it's just the New Relic. There is the one that is New Relic, and then is New Relic APM. It's a bit confusing.

Normally when I use it, it takes me 20 minutes to pull all the data, and I use it maybe once or twice in a month.

We would run a low test, and then after the test, we would log into New Relic and then look at things, including: what are the top five slowest interactions on the servers? What are the slowest database calls? Then, we just pull the graphs from New Relic, and then we give it to the customer and show them here are the calls are being made the most, and that correlates to a slow response time. Then they'll be able to focus on it and try to maybe fix it.

There's another user on our team that sets up the list of servers that need to be monitored. You just click on those servers and then from there you can pull all the data, so that's really helpful. You don't have to go through a list of 500 servers. You click on one server, and it brings up ten servers that are in that environment. You don't have to choose those same ten every time. Instead, you just click on that one link. You just have to click on the name of the group you want to look at, and it'll pull metrics for those same ten or 15 servers each time. That's very helpful.

The customization of the start and end time is kind of cool.

It's stable. 

The solution can scale. 

One of the metrics is total time. I would like to see the true response time of a particular call. It might say top five slowest calls. However, I don't know how they're calculating it. Maybe if they could have documentation for how those things are calculated, that would be a lot easier. If they say the top five slowest methods and the slowest one is three seconds, yet we know that there's a process that's taking ten seconds, it can be kind of confusing. If they could add in their help files, how these columns are calculated, that would make it more transparent. They need to clarify: What does it mean, total time? And how do they calculate the total time? How do they calculate average time? How do they calculate the top five slowest? What is it actually pulling?

I would like to see them introduce integration with LoadRunner; that's a bit easier.

I've used the solution for six to eight months. 

It's a very stable product. Overall it's a good product.

We have eight or ten people using the solution at this time. It is used occasionally, once or twice a month, just to pull out the data for the server monitoring and for the reports.

The solution can scale well. 

I've never called New Relic support. I never really needed to.

I'm also aware of Dynatrace. In Dynatrace, they have an integration with LoadRunner. You just have to add one or two lines of code in LoadRunner, and it will integrate with that, which is really good. 

New Relic doesn't have the option of integration with LoadRunner.

I did not install New Relic. By the time I was put on the project, it had already been installed.

They just let me know the ID and password, and I just logged in, and that was it.

As far as pricing goes, I heard that they charge per user ID. If we have ten people with ten IDs right now, if we want to add another five more, they'll charge us for each ID, so that is something that is maybe a concern. I actually heard this from one of their competitors. I've heard Dynatrace say that New Relic's pricing model was very expensive, so that would be a concern.

I'm not sure of the exact price of each user ID.

My organization is a customer of New Relic. 

I'd rate the solution eight out of ten. If it had better, easier integrations, I'd rate it higher. 

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.

We use New Relic APM to gather performance monitoring metrics such as thread count, CPU, response time, JVMs, and DB connectivity. New Relic APM is an observability tool.

To me, the most valuable feature of New Relic APM is the traceability, mainly based on the time travel method, so you get the overall response time, which is pretty helpful for developers and ADR techs looking into issues on a deeper level.

New Relic APM is a very good, tailor-made solution.

Documentation could be improved in New Relic APM, so users would have more clarity on configuring the dashboard. If New Relic gave better guidelines, users would find it easier to understand the metrics and features of New Relic APM.

Another area for improvement is integration with Kubernetes. Currently, the process isn't user-friendly. It's challenging and lacks documentation for users to understand how to integrate New Relic APM with Kubernetes quickly. With multiple levels of Kubernetes dockers and other DBs on different clouds, it's tricky to gather all into New Relic APM on a single dashboard.

What I'd like to see in the next version of New Relic APM is a single dashboard where you can easily view which applications fall under specific APMs. If there's a search feature where you can type in a keyword to find out if an APM is related to a particular application, that would be great.

I've been using New Relic APM for four years now.

New Relic APM is a stable solution, and I've never seen any outages from it.

New Relic APM is a scalable solution.

Support for New Relic APM is up to the mark, mainly because I belong to a big organization with dedicated email and Slack support. The support team gives clarifications about usability and configurations. I'm giving New Relic APM support a five on a scale of one to five.

My company also uses AppDynamics and Datadog for some of the applications, but those will be moved entirely to New Relic APM, as the tool is very user-friendly and has no lags. AppDynamics, on the other hand, has some delay, and you have to inject some methods in writing applications to gather the metrics. Performance-wise, New Relic APM is better and doesn't cause a high response time compared to other solutions.

Other teams handle the installation and configuration for New Relic APM.

I'm unaware of how much the license for New Relic APM costs.

My company is currently using New Relic APM.

Over a thousand people from different teams use New Relic APM within the company. My company currently has two hundred to three hundred applications, so even if New Relic APM is used occasionally, because of the number of applications it's being used on, usage of the tool could result in almost daily usage.

As New Relic APM is user-friendly, it's a tool I can recommend to others, but before making the purchase, you should utilize the free trial version, and also look at the sample dashboards provided by New Relic, which you can show to the customers to better explain how the dashboards look and what New Relic APM is used for.

My rating for New Relic APM is eight out of ten, as there's always space for improvement.

My company is a customer of New Relic APM.