New Relic Reviews

I used it in another organization. I had a project where we were using New Relic for monitoring APIs and utilization of nodes or hosts. It was a standard implementation that involved getting the statistics and configuring New Relic agents on the application servers. The data was sniffed from the network based on the configuration and then it was saved. We were using the out-of-the-box capability of New Relic. We didn't do any customization on New Relic.

It was a good solution. My boss, who was a VP, was very happy with the system, and he didn't want to change the system because it was working well. Whenever anything went wrong, we got clear information about that on the fly. This information helped the operations team in sorting things faster. It gave clear information and a complete picture of what was happening in our system, which helped the operations team in performing the required actions.

The alert mechanism is quite accurate when something goes wrong in your system. For example, if you have hundreds of APIs on your server, and any of the APIs is not performing well, you get an alert. When there is a drop or change in the threshold value, the beauty of New Relic is that within a fraction of seconds, all the stakeholders who are configured in the New Relic system will get an alert. That's one good thing.

There is a dashboard where you can view API-wise performance. When you click specific APIs, you can get detailed statistics for the same.

One thing that we noticed was that historical information was only for a limited period, which was not helpful in certain scenarios. For example, if I want to size my system for an event for New Year or Christmas season based on the historical data, I won't be able to find the historical data. Currently, the data is limited to three months. It would be helpful if they can provide historical data for a longer duration so that we can plan our system accordingly.

It was used for more than four years.

Its stability is quite good. We don't see any issues with the stability.

We never had any challenges because our servers were scaled based on the load. When our load increased, we used to keep adding our servers to New Relic. We didn't see any challenges. It just required the agent configuration on the server. The only thing is that you have to put in more money when you are adding servers.

It was straightforward. We didn't see any complexity because the setup of New Relic on the client side or the application side is more of the agent configuration.

Once your agents are configured in the pre-prod or production environment, the feed used to be taken automatically. The only thing is you have to open the proxy to the New Relic system. If that is done, the rest is taken care of automatically. I don't see any challenge.

For the setup, we had one person from the customer IT who coordinated with the network team and got the proxy opened, and then tested connectivity between the on-premise site and New Relic data center. 

Later on, we had one person for configuration because sometimes, we also did data masking when we wanted to mask certain data. We didn't want that feed to go to the New Relic data center. We didn't want that data to be exposed. To query the system, there were queries available in the New Relic documentation, and we used to follow that. We also had a customized dashboard. We could prepare our own dashboard for our critical use cases such as payments.

I would rate it a four out of five in terms of ROI. 

If I remember it correctly, the pricing was based on the core, and the monthly subscription used to cost us $1,500 or $2,000. 

We had pre-prod and production services. Costing was different for pre-prod and production. For pre-prod, it was 40% less than the production service cost. It was a combined package. 

With our licensing, we could only query three months of data from the New Relic system. When we wanted to have the historical information, they said that it is going to be an additional licensing at an additional cost.

You have to see the costs. If you want to scale to a larger system or you want to implement New Relic for the entire enterprise, the cost is going to be high because you have to run hundreds of servers. If you take the frontend applications, mobile applications, and required servers, there will be a huge load and traffic. Dynatrace is one of the alternatives. Our last customer wanted to scale, and they found Dynatrace to be better than New Relic in terms of features and price. 

I would rate this solution a nine out of ten. It is one of the best products. The customer used it for more than four years before moving to Dynatrace. We were happy with it. The alert mechanism and other features were quite good. 

The service map feature is very useful.

The simplicity of the dashboard is very good. It shows the throughput latency and all of the transactions.

It offers transactions, but it does not offer an endpoint-level insight at the URL level. When we get a request, we want to know what the life cycle of that service is, and where the cycle is. This is what I am trying to locate with most of the solutions now.

I am trying to research how to find a cycle per endpoint and not at the service level.

It is very difficult to award the service level cycles at an endpoint level. It is important for us to get new insights to create better hygiene around the business use cases.

At the endpoint level, the visibility is not that great, and metrics are not available. It gives you a full view of the entire function's execution and not from the context of the URL altogether.

