New Relic Reviews

We use New Relic for monitoring and alerts. 

We detect issues using dashboards that we built on New Relic. For example, if our drivers are taking too long to get rides, we usually detect the problem using New Relic dashboards.

The user experience with dashboards and the machine learning features are its most valuable features. The dashboards are useful for BI and fraud detection, if implemented the right way.

The APIs could be better. I would also like more APIs and features to integrate with streaming solutions, like Kinesis or Kafka.

The stability is good. Because it is calibrated for SaaS, it is transparent for us.

The scalability is good because it is SaaS.

The technical support is good.

The integration and configuration was good for our containers and LAN disks.

The detection piece of it brings us a big return on investment.

Splunk and Dynatrace are the alternatives in the market. New Relic is the solution that our company purchased.

I have used another product at my company called Dynatrace. Though, I think New Relic is better because its dashboard is more intuitive for users. I use Dynatrace at my company because we have a partnership with them.

New Relic is the best choice because the product has good dashboards, scalability, and environments.

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.

• Infrastructure management
• Application management

We have an operations center which uses it quite extensively to manage production. They can go back and look at trending and history of the applications. They have alerts set up which trigger off of it. 

I go in afterwards and help do the root cause analysis and troubleshooting.

It is a software solution as a service, so I don't have to manage it on-premise.

I would like to have storage monitoring. E.g., being able to monitor SANS, specifically protocols, like NFS and CIFS metrics. I have not seen the ability for it to do this and having some way to do this would be awesome.

The stability is fine.

It seems scalable enough. We are always hitting the limit of the number of agents that we have, then we buy more and it works.

I have not used technical support.

New Relic SaaS seems to do some things much better than SolarWinds, which we have on-premise.

Give it a try, install it, and use it. I don't have to manage the server and worry about the database, storage, and VMs being up and running, etc. It is always there.

We use it for application performance monitoring.

Its most valuable feature is application performance monitoring.

It gives me a complete x-ray of the application to understand where the bottlenecks are, then improve and fix issues.

We send through all our real-time transactions through it, and it is very stable. 

The scalability is very good. We have a large real-time environment for processing payments.

Their technical support is pretty good and responsive. We have a real good relationship with them.

The integration and configuration of New Relic was straightforward and easy.

It works well with the AWS platform that we are using. The integration with AWS was straightforward and easy.

We have seen ROI.

Comparatively, the pricing is expensive.

I zeroed in on New Relic. I was looking for a cloud native product at the time that I was looking for a solution, and two years ago, it was one of the leading products. It was quick to market, and we wanted to implement something quickly. It provided all the features which were required, and we didn't have to do our own installs within our data center.

Give it a shot. See if it meets your use case.

I have used the on-premise and AWS versions. The versions are very similar.

We are monitoring our server database to see if there are any anomalies or problems with the servers and databases.

Since we migrated from on-premise solution to the cloud (AWS), we have migrated somethings into Lambda API Gateway and DynamoDB. We have also done the New Relic integration with Serverless AWS, which has helped us with monitoring, and keeping our monitoring from our on-premise part with the cloud part.

• The alerting system
• The integration of API Gateway with Lamda and Serverless AWS.

We are sharing different AWS accounts, and if a Lambda has with the same name but a different AWS account, it is a little hard to understand whether AWS or Lamda belongs to that account. Also, we have multiple accounts on the drop down to filter by Lambda, but we see two Lambda with the same name, then we don't know which one to choose. So, it needs to improve its filtering.

We would like a more sophisticated filtering for the Serverless AWS pieces.

We have not had an issue with stability, so we are happy with it.

For all the features that they have and for the amount of data that we feed them, it handles the stress well. 

We run 20 web servers, 500 Lambdas, and 50 DynamoDB tables. We also have an enterprise SQL Server with different instances along with MySQL databases and mobile applications.

I would rate the technical support an eight out of ten.

We were previously using Datadog. At the time of the switch, both companies were closely related product-wise, and some of our company was already using New Relic. We also chose it because the monitoring tool and alerting system fit our needs.

The integration and configuration of this product in our AWS environment needs improvement on the filtering part. I would like it to go more granular on accounts. There is also some room for improvement on the integration with Serverless AWS.

Because of budget, we are not using the mobile app part of this tool.

