New Relic Reviews

It helps us organize the data from our clients and reason with it. Moreover, with the client JS API, we can report data to New Relic and query it with Insights. It is easy to use and has an understandable graph editor. 

This is the real deal.

Tracking and monitoring production is mandatory, however, we did it for years only for the back-end side. As the client-side applications grow bigger and get more complex more responsibility gets to the client. Because of that we must be able to understand if our clients are "healthy". The term "healthy" is not clear to what it means. 

Presently we report data to New Relic Insights, and we've built some really readable and understandable graphs. We monitor with those graphs every deploy to production, and we are advising the graphs to resolve current problems with our application, like errors and problems with the load and response times.

New Relic comes with some features out of the box, but not enough. There are some essential features that New Relic needs to implement that their competitors already support, like special treatment for AngularJS/React applications. We had to implement (with the JS API) the ability to query errors through Insights which is essential. Currently, we don't have a way to send alerts which is a real pain.

We are using it in conjunction with APM and Insights.

We've had no issues with deployment.

We've had no issues with stability.

We've had no issues with scalability.

We also looked at Raygun.io and TrackJs which are great products, but neither has the tri-factor, which is:

1. Tracking errors with integration to the server
2. Ability to report you own data
3. Ability to build you own custom dashboard

New Relic has a good separation between the data that you report and how you show it, along with data you get out of the box. My advice is about how to show the data in a way that it will be easy to reason with it.

You can build many different graphs, really try them all, and then decide what fits best for your organization. That's what we did. The way you handle data varies between organizations and even between teams in a organization, and the ability to show the data in different ways is very helpful with that.

New Relic always gets new things done. The system is always changing and in a good way. New features are always coming into the system and we are very happy with it.

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.

The ability to trace transactions all the way down to find where the software is broken - database, web services, etc., and all the way down, with the trace dumps, to see where our application is broken.

When our app passes critical threshold, can quickly go to Transactions and/or Database views and immediately see the code areas causing the issue. Saves so much time in debugging our code and environments.

I can have my developers find bugs and fix them in one-tenth of time they used to take. It enables the stability of our product, and it's allowed me to keep human resources at a minimum so that we have a smaller number of people to do better things.

In Alert History, while you can see the trending in response time by Request Queuing, .NER CLR and Database, if you had the ability to see which transaction type was the slowest during the timeframe when the critical error occurred by displaying the info within the same “tool tip” hover window which currently gives me the time per request and number of transactions, i.e., if it had the additional correlation information of “StatusCode/403” which you can get from the Events Errors hover. This has the potential of saving a lot of analysis time going back and forth between views.

We didn't have any deployment issues.

I haven’t had any issues with stability.

It’s scaled for us. We’re still relatively small with just 16 servers.

When my IT manager did the initial install, they were very responsive.

It was straightforward, but the issue was the unfamiliarity of our IT manager outside the Microsoft world.

If you want to save money, go for it. Time is money, and it saves you so much time to be able to find issues and to fix them.

It allows flexible queries, allowing me to find answers easily.

It’s been helpful to get a unified understanding of how our application is being used, usage patterns, etc. We get a shared organizational understanding.

Alerting based on custom insights queries. If I set a custom query to give me some value, I want to be able to set an alert for that.

No issues encountered.

It’s been scaling along with our growth.

Great tech support, very responsive. They've helped us solve some perplexing problems.

Very straightforward. Worked through our account manager.

You’ll get way more data than you thought.

The thing I use the most is the ability to tell at a glance that we’re in a red state. We have dashboards around our office which let me know what I need to pay attention to. I can dig into the error. It also has high throughput.

Mean time to recovery has improved, leading to cost savings and reduced customer dissatisfaction.

One of my issues was with not getting enough insight into errors, as I can only go back seven days. The data collection on it is not a long enough period of time if I want to see some trends. If someone is having some errors, I can’t get historical insight.

We had a problem where our application crashed because of New Relic. They acknowledged the problem and we just had to turn it off for six months.

It’s been scaling along with our growth.

Great tech support, very responsive. Have helped us solve problems.

I wasn't involved.

It’s just so easy to set up and use with little training. The barrier to entry is extremely low and it adds a high-value.

We primarily have an API so our front-end apps aren’t a huge part of our business, but Browser allows us to see geo-location to see where requests are coming from.

