New Relic Reviews

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.

The primary use case is monitoring.

It gives insights to non-technical people about what technical issues are most important, how much it impacts customers, and potentially, where we should be targeting our development teams when they have time.

It has in-depth analysis using developer code for someone whose not traditionally a developer.

They could improve the education process and how people understand that these tools are very technical. I understand everything very quickly and where it all comes in because I grew up with the product, but right now if someone was to pick it up from day one, it is a very steep learning curve.

The monitoring is only as good as the alerts that it produces. By having it set up fine grain alerting, it is a bit of a pain. They already have all these other companies that use their system, so they should easily be able do alerts based on deviations that we don't need to program on a per instance or artifact basis.

It has been stable for all our work lines.

So far, I haven't hit any scaling issues with them, and the environments that I have come from have thousands of servers being monitored.

Their technical support has been pretty good.

It was quite hard to integrate, if you weren't technically skilled. 

A lot of people who consume this product may not be technically skilled, but if you are, it is easy to use. From this perspective, it is really good, but this is an important aspect as well.

This was recently implemented at the current place that I work. Previously, without a monitoring solution, a developer could potentially spend a day working on a feature or a bug to try and resolve and issue. Now, a lot of the times, with monitoring put in place, we can understand if a customer is actually hitting this bug, and how often they are hitting it, and how much frustration they are dealing with on a day-by-day basis, then reprioritize our tasks. It gives our developers that insight, or it gives less skilled engineers or less technical leads the ability to ramp up quickly on what that particular bug is, so we can easily scale out. So, the cost of solving that problem isn't just reliant on a tech lead understands the system or built the system. Anyone can find the issue, including associates, and the amount of time they spend debugging has been reduced by a lot.

They gave us aggressive discounts when they were brought in for the first time, but they have also kept them for the year-on-year renewals, which has been absolutely fine. Thus, we haven't looked to change.

The pricing and licensing are good if you have an account manager and a partner manager who are looking to help out. 

We also evaluated AppDynamics and Dynatrace. 

We chose New Relic because they have a slightly different pricing model. We were aggressively negotiating price, which means they gave us a pretty good price. Since then, they have continued upholding that same level of customer service, discounts, and partner level. So, it has been really nice working with them.

You definitely need this product if you want scale and stability.

It fulfills what it's designed to do. Their constant iteration of features means it will always keep us well-informed about that particular requirement about the software.

We are also using New Relic with PagerDuty and Slack. They integrate pretty seamlessly. A couple of button pushes, and it was done.

We are using the SaaS version.

I use the product for monitoring many types of metrics, e.g., availability and comparing numbers in relation to products. I evaluate the response time of servers and the product to determine the health of the servers.

Sometimes, I monitor the user's time of response and use this information to improve the number of servers on the back-end. Or, I can use it to change my back log for front-end developers and improve their response times. It's very important in this case because I can improve the experience of the final user.

Time of response for back-end and front-end (user) requests.

There is a picture which goes to your browser and it monitors requests from other users. However, it's impossible to use now because the price is very high. The feature is very nice, but I tried it during the trial period, and the current price makes it impossible to use.

The infrastructure of New Relic is very stable, and it works well.

We are using AWS Cloud, and I integrated New Relic with our software, was very simple. It is easy to use the New Relic product, and it is not a hard connection between AWS Cloud and it.

The return of investment is very good.

New Relic browsers are very expensive.

I recommend using the free version of New Relic. If you like the free version and understand its importance for your company, you can move to the trial. Then, you can migrate to the paid version.

I have tried other competitors of New Relic, but the other competitors which I tried were not good. On the other hand, the competitors are cheaper than New Relic.

We chose New Relic because it has all the attributes which we are using to monitor the health of servers.

I use other type of software for database, e.g., MongoDB and GraphQL. It is easy to integrate New Relic with these third-party softwares. I don't spend more than one or two days for integration, as it's very fast. It can monitor our codes and third-party codes in these softwares.

We use it for server monitoring and strictly for our EC2 instances.

It has helped us maintain a much higher uptime than we had previously.

It fulfills the need that we had for the product.

Server uptime is its most valuable feature.

We have had issues with our agents going offline.

The stability has been fine.

Our environment has 25 servers.

The help from the technical support has always been good.

We have to install an agent on each of our instances.

New Relic was the main product that we looked at.

If you are looking for this specific type of application to keep a record of your inventory, then it does exactly what it is supposed to do.

We use their cloud version of it.

• Mostly monitoring
• Analytics
• Troubleshooting
• PagerDuty

• It visualizes metrics well and tracks our incoming requests, providing a lot of detail which is useful for troubleshooting. 
• It can track cross-application, knowing when you go from one application to another, like a request stop. 
• It's very visually appealing and useful.

It is a one stop shop and integrates with PagerDuty seamlessly. The solution is pretty self-contained.

We would like to receive more AWS-specific details from the New Relic Dashboard, like EC2 health.

I haven't seen any problems with it.

Scalability is good. We are using it at an enterprise level and have 20 companies in our corporation.

It has a good presence on the Internet, in terms of support and community. Answers are out there and easy enough to find.

The AWS integration was seamless for us. It was implementing stuff that other people have done so many times before, and the team which headed it up knew what they were doing. From my understanding, there was very minimal configuration. Maybe there was more on the New Relic side, but as far as feeding it, it was pretty easy.

We were also looking at CloudWatch and a homegrown performance-type solution.

We chose New Relic because it is all-inclusive. It has everything right there.

I just starting using it, but the product is pretty impressive.

We are hosting it through AWS.

The primary use is for data application monitor, we used to add some backlogs into the application to see where the progress or the border makes in the process. So far, it is a good program.

I think it is the possibility to see the application flow, and gives us suggestions how to manage it. We have a mode we call "influx" where we can see statistics, traffic jams or other important information.

I think the APM mode can be improved. 

In addition, its difficult to have a predictive tool to see how the application would behave in the future when it basically only shows the historical data.

The solution is very stable.

The solution is very sclable.

We looked at Dynatrace. We analyzed the differences between New Relic and Dynatrace and we realized that New Relic was easier to implement and that our Miami office had experience to do so. They had already started using it there, in the Operations office. So, we went with New Relic.

In my opinion, New Relic is a good tool, and if a colleague was asking my opinion, I would say "Go ahead and use it!" It is a good solution.