New Relic Reviews

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.

• Ease of installation
• Ease of use
• It provides a common platform for Dev and Ops to be able to pinpoint and communicate problems
• The solution allows us to quickly pinpoint problems
• There’s good integration between all the products in the suite – browser and some of the plugins

Being able to quickly figure out the root causes of issues. It also makes it very easy to share that information with developers and other people within engineering – we can drill down in parallel.

There are a number of plugins that New Relic makes. It would be nice to be able to instantly integrate that with APM. Right now, they’re in their own little area, so it’s not as easy to quickly dive into a problem, for example in PHP. It’s a little hard to get data on the back end.

The stability and uptime have been great. They do a great job in notifying of maintenance windows. We have had some graph inconsistencies which might represent a quirk in the solution, but we haven’t seen that in a while.

It’s a very scalable solution. We have it on maybe a couple of hundred hosts today. We use an automation tool, Puppet, so we’re able to quickly install the New Relic agent across classes of servers easily. On their end as well, they’re collecting more data, so it seems like they’re scaling out very well too. There are no performance issues with scale.

Actually we haven’t had to use it yet.

Prior to New Relic, we did not have an APM solution. We had a lot of home-built tools but nothing like this with dashboards. Mainly the maintenance of the home-built tools was difficult. It was tribal knowledge with no documentation, so we were constrained by the engineers and their specific knowledge of the tools.

Very straightforward – it was great that everything was packaged so we didn’t have to do too much customization. We changed maybe two lines in the config. The documentation was very straightforward. Once we installed it a couple of times manually, we were able to script it, which was very easy as well.

There weren’t really any contenders – it was go with our home grown solution or this. Initially the product effectiveness was the top of the list. Cost is a consideration. Really cost was secondary to whether the tool actually worked and delivered value. Support wasn’t high on the list but it was a consideration. Mainly the ease of use and product effectiveness are the two main considerations.

It’s a solid product. They continue to innovate year after year. They’re getting closer to a 10, but because of the speed of innovation I think there are a few disconnects within the suite/product line. That’s the main thing that keep sit from being a perfect solution, but they’re a very solid product and a very solid company.

It needs to be a cross-organizational evaluation. Can’t be Dev or Ops-only. The solution definitely needs to be low friction to get it into the environment. Being open to the customers in terms of what their product roadmap is and what the customer can expect, and then getting feedback from the customer to help them along as well is important.

Reviews are important. A lot of times other companies are trying to solve similar problems. People are going to be trying competitive solutions, so getting feedback is important to the vetting process.

I used New Relic Insights to create dashboards, to receive some metrics regarding performance, and alerts regarding any kind of issues with the performance. Additionally, we used it for SQL and Oracle to receive metrics related to performance, such as CPU and memory.

Depending on the type of dashboards we wait for some time and then we build alerts in New Relic Insights for the metrics to prevent issues.

There are times when you restart the engines and the servers have a unique ID for the host and you need to remove the server. It is difficult because some are on-premise and others are production hosts. Having downtime is not very good when updating. However, it is not a constant issue.

I have used New Relic Insights within the last 12 months.

We have some performance issues with the servers. Sometimes the server is consuming a lot of CPU or memory, and New Relic Insights fails. They don't receive any information from the server or to the dashboard.

The solution is scalable, and it is easy because all the documentation is available.

There were approximately 11 people using this solution in my organization.

I have not contacted support. There is a lot of documentation available and you can search it globally. You can find a lot of the content on various topics regarding your issue.

The installation was simple. We don't need to use a user interface to install it. We can use two or three commands in the PowerShell or three or two commands in the batch. One device can take 10 minutes, and 100 devices can take one hour depending on many factors.

The script takes the information for the device from the system information but if you are using an interface, such as a wizard, you need to modify files and put all the information regarding the devices and environment, such as the license and hostname. All the information should be put in there. It is very easy.

To set up the metrics, you need to build the dashboard and after that, when you add a new device, it's automatically added.

To receive all the metrics for each system regarding its application, the user in the interface for all the dashboards can type the hostname and can see all the tools in that host, it is a very powerful view. You can modify some of the parameters to fit your needs.

One person can do the implementation. However, depending on how many devices you have it could require a little more work. There are third-party scripts that are available to install New Relic Insights across all devices.

In AWS or Azure, we have a root command that can select multiple devices making the process easier.

