New Relic Reviews

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.

The ability to do layered reporting quickly and in real-time on stats is the most valuable feature to us.

It makes my executives happy because it allows me to provide them with usage statistics. We have three types of users: customer, internal, and vendor. We can see who’s logged on, when, how long, what views they’re using, what data elements they’ve updated and how often, and which features of all reports that customers retrieve and use the most. And management knows who’s doing work and who’s not, and who's doing what they’re supposed to be doing.

I'd like to be able to do visual selection of fields, so that executives who don’t enter queries and select what they want, but they’ve already announced that -- all that's now available. The only limitation we experience is with Insights query limit of 1,000 transactions. If there was an ability to do a “true” 4 weeks of transactions either by running Asynchronously in the background and returning an excel dump or by paging/tabbing the 1,000 transactions per window view, it too, would be perfect.

It has a limit of only 1000 records. I can run a query, and it will only give me feedback on 1000 regardless of the filters I use. Some users are heavy users and have more transactions. I’d like the ability to do 10,000.

I would like more than 1000 views.

First time we tried to do dashboard with nested queries, we had trouble getting syntax correct with tags. Tech support was very supportive with three one-hour sessions with my developers. Since then, it’s never been an issue. They literally hand-held them to get them to put the tags within our code to get the right results.

There were no problems.

If you invest in it and take the time to set it up correctly within the application, the sales and marketing information of the product will pay for itself within the first day or two.

The solution is an APM monitoring tool.

We will be monitoring all kinds of server details, including how the application is handling things and any threat count, as well as if there are any network utilization failures or problems with DNA instance ports.

The transaction summary is great. It's very helpful for reporting. 

The initial setup was not that difficult. 

It's stable.

The pricing is pretty good. 

The solution is scalable. 

There were some settings we had issues with. For example, a certain setting to change the time zone. If we change the time zone, it will take 24 hours to reflect the time zone and make the changes. It'll be great if the settings once we change them, reflect the change at least after one hour. That would be helpful so that we don't need to wait for one complete day to see the changes.

I've been using the solution for one and a half years. 

The stability is great. It's reliable. I'd rate the stability four out of five in terms of reliability. There are no bugs or glitches. 

The scalability is good. I'd rate it five out of five. It is easy to expand. 

I've never dealt with technical support. 

There were no other tools being used previously. This was the first we were recommended, and we deployed it.

It's a straightforward setup. It's not overly difficult or complex. 

I'd rate the solution four out of five in terms of ease of setup. 

Mainly the setup was done by the box team, so they were using it for their purposes and for the log activity. I'm just part of testing team, so I'm focusing more on the reporting side. The setup was not done from my end; the DevOps team managed the process.

We have mostly one person handling the setup and it took about two to three weeks.

We have a third party that manages the maintenance. There might be four to five people maintaining everything. 

Our own team handled the initial setup. 

I'm not sure if we've seen an ROI at this point. 

I'm not aware of the exact licensing costs. My understanding is that it is affordable. I'd rate it four out of five. 

We likely py a yearly licensing fee. It's all-inclusive, and there are no extra fees. 

I did not handle any evaluations on my end. I'm not sure if the company looked at other options. 

We are customers and end-users. 

Since we're working on a cloud-based deployment, the solution is always up to date. 

I'd rate the solution nine out of ten. It's user-friendly and has many automated features. I'd recommend the solution to others. 

We have our current parameters and our current dashboards. Our main purpose is to continue to migrate and get the same metrics in New Relic. We will prepare another secondary dashboard between the parameters. And we will do a lot of monitoring on it as it is mainly used for monitoring purposes.

The monitoring so far has been good and we are happy with it. 

I haven't come across any features that are lacking. 

I've only used the solution for two or three months. 

It's very stable. We have currently around 150 GB of data that we are going to analyze. Almost each and every day around 75 to 80 GB is analyzed. We haven't had issues with the volume or with bugs or glitches. 

The solution scales well. 

London mostly handles any troubleshooting. I don't have to worry about reaching out to technical support. we do have the documentation we can reference, however, if we do need assistance. 

I've used Stackdriver in the past. However, it doesn't work well, with, for example, virtual machines.

The initial setup was done by our London team. I wasn't involved in the process and don't have any real details about how it went. 

I'm not sure if any ongoing maintenance is needed.

