New Relic Reviews

The main APM page with the graphs. We leave that up on our wall and we can tell pretty quickly if something is about to go wrong, or if the response time slows down. Database queries are really helpful as they helps to figure out where the low hanging fruit is in terms of making the site faster on the database site. 

I use key transactions a lot when I’m tweaking the resources for the site. There are certain transactions that I care about more than the rest. 

I use the throughput numbers a lot, especially working on workers as opposed to web. If I’m going to add more workers, first I want to know if there will be a bottleneck somewhere.

It saves time and engineering resources in terms of making things faster and diagnoses problems. For us, engineering uses it but no one else even knows what it is. Overall, it improves the experience of the customers and site users.

It’s pretty solid. Sometimes they have downtime – for the most part the New Relic site is up all the time, but once in a while the data is delayed on the graph (like every month or two), but other than that it works!

It’s scalable – thumbs up. We turn on new servers and New Relic just works.

It was already in production when I joined.

All the information is there, but sometimes it’s hard to figure out what it means. You have to have used it a number of times in order to understand where to look. It doesn’t tell you the whole story, it just gives you pieces.

• It provides information on where time is spent overall in server requests.
• It performs database query time analysis.

New Relic APM generates weekly performance reports, but they aren't really actionable.

No, but it was deployed before I arrived at the organization.

No, the service appears very stable. We get occasional 503 errors when pushing data to New Relic, but it's fairly infrequent.

No issues encountered.

We haven't had to interact with customer service at all.

I haven't had to use technical support.

We've always used New Relic.

It was done in-house.

We never quantified this.

New Relic was the market leader at the time. It still is, although there are more competitors now (AppNeta, sysdig).

• App server monitoring
• Response time
• Error Rates

We used to get lots of complaints from clients on app slowness. Using New Relic we are able to solve the slowness issues based on traffic and server response metrics.

Errors insights have room for improvement especially error analysis part which is somewhat less compared to similar tool Splunk.

Over 2 years.

No issues encountered.

None encountered. It's quite stable.

No issues encountered.

9 out of 10. They have a great support team.

9 out of 10.

No but we are using Splunk and New Relic along with Stackdriver Simultaneously [Don't want to depend on one and use the features of all].

We followed their documentation and it was good enough to set it up.

In house team.

About 50-60%.

We spend around $100 per month.

We analyzed AppDynamics as well but found New Relic better suited for us.

Please go ahead and try this and you won't regret having it.

• Infrastructure management
• Application management

We have an operations center which uses it quite extensively to manage production. They can go back and look at trending and history of the applications. They have alerts set up which trigger off of it. 

I go in afterwards and help do the root cause analysis and troubleshooting.

It is a software solution as a service, so I don't have to manage it on-premise.

I would like to have storage monitoring. E.g., being able to monitor SANS, specifically protocols, like NFS and CIFS metrics. I have not seen the ability for it to do this and having some way to do this would be awesome.

The stability is fine.

It seems scalable enough. We are always hitting the limit of the number of agents that we have, then we buy more and it works.

I have not used technical support.

New Relic SaaS seems to do some things much better than SolarWinds, which we have on-premise.

Give it a try, install it, and use it. I don't have to manage the server and worry about the database, storage, and VMs being up and running, etc. It is always there.

For the way we use it, we like the monitoring of websites and it allows us to look at the trace stacks to identify problems. We’re also able to compare the day and the week before to see whether problems are reoccurring.

Before New Relic, dev and ops were separate, and now they’ve come together more and there’s less finger-pointing. There’s a clear understanding of where the problems are and so the people responsible can solve the issues. There’s more trust between the two groups and people are more willing to work together.

Stack traces don’t go far enough. They get to a point, indicate a question mark, and then stop. But New Relic is working on it. Also, one can get lost in the data.

We’ve been using it for two to two and a half year.

We've had one or two occasions of a few wide spaces in the graphs where the response time didn’t keep up. Sometime it’s a bit slow in processing data, but now it’s much faster and more stable with new releases. Some of the releases I think are already there in production.

We’ve been able to scale without issue. We’ve installed it and it works.

I haven’t had to use technical support. When we decided to use it, our CTO went to FutureStack and got a lot of knowledge.

So easy, very straightforward. Our developers, at the beginning, created some templates for data they wanted to track and that was it.

Just go for it. When I show people what it can do, it’s mind boggling. What’s coming up in the new release -- wow!

Monitoring, Custom Dashboards

New Relic gave us a quick, easy way to monitor our web application for all of our systems. This changed how and what we responded to.

I would like better alerting. I also would like to see a bit more detailed information. Though I was happy with the detail I did get.

2 years

No, deployment was easy.

None

None

We had several solutions in-house.

This was a simple setup. I never received training and I was able to get in to the admin console and set up the dashboards I wanted.

In-house

Get over the SaaS security concerns.

We can place ad hoc queries to understand user behavior and customer patterns. The data can be collected for any activity that we want to see on any part of our website.

Its greatest benefit comes from its ability to provide trending/marketing data. We can replace some requests from our data warehouse and get a quick glimpse into that data, especially with our mobile platform and website for different browsers.

The metrics that I want are already pushed to New Relic, but some data we haven’t pushed to New Relic. Internally, we have a solution that’s better than Insights to provide us analysis of that data. I’d like to see Insights take care of that analysis and use its graphic engine.

Not enough working experience to comment on this, but in my experience, no instability.

I haven't had to use it.

I wasn't involved in the setup.

The things that I would need are proprietary, and I don’t think that data can be pushed out to Insights. Take a look at internal processes to see what can be done quicker by Insight and make a good test case of it. You must present it as a better alternative to the existing issues. Get early adopters excited about it and build a relationship based on that.

It is easy to set up from scratch, as you don’t need resources.

Also, the response time and PHP are valuable.

From an ops standpoint, we can know and pinpoint what the problem is. We're excited by down-to-the-server performance, as this was missing before.

If they added the monitoring to the ops-server side, it would be better.

We're using it alongside Insights for about three years, and heavily for the past two years. We had logic monitor that helped us at server level.

We're moving our infrastructure to AWS, as they are integrated with it.

No issues with tech support.

It was easy.

It's easy to deploy and maintain, and all bugs can be handled.