There was zero maintenance needed for New Relic Insights, it automatically updates.

My advice to those wanting to implement this solution is for them to create a test environment and try different operating systems, such as Windows and Linux. Test different applications in both environments to see what fits the use case best.

I rate New Relic Insights an eight out of ten.

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.

We've been able to automate a lot of our interactions with it. Also, it has the ability to monitor random URLs not tied to the one pinger per application (though it costs extra).

I think that there have been some questionable product enhancements. Over a year ago, New Relic rolled out a new navigation that really disrupted our workflow. It added many more clicks and was surprisingly frustrating. Luckily, that was mostly reverted, but more recently, around six months ago, they redesigned the error reporting page. This is another example of a tool that worked fine, but which is now very hard to use.

About six months to a year ago, we invested a lot of time automating a lot of our interactions with New Relic. However, their API couldn't do a lot of things, and even getting a list of errors was impossible without scrubbing every application/server manually and checking health conditions yourself. This seems very basic. While they have made a new API version, we've had difficulty with that as well. 

Additionally, I'm told that they will deprecate completely the old API, which now means I need to reimplement everything that was working in this new version.

It's been a stable product. We haven't had any issues with instability.

It's scaled for our needs. We haven't had any issues with scalability.

Cost is significant with a lot of extras. For instance, another big negative point is the inability to monitor random URLs not tied to the one pinger per application. They've added it which is great, but now it costs extra for using it in any real capacity.

The most valuable feature is the transparency into how applications are running. That’s huge because we previously didn’t have it and we had no idea what was going on. Now, we can see exactly what’s going on and are able to understand what code paths are running. That stuff is hugely beneficial to us.

The biggest thing is being able to give our customers a world-class experience. As we’re in media, this means things like hockey results, election results, favorite TV shows, etc. We’re able to cover all our bases to make sure our customers get what they love.

When I look at APM now, it’s very web-centric, but we have certain infrastructure components that are very service-based which take data from one area to another. With APM, it’s a little difficult to fit into that. So, what I’d like to see is the ability for the dashboard to be customized where it can display collection jobs and how they break out one by one.

It also needs some web UI tweaks. It’ll be interesting to see where it evolves with the “analytics everywhere” theme and incorporation of all the other items.

There are no stability problems. There have been slow points where data loads slowly, but it can be solved just by clicking refresh. No problems with agents crashing or not reporting data. So no reason for me to worry about its stability. I never have to worry about not collecting data.

It’s scaled to all our needs. We have apps for on-site and in-cloud, and it’s worked well for both.

We haven’t had to reach out yet, and hopefully things keep going smoothly.

It’s easy to use, has a low barrier of entry, you can craft custom instrumentations, and craft your own metrics to get your own details out of it.

• On-demand profiling – This gives us the ability to execute a thread profiler on demand and get a very in depth view of call costs
• ApDex/Error monitoring – As a dev-ops solution, this is a great tool because we’re able to help predict issues before the end-user starts notifying us. We can set thresholds that are based on our metrics

We are now able to quickly identify how our product behaves in production. Before New Relic APM, we would push a build, and try to dig through a plethora of information (event logs, error messages, customer feedback, etc) to find problem spots. Instead, we now publish and can see all the key stats (apdex, response time, error rate, etc.) and quickly drill into what’s causing an issue.

More configurability through the dashboard, for example, being able to ignore transactions without the need to update the config or code.

I've been using it for two years and alongside Insights for one year.

No issues encountered.

No issues encountered.

No issues encountered.

Really high. While we’ve never had any major issue, the ticket I’ve opened have received responses within a couple hours with quality answers.

We didn’t use any other solutions prior to this.

It was straightforward. On each of our servers, we installed the agent, added our key to a config, and then within minute we were seeing metrics on our site.

In-house. Always start with your development or QA environment. While we had no issues, it’s best to take a dry run, and get a feel for how the app affects performance to see if the data is what you’re looking for.

I have no hard numbers detailing how much we get back for what we pay. However, as a dev-ops tool, it has been priceless. We are now able to pinpoint issues much quicker and can significantly reduce our downtime.

We did evaluate one additional tool but the install and integration was significantly more cumbersome. The core reason we chose New Relic was the ease of us and the quality of the metrics it gave us. Within hours of demoing the product, we were already learning more about our application than we expected.