New Relic Reviews

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.

We used New Relic APM for monitoring our data.

The synthetic alert is the most valuable feature in New Relic APM. I also like the time travel feature and find traceability useful in the solution.

New Relic APM also has good response times.

In the pro licensing model of the solution, my company used the data analysis feature more and took care of more complex workloads that my team could easily track. Data analysis is another feature of New Relic APM which I found helpful.

The UX/UI design of New Relic APM could be improved. The solution currently has some slow pages in terms of loading and viewing the pages, for example, the reports. The reports and other pages take a long time to load, so if that area could be improved, especially when looking for data, it would enhance New Relic APM.

I started using New Relic APM around March of this year, 2022, until June, so my experience with it is almost a year.

New Relic APM is a very stable solution.

You can scale New Relic APM, but I expected it to be more scalable.

If you contact New Relic APM technical support during office hours, then the team is responsive, but sometimes, it's delayed, especially when you contact support during offline hours. New Relic APM support is limited, so I'd rate this area as three out of five.

I used Dynatrace before using New Relic APM, but that was in my past organization. I switched to New Relic APM because I moved to another organization. I also use Datadog, but mostly, it's New Relic APM that I'm using.

In my current organization, I did some POCs, but not effectively, so I've only used New Relic APM and no other solutions, at least in the organization I belong to now.

I used to handle the New Relic APM setup process more for algorithms, mainly writing algorithms to define the rules for better tracking. I focused on the time travel, traceability, and other valuable features of the solution, primarily monitoring and not the initial setup for New Relic APM because the IT team took care of that process.

On the part I handled, the process was seamless, and there was nothing complex about it, but it could be because I asked for help from the IT team. The process was average. It wasn't very smooth and wasn't very complex either, so neutral.

The initial setup for New Relic APM, which was done by the IT team, took more than a day.

The IT department took care of deploying New Relic APM. The implementation was in-house, and New Relic gave my company a server similar to a one-of-a-kind setup tool that you can install within half a day.

The IT department handles New Relic APM licensing, but the solution is priced reasonably. I'm actively using the mobile monitoring function of New Relic APM, and it's one of the best products for me because it's economical, so anyone can easily pick it over other solutions and use it. It has basic features.

My company went for the New Relic APM sixty-day free trial, so there was a limitation to the number of people that could use the product. It only allowed twenty-one users maximum.

New Relic presented New Relic APM pricing and packages very well. For example, there's silver and platinum, and each package was easy and more economical than other tools. In this context, I'd recommend New Relic APM because of its reasonable price and package.

My company initially used the standard New Relic APM package, and by the end of the month, it moved to the pro model, which had low, flexible pricing.

I was into this Dynatrace, a monitoring tool in my previous organization, but not now.

I'm now using New Relic APM at an organizational level rather than a personal level.

New Relic APM has an on-premise deployment; though my company planned to deploy it on the cloud, it wasn't successful, so another solution for cloud deployment is now being tested from AWS.

As New Relic APM is one of the best solutions in the market, my rating for it is eight out of ten. I didn't give it a ten because of the support, reporting, and UI/UX that need improvement.

I'd recommend the solution even to startups or novices planning to do some monitoring, and in the future, New Relic APM could compete with similar tools used by the experts.

At the moment, nine people, mostly software engineers, use New Relic APM within my organization. The software engineers get the alerts from the product.

New Relic APM requires maintenance by a minimum of three resources, and it would depend on the requirements, tools, and features. For example, my company currently uses three New Relic APM platforms, web, mobile, and desktop.

My company is just a user, not a partner of New Relic APM.

The primary use case is for synthetic monitoring of all the APIs. It helps to detect if any APIs are failing before a customer detects an issue.

The solution was deployed on cloud.

There were 15 people using this solution. They worked on the configurations and setting alerts for new environments and customers. The solution was used on a daily basis.

At my previous organization, they were planning to replace New Relic with Google Apigee. That was only to be done in conjunction with the cloud migration from the in-house hosted apps.

One valuable feature is that the synthetic alert stays open until the issue is resolved. You can actually monitor whether your system is back up.

I would like the ability to set up certain dummy accounts and do the actual things that the customer is doing, without impacting the production environment. Only the read APIs are called from New Relic, not the write APIs. If we had a test account to do the write part of it, it would give us better monitoring. For example, if we are selecting the data for an existing account, we can do that part of the monitoring with New Relic.

When we see failures and slowness, I would like there to be an option to do a deep dive into a collection of metrics to show the bottlenecks. It would be helpful if it didn't just state the problem, but indicate the areas to look at for a deeper resolution of the problem.

I have used this solution for three years.

It's mostly stable.

It was scalable.

Technical support is responsive, but you need to create a support ticket with the right priority, which is based on certain questions that they ask. If it's created with the right priority, they will respond. If your ticket is created with a lower priority, they will respond on the next business day.

I would rate technical support as five out of five.

I have also used AppDynamics to show us the time that the APIs were at a certain level, like the database level or application level. I think New Relic has started implementing the ability to trace transactions to that level, but I don't know if that feature was well developed because I didn't use it a lot in New Relic. 

In Apigee, for example, they monitor a certain percentage of the transactions to show where the bottlenecks are.

The supportability in AppDynamics is good.

Setup was pretty smooth. I wasn't involved in initial setup, but for newer customers and installations, setup wasn't very cumbersome.

Initial setup was done by New Relic, but we did later installations ourselves.

The pricing is fine.

I would rate this solution as nine out of ten. 

My advice is to have a project plan in terms of what you want to monitor. You can monitor various micro-services, but you probably want to restrict the monitoring to what exactly impacts the customers. Have a plan for implementation, the components you want to monitor first, the components you want to monitor later, and an automation strategy for synthetic monitoring. For example, for the right APIs, think about whether you can have monitoring using synthetic accounts.

We use New Relic APM to gather performance monitoring metrics such as thread count, CPU, response time, JVMs, and DB connectivity. New Relic APM is an observability tool.

To me, the most valuable feature of New Relic APM is the traceability, mainly based on the time travel method, so you get the overall response time, which is pretty helpful for developers and ADR techs looking into issues on a deeper level.

New Relic APM is a very good, tailor-made solution.

Documentation could be improved in New Relic APM, so users would have more clarity on configuring the dashboard. If New Relic gave better guidelines, users would find it easier to understand the metrics and features of New Relic APM.

Another area for improvement is integration with Kubernetes. Currently, the process isn't user-friendly. It's challenging and lacks documentation for users to understand how to integrate New Relic APM with Kubernetes quickly. With multiple levels of Kubernetes dockers and other DBs on different clouds, it's tricky to gather all into New Relic APM on a single dashboard.

What I'd like to see in the next version of New Relic APM is a single dashboard where you can easily view which applications fall under specific APMs. If there's a search feature where you can type in a keyword to find out if an APM is related to a particular application, that would be great.

I've been using New Relic APM for four years now.

New Relic APM is a stable solution, and I've never seen any outages from it.

New Relic APM is a scalable solution.

Support for New Relic APM is up to the mark, mainly because I belong to a big organization with dedicated email and Slack support. The support team gives clarifications about usability and configurations. I'm giving New Relic APM support a five on a scale of one to five.

My company also uses AppDynamics and Datadog for some of the applications, but those will be moved entirely to New Relic APM, as the tool is very user-friendly and has no lags. AppDynamics, on the other hand, has some delay, and you have to inject some methods in writing applications to gather the metrics. Performance-wise, New Relic APM is better and doesn't cause a high response time compared to other solutions.

Other teams handle the installation and configuration for New Relic APM.

I'm unaware of how much the license for New Relic APM costs.

My company is currently using New Relic APM.

Over a thousand people from different teams use New Relic APM within the company. My company currently has two hundred to three hundred applications, so even if New Relic APM is used occasionally, because of the number of applications it's being used on, usage of the tool could result in almost daily usage.

As New Relic APM is user-friendly, it's a tool I can recommend to others, but before making the purchase, you should utilize the free trial version, and also look at the sample dashboards provided by New Relic, which you can show to the customers to better explain how the dashboards look and what New Relic APM is used for.

My rating for New Relic APM is eight out of ten, as there's always space for improvement.

My company is a customer of New Relic APM.

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.

I use New Relic for monitoring and observing the entire environment. It offers end-to-end monitoring and observability to predict potential impacts in the coming weeks. For instance, it can detect if two endpoints start consuming more bandwidth than usual, thereby providing more insights about potential impacts on the environment.

New Relic helps us maintain and shape the environment from a network perspective by providing end-to-end monitoring and observability. It offers insights into normal and peak behaviors, alerts us to any issues, and assists with remediation plans.

The APM feature is highly valuable as it can record session hosts, usage, and diagnose customer behaviors. Additionally, we can simulate user actions to assess the user experience. The alerting capabilities are also efficient, sending emails and desktop notifications, and providing remediation options.

The pricing could be improved as it is quite high relative to what is offered. The cost versus performance efficiency could be better. Apart from that, I don't need any specific improvements to the features themselves.

I have been working with New Relic for over one and a half years.

New Relic is highly stable. I have never experienced an outage or any misbehavior with this solution.

New Relic offers high scalability. It is quite flexible and can scale according to our needs.

The technical support team for New Relic is good. I would rate them a nine out of ten.

Positive

Before New Relic, we did not use any specific solution for observability. We used normal monitoring tools.

The initial setup of New Relic is super easy and straightforward. It involves proposing the solution to the client, activating administrative users, and customizing dashboards and alerts based on customer needs. Training and preparation made the process smooth and efficient.

The deployment typically requires two to three tier-one or tier-two team members from the technical team.

The pricing is relatively high. It can be quite costly compared to the performance efficiency, making it not very value for money, especially for smaller businesses.

We evaluated several other options like Datadog. However, after comparing prices and support, we chose New Relic.

Do not implement New Relic until you have identified your needs and ensured that it meets your specific requirements. Proper assessment and planning are crucial.

I'd rate the solution eight out of ten.

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.