New Relic Reviews

I think the downtime alerts as well as the insight into performance killers from database queries are the most valuable feature for us.

I think that we didn’t have much insight into which things were causing the biggest performance hits, so it gave us instant feedback on incidents which may have caused users enough pain.

They have integrated alert and performance monitoring which they’re rolling out as a beta now. A lot of the features for application monitoring and uptime, and alerts for alerting the appropriate people when something goes wrong are not quite there yet.

We’ve never had any problems whatsoever.

It’s been useful as we’ve grown our user base; we haven’t had any scalability issues. We’ve done tens of thousands rather than tens of millions of transactions.

I’ve only used it a couple of times. They escalated the issues appropriately and it always seemed like someone who understood the issue jumped on the ticket, and we’ve had the issued resolved in a timely fashion.

We were previously using nothing else. We were reading through logs trying to interpret our own data, which was challenging. Someone suggested New Relic and we went with it right after; they’re the only player in town for this sort of environment.

The initial ground level setup was very easy, very intuitive, and went very quickly. Some of the more advanced features did require a lot of review of their documentation and a few support tickets to figure out.

I think documentation is probably key for us, and then support. Reputation and long-term relationship doesn’t matter so much if they have a good product. For this product we didn’t really have a viable alternative. We couldn’t find anybody else who did something similar.

We’re very satisfied with it. We had a little difficulty plugging in some more of the advanced features. It’s so big and so complex, but New Relic does invest in education.

This is the best tool for gaining insight into SaaS or cloud-based applications that we’ve seen. Unless you’re going to roll your own solution, you pretty much have to use them.

Debugging tools, as we’re huge on this. Being able to drill down into what’s actually going on with our stack, being able to see the performance issues, where our bottlenecks are.

We do continuous deployment and delivery. One of the things that’s useful is to be able to detect when we deploy bugs and issues into the live platform – error reports are hugely useful.

Throughput, apex, those kinds of things, so we can always see what’s going on. The New Relic Browser also gives us the front-end reporting, versus APM on the back-end.

Speed to issue resolution – making sure our stack is healthy. If someone reports an issue we’ll always go to New Relic first; that’s where it becomes a good product in and of itself. It gives us all the information we need in one place.

We have custom insights dashboards – massive screens with all this information aggregated.

A few issues in the past; there were some CSS issues where sometimes the CSS wasn’t rendering, but they seem to have overcome those. I’ve never experienced downtime which is impressive.

We use the APM scalability tools; more so in the past. Now we’re in the cloud we can see how the stack performs. We use some of the graphing to see at what point we’ll hit bottlenecks, and the in-depth reporting to identify weak points.

We’ve used it a couple of times. They’re great. They follow up with us as well, which is nice and quite unusual.

It was already in production, but I have done it in the past elsewhere. It’s so straightforward it’s ridiculous.

I like the solution so much I haven’t necessarily tried other products and don’t need or want to. Ask if the solution has the main features your stack needs. Does it support your languages, frameworks?

I like the integration with PagerDuty, so that helps spread out our on-call schedule. Application performance helps us drill down on the bottlenecks in our applications, to save us a lot of development time.

The real benefits are for end users. They’re getting a better experience with our software. It allows us to respond faster to any incidences.

• Better error reporting
• Better ability to drill-down into errors

No problem at all.

It's absolutely great.

No problem at all.

They were fine. I spoke to a developer from the mobile team and he answered the question on the first attempt.

This is our first APM. We were looking for a solution that helped us to improve our customer experience. It was borne out of database issues we were having at the time. We had no APM solution prior – it was all done manually.

Straightforward. It would have been better to have more transparency to understand how New Relic actually slots onto your page, how it fits into your application.

We also looked at AppDynamics. New Relic felt like a better solution and the data that came out during the trial was better.

Breadth of features, user experience, and constant development of the platform, as well as the value it’s adding to our business. Our products have grown with the New Relic platform; we see the value that people are getting from the platform. The data pretty much speak for itself – sign up, get a trial, and use it in production immediately.

The ability to have real-time performance statistics, as we need to know if the main features of our website are working and responding fast enough to our clients' clicks.

New Relic helped us in realizing that sometimes our online service wasn't as fast and reliable as we expected it to be. With the help of New Relic tools, our organization was able to detect, track, and fix errors in our website, so we focused our efforts in these areas.

The pricing model. New Relic can be expensive for growing startups. Maybe they should think of some more choices.

I've used it for two years.

