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. 

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. 

The APM is great.

The solution can scale well. 

We've found support to be helpful.

It has a simple initial setup. 

The browser isn't exactly reliable. 

There are dashboard issues that need to be dealt with. 

There's no proper management of roles and divisions. For example, let's say if I create a dashboard and I want to give access only to a set of people and not to the other set of people, I can't do that, and that's where it has a lot of problems. If I develop a dashboard for myself, everyone else has an access to it. There's no proper access management. You just add someone to the platform, he gets access to all the dashboards. Yet there should be proper division of people who need to have access to a certain dashboard. 

I've been using the solution for three years.

While the APM is stable, the browser itself isn't too reliable. 

It's a scalable, reliable solution. 

We have 30 to 40 people working on the solution generally.

The technical support is quite good.

Positive

The solution is very simple to set up. I'd rate the entire implementation and deployment experience a five out of five. 

I've not witnessed any ROI. That's beyond my scope. 

I'm not aware of the exact licensing cost. The contracts are handled at an organizational level. 

We have a partnership with New Relic.

I'd advise potential new users to go through the docs first. They have very good documentation. Anybody who's going to start should first start with reading the documentation in order to get a good understanding of the product.

I'd rate the solution seven out of ten. I'd rate it higher if the browser rate was more reliable. 

We use this solution to provide insight into how the UI is performing.

We appreciate the way that this solution allows us to monitor the ongoing status of the UI at any given time.

We would like a dashboard feature to be created for this product.  This would allow us to monitor both the front and back-end of our UIs performance, and then report on it.

We would also like the solution to increase the details that are provided when there are system abnormalities.

We have been using this solution for three years.

We have found this to be an overall stable solution.

We have found the cloud-based version of this product to be scalable.

We use an in-house support team for this solution. They are our first-line contact point to resolve any issues that arise on a day-to-day basis.

Positive

We were previously using a different, comparable solution. However, we decided to switch to this product as it provided lower response times.

I would rate this solution a nine out of ten.

We have both the mobile and web applications which use the APIs in the back end. The New Relic Browser also monitors all our review servers and has mobile and browser compatibility. Most of our stakeholders view the data on mobile and don't need to open their laptops.

Stakeholders can install New Relic on a mobile device, whether iOS or Android and monitor the enrolment. It is more compatible with the mobile device, but we can view it on the web browser, and the same features are supported for both. In addition, stakeholders can access the system 24-7 and can monitor it from anywhere, anytime.

We can view the system in one view, showing the utilization and server activity. It lets us tell if our server utilization is high, conduct a memories review, and view it in one dashboard.

The solution only supports the cloud platform and not on-premises. Therefore, they should assess supporting the licensing on-premises as well.

Stability is good, and we had no challenges while accessing the New Relic system from the browser.

Scalability is good, and there are no limitations. Once we add our users to our account, they can access it anywhere in the browser. We have never experienced any technical problems.

We have more than 30 users that are already configured in our system. The pricing depends on the number of users we have, and we currently have only about five or ten active users out of the 30. Only our operations team typically accesses the browser.

We have four to five people who maintain and manage the day-to-day operations. They have other tasks at the company and are not dedicated solely to the maintenance of this solution. They monitor how the servers are performing and get alerts to their emails.

New Relic technical support is good whenever we raise a ticket. They reply and provide knowledge sharing for new features. For example, before the COVID-19 pandemic, they would come into our office and share knowledge with all the operational and delivery teams and others using the New Relic system. Their support and contributions are good whenever we need them.

The initial setup was straightforward and didn't require much work on the browser configuration. The user administration is also good if there is an existing New Relic account. It allows the restriction of privileges and control of users accessing complete information. In addition, it provides for a bucket of developers, stakeholders and operations and restrictions of certain access to view dashboards or features.

Browser implementation is also simple when an account and servers are added to the New Relic system. Those servers are automatically reflected on the New Relic account, and we don't need to do much. It is straightforward, and once we configure the agent, all our servers are under our account.

The pricing is a bit high, but the features are very good. It costs about 1500 per month, but historical information was something we had to buy at an additional cost. Other than that, the rest of the capabilities and features are bundled in one package.

I rate this solution a nine out of ten. We have never faced any issues with this solution, and we are not worried about the technical capability. If we have a team that understands the system and the new capabilities, it can be used effectively.

New Relic APM is an application monitoring tool.

There are many valuable features in New Relic APM. We developed some software applications and we are able to monitor the errors very easily. Their log security retention is very good.

