New Relic Reviews

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.

We do have a couple of applications for one of our customers. We are involved in performance testing and engineering of those applications. We use New Relic in multiple areas. It's used to monitor infrastructure in this use case. We capture the metrics around the utilizations on the infrastructure. 

We do also identify bottlenecks of the services or the calls, which are causing high response times. 

Those are two key areas where we have been using New Relic. We have been able to identify calls that are causing a lot of performance issues in the overall application, and then that, in turn, helps us to see what can be tuned to bring the performance to a better state.

It's a build-down feature, so you have the option to drill down when a call is being received. It further drills down the method level and shows which particular method or hit is actually causing the performance issue.

It's a common feature for all APM tools. That is the key benefit of any APM tool - it helps you to understand and get to the bottom of the issue or the root cause at the earliest possible time.

The solution offers good documentation. 

It's pretty easy to set up.

Real-user monitoring would be helpful as it would help me to really understand the client-side performance of the application. Maybe for whatever reason, we have not got to explore a similar kind of feature in New Relic.

I've been working with the solution for a year.

The stability is good. There are no bugs or glitches. It doesn't crash or freeze. 

The solution is scalable. The deployment is not done by us; however, when we have to add new services or new components, it is pretty easy. The turnaround is also pretty quick.

Our team just accesses the client's New Relic tool. It's typically just used by performance testers and engineers. It also sometimes gets used by architects as well the development team. From our side, we have three people working on the solution. 

While my understanding is they do provide technical support, I've never needed to reach out to them. I can't speak to how helpful or responsive they would be. 

I'm more familiar with the likes of Dynatrace, AppDynamics, and New Relic.

We are just getting into a scenario where we might end up using AppDynamics. Otherwise, I haven't used anything before New Relic in a similar way.

From a documentation standpoint, it is pretty straightforward to set up New Relic assets. The infrastructure isn't that complex. To be honest, we haven't been involved in setting it up from an infrastructure setup standpoint. We have more consumers from which we use a setup that has been done to identify bottlenecks.

There's no specific maintenance that's been required unless they've changed endpoints which would need to be configured. It is something that's natural. When we do changes to the application and change endpoints, we'll have to configure the right endpoint. Otherwise, from a maintenance standpoint, given it's cloud and it's a storage medium, it doesn't need any major maintenance activity.

The customer tends to handle the deployment process.

I've done some research, more towards trying to understand various features. The customer, however, decides what tool to use. I don't really have the authority to compare anything and make suggestions. 

That said, when it comes to New Relic against AppDynamics against Dynatrace, or for that matter, Datadog, there are a few which have a higher price and provide richer UI. We did not really end up seeing a very major difference except in terms of monitoring.

We are likely working with the latest version of the solution.

The product has been pretty easy, and it is quite user-friendly in terms of trying to understand it. New Relic looks more at observability as a key factor. With it, you have front-end observability and back-end observability. My suggestion to others would be to go over them and also see if they can look at getting the documentation that's available to explore New Relic and then start with it that way so that it's easier for them to get started.

The other part is once they are used to New Relic, they can also look into a bootcamp that's run by New Relic, or a workshop. If they could attend it and then go into New Relic, that would be easier. They do have certifications as well which would also validate the knowledge that they gain on New Relic. 

I'd rate the solution eight out of ten.

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.

We use it for application performance monitoring. It helps us to track down the bottlenecks in the application, whether it is in the database or the front-end. It is helpful for our developers when they are tracking down issues.

We are concerned about our application's print and load times. It should be faster for the end user's experience. New Relic has helped us in terms of the optimizing our print and loading times.

It has solved many of our performance issues.

The deep insights, which will give you the metrics (not a high level), so we can build out at the database level where the bottleneck is. This has been pretty helpful.

The stability is good. We haven't had any issues with New Relic. We load test for about 10,000 users accessing the application for every five minutes. This is our use case, and New Relic was used to monitor how the application is performing.

We use SaaS, so we don't really manage New Relic in any of the boxes.

The scalability is good, because it is already running on AWS.

We have not used technical support.

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

We have plans to integrate with other products going forward.

It has saved on our developers' time when digging into performance issues.

The pricing model is a little confusing for beginners. They find it a little expensive, and if you are using it already, then that is not good.

Purchasing from the AWS Marketplace is very straightforward. When you buy it from AWS Marketplace, you can go with both options: URL SSL license and On Demand. So, when you are building, it is part of AWS, and this is convenient for end users.

We deploy everything on AWS. Purchasing the product on AWS Marketplace made it easier for us.

The pricing is okay comparatively their competitors. The only concern was whether it should be purchased on demand or bring your own license, and which way passes some savings onto the end customers.

We evaluated a couple of other vendors: AppDynamics and Datadog. They were quite a few other players as well, but we are happy with New Relic because it is simple to use and the developers can use it in their development.

Evaluate it, because it supports almost all the popular run times. Most of the popular languages support this, like Java. So, it makes it adaptable and easy to use.

I work predominantly on AWS.

The most valuable features to us are--

• Measuring performance from the applications point view against the view of the customer's browser,
• Being able to troubleshoot issues due to an app or network issue, and
• The error rate is helpful in finding issues in the server pool.

It helps us troubleshoot issues quicker, and when we're using it for performance analysis, several items can boil to the top. We can look at what's going on and what's slow and causing problems, instead of looking in general at which queries or operations are causing slowness.

I can't think of much to improve. We're very used to the way it looks and the traces. It's much better than it used to be, but perhaps the retention on some of the old problem traces would be an improvement. I think they run out after a relatively short amount of time and being able to look back and spot check some of them. If we have a problem today, it would be nice to look at back at the traces by, say, a week or a month even if there wasn't a problem then, so we can compare whether it's relatively slow or it suddenly become slow.

But I think the data layout is great as everything you need is at the top and we can able to drill down further and further to individual server,s or into the error rate and individual transactions.

The code is great. We don't have any issues, and I think that's the majority of New Relic customers. You have issues with your first customers, fix the issues, and then leave it alone until the next issue comes along.

Our track record is the same, we used it, troubleshot it, and then the developers fixed it.

I think we're finding more and more ways to use it. Because of plug-ins, we are pushing as much information in front of the app to the developers. I think too many companies end up with too many tools, but with New Relic, we want to keep in front of our developers all the time.

We've had to contact tech support several times, and each time they've been great. Their one-time survey call is good.

We've been using AppDynamics alongside New Relic. We had issues finding some problems, so we brought in AppDynamics and were able to dive further in, but after about six months, New Relic traces we're exactly as in-depth and usable. We were pretty confident with New Relic, and brought AppDynamics in to dive deeper, but their interface was Flash, which was slow and not nice.

Everything else about New Relic was nice. We could put different pieces of data in front of the developers, which is nice. They don't have as much information as we do in Ops from our other tools, but they get just the right amount of information to see where the bottlenecks are.

It was quick and simple. Always, whenever we look at a product, including ours, we've got in the back of our heads, what's the mean time to pretty graph? How quick is it to get data in front of you and that's usable? Within minutes we were able to get the information, and the first hour was great with New Relic.

When we're looking at new products, we look at whether the product works, how it works. Doing tests that are long enough is hard as no one wants to spend the time doing it, so I try to make sure that it won't take more than 14 days to set up correctly. If it's important enough, then the trials will be done.

It is one of the things that helps DevOps work in our organization and has helped stop finger pointing. It gives both sides enough info to help point us in the right direction of finding where an issue is. It gives us the insight into production to developers that operations doesn't want developers to have, and it allows them to use it all the time.

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.