Not at all.

No, access to the New Relic website and reports was always stable. Monitoring, events and reports are always available and we didn't notice any kind of downtime.

No, our website started with a small number of users and grew to hundreds. New Relic was always working as expected.

Customer service has always answered our questions very quickly, even on weekends. It seems very effective. 10/10.

We previously tried some hosted solutions using a variety of tools to perform monitoring and reporting tasks. We decided to switch to New Relic for its simplicity on setup and maintenance. We are able to quickly deploy new servers using New Relic in zero time.

New Relic offers great tools to integrate your software stack with their tools, and everything worked like a charm.

We implemented New Relic ourselves

Pricing can be dangerous if your product grows a lot. You should start with the free lite option to see if you can find New Relic useful for your application, and then try the Pro version with one or more hosts.

No other options evaluated,

Search in the plugins repository to see if there's already a package for your CMS framework. Install que iOS/Android mobile app to monitor your sites and get alerts.

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.

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 helps us keep our customers happy, that’s the bottom line. When it responds the way they expect, they’re happy.

It shows us where the bottlenecks are in our code. It was great to reveal where our code was insufficient or needs to be refactored. The most important thing is that it tells us where the latency in throughput and response time are.

What we have we’re happy with, but we’re still evaluating.

Very stable. Never had any issues.

Very extensible. Support and QA can look at the parts they care about and that allows for feedback and communication across the teams. It’s been great for our support team.

Never had to contact them.

We knew that we were going to move into SaaS, and these are the kinds of tools we’re going to need to get there.

Very straightforward. In this day and age, that’s what you expect from a service like that. Being able to set my alerts and the thresholds for those alerts is very intuitive.

We look at what it produces – I don’t look at cost. We look at what you can get from the product. If it’s the right tool, it doesn’t matter what it costs because you’re going to get it back many-fold from your productivity.

New Relic was it. We looked at other things we could put together ourselves, but they weren’t the full package. Something like this is all-inclusive; it’s a one-step.

We look for their reputation, how many people are using the solution. When your peers talk about it, you know that’s something you should consider. Knowing also who their customers are and how long they’ve been around is important.

The ease of use, the information you can get out of it from the very little things you do – you get so much out of it. It’s very intuitive. You don’t have to read a manual – you just use it.

It helps you to define the transaction percentages, average time, and highest throughput. Also, it tells us the transactions that take the most time on average. Those are the high level, most useful features.

It also tells us about every single request that comes in and how the system reacts to it. You get to see everything from the dashboard, all these breakdowns per layer of your architecture.

Error rate is the second most useful feature – there are alerts tied to that. You get paged when the error rate is above an expected percentage and that has worked very consistently and reliably for us.

The best thing is that the team has grown, and a lot of people are developing the code, but you tend to have regressions that are clearly visible in those transaction traces.

When there’s a deployment, it shows by graphing if a regression has happened, and it allows us to react. Catching regressions in performance is very important, and since we now see the breakdown in every single layer in the application, you know right away if there’s something you’re not expecting. We can then go and figure out if it’s an infrastructure or code issue. It gives you a high level view of all of the requests coming in. Error rates are a good indicator for potential rollbacks for a potential deployment – and usually it’s pretty instantaneous. At the end of the day as users, we get what we want.

For the purposes for which we’re using it, it just works. So far I don’t have any requests for new features.

Currently, it is not the only solution we have for monitoring so there are things that it’s missing – for example what Datadog does for us. Timeline series, custom timelines and graphs, and I’m not aware of those features in New Relic.

Every now and then there are little quirks, like the web site will stop refreshing by itself, or the graphs will show something that’s not happening. But in my experience just refreshing the graphs will fix it. But we’ve never had any downtime with New Relic.

We have scaled up as well in terms of number of hosts. There is some perceivable difference in performance when you’re looking at a graph versus number of hosts, but so far it has been fine. It’s definitely not the same looking at a single host versus many hosts.

The fact that I’ve never had to contact support by email or phone is a good thing. The online documentation has been fantastic. Everything you want is available in the documentation.

It was already in production. I did deployments in the staging environment, but not the first deployment. We will be doing the first deployment for mobile as well.

It was already in production. I did deployments in the staging environment, but not the first deployment. We will be doing the first deployment for mobile as well.

You need to understand what’s in their stack, what technologies, what libraries, and it takes someone who has experience with those technologies to help make the decision. It also comes down to best bang for your buck, and I’d definitely recommend New Relic APM.