New Relic Reviews

We use it to monitor servers. It's just a log in New Relic. I set the start and end times, and then I just pull down the server metrics.

It's not the New Relic APM, it's just the New Relic. There is the one that is New Relic, and then is New Relic APM. It's a bit confusing.

Normally when I use it, it takes me 20 minutes to pull all the data, and I use it maybe once or twice in a month.

We would run a low test, and then after the test, we would log into New Relic and then look at things, including: what are the top five slowest interactions on the servers? What are the slowest database calls? Then, we just pull the graphs from New Relic, and then we give it to the customer and show them here are the calls are being made the most, and that correlates to a slow response time. Then they'll be able to focus on it and try to maybe fix it.

There's another user on our team that sets up the list of servers that need to be monitored. You just click on those servers and then from there you can pull all the data, so that's really helpful. You don't have to go through a list of 500 servers. You click on one server, and it brings up ten servers that are in that environment. You don't have to choose those same ten every time. Instead, you just click on that one link. You just have to click on the name of the group you want to look at, and it'll pull metrics for those same ten or 15 servers each time. That's very helpful.

The customization of the start and end time is kind of cool.

It's stable. 

The solution can scale. 

One of the metrics is total time. I would like to see the true response time of a particular call. It might say top five slowest calls. However, I don't know how they're calculating it. Maybe if they could have documentation for how those things are calculated, that would be a lot easier. If they say the top five slowest methods and the slowest one is three seconds, yet we know that there's a process that's taking ten seconds, it can be kind of confusing. If they could add in their help files, how these columns are calculated, that would make it more transparent. They need to clarify: What does it mean, total time? And how do they calculate the total time? How do they calculate average time? How do they calculate the top five slowest? What is it actually pulling?

I would like to see them introduce integration with LoadRunner; that's a bit easier.

I've used the solution for six to eight months. 

It's a very stable product. Overall it's a good product.

We have eight or ten people using the solution at this time. It is used occasionally, once or twice a month, just to pull out the data for the server monitoring and for the reports.

The solution can scale well. 

I've never called New Relic support. I never really needed to.

I'm also aware of Dynatrace. In Dynatrace, they have an integration with LoadRunner. You just have to add one or two lines of code in LoadRunner, and it will integrate with that, which is really good. 

New Relic doesn't have the option of integration with LoadRunner.

I did not install New Relic. By the time I was put on the project, it had already been installed.

They just let me know the ID and password, and I just logged in, and that was it.

As far as pricing goes, I heard that they charge per user ID. If we have ten people with ten IDs right now, if we want to add another five more, they'll charge us for each ID, so that is something that is maybe a concern. I actually heard this from one of their competitors. I've heard Dynatrace say that New Relic's pricing model was very expensive, so that would be a concern.

I'm not sure of the exact price of each user ID.

My organization is a customer of New Relic. 

I'd rate the solution eight out of ten. If it had better, easier integrations, I'd rate it higher. 

• 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 case of the solution is to monitor, log, and investigate incidents.

The most valuable features are the dashboards and tracing.

It is complex to use and it can be improved by simplifying it by making it more user-friendly. I would like to see the option to group alert conditions added.

I have been using the solution for two years.

The solution is stable.

The solution is scalable.

The support team helped to resolve any issues I had.

The setup is moderate. 

I give the solution an eight out of ten.

I suggest anyone interested in using the solution should learn the query language first. It is a serious tool and requires a lot of time invested in order to understand how it works.

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.

I'm working with a banking client. Apart from a uniform monitoring platform experience, they are looking for a solution that is scalable and also ready for cloud services monitoring and container-based workloads.

NewRelic provides a one-stop shop monitoring solution for organizations that are looking for 360 degree monitoring solution. Application, Infrastructure, Network, Database, Enduser monitoring, Mobile everything under one roof. Apart from that, as per Gartner Magic quadrant, NewRelic is among the top leaders.

The one thing that I like the most is the tight integration between different layers like APM, Infrastructure, Logging etc.. I don't have to go to a different UI to view different metrics. Secondly, health maps and service maps helps to evaluate the overall health of all the applications and any dependencies.

With Insights, I can create some powerful impactful dashboard that gives organization the business value they expect from the data collected from different data sources 

The solution needs some sort of improvement on the synthetic monitoring site.

The product has good documentation for Linux, however, their documentation for Windows is lacking substantially. It's something they need to develop and mature over time.

It would be great if it had out of the box integration with AWS, GCP, and other clouds. For example, if I'm using BigQuery in GCP, I want the data that I am executing in BigQuery to be reflected in New Relic. 

I'm working for a client where I'm proposing NewRelic solution to them. They have been looking for an intelligent monitoring solution that can provide a uniform monitoring platform experience to monitor application performance, infrastructure, end-user experience where NewRelic is the best fit.

The solution is quite stable. We don't have any issues there. There aren't bugs or glitches. It doesn't crash. It's reliable.

The solution is both scalable and fast. We have no complaints about it at all in that regard.

It's multitenant on the cloud which helps make it very easy to expand as needed.

I've found technical support to be pretty good. They accept the new feature ideas quite readily and their SLA is also very good.

I kind of have worked on different tools, but then no one has provided a unified solution. I've worked on ELK, Sumologic for centralize logging specifically. I've also worked with Splunk.