While it's my understanding that our in-house London team handled the implementation, I can't say if they needed help or recruited consultants or integrators to assist in the process. 

While we do pay for the solution on a monthly basis, I can't speak to the exact cost of the product. There might also be some additional costs on top of the licensing, however, I can't say with certainty. 

I'd recommend companies try it out and see if they like it. 

I would rate the solution eight out of ten. We've been happy with it so far. 

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.

Regarding use cases, we use it for app support. So basically, we use the APM module, and we also use it for monitoring.

It has helped my organization to dive deeper into the application using the APM module is very helpful. So when we're looking for problems of why an app is behaving incorrectly, we can dive deep into it using the APM module.

I would have to say the APM module is its most valuable feature.

Documentation is one of the biggest things that I have a problem with since its documentation is not clear sometimes.

Logging right now is something I want to improve. So, every log that you have has to have an issue. So logging needs to be probably set right.

I would like to see more logging capabilities in the solution. If they can accept logs, they just can't report. So, I guess reporting on logging is something I want to see in the future.

I have been using New Relic for ten years. Also, I am using the solution's latest version.

The stability of the product is high.

It is a very scalable product.

I rate the support a four out of ten. One of my biggest frustrations was related to its support.

Neutral

New Relic is deployed on the cloud. The ease or complexity of deploying the solution depends on the piece that you're deploying. The app pieces are pretty standard when the infrastructure is more complex.

I have not experienced any return on investment using the solution.

I think it's overpriced for the technical support that we get. We spent over 1,00,000 USD a year.

To those planning to use the solution, I would say to do as much setup as you can upfront with the technical support reps that helped set things up because trying to set it up later is more difficult.

I rate the support a six out of ten.

• It's easy to install and to configure.
• The UI interface and navigation make it easy for a novice user to quickly use the provided relevant performance application data to determine how well their application is performing and to see other areas which may require some further tuning.

It provides a single pane for operation teams to look at and get to the root cause of issues. This allows them to take the required corrective actions and to remove some of the blame game. People can only look at their own isolated metrics.

• Ability to set-up maintenance windows, so silent time can be given to monitors for a defined period of time.
• Alerts tend to show how an entire cluster is performing, and not only that a given node is having an issue. To get around this issue one can use parent-child relationships in the naming of given applications and set the alert conditions at the child levels.
• For browser, the need to provide an interface which allows us to define a given business transaction, e.g. define all the steps of a given credit submittal. This is somewhat possible using “Funnels” with New Relic Insights.

We've been using it for a little over a year and a half and have it in the following -

• APM deployed across JBOSS, Tomcat, WebLogic, Glassfish, ActiveMQ, .Net
• Server deployed across RedHat, CentOs, and Windows 2008/2012
• DevOps deployment of APM and server agent using chef cookbook

APM and server agents are deployed via a chef cookbook or shell scripts. In one case, we had a very old version of Java running and had to deploy a corresponding older version of New Relic.

It has been operational for over a year and a half across over 200+ applications on Java and .Net, with no negative impact to any of the systems.

Given that New Relic is a SaaS model we haven’t had any negative impact utilizing their UI to view given applications or do analytics with Insights.

They are very dedicated and attentive to our needs as well as how their products can be utilized to enhance our support of given applications - 10/10.

Their on-line technical support has always provided timely updates of any open tickets as well as very open to getting on a chat Webex to resolve issue. Many issues have been resolved on either the first or second exchange of notes in their ticketing system - 9/10.

We previously used HP Diagnostics and CA Introscope. We switched for several reasons -

• UI interface required more training of the support teams to utilize the product because it wasn't as intuitive.
• Large infrastructure to support and administer the environment.
• Requires RUM appliance to tap the network so that we can gain insight into the end-user response.

We deployed the agent via simple manual steps or via in-house written scripts.

It was deployed by an in-house middleware team with vendor consulting in a few areas where the browser auto injection failed. The vendor team was very knowledgeable of their products and how to deploy and configure across an array of platforms.

Implement APM and server on non-production environments as well, especially an environment where you are running performance testing from. BrowserPro should be a requirement, and you should look into New Relic Insights as it is a great diagnostic tool. Make sure you keep, at a minimum, a few months worth of detailed data as well as populating it with additional custom attributes or data from other systems.

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.