New Relic Reviews

Just to show the response time of the app, and how much time each request spends in the tiers. Database is a tenth of a second, web takes two-tenths, and Ruby takes one-tenth.

I can tell you that there are two use cases. One is to look at how we are performing on average over time. So, assuming the systems are healthy and we look at the last month, the average response time is very good at telling us that. Let's say I add capacity, I can see it trend downwards. The other use case is pinpoint key problems happening right now. Uber called and they are saying that their Freshdesk isn’t working. We look in and can see clearly that only the database is taking 27 times longer than it should, and it helps us solve acute broken things.

It helps with current broken things and help us understand what is happening on our system overall.

It just gives us an idea for how fast were running. That cuts down to it -- how fast we're running, and if there is slowness, where it's coming from. It's really fast at telling us.

I would say that the user interface is maybe a little bit overly complicated. But I don’t have any specific way to improve it. I would say that what’s not commonly used, that are rarely used, should be less conspicuous and buried behind. Like your iPhone has one or two buttons -- if you need settings you can dig down to that stuff, but you don’t want that in your face when you take a call. Similarly, when you are in New Relic there are all these things that I need to sift through mentally. I just want to see how fast the apps are responding. You can’t change that.

I want to see the potential for Docker statistics or container statistics. Like if we start running containers, will it be able to track data for a given container. If one container serves one purpose, we need to track how many requests per day, when does the usage peek, how much does it vary week to week. And then that needs to be organized per container.

Finally, there's lot of noise on the front page that I don’t want to see. If it is customizable then it isn't obvious. Another nuance is that it always shows the wrong throughput for the most recent five minutes, and it's always wrong. The system is wrong for the most recent five minutes. They show wrong data and that changes after the five minutes is up.

We've had it for more than two years.

10/10 - it's very stable. It went down, maybe, once.

Super scalable. For us it scales for what we need. Scale means does it work as well if you have three nodes or 500, and it does. It doesn't break when you scale it up.

I don’t know. Never had a problem. Never had an issue with it. Really simple, like your microwave. Does it well so I never needed support.

This has always been our solution since we started.

We looked for a product that gives the data in a way that is easy to visualize, is reliable, and is simple.

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.

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

Transaction trace under APM.

Ajax section under browser

Helped us pin point the exact piece causing the performance bottleneck by using the transaction trace view.

Instead of picking up a few values under trace, it can provide a list of every hit and their traces while keeping minimal overhead.

6 Months

Yes. Installation of plugins seem to be really difficult due to the documentation available.

No issues.

No issues yet.

Yes, installation of the APM piece and Server piece is straightforward but the plugin may cause an issue.

Trends and Alerting have been valuable features.

We can analyse events after the event has occurred. This gives us better visibility to plan resolutions in a timely fashion.

Performance/bugs.

6 months.

Sometimes we've noticed agents fail to report/respond.

Yes, we have encountered issues with stability.

No issues with scalability.

Excellent.

Excellent.

No.

No, simple setup process.

In-House.

Unsure.

< $1000/month.

None.

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.

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!

The most valuable features for us are:

• Application performance index score
• Error rate
• Transaction traces

When an app goes down, we can get insights into the issue with New Relic. It tells us what the problem is. For example, if there is an issue in the code, we see a spike in the error rate in the applications. The load environment lets us stress test our application to find the bottlenecks in the code.

They already have everything we need, so I can't suggest an improvement.

I was not involved with deployment.

Very stable. No problems.

No problems.

One issue – there is no option for live chat or phone support. We can go to the community forum to post a question and wait for the answer.

The solution was already in production when I got to the company.

New Relic is the right solution in my opinion. The light version of server monitoring is free with New Relic, and application performance index and error rate are the key features to look into.