AppDynamics also provides these features, but I have not explored AppDynamics so much.

The solution is straightforward to set up. It's not a complex implementation. They are more compatible on Linux side of things, however. 

They need to provide more documentation for Windows. For example, I was trying the New Relic logs feature yesterday, and they have very good documentation for Linux, and can explain quite well how to do log forwarding on Linux. Then, for Windows, they do not have that specific documentation. I was stuck and I haven't worked on it today due to this lack of documentation. 

The pricing is reasonable. APM is a bit on the higher side, however, their service offering is quite good.

The solution is more mature than a lot of options on the market. If a company is looking for something that offers a unified scalable solution where they can monitor everything in one place, then NewRelic is definitely the option they should look out for.

I'd rate the solution eight out of ten.

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.

The ability to look at applications directly and be able to dig down to server error details.

In APM, we can see error details for things that we never logged before – things that were occurring in our apps that we never knew about. The “a-ha” moment is the first install, and we immediately started to fix things.

We work in a small team in a startup with a lot of customers. From a customer to a software engineer was a one-step process, so tickets could come directly to me. I could go directly into New Relic to investigate what the customer was reporting and verify what they were saying. We can address those issues much faster with New Relic, which is brilliant. That changed things drastically for us.

Previously, we didn’t know what was broken. Now, New Relic tells us so we can prioritize what our teams work on. More importantly, it gives us the ammunition to go back to our product development team to convince them of the priority of fixing certain issues, which helps us prioritize our team’s activities.

Based on what New Relic is adding to the product, they’re adding more real-time graphs and ability to see interactions in real-time. For our business those features could really impact our business.

Never had any problems.

We had agents on servers delivering service from 11 different data centers worldwide. We never experienced a problem. Once the agents were installed, we forgot about them. We've never needed any special maintenance or anything. It scaled really well.

Never had occasion to use it.

Not involved in the initial implementation, but I was involved in agent deploys and bootstrapping data centers. It was super easy.

It’s hard to compare it to other vendors because nobody offers the quality of monitoring tools that we get with New Relic. Otherwise, it’s choosing among disparate products.

When looking, we look at the reliability of the vendor and the level of adoption of the solution we’re interested in.

I feel like it’s the best-in-class, and its differentiator is aggregation and the speed at which you can query large amounts of data. I don’t think any other product gets close. The easy of adoption, also. Start opening up servers and adding agents, and you’re done. You immediately have data.

Just get started. Pick something and try it. Regarding New Relic, you’re going to learn a lot about yourself even if you can’t afford it and you’re going to pick another solution. Too many of us do analysis paralysis on these sorts of things when you should just get started. That’s why trials are so valuable in the vendor space – if you have a way to try it out and you can immediately see the value, you can prove it to someone else.

I use the solution in my company to monitor the applications' performance and do some stress tests on the application. In our company, we use the tool to monitor the core application inside the data center. In some cases, New Relic is used to monitor users' access to the applications.

The most valuable feature of the solution is its ability to execute queries and analyze the data. For all the data, the tool has a specific function with which you can spot and mix the data or correlate the data wherever you want. It is easy to simulate and execute queries, and the availability of the data is very nice. The tool gives you a basic way to manage the data.

The product's initial setup phase is not straightforward to manage if you have no experience with installations, making it an area that can be improved.

I have been using New Relic for a year. My company is in partnership with New Relic.

I think the support of the tool is a good option. I think the support of the tool. I rate the tool's support an eight and a half out of ten.

Positive

I have experience with Catchpoint. With New Relic, you monitor the application from within. You monitor all the communication calls between the application and all the systems that the application needs to use, such as databases or servers. With Catchpoint, you can monitor user experience and how it interacts with the application, so we are monitoring from the outside, which is from the user to the application.

For the product's initial setup phase, you need to have a background of doing installations. It is not a straightforward process, as you need to have more skills to do the tool's setup. The tool's setup phase is a little bit more complex but with the correct knowledge, it can still be very easy. You have to have some prior knowledge in installation to start with the tool's setup phase.

For the product's deployment phase, you need around 20 people because you need the people who do the installation and connections, along with the owner of the platform or the database, for which there is a need to create some access using New Relic. You have to do some configurations or partitions to install the agent. You need to have an expert on New Relic, as well as the user or the administrator of the infrastructure where the tool will be installed, so customizations can be done if needed.

The time required to deploy the solution depends on the amount of installations required and the architecture where the solution will be used. One agent can be deployed in maybe 30 minutes. Depending on whether you have everything in place and people know what they are doing, it may take 30 minutes to deploy the tool.

The tool can not be related to productivity. The product helps the development team that develops and makes changes in the applications. The tool helps a lot and provides a lot of information to the development teams so they do not have to do simulations. With all the information that New Relic provides, the development teams can just make decisions about the changes within the applications during the development. The tool offers information about the business process. With the tool, you can have all the information related to all the purchases from the marketplace and understand why the purchases were okay or why not, why the people that are logging in are not making any purchases, along with all the information related to the business process that are very helpful for the business.

The product is neither cheap nor expensive, and I believe that it is a competitively-priced tool.

I don't know how the alerting mechanism in New Relic has improved our company's response time. I am more into the demo part, so I am not a user of the tool.

I rate the tool a nine out of ten.