New Relic Reviews

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 are monitoring our server database to see if there are any anomalies or problems with the servers and databases.

Since we migrated from on-premise solution to the cloud (AWS), we have migrated somethings into Lambda API Gateway and DynamoDB. We have also done the New Relic integration with Serverless AWS, which has helped us with monitoring, and keeping our monitoring from our on-premise part with the cloud part.

• The alerting system
• The integration of API Gateway with Lamda and Serverless AWS.

We are sharing different AWS accounts, and if a Lambda has with the same name but a different AWS account, it is a little hard to understand whether AWS or Lamda belongs to that account. Also, we have multiple accounts on the drop down to filter by Lambda, but we see two Lambda with the same name, then we don't know which one to choose. So, it needs to improve its filtering.

We would like a more sophisticated filtering for the Serverless AWS pieces.

We have not had an issue with stability, so we are happy with it.

For all the features that they have and for the amount of data that we feed them, it handles the stress well. 

We run 20 web servers, 500 Lambdas, and 50 DynamoDB tables. We also have an enterprise SQL Server with different instances along with MySQL databases and mobile applications.

I would rate the technical support an eight out of ten.

We were previously using Datadog. At the time of the switch, both companies were closely related product-wise, and some of our company was already using New Relic. We also chose it because the monitoring tool and alerting system fit our needs.

The integration and configuration of this product in our AWS environment needs improvement on the filtering part. I would like it to go more granular on accounts. There is also some room for improvement on the integration with Serverless AWS.

Because of budget, we are not using the mobile app part of this tool.

New Relic has been in the business for a while. It offers a wide selection to attach a monitoring mobile app, server, and cloud. If you want to go with just one product, it fits all your needs.

We were using the on-premise version before going to cloud. So, we were using it on the physical data center, then we migrate to cloud and started using it with AWS. We haven't seen any different between the two products. We have been able to monitor in both.

• It's easy to install and to configure.
• The UI interface and navigation make it easy for a novice user to quickly use the provided relevant performance application data to determine how well their application is performing and to see other areas which may require some further tuning.

It provides a single pane for operation teams to look at and get to the root cause of issues. This allows them to take the required corrective actions and to remove some of the blame game. People can only look at their own isolated metrics.

• Ability to set-up maintenance windows, so silent time can be given to monitors for a defined period of time.
• Alerts tend to show how an entire cluster is performing, and not only that a given node is having an issue. To get around this issue one can use parent-child relationships in the naming of given applications and set the alert conditions at the child levels.
• For browser, the need to provide an interface which allows us to define a given business transaction, e.g. define all the steps of a given credit submittal. This is somewhat possible using “Funnels” with New Relic Insights.

We've been using it for a little over a year and a half and have it in the following -

• APM deployed across JBOSS, Tomcat, WebLogic, Glassfish, ActiveMQ, .Net
• Server deployed across RedHat, CentOs, and Windows 2008/2012
• DevOps deployment of APM and server agent using chef cookbook

APM and server agents are deployed via a chef cookbook or shell scripts. In one case, we had a very old version of Java running and had to deploy a corresponding older version of New Relic.

It has been operational for over a year and a half across over 200+ applications on Java and .Net, with no negative impact to any of the systems.

Given that New Relic is a SaaS model we haven’t had any negative impact utilizing their UI to view given applications or do analytics with Insights.

They are very dedicated and attentive to our needs as well as how their products can be utilized to enhance our support of given applications - 10/10.

Their on-line technical support has always provided timely updates of any open tickets as well as very open to getting on a chat Webex to resolve issue. Many issues have been resolved on either the first or second exchange of notes in their ticketing system - 9/10.

We previously used HP Diagnostics and CA Introscope. We switched for several reasons -

• UI interface required more training of the support teams to utilize the product because it wasn't as intuitive.
• Large infrastructure to support and administer the environment.
• Requires RUM appliance to tap the network so that we can gain insight into the end-user response.

We deployed the agent via simple manual steps or via in-house written scripts.

It was deployed by an in-house middleware team with vendor consulting in a few areas where the browser auto injection failed. The vendor team was very knowledgeable of their products and how to deploy and configure across an array of platforms.

Implement APM and server on non-production environments as well, especially an environment where you are running performance testing from. BrowserPro should be a requirement, and you should look into New Relic Insights as it is a great diagnostic tool. Make sure you keep, at a minimum, a few months worth of detailed data as well as populating it with additional custom attributes or data from other systems.

The ability to trace transactions all the way down to find where the software is broken - database, web services, etc., and all the way down, with the trace dumps, to see where our application is broken.

When our app passes critical threshold, can quickly go to Transactions and/or Database views and immediately see the code areas causing the issue. Saves so much time in debugging our code and environments.

I can have my developers find bugs and fix them in one-tenth of time they used to take. It enables the stability of our product, and it's allowed me to keep human resources at a minimum so that we have a smaller number of people to do better things.

