New Relic Reviews

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 are basically testing three products before going live with the new release of the software. We are also using it to monitor our production.

You can immediately see if there is some slowness. It can also alert you, and you can fix the problem pretty soon. In pre-production, you can ensure that everything is okay, and you don't put the worst performance to production. The performance should at least be at the same level as before.

The breakdown of the response time of different components and getting in-depth details of the slow component are the most valuable features.

It is easy to use, and it gets the job done.

There has been some problem with the agent, and it is just not working well. It is not able to record information with the application server. They have been able to fix the issue, but it took quite a long time. This is the main issue in the APM products and also in New Relic.

The mobile application monitoring has been pretty difficult to set up and also quite expensive. It should be a little bit easier and cheaper. Because it is pretty difficult and expensive, many customers don't take it.

I have been using this solution for four years.

Their technical support is pretty good. Sometimes, they took longer than I hoped. There were times when they took a couple of days, but I got help, and it is working.

They seem to have a new pricing model, and I would advise others to look out and ask them before buying.

The biggest lesson that I have learned from using this solution is that you don't always guess right. Without APM, you can guess where the problem is, but with APM, you can actually see where it is, which is nice to know.

I would rate New Relic APM a nine out of ten. It is a good product. There might be another product that is better than this, but this is the product that I use and recommend first.

• It integrates everything, which is awesome.
• The level of detail and customization, and integrating Insights with an application.
• Using analytics as an application database.
• DevOps for marketing.

Error handling and reporting is a little lackluster, but they're announcing a whole new analytics approach.

We have a big deployment and use all of their product offerings except Mobile and Plugins. We use APM, Browsers, and Insights.

No issues. It’s expected since they’re cloud based.

They’ve been friendly and responsive.

We compared them to others, but they seem to be pumping out more features. Insights has no competition. They pump APM and browser data automatically so that it’s all seamlessly integrated into their insights.

The way some transactions are recorded, you can dig through and see what’s going on with the request, how many times you’re making a certain call. That’s the biggest part – almost like application profiling.

We get greater insight into what our application is doing once it’s in production. We can identify issues faster, and being able to identify issues before they become a big problems is an improvement. We use it in load testing to identify inefficient query patterns.

At times some of the data can be opaque. Some of the aggregates over time tend to become more vague, so you lose resolution. Greater resolution going further back in time would be nice. If I start going back a month or two, the resolution is a lot lower, which is kind of challenging and makes it harder to do in-depth historical analysis.

Alongside APM, we're using New Relic servers, plugins, and pretty much everything else except Insights, Synthetics, or the mobile product.

Pretty stable. Sometimes the charts will fail to load or there are some random errors. But because of the way we use APM, there’s no significant impact.

Our use doesn’t really push the limits of New Relic, but it looks like it will scale just fine.

It was already in production when I joined the company.

I don’t see us being able to operate without New Relic. It’s important to collect a lot of metrics, but it’s more important to identify the ones that are essential to your business purposes. Know which data are really important and what you should keep an eye on.

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.

We primarily use the solution for watching user behavior, among other use cases.

The VPN is one of the solution's most valuable features for us.

We like that we have the ability to view users and speculate.

The initial setup is very easy.

The older view is much better than the new view that they have. We'd like to go back to that previous version. The user interface just isn't as nice as it used to be.

The solution does not seem to be lacking any features. I can't say that I recommend any specific features for the next release.

I've been using the solution for about 2 months, more or less. It hasn't been too long just yet.

The stability of the solution has been good for us so far. We don't have any problems with it. It's reliable. It doesn't crash or freeze. There aren't bugs or glitches. 

We've found the scaling to be good. If a company needs to expand it, it should be able to do so without any problems.

Currently, we have four or five people using the solution. Our company, however, works for my customers, and therefore we have a lot of ongoing projects.

Technical support has been good so far. That said, we haven't really had any technical issues either. We're satisfied with the level of service we've received so far.

We didn't find the initial setup complex. The implementation was straightforward and simple.

The deployment was pretty quick as well. It might have taken us one to two hours to get everything done.

We're just customers. We're end-users. We don't have a business relationship with the company.

I would recommend the solution to other organizations. We've had a good experience with it so far.

On a scale from one to ten, I would rate the solution at a ten. It's pretty much perfect for our purposes.

The most valuable features for us are--

• Real-time monitoring
• The interface
• The look and feel
• We can check the environment periodically throughout the day
• Good forensics tool if there's an issue

We can monitor response times, volume, and Apdex. Our alerting is based on Apdex. It's a great sanity check. It's helped us to find problems early and to make sure that what we're doing is working.

I'm on a small team and have an interaction with the Ops teams only when a negative happens, but I've used it a couple of times to pass problems from my plate to someone else's as I've proved it's not my problem.

It doesn't give us rich process tracing, which is the only complaint I have. It divides our system into four parts, and I would like it to go deeper into the code. However, this can be a challenge because of the way it is configured with us, but they are working on it.

It's fantastic, with no bugs or lag.

It scales, and I can't speak about this, but we are moving everything to AWS and it should be fine.

I've never needed them, and the one issue I had, our Ops guys told me what to do.

I would just advise you to use the tool.

It was already in place when I joined.

There are many things, but in particular I like the real-time monitoring. We get to know when a specific service or specific URL is failing and not performing. We can set certain delivery thresholds, which, if broken, we hear about it immediately.

It allows us to monitor in our little part of the company, but it plays a role in the larger functioning of the company because we have our hand in so many areas.

Nothing. There’s not really anything I don’t like about it.

It’s generally stable, but last year it was a little flaky. It wasn’t as responsible as it should have been, as sometimes you would lose some things that you’d worked on, but very few incidences. But currently the newer version is very stable.

It's scalable, but it comes with a price.

I used tech support a while back, but I can’t remember if it was a positive or negative experience. We only had a small issue. But they’ve improved a lot in terms of a larger knowledge base and the usability of the solution itself has improved.

No previous solution was used.

I was not involved as it was already set up when I came. At my previous company two years ago, I helped set up, and it was a little bit of a hassle, but it was a different platform (Java). Now it's nodes.

Licensing is based on scale.

It depends on your business, but it's a very useful tool. If you're in the web, you probably need it.