New Relic APM could improve error debugging and the correlation with the logs. We are receiving some alerts or alarms but we need to correlate with the error log, but it is difficult if it is more than seven months retention period, it is hard to trace. We need this especially for getting historical information. 

Within short periods of monitoring, we do not have a problem it is only when it crosses the retention period that we are not able to correlate the errors with the log.

I have been using New Relic APM for approximately two years.

New Relic APM is stable. In the last two years, we have not faced any stability issues. If the vendor is having a maintenance issue they will notify us in advance.

I rate the stability of New Relic APM a six out of ten.

They are a costly solution and the stability should be better for the price.

The scalability of New Relic APM is good.

There are two types of users, one is the basic user which is free and has limitations. We have approximately 40 basic users. The second type of user is pro which does not have the limitations of the basic user. We have 10 pro users.

The support from New Relic APM is good. We create a ticket, and immediately after we have the support. 

I rate the support from New Relic APM a five out of five.

We were using another solution previously. New Relic APM was picked by the organization because they preferred it, and this is why we switched. New Relic APM is easier to configure.

The initial setup of New Relic APM is simple.

The price of New Relic APM could be less expensive. We are using the New Relic APM pro account and it is more costly. When compared to competitors the solution's pricing should be much more realistic.

I rate the price of New Relic APM a one out of five.

We evaluated other solutions, such as Dynatrace and Datadog. When comparing New Relic APM to other monitoring tools, it's not complex and is similar in features.

I rate New Relic APM a six out of ten.

Our use cases were varied. We had front-facing applications, message brokers, API gateways, legacy applications running on RPC, and platforms. We used New Relic for instrumentation, and we discovered different metrics using it.

New Relic is an APM tool, similar to Dynatrace or Datadog. It uses an agent to discover metrics based on browser, mobile, and custom matrices. We can also develop synthetic monitoring. It has helped us in exploring the metrics.

The best feature of New Relic is its simple look and feel, making it easier to use than other tools.

One thing New Relic needs to improve is the user data schema. It wanted us to move from version one to version two, but that was difficult because we wanted to do single sign-on, and it couldn't support our Ping Identity platform. That's something New Relic needs to work on.

Another issue I have with New Relic is its suite licenses. It has a two-tier system: the full-stack observability, which requires a suite license, and the free version, which doesn't offer any peer review capabilities. It needs to change because having a suite license for a user who can only view the post-stack, not even the curated view, is a big no-no. Dynatrace or SAP don't have this issue.

I should point out one more thing about New Relic. We use it with OpenShift, and one of the issues we faced was that New Relic required root access, which was a concern because no admin in the world would give any third-party vendor root access. However, they seem to have corrected this in the next version. 

I have been using New Relic for three years. We're using version 8.0.

It has its limitations, but it is a stable solution. 

It is a cloud-based solution, so the platforms automatically scale. 

We struggled with the support. 

We are currently using Dynatrace. We have moved away from New Relic because of its shortcomings – the user data schema. They had two versions, and we couldn't group different entities under version one. For example, our enterprise applications are numerous, including activation, OSS, BSS applications, and so forth.

It is an expensive solution. The licensing scheme is based on users having to have full stack observability, and there is no free version for non-seat license users to access what they want to see. I believe it's an expensive tool. They were not like that a couple of years back. Their new licensing scheme is based on full-stack capabilities; many clients would not like it. I would rate the licensing model a four out of ten. It is a very poor licensing scheme. 

It works well, and it has a very good look and feel to it. However, it also has its limitations. So some clients may like it. That's why they will be willing to pay more for New Relic compared to any other API. It's fine.

Overall, I would rate the solution an eight out of ten. 

We are currently in the POC phase with New Relic APM and are looking at using it mainly for analytics.

We integrated the library within our backend service to see the throughput and to monitor latency. We also created a few dashboards in the New Relic dashboard section to observe the traffic and monitor how the system performs during the day.

It is easier to create new dashboards in the New Relic interface, and it is also easier to query if when I want to monitor a different parameter or time duration on my dashboard.

I like the overall monitoring and analytical features. It is a complete platform in that regard.

Some AIOps are missing in New Relic APS, and I would like to see more features in this area.

I've been using New Relic APM for approximately four months.

I would rate New Relic's stability at eight out of ten.

On a scale from one to ten, with one being low and ten being high, I would give scalability a rating of eight.

The initial setup is straightforward for this solution.

New Relic APM is a mature platform, and in terms of features and maturity, it is up there with other APMs like Datadog and a few others. Therefore, it is definitely worth considering.

Overall, I would rate New Relic at eight on a scale from one to ten.