It also provides us with really valuable information such as which different browsers and versions our website visitors are using.

As a QA manager, it helps me to know exactly where to focus our attentions because we can pinpoint specifically where there may be issues -- where geographically, which browsers, which browser versions, and other very granular details.

I'd like to see alerting based on custom insight queries. If I set a custom query to give me some value, I want to be able to set an alert for that.

No issues with deployment at all.

No stability issues.

It’s been scaling along with our growth.

I haven't had to use technical support.

Setup was very simple and straightforward.

The APM Transaction monitoring is the most valuable feature. Being able to define key transactions and collect traces has been essential to providing actionable data for fixes and improvements.

Early in our app lifecycle we would receive random reports of slow response times from users. Of course, they were never reproducible in our QA environments nor did our OS-specific monitoring tools show any problems. Implementing the APM with our app servers gave us visibility into what our Java code and JVMs were doing at the time users had problems. This allowed us to zero in on infrastructure and code issues as well as implement monitoring cases specific to our app.

Last year, there were several New Relic outages where alerts were either fired in error or not fired at all. These have been remedied over the last year, but it negatively impacted our trust in using New Relic as our sole source of analysis and alerting.

As far as suggested improvements, the Synthetics module could be much more useful if one did not have to learn yet another analytics query language.

I have used New Relic in production since mid-2013.

Since we use a 1.x version of Play Framework, there were some initial challenges in implementing the Java APM agent. The later versions of the agent have drastically improved since then and deployments are considerably less cumbersome.

The aforementioned outages and issues were vexing but, fortunately, are well in the past.

No issues encountered.

Generally excellent.

Generally excellent.

New Relic was an add-on to our existing operations analytics systems. We selected New Relic solely on the basis of the application monitoring feature which our existing systems did not provide.

Once we overcame the challenges of implementing the early Java agent, the remainder of the implementation was effortless. We had 90% functionality within the first 12 hours of implementation.

I performed the implementation personally.

At our usage level, the cost has been trivial compared to our overall operations monthly costs. What the product has done for us was expedite our ability to discover actionable data that led directly to improvements in our app which would have taken considerable longer if we'd had to build similar functionality ourselves.

Whilst it may be tempting to instrument all of your production and non-production environments, this is a tool that is best used where appropriate, rather than as a blanket deployment.

We evaluated building similar functionality ourselves using open source JVM monitoring and log analysis tools. We also evaluated a few semi-competitors. The home-brewed solution would have required additional engineering staff and a much longer build time. The also-ran services were astronomically more expensive.

It's a great tool for monitoring infrastructure and application performance. The only drawbacks have been cost and a few issues with outages and monitoring/alerting failures.

I think the downtime alerts as well as the insight into performance killers from database queries are the most valuable feature for us.

I think that we didn’t have much insight into which things were causing the biggest performance hits, so it gave us instant feedback on incidents which may have caused users enough pain.

They have integrated alert and performance monitoring which they’re rolling out as a beta now. A lot of the features for application monitoring and uptime, and alerts for alerting the appropriate people when something goes wrong are not quite there yet.

We’ve never had any problems whatsoever.

It’s been useful as we’ve grown our user base; we haven’t had any scalability issues. We’ve done tens of thousands rather than tens of millions of transactions.

I’ve only used it a couple of times. They escalated the issues appropriately and it always seemed like someone who understood the issue jumped on the ticket, and we’ve had the issued resolved in a timely fashion.

We were previously using nothing else. We were reading through logs trying to interpret our own data, which was challenging. Someone suggested New Relic and we went with it right after; they’re the only player in town for this sort of environment.

The initial ground level setup was very easy, very intuitive, and went very quickly. Some of the more advanced features did require a lot of review of their documentation and a few support tickets to figure out.

I think documentation is probably key for us, and then support. Reputation and long-term relationship doesn’t matter so much if they have a good product. For this product we didn’t really have a viable alternative. We couldn’t find anybody else who did something similar.

We’re very satisfied with it. We had a little difficulty plugging in some more of the advanced features. It’s so big and so complex, but New Relic does invest in education.

This is the best tool for gaining insight into SaaS or cloud-based applications that we’ve seen. Unless you’re going to roll your own solution, you pretty much have to use them.