Also the response time, the latency contribution, and the throughput contribution are areas that need improvement. You can get the throughput contribution from New Relic, but not the latency contributions. You cannot get it at all.

These are the major limitations. When working with AppDynamics, I did not find any limitations, but the same can not be said with New Relic.

The way that it classifies the actual services is a bit ambiguous. It's not perfect. For example, I see there are certain solutions that are listed as extra services, as a dependency, and still I find that among load contribution, it tries to show that those services separately, which is confusing.

With the transactions, when it tries to show a type of "bufferHandler" from inside, it doesn't show what the nature of the request is. Especially with Microservices, it doesn't show what kind of method is present, which makes finding data very difficult. Instead, you need to go to the raw data. I think that defeats the purpose of using this tool.

The transactions do not show the time consumed by the request, from the metrics execution perspective. It was suggested that I did not know how to read it but I have done all that I could. It is very difficult to relate to and requires a lot of experience and time to read through, which it should not.

It should not be difficult to find the latency and throughput for the entire system when requested. It should not be difficult to develop the data that relates to the various types of execution.

It should have complete exposure around the endpoints.

The services-to-service dependency is fine but most of the startups have only one or two services that are all cycled. It does not provide you with a lot of help when you are showing that the two services are dependent.

What all of the dependent endpoints are and how are the cycles being formed is information that should be available in most tools, but not with New Relic and some other tools.

I have been using New Relic APM for one year, but in-depth in the last two months.

We are not using the latest version but within the year.

Almost all of the developers are using this solution in our organization. We have approximately 60 users.

It is used on a day-to-day basis.

I have not used technical support.

Previously, almost four years ago, I used AppDynamics. I think that it is a very good tool. I would rate AppDymanmics an eight out of ten.

We changed to another solution because of the cost. All of the developers loved the AppDynamics dashboard. It was very clear.

I was not a part of the team for the setup but my impression is that the documentation could have been better. It didn't make much sense. 

For beginners using New Relic, the setup can be difficult and should be simplified. 

We have a DevOps team to maintain this solution, but it doesn't require a lot of maintenance.

I think the pricing is reasonable.

There is a good bare minimum of required features for this tool, but if they are out to the in-depth analysis then finding a cross-dimensional relationship is not straightforward. It is difficult to implement.

If you are concerned about how your services behave, then New Relic shouldn't be your first choice. However, if you are considering New Relic APM, is a very affordable choice.

I would rate New Relic APM a seven out of ten.

Mainly our developers use this solution, and the executive management. They love seeing all the reports and dashboards. There are two things: your current features, how many people are using them, and that also gives us the sense of what people really want.

It’s like a marketing opportunity also. It gives something more which adds value. From a developer’s standpoint, we can practically put customer attributes for every transaction. We just keep pushing data, different customer attributes, into New Relic, and we can understand quickly what happened in a time frame, plus all of the dashboard views, drill-down reports – you can have multiple reports. The good part is that we don’t have to implement anything on our side – we just use the features.

Every action we have certain attributes that we keep pushing data and we don’t have to worry about it. It captures everything, which we can send to executive management. We can put a feature out and see how people respond to it, and that can go into a release which will help make money for the company and add value for the customer.

Probably make the query language a little bit easier. Improved documentation. The reasons we had to call them (they were super helpful) is because we couldn’t find the documentation. It would really help if they were to come up with some online help where you just type something in and get the answers.

In the last year, I’ve never seen Insights go down. In the first couple of months we had a little bit of trouble understanding it, but that’s OK. The query language is a little bit different. It never breaks.

I’ve spoken to them about 20 times after we started using Insights, and they were just brilliant. No doubt about it. Even the account manager could help direct resources to us to help solve issues. All we do is call the account manager and he would get us the correct person; we like to send all of the questions in an email in advance and we’d make arrangements to go through the issues or questions immediately in a meeting.

I was the one who recommended Insights. We implemented a trial for 60 days and we ended up saying yes. We love it. We do a lot of dashboard stuff. Especially the executive management, they just want to see what happened in a given week or time. What did the vendors do? What did the customers do? Who’s working on what?