In Alert History, while you can see the trending in response time by Request Queuing, .NER CLR and Database, if you had the ability to see which transaction type was the slowest during the timeframe when the critical error occurred by displaying the info within the same “tool tip” hover window which currently gives me the time per request and number of transactions, i.e., if it had the additional correlation information of “StatusCode/403” which you can get from the Events Errors hover. This has the potential of saving a lot of analysis time going back and forth between views.

We didn't have any deployment issues.

I haven’t had any issues with stability.

It’s scaled for us. We’re still relatively small with just 16 servers.

When my IT manager did the initial install, they were very responsive.

It was straightforward, but the issue was the unfamiliarity of our IT manager outside the Microsoft world.

If you want to save money, go for it. Time is money, and it saves you so much time to be able to find issues and to fix them.

Mainly our developers use this solution, and the executive management. They love seeing all the reports and dashboards. There are two things: your current features, how many people are using them, and that also gives us the sense of what people really want.

It’s like a marketing opportunity also. It gives something more which adds value. From a developer’s standpoint, we can practically put customer attributes for every transaction. We just keep pushing data, different customer attributes, into New Relic, and we can understand quickly what happened in a time frame, plus all of the dashboard views, drill-down reports – you can have multiple reports. The good part is that we don’t have to implement anything on our side – we just use the features.

Every action we have certain attributes that we keep pushing data and we don’t have to worry about it. It captures everything, which we can send to executive management. We can put a feature out and see how people respond to it, and that can go into a release which will help make money for the company and add value for the customer.

Probably make the query language a little bit easier. Improved documentation. The reasons we had to call them (they were super helpful) is because we couldn’t find the documentation. It would really help if they were to come up with some online help where you just type something in and get the answers.

In the last year, I’ve never seen Insights go down. In the first couple of months we had a little bit of trouble understanding it, but that’s OK. The query language is a little bit different. It never breaks.

I’ve spoken to them about 20 times after we started using Insights, and they were just brilliant. No doubt about it. Even the account manager could help direct resources to us to help solve issues. All we do is call the account manager and he would get us the correct person; we like to send all of the questions in an email in advance and we’d make arrangements to go through the issues or questions immediately in a meeting.

I was the one who recommended Insights. We implemented a trial for 60 days and we ended up saying yes. We love it. We do a lot of dashboard stuff. Especially the executive management, they just want to see what happened in a given week or time. What did the vendors do? What did the customers do? Who’s working on what?

It was pretty straightforward. We just put the DLLs into the solutions, make a couple of config changes for New Relic so it detects the name of the product or web app or whatever it’s trying to monitor, and just keep pushing customer attributes or whatever you want. It was very simple. Within 30 minutes you see customer attributes in the environment and it starts capturing.

I think we also looked at one or two. The first one we tried was New Relic. The reputation of the vendor – we decided to give New Relic a try after hearing about how it was used to fix the Affordable Care Act implementation. That’s how we heard about New Relic. We needed to set up monitoring and alert – when we saw New Relic we liked it and its ease of setup. We gave it a 30-day trial and after that there was no looking back.

I really love it. I’m not a developer, but I can just walk up to a developer and ask them to push some data so I can see what’s going on. It’s very easy. The whole ease part; once the code is pushed I just wait to see what events occurred.

If they don’t want to build something on their own (and it all depends on company size resources, etc.) an APM solution is the right answer. Given we have only one infrastructure guy and he can manage all of this, and a small team, everyone can use it all for different purposes. Stress testing, load testing, and evaluating performance. Each team has different ideas about how to use the reports, so it’s good for everybody. Different skill set people can use the entire NR suite for different reasons. It’s the whole package.

We have service in multiple countries, so the monitoring and alerts are valuable features for us. 

Given that the size of the team is small and we have one infrastructure engineer, it’s good that we constantly get alerts if something is going wrong somewhere. You see the spikes. Since we are a small team, one person can set up alerts for three instances, and other instances in UAT, test, and QA environment.

First of all, it tells us loopholes in our system. The whole error-reporting thing lets us identify problems faster so we can take corrective action sooner. We can think about performance of certain code that’s been written, so we can take preventative actions.

They’re adding analytics, geo analytics, more mobile app monitoring. They have the data explorer – all those features will really help.

In the last year I’ve never seen APM go down.

APM was already in production when I joined the company.

I think we also looked at one or two. The first one we tried was New Relic. The reputation of the vendor – we decided to give New Relic a try after hearing about how it was used to fix the Affordable Care Act implementation. That’s how we heard about New Relic. We needed to set up monitoring and alert – when we saw New Relic we liked it and its ease of setup. We gave it a 30-day trial, and after that there was no looking back.

The error analytics thing – we always wanted that. This is something that is coming up in December. Geoanalytics will be super helpful. There’s always room for improvement, and they’re still getting there coming up with new ideas to make it super comfortable.

If they don’t want to build something on their own (and it all depends on company size, resources, etc.), an APM solution is the right answer. Given we have only one infrastructure guy and he can manage all of this, and a small team, everyone can use it all for different purposes. Stress testing, load testing, and evaluating performance. Each team has different ideas about how to use the reports, so it’s good for everybody. Different skillset people can use the entire NR suite for different reasons. It’s the whole package.

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.