New Relic Reviews

We use New Relic to generate log management, like the different kinds of logs and alarms, and automate the same easily.

The versatility of the solution is its most valuable feature. It offers features like user behavior and user experience monitoring besides log management in one suite. When comparing it with other tools, other tools are primarily focused on only the management or only user behavior, but New Relic has both features.

The initial setup can be made easier. Like Mixpanel, New Relic can also have a step-by-step guide for the setup process. It needs slight improvements to be made in the user experience.

I have been using New Relic for two to three months.

It is a stable solution. I rate it eight out of ten.

It is a scalable solution. I rate it eight out of ten.

The initial setup was simple, but it can be made easier. I rate it seven out of ten. I did not deploy it a hundred percent because I was testing it out. The solution was deployed on the cloud.

I will recommend the solution, especially for a large product. So that one can have complete monitoring from the front-end tool and back-end server side.

I rate the overall product an eight out of ten.

If we receive errors or exceptions, or we need to check the load we use New Relic.

The most valuable features of New Relic are the reports and ease of use.

The price could improve.

I have been using New Relic for approximately one year.

I rate the stability of New Relic a nine out of ten.

We have approximately five managers using this solution.

I rate the scalability of New Relic a nine out of ten.

I have not used the support from the vendor.

We are mainly using Tomcat, but we use New Relic simultaneously. New Relic works as well Tomcat.

We have a team that does the deployment of the solution.

The price of New Relic could improve. It is expensive.

I rate the price of New Relic a six out of ten.

We have not evaluated other solutions.

One administrator can handle the maintenance on the weekends.

I would recommend this solution to others.

I rate New Relic a nine out of ten.

We are currently in the POC phase with New Relic APM and are looking at using it mainly for analytics.

We integrated the library within our backend service to see the throughput and to monitor latency. We also created a few dashboards in the New Relic dashboard section to observe the traffic and monitor how the system performs during the day.

It is easier to create new dashboards in the New Relic interface, and it is also easier to query if when I want to monitor a different parameter or time duration on my dashboard.

I like the overall monitoring and analytical features. It is a complete platform in that regard.

Some AIOps are missing in New Relic APS, and I would like to see more features in this area.

I've been using New Relic APM for approximately four months.

I would rate New Relic's stability at eight out of ten.

On a scale from one to ten, with one being low and ten being high, I would give scalability a rating of eight.

The initial setup is straightforward for this solution.

New Relic APM is a mature platform, and in terms of features and maturity, it is up there with other APMs like Datadog and a few others. Therefore, it is definitely worth considering.

Overall, I would rate New Relic at eight on a scale from one to ten.

Our primary use case for the solution is notification, customization, and everything from New Relic. Before adding a monitoring tool to New Relic APM, we need to add a subscription and specify the target we want to add, and this is a blank dashboard where we have to select, step by step, which modelling we want to understand. The solution is very similar to Azure monitor.

The new release is very valuable because it is well integrated.

We have been using the solution for approximately two years.

The solution is stable.

The scalability is good but can be improved.

The initial setup is straightforward. It is easy to track and easy to follow. It's somewhat like creating a graph where drag and drop features.

I rate the solution an eight out of ten. The solution is good, but the scalability can be improved.

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

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 can improve the information when we dig deeper to check a problem. There should be more detailed information provided.

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

The stability of New Relic APM is very good.

The scalability of New Relic APM is good. We have not had any issue with scalability when we use different types of loads, it worked very well.

The technical support from New Relic APM is very good.

The ROI from using New Relic APM is good.

I rate New Relic APM an eight out of ten.

We are using New Relic APM to monitor our production application and to get some insight into performance.

The most valuable feature is the ability to receive in-depth information about applications. It can detect a lot of important information.

The solution could improve by having more network monitoring features, such as for all the infrastructure.

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

The stability has been fine.

The solution is scalable. We had a lot of infrastructure at the beginning and it worked well.

The support could improve because they are not very fast and the information was not very accurate.

I would rate the technical support a three out of five.

The installation is straightforward, and it only took approximately one month.

Our office did the implementation of the solution.

The price of the solution could be less expensive. You have to pay a lot for each user. There is an additional cost for extra features.

My advice to others is this solution is working fine for me and it might most likely be for you too.

I rate New Relic APM a nine out of ten.