New Relic Reviews

The website is much more responsive because we are able to quickly pinpoint the worst pages – we can be really targeted with where we put our resources. In a lot of areas, one page takes one minute, the next can be ten, then some take one, some take 30 seconds. You have to decide at what point you want to focus, this allows us to find the pages that are really painful for users, and fix those and make them a lot better.

It’s absolutely the ability to get a really specific read of what is taking up time. For example, if a webpage takes two minutes to load it tells you why it’s taking so long.

They instrument up from the bottom to the top – every piece of code - they have a very perfect read of what’s being done, and how long it’s taking. And, a super nice way of presenting that.

It gives you amazing statistics, but doesn’t give you enough information about what to do with the statistics. The sales people need to be on board on this end.

There were no issues.

From a point of view of showing you what to do fine but in terms of showing you what to do with the data infuriatingly unhelpful. Very friendly and available however.

There was no solution in place previously.

We implemented in-house.

It was able to really effectively find the problem and solve it – it sped up the pages considerably.

The monthly cost os $1000 per server per month, but it could be even more. We pay about $250 for the server, and then New Relic wants over $1000 to give us statistics on those servers.

The alternative is to do UNIX profiling. Basically, you do it piecemeal, and amongst those piecemeal solutions is also browser profiling, and it’s really hard to justify. We thought about it, as if you’re a relatively small company New Relic is expensive, but it's way better than that. The price point is an issue so we turn it on and off when we need it. Not a great solution for a start-up.

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

At the moment, I think the aspect of their product is the most useful to us: server monitoring. We actually display the status of our servers continually in our dashboard (using https://Screensaver.Ninja) because that's a critical aspect of our operation. This is only true because our most used product is not gaining new features as we are re-writing it from scratch, but while we were developing new features, their performance report on which controllers are taking the longest and which parts of the application are consuming the most resources is incredibly useful.

Very simple, using server monitoring. I saw over a period of time our disk usage increase until some servers went into yellow alert (above 70%). Then we started working on this issue without a rush because we knew we had time, and instead of increasing the size of our servers and thus having extra cost, we managed to find how to reduce our storage footprint to fit within our current servers. Constantly seeing the green status of all my servers makes me sleep well at night.

I think their dev packages for server monitoring could handle configuration a bit better. We install upgrades and patches every day and their packages seems to require manual intervention due to the configuration file more often than other packages. Since we use Puppet, it's trivial for us to deal with it, but sometimes we do have to look at the configuration file to figure out whether something really changed or not. To be fair, this hasn't happened in a while, so maybe they improved it already.

I've used it for five years over multiple projects in multiple companies.

No issues encountered.

No issues encountered.

No issues encountered.

I don't think I ever needed it, no.

I don't think I ever needed it, no.

I don't think New Relic has a lot of competition. We also use Linode to monitor our servers (but not our app).

I think this is one of the aspects in which New Relic shines. They designed the product to be easy to install and integrate, it's part of their guiding philosophy and probably what made me try it in the first place.

I implemented it myself.

We are happy with the free version, so I never properly evaluated this.

New Relic is not cheap, but I have a few colleagues that need the paid accounts, and although it hurts, generally not having New Relic hurts more.

Not really.

Just go ahead and try it.

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.

We use it for application and infrastructure monitoring. It covers all of our systems, including our main eCommerce system.

As soon as it monitors all our systems and is integrated with PagerDuty, the operations team just needs to wait for alerts on their cellphones to fix things.

It's reliable, and the APM is the best of the market today.

I would like if it could have predictive analysis. Today, we only have the option to configure thresholds.

In addition, it would be nice to have centralized log management, like Datadog does. As New Relic already has all of the application information and traces, it could compare them with application logs and do better analysis.

Thus, it could be cheaper, have predictive analysis and log management.

It supports our Black Friday week, when our requests increase about 500 percent. It's very stable.

We never had any issue with scalability. It is perfect. It currently monitors about 150 EC2 instances and several AWS services.

For the integration and configuration of New Relic in our AWS environment, we need to install an agent on all the EC2 instances to get the APM working. Also, it has an IAM user on the AWS Management Console, allowing for AWS metrics and for it to monitor other services.

We renewed our contract directly with New Relic since our systems were hosted on on-premise data centers.

The new licensing model is great, as we pay for what we use (in computational units). However, the pricing is expensive compared to other tools.

It easily integrates with PagerDuty, our on-call management and notification system.

We use it for monitoring the CPU, memory, services, email rates, etc.

We monitor the Internet daily, or every few days. Then, every time there is a crisis, high traffic, or if we see a problem with a server, we go to New Relic and monitor it to determine the cause.

• The APM
• Monitoring
• The capabilities which allow you to easily see whatever you are looking for.

• I would like to be able to invest less time in IT and ad hocs. We should be concentrating on other issues.
• I would like more deep dive monitoring into services and being able to install it on some apps.

It is stable. We don't have any issues.

The scalability is good. We have a few thousand servers, and it is up and down based on the traffic and need. We have New Relic on all of our servers.

We don't use the technical support.

The integration and configuration of this product in our AWS environment was quite easy.

We have it integrated mostly with our physical servers.

The product saves time and money.

Purchasing through the AWS Marketplace was easy. The product is easy to deploy and manage, which is why our company purchased through the AWS Marketplace.

The pricing could be better. We did not purchase the full version. Maybe if we applied all the other features of the full version of New Relic, we could get all the features that we feel are missing.

In addition to New Relic, we evaluated Monitis and Dynatrace. We chose New Relic because it was cheaper for us as a startup, and it is also faster and more user-friendly.

Go with it. It is a good product. It gives us the visibility that we need in monitoring.

The AWS version is easier to deploy than the on-premise version.

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.

I've found the most valuable feature to be--

• Being able to drill down to see data, and
• Being able to capture all the timing information and different functions.

It comes in as part of the regular process for every application roll-out. We have a standard visibility process for any application that rolls out. It gives us the ability to train our people and provide a more responsive application. We used to have many tools with many different functions, and now APM allows us to consolidate a lot of it.

The mapping between applications to servers is not very intuitive.

Another thing we come across is that our technology just doesn’t have reporting to New Relic, but that can be addressed with a plugin/SDK. However, we can’t really make the case to put in the investment to have that happen yet.

Another thing is that we’re micro-service based, and the New Relic interface only gives us views into the top 100 services out of 50,000. Typically when we monitor our system, we use a heat map, and New Relic only provides us the second-level view of that. Ideally, it would also provide us the first-level view. Eventually, we’d like New Relic to step up to do that.

Finally, it should ideally do two things -

1. Isolate the problem right away without the user having to do a lot of analysis. Right now, New Relic provides a lot of data points that require me to go in to understand.
2. It has its own dashboard, and I’d like to be able to bring that/integrate it into our own system (use an API to pull out data).

Sometimes when we pull data from New Relic, we time-out or drop data, and we can see when that happens, but we're not sure if it’s us or them.

Also, the alerting system has trouble with large alerts that come up slowly, requiring the operator to know the system well (yellow, red, orange) and to know what the alerts mean.

It hasn’t scaled quite right now. We use another tool for out-of-gate view. Currently, we manage about 60,000 servers in total and we don’t have a good roll-up view of the entire system. The application on the server side is OK. We use other tools to monitor the environment.

So far, the interactions have been good, and they keep us in the loop as to what’s been done. In terms of the solution, it’s just OK.

I wasn't involved in the setup.

Engage the development community within the company early, and request an integration tool to make implementation easy.