New Relic Reviews

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.

Our company uses the solution for time series analysis. 

The solution is good for sending alerts, drawing graphs about system usage, and creating plug-ins. 

The solution should include more detailed reports for SQL database requests. 

I have been using the solution for three years. 

The solution is very stable and working fine. 

The solution is scalable and has been used for both small and big projects that scaled over time with no issues. 

Technical support is knowledgeable, responds quickly, and provides good assistance.

I rate support a ten out of ten. 

Positive

We migrated from AppNeta because the solution is more stable and cost effective. 

The setup is easy and plug-ins can be written for any differences required. 

I rate setup a ten out of ten. 

We implement the solution in-house for customers and offer both on-premises and cloud options. 

I prefer the on-premises option because I like to configure and set things up rather than using ready-to-go options. 

The solution does not require ongoing maintenance because it works fine and runs with no troubles. 

The solution is less expensive than AppNeta. 

There were some benefits to using AppNeta. It provided more detailed stats and graphs for hosting products. If you need more specific digitalization based on system stats, you might want to go with AppNeta. For our use cases, it was less stable and more expensive than the solution. 

The solution is an excellent product for time series and operation analyses. It is a good and stable solution, has a good price, includes good usability features, and includes good support. 

I rate the solution a ten out of ten. 

The APM is great.

The solution can scale well. 

We've found support to be helpful.

It has a simple initial setup. 

The browser isn't exactly reliable. 

There are dashboard issues that need to be dealt with. 

There's no proper management of roles and divisions. For example, let's say if I create a dashboard and I want to give access only to a set of people and not to the other set of people, I can't do that, and that's where it has a lot of problems. If I develop a dashboard for myself, everyone else has an access to it. There's no proper access management. You just add someone to the platform, he gets access to all the dashboards. Yet there should be proper division of people who need to have access to a certain dashboard. 

I've been using the solution for three years.

While the APM is stable, the browser itself isn't too reliable. 

It's a scalable, reliable solution. 

We have 30 to 40 people working on the solution generally.

The technical support is quite good.

Positive

The solution is very simple to set up. I'd rate the entire implementation and deployment experience a five out of five. 

I've not witnessed any ROI. That's beyond my scope. 

I'm not aware of the exact licensing cost. The contracts are handled at an organizational level. 

We have a partnership with New Relic.

I'd advise potential new users to go through the docs first. They have very good documentation. Anybody who's going to start should first start with reading the documentation in order to get a good understanding of the product.

I'd rate the solution seven out of ten. I'd rate it higher if the browser rate was more reliable. 

We use this solution to provide insight into how the UI is performing.

We appreciate the way that this solution allows us to monitor the ongoing status of the UI at any given time.

We would like a dashboard feature to be created for this product.  This would allow us to monitor both the front and back-end of our UIs performance, and then report on it.

We would also like the solution to increase the details that are provided when there are system abnormalities.

We have been using this solution for three years.

We have found this to be an overall stable solution.

We have found the cloud-based version of this product to be scalable.

We use an in-house support team for this solution. They are our first-line contact point to resolve any issues that arise on a day-to-day basis.

Positive

We were previously using a different, comparable solution. However, we decided to switch to this product as it provided lower response times.

I would rate this solution a nine out of ten.

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 have both the mobile and web applications which use the APIs in the back end. The New Relic Browser also monitors all our review servers and has mobile and browser compatibility. Most of our stakeholders view the data on mobile and don't need to open their laptops.

Stakeholders can install New Relic on a mobile device, whether iOS or Android and monitor the enrolment. It is more compatible with the mobile device, but we can view it on the web browser, and the same features are supported for both. In addition, stakeholders can access the system 24-7 and can monitor it from anywhere, anytime.

We can view the system in one view, showing the utilization and server activity. It lets us tell if our server utilization is high, conduct a memories review, and view it in one dashboard.

The solution only supports the cloud platform and not on-premises. Therefore, they should assess supporting the licensing on-premises as well.

Stability is good, and we had no challenges while accessing the New Relic system from the browser.

Scalability is good, and there are no limitations. Once we add our users to our account, they can access it anywhere in the browser. We have never experienced any technical problems.

We have more than 30 users that are already configured in our system. The pricing depends on the number of users we have, and we currently have only about five or ten active users out of the 30. Only our operations team typically accesses the browser.

We have four to five people who maintain and manage the day-to-day operations. They have other tasks at the company and are not dedicated solely to the maintenance of this solution. They monitor how the servers are performing and get alerts to their emails.

New Relic technical support is good whenever we raise a ticket. They reply and provide knowledge sharing for new features. For example, before the COVID-19 pandemic, they would come into our office and share knowledge with all the operational and delivery teams and others using the New Relic system. Their support and contributions are good whenever we need them.

The initial setup was straightforward and didn't require much work on the browser configuration. The user administration is also good if there is an existing New Relic account. It allows the restriction of privileges and control of users accessing complete information. In addition, it provides for a bucket of developers, stakeholders and operations and restrictions of certain access to view dashboards or features.

Browser implementation is also simple when an account and servers are added to the New Relic system. Those servers are automatically reflected on the New Relic account, and we don't need to do much. It is straightforward, and once we configure the agent, all our servers are under our account.

The pricing is a bit high, but the features are very good. It costs about 1500 per month, but historical information was something we had to buy at an additional cost. Other than that, the rest of the capabilities and features are bundled in one package.

I rate this solution a nine out of ten. We have never faced any issues with this solution, and we are not worried about the technical capability. If we have a team that understands the system and the new capabilities, it can be used effectively.

New Relic APM is an application monitoring tool.

There are many valuable features in New Relic APM. We developed some software applications and we are able to monitor the errors very easily. Their log security retention is very good.

New Relic APM could improve error debugging and the correlation with the logs. We are receiving some alerts or alarms but we need to correlate with the error log, but it is difficult if it is more than seven months retention period, it is hard to trace. We need this especially for getting historical information. 

Within short periods of monitoring, we do not have a problem it is only when it crosses the retention period that we are not able to correlate the errors with the log.

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

New Relic APM is stable. In the last two years, we have not faced any stability issues. If the vendor is having a maintenance issue they will notify us in advance.

I rate the stability of New Relic APM a six out of ten.

They are a costly solution and the stability should be better for the price.

The scalability of New Relic APM is good.

There are two types of users, one is the basic user which is free and has limitations. We have approximately 40 basic users. The second type of user is pro which does not have the limitations of the basic user. We have 10 pro users.

The support from New Relic APM is good. We create a ticket, and immediately after we have the support. 

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

We were using another solution previously. New Relic APM was picked by the organization because they preferred it, and this is why we switched. New Relic APM is easier to configure.

The initial setup of New Relic APM is simple.

The price of New Relic APM could be less expensive. We are using the New Relic APM pro account and it is more costly. When compared to competitors the solution's pricing should be much more realistic.

I rate the price of New Relic APM a one out of five.

We evaluated other solutions, such as Dynatrace and Datadog. When comparing New Relic APM to other monitoring tools, it's not complex and is similar in features.

I rate New Relic APM a six out of ten.