New Relic Reviews

It helps us profile specific web server endpoints and identify what can be improved.

On a regular basis, we're able to identify incorrectly optimized SQL queries, external machine bottlenecks (i.e. higher throughput than can be handled), and other low performance issues.

I hope the next release has the ability to retain historical data.

A current limitation is comparing a present call with that of the same time the previous day, or previous week. It would be great to identify exactly which hours and days had lower performance than usual.

I've used it since November 2013.

It's trivial.

It's trivial.

Support is quite good, around 8/10.

There is a lot of available resources online, and support leads you to their forums initially. Response times are within 24 hours if contacted by email.

The initial setup was very straightforward.

The documentation is very complete and the procedure itself takes about five minutes, plus deployment time.

New Relic is a software as a service so there is no implementation per se, just a setup.

Pricing is great!

There are many free plans, and the for pay ones add a few important features such as longer log backup.

I chose this product for its ease of integration with our software stack, and its very attractive price plan.

New Relic is a great SaaS which I will definitely continue using and will use in future products.

We're a very happy customer.

The thing I use the most is the ability to tell at a glance that we’re in a red state. We have dashboards around our office which let me know what I need to pay attention to. I can dig into the error. It also has high throughput.

Mean time to recovery has improved, leading to cost savings and reduced customer dissatisfaction.

One of my issues was with not getting enough insight into errors, as I can only go back seven days. The data collection on it is not a long enough period of time if I want to see some trends. If someone is having some errors, I can’t get historical insight.

We had a problem where our application crashed because of New Relic. They acknowledged the problem and we just had to turn it off for six months.

It’s been scaling along with our growth.

Great tech support, very responsive. Have helped us solve problems.

I wasn't involved.

It’s just so easy to set up and use with little training. The barrier to entry is extremely low and it adds a high-value.

It allows flexible queries, allowing me to find answers easily.

It’s been helpful to get a unified understanding of how our application is being used, usage patterns, etc. We get a shared organizational understanding.

Alerting based on custom insights queries. If I set a custom query to give me some value, I want to be able to set an alert for that.

No issues encountered.

It’s been scaling along with our growth.

Great tech support, very responsive. They've helped us solve some perplexing problems.

Very straightforward. Worked through our account manager.

You’ll get way more data than you thought.

We primarily have an API so our front-end apps aren’t a huge part of our business, but Browser allows us to see geo-location to see where requests are coming from.

It also provides us with really valuable information such as which different browsers and versions our website visitors are using.

As a QA manager, it helps me to know exactly where to focus our attentions because we can pinpoint specifically where there may be issues -- where geographically, which browsers, which browser versions, and other very granular details.

I'd like to see alerting based on custom insight queries. If I set a custom query to give me some value, I want to be able to set an alert for that.

No issues with deployment at all.

No stability issues.

It’s been scaling along with our growth.

I haven't had to use technical support.

Setup was very simple and straightforward.

The overview itself provides us clear visibility of how applications are doing, and provides us our response times, data rates, and Apdex score.

We’re able to see how deployments are affecting the application, both good and bad. APM surely shows us the change in behavior. It lets us know how our application is doing. A lot of our information comes from trouble tickets, and we can correlate back to APM to see what’s going. It’s not so accurate, but it has to do with the data integration, but New Relic has said that it’ll give more data points and real-time data.

We always talk about, what is the data missing from New Relic? It constantly aggregates data so it’s not a true indication of how our application is doing. It’s not real-time. That was my concern, but after data presented by their CEO at Futurestack, they announced that they recognize the issue and are looking into solving it.

For New Relic in general, the mobile site doesn’t have single sign-on for iOS.

I haven’t noticed any issues. There may have been a couple of instances two years ago when New Relic stopped reporting data, but nothing that I know of since then.

We are using APM to use capacity planning, and the info we get has been able to help us.

We had an issue two years ago, and they were responsive and solved the issue.

I wasn't involved in the setup.

It loses points because our applications are running on Ruby on Rails, and our tech stack is not up to date, so there are some glitches integrating with APM. I'd like to see a fix for that.

Other than that, just go for it, you won’t regret it.

The application performance and monitoring. That’s the biggest thing for us as we previously just had a hodge-podge. 

New Relic gives us one view over all our assets. It lets us judge the servers and get a peek at the applications, to figure out if there are any errors.

We can make sure sites are up and running and that they’re performing normally. If we see any spikes we can troubleshoot – if they’re in house or in the cloud. Sometimes we can get to the systems faster because of the insights.

The one thing I really wanted to see was to getting more granular with the data, which may be coming in Insights. Being able to say, “What is the customer funnel? Where are they going to my site? How deep are they going?” At least from the demo it seems like they’re doing this in Insights.

Very stable. No issues.

It was already in production when I joined, but rarely used. Our group and our web assets decided to utilize it after a three month evaluation. We did it just for one application, but now have it installed across the board.

We’re still evaluating it since it’s relatively new in our environment. Make sure you understand the cost structure and that the solution will work across multiple OSs.

The alerting is by far the most valuable feature, closely followed by the way the platform correlates incidents across applications and components.

We are able to derive very valuable insights into the performance of the entire stack, and most importantly, we get a view as to which components have the biggest impact on the customer experience.

We have both Ops and Tech Leads subscribed to the alerts now. In general the Ops team only responds to "server down" or other infrastructure issues, whereas the Tech Leads will become interested if errors are being thrown or the Apdex scores are affected. They then have the chance to observe the system during an issue, as well as grab stack dumps and thread traces that allow us to quickly identify issues that are hard or impossible to replicate in a test environment.

I would like some additional fine tuning control around the alerting. I would also like the ability to "store" particular errors or traces for longer than the normal week.

We are yet to investigate creating dashboards and building extensions so there's a lot about the platform we still haven't found.

The biggest issue is the lack of mobile support from the website. They do have an Android and iPhone app but I have a Windows Phone and it's virtually unusable.

We've used it for about a year, and there are still a number of features we've yet to fully explore.

We see some exceptions in the machine Event Logs from time to time, and we occasionally see high CPU usage from the monitoring components but we've not seen any activity that compromised the stability of our systems as a result.

Support people are very helpful and turn-around times are short. I have raised a number of tickets and I've always been happy with the outcome.

We used to use Microsoft System Center Operations Manager but this is really not ideal for our cloud-based deployments

Deployment to our Windows, Ubuntu and .Net environments was very straightforward.

We provide managed services on Microsoft Azure and Verizon Terremark for a number of enterprise organizations including Government, Motor Vehicle Manufacturers and FMCG.

The hardest part was understanding the licensing and billing. The licensing and pricing was a challenge for us to understand, so speak to an Account Manager rather than simply buying online. I think they need a blog post about this.

We evaluated a number of solutions but this is the only platform we've fully deployed to production. We looked at MS System Center, DataDog, Paraleap and SolarWinds.

Start with a trial to get a sense of which components perform what kind of task, then divide your environment into applications and servers that require data retention, and those that don't. Put them into two separate accounts. The ones that require retention will eventually become a Pro account.