New Relic has been in the business for a while. It offers a wide selection to attach a monitoring mobile app, server, and cloud. If you want to go with just one product, it fits all your needs.

We were using the on-premise version before going to cloud. So, we were using it on the physical data center, then we migrate to cloud and started using it with AWS. We haven't seen any different between the two products. We have been able to monitor in both.

It monitors all of our services that are running. It also monitors our infrastructure. Therefore, we use it for monitoring, identifying when services go down, or when they are outside of what we would consider normal operations.

We have been able to proactively identify failures before they happen. As an example of something in the last week, we had an instance where a volume was filling up on one of our VMs, so we set up a basic alert that if it got to a certain point, it would send me an email. This way, my support team or I could take some action on it and execute a run look. This has prevented failures from occurring in our production environment.

The alerts that it provides is one of the most common things that we use. As an example, when a service isn't performing how we anticipated it, either I receive an email or my support team receives an email, then we can take action on it.

It is complicated, especially in how you interpret the data that it provides. For someone who works in it every day, I can figure out what I want. For the general, every day developer who uses it once a month, there is large learning curve to figure out exactly the information that they want from it. If it had a bit more canned, out-of-the-box features, especially some of the reporting features, that would be more useful.

Sometimes, it is difficult to work through and figure out. Some things are difficult to work through which is why I haven't done them yet, because it will take me six hours to figure out how to set them up, e.g., the dashboard. How I want it to look and how the developers might want to interpret that data, but I don't have six hours to go figure this out, and it takes a long time to do this stuff.

They have this alerting capability where I can set up an alert policy, then within that alert policy, I can set up as many alerts as I want. I can set up one or I can set up a 1000. I would like a feature where I can turn off alerting at a policy level. Thus, when a policy is inactive, I can shut down all of my alerts within the policy. Right now, I have to go through them manually and deactivate each one that I don't want to use.

I have never seen it be down or unavailable. So, the stability is good.

I've never had an issue with scalability. They have been able to scale and handle everything that we've sent them.

I have used their online support. I don't think I've ever had a phone call from anyone, but I've definitely exchanged some emails with their online support forums, which has worked out well.

We used to use AppDynamics, which is one of their big competitors. I don't exactly know why the switch. We were told to go to New Relic. I think a lot of it had to do with the cost. Possibly, they found New Relic to be a cheaper alternative to AppDynamics.

The configuration and installation were good. New Relic has some very good documentation. Everything in their API is some of the best that I have seen. It wasn't without issues because it's a piece of technology, and we had to figure out how to use it, but everything has worked well.

The issues were working through the documentation and figuring out exactly how to implement on some of the technology.

I did all the configuration, so there is a portion where we install an agent on our infrastructure and on our web services that run. I did all of that configuration. They gave me the account ID and the license to go with it, and I configured that in some of their config files, then I knew exactly where to send the logs to, etc.

Corporate handled the licensing and the purchasing of it, then they gave me a license key. However they configured it is how we use it.

If you are looking to evaluate New Relic, compared it to other products, it is very powerful in terms of what it can do. However, it is a complicated to interpret some of the data which is provided with it. There is a trade off if you want to implement this product versus implementing something that is simpler and out-of-the-box, but not obtaining as much depth in what you can learn.

It has some advanced plugins for EngineX, which is a web balancer that we use. So, we do integrate with these, which is a little bit outside of their normal realm. There is also an Apache one that we use. The integration is good. Once you figure out how to install it and read through the documentation, it works as anticipated.

Monitoring the health of our infrastructure.

It has given us better insight into the performance of the system, allowing us to prepare things, if necessary. It has been helpful to patch things before they are a problem.

We are able to drill down and see what is going on in the system.

The price needs improvement.

It is on our production workload, so we put a fair amount of stress on it. However, it is sort of self-contained. We do not really have to do much with it.

Size of the environment is 30 VMs which are instrumented with New Relic. 

I haven't had any scaling problems with it.

We receive technical support as part of our subscription.

The integration and configuration of the product into our AWS environment was extremely easy.

The pricing and licensing are too high.

We evaluated Dynatrace and a few others. These competitors did not provide as much in-depth information, but they were considered because they were far more cost-effective.

We went with New Relic because it was best of breed.

I would recommend to go with New Relic.

It integrated well with Docker. They have Lambda support now, so it has been fairly seamless.

I have only used the AWS version.