It was pretty straightforward. We just put the DLLs into the solutions, make a couple of config changes for New Relic so it detects the name of the product or web app or whatever it’s trying to monitor, and just keep pushing customer attributes or whatever you want. It was very simple. Within 30 minutes you see customer attributes in the environment and it starts capturing.

I think we also looked at one or two. The first one we tried was New Relic. The reputation of the vendor – we decided to give New Relic a try after hearing about how it was used to fix the Affordable Care Act implementation. That’s how we heard about New Relic. We needed to set up monitoring and alert – when we saw New Relic we liked it and its ease of setup. We gave it a 30-day trial and after that there was no looking back.

I really love it. I’m not a developer, but I can just walk up to a developer and ask them to push some data so I can see what’s going on. It’s very easy. The whole ease part; once the code is pushed I just wait to see what events occurred.

If they don’t want to build something on their own (and it all depends on company size resources, etc.) an APM solution is the right answer. Given we have only one infrastructure guy and he can manage all of this, and a small team, everyone can use it all for different purposes. Stress testing, load testing, and evaluating performance. Each team has different ideas about how to use the reports, so it’s good for everybody. Different skill set people can use the entire NR suite for different reasons. It’s the whole package.

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.

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.

We use New Relic as an infrastructure management tool. 

The tool's most valuable features were APM and core reliability. We get alerts whenever an anomaly is detected. The solution is very friendly. 

The solution needs to have staging. 

New Relic is stable. 

My company has around ten users for the product. 

The tool has good support. They have big communities and forums apart from the tech support. 

New Relic's deployment was easy. They had good documentation. 

The solution is cheap, but prices can go up when users grow. 

I rate the product an eight out of ten. 

We were using New Relic to build performance, application monitoring, security aspects, infrastructure, exporting from databases, lower-performance tips, and trying to identify deadlocks.

Yes. However we dropped due to not able to achieve RoI due to high cost

The most valuable feature is application monitoring.

The main reason we switched away from New Relic is that the cost is too high. They should bring the pricing down to be more competitive.

I would like to see the capacity planning improved.

The security standard and compliance are areas that should be improved.

We had been using New Relic APM for a few years and have now switched to DataDog.

There is no question about this product's stability. It is very good and I would continue to use it, but the price has caused the organization to move on to the DataDog solution.

New Relic is a scalable solution. I have between 10 and 15 large customers who use it.

I have never been in contact with technical support. I am comfortable with using the product.

We have switched away from New Relic and have begun to use DataDog.

This is a cloud-based solution that doesn't need to be installed.

This is an expensive tool.

This is one of the best tools that I have used. I have recommended it to customers in the past and would continue to do so. In summary, this is a very good product and the only real problem is that the cost is on the higher side.

I would rate this solution an eight out of ten.

With the help of New Relic APM, we managed to deliver an online B2B application with average response times below two seconds, where with v6, the average response times was about 30 seconds.

The most valuable feature is the New Relic APM module to deep-dive into the application, to get bottlenecks to the surface, and to improve application performance. Also, the New Relic Insights module creates a real-time dashboard on application performance to create awareness for the DevOps team.

They need to improve the alerting and dashboarding as these are the key features in DevOps.

Once we had stability issues when the New Relic agent was overwhelming the IIS process, but that was a long time ago. We spoke to New Relic, and they delivered an agent to fix the problem.

We've not had any issues scaling it. We work with Java, and the agent is easily implemented.

Customer Service:

Many times, they have been of great help even though support is in America and we are in Europe; we get help within eight hours.

Technical Support:

The support department has good technical knowledge and is customer-friendly. Even if you don't answer their follow-up questions, the issue is resolved.

The setup is really straightforward. Install a server agent on the operation system, and install an application agent in the application.

We developed in-house and also maintain the developed application.

I don't have actual numbers, but as we improved the quality of the application, we received less incidences compared to applications without New Relic.

New Relic is either free with low retention and minimal functionalities, or expensive with full options and retention. I suggest a pricing between.

We did investigate other software, such as Ruxit and AppDynamics, but the price and quality of New Relic made us choose New Relic.

I think all online applications need to have APM software implemented to actually knów the performance state of the application.