New Relic Reviews

I like the integration with PagerDuty, so that helps spread out our on-call schedule. Application performance helps us drill down on the bottlenecks in our applications, to save us a lot of development time.

The real benefits are for end users. They’re getting a better experience with our software. It allows us to respond faster to any incidences.

• Better error reporting
• Better ability to drill-down into errors

No problem at all.

It's absolutely great.

No problem at all.

They were fine. I spoke to a developer from the mobile team and he answered the question on the first attempt.

This is our first APM. We were looking for a solution that helped us to improve our customer experience. It was borne out of database issues we were having at the time. We had no APM solution prior – it was all done manually.

Straightforward. It would have been better to have more transparency to understand how New Relic actually slots onto your page, how it fits into your application.

We also looked at AppDynamics. New Relic felt like a better solution and the data that came out during the trial was better.

Breadth of features, user experience, and constant development of the platform, as well as the value it’s adding to our business. Our products have grown with the New Relic platform; we see the value that people are getting from the platform. The data pretty much speak for itself – sign up, get a trial, and use it in production immediately.

• Real-time transaction monitoring.
• Seeing a failure from somewhere in the system that you do not have deep-level access to.
• Instantly being able to drill down. For various reasons, developers rarely have access to the production environment. So instead of three days of back and forth with approvals to gain access to the system, we have instantaneous insight into these systems.
• If there was a silver bullet, it tells us in real, actual time where time was spent. We can run it in production on all of our nodes without a performance hit. It doesn’t impact the end user.

Short turn-time to resolution is essential. It’s the flashlight to the core of an issue in a production environment that everyone may have missed in development, QA, and implementation.

So basically it allows the business to more efficiently spend its money rather than in QA. The faster you can identify these question marks and find answers, the faster we can solve the problem, and the quicker we can solve the problem. We can focus on net new value.

The new Insight stuff is pretty exciting, so that’s interesting to some of our clients. Some way to disable data scrubbing manually would be a big feature.

We’ve been in production for five years.

Never had an issue.

Again, no problems, but I've never run it at a site that is truly a top-100 site. We know there is some overhead, but nothing Google-scale.

The cost of the solution is high on a per-node licensing scheme and that’s the prohibitive factor, but in terms of the actual scalability there are no issues.

The licensing fee for a single node can be comparable in price to running that node, certainly in the modern cloud world.

We haven’t had an opportunity/need to use it.

The solution we were using before was cobbled together from a mixture of sources, various monitoring solutions. None of them really offered the visibility of the overall health of the application. They’re all sort of looking at unrelated data points and we were left to infer what was happening.

New Relic understands the common tools you’re using; they had the first player advantage, plus the kind of nailed everything else. When they first released APM for Ruby there was nothing else like it, and there was barely anything else like it for any other tech stack. When they first hit market they were fundamentally different and better.

New Relic “hides” all of the stuff that is less valuable and lets the good stuff bubble up which lets you focus on that rather than anything else. A huge part of it has been the lack of having to do any app configuration to get started.

Incredibly straightforward. Procurement is the hard part.

Dynatrace came up in conversations, but not really. Solarwinds also.

New Relic is the first thing we bring up. When the vendor is aligned with the rest of the development community around the technologies. They have nice trial periods, month-to-month, which does make it easy. We are looking for solutions that allow us to say with a straight face to our clients that they work and they’re safe.

They didn’t rake us over the coals to start extracting value, and there's no lock-in. We got really fast results times and it's a pleasure to work with. A growing suite of tools that work together, New Relic is going after bringing solutions to a contiguous set of needs. It’s a win for the clients, and it’s a safe bet for the future.

Understand whether you’re using a SaaS; the organization needs to be warm to the solution. Put together a PoC to show the value of the product – put it in a dev environment and start feeding it data to be able to understand the value of it.

We can, in seconds, discover and point to the component/code that is giving us performance issues without debugging all the code.

After some days of using the product, we could optimize the code of multiple critical application used by our customers and, therefore, provide better, more stable services.

The ROI was there already after several days. Debugging and finding issues was taking, at a minimum, several days, now we can do it several hours.

We can get a complete and detailed view of each component of our product and focus immediately on performance issues, or give priority to the code/component we want to optimize.

Also, with the reporting/alerting and SLA feature we can generate reports to see the average response on days/weeks/months.

Lastly, it can help us compare between days, so we can see the impact of a deployment of new code on performance.

Labelling and tagging should be more user-friendly. It needs some more features.

We've used it for more than one year, almost two. For some months we had temporary licenses, then we bought the required licensed when we saw the add-on value of the product.

There were some small bugs with the ability to update the dashboard the driver, RAM, and CPU after we upgraded to a server application. We had to ask New Relic to manage this issue on their side.

No issues encountered.

9/10 - very good and fast response. They always try to provide real support to understand your target, your issue, and try to find a solution to reach their customers target and satisfaction.

9/10. They know their product and most of technical replies are very clear, working, exactly as they say, and are easy to implement.

The deployment is easy, and it only takes one minute to install the package at the OS level for a server via RPM, and via agent for different applications where you integrate them in your application. It would be difficult to do make it simpler.

It was peanuts, and you install the agent/plugin on your OS or application, then you start your application or the agent on the OS, and it is automatically integrated in the dashboard on the cloud. It's impressive how it is so simple.

You install it yourself.

In several days, we got a great ROI due to an issue in an customer application. In the past, it was taking days for our developers to find the root cause of performance, and the slowest component. Now, in seconds, we can point direclty to the code/component that is slow, that has issues, and allow the developers to directly focus on working on the code to provide an optimized and stable code to deliver better service to the customer.

Price and licensing is very efficient and correct.

We looked at other products, but we had first priority on an ROR/Ruby application for a new application. The payroll exchange used by our customers all over the world and some good competitors didn't support ROR/Ruby applications.

It's very good but still needs to be enhanced. Test it by implementing it, and in minutes, you will analyze the results and the dashboard and adopt it.

My organization follows SOA architecture to address the overall complexity. We have broken our system into different services according to complexity and functionality. When we serve a customer, multiple services come into picture. To identify the exact time taken by a service or failure in a service, we had two options:

a) Go through the logs and identify the exact issue or time taken by the component (too complex and takes a considerable amount of time).

b) Install an application monitoring system that can measure the performance of different services from the customer themselves and, in the case of issues, identify the issue and/or alert (less time required to diagnose the actual issue with visual representation).

The second option is much better in all scenarios.

The installation for New Relic is butter smooth and hardly took 5 minutes for the first server. It even reduced to less than 2 minutes for additional servers.

We found the following benefits after installing New Relic:

a) Ability to pin-point the exact module/service creating issues.

b) Lightening fast issue identification since there is no need to go through gigabytes of log files and, since we have a number of servers in our cluster, it isn't even feasible to check each and every server.

c) Access to web page load-time, size, and error tracking, vital for a e-commerce.

It would have been great had it provided thread-dump analysis and a few additional JVM-related stats. For reference, we can check JVisualVM.

We have used this solution for over 3+ Year. We put this system in 2012 and it is still up and running perfectly fine.

There were no issues encountered at all.

We didn't encounter issues with stability.

There were no issues with scalability.

They were pretty helpful and quick in addressing our concerns.

10 on a scale of 10.

We did not use any other solution.

It was very simple and took minimal effort and time.

New Relic only comes in SaaS flavor and installation is pretty quick. We used our in-house team for implementation.

From the perspective of effort and time taken while identifying issues and resolution, we have gained a lot. Not sure about the financial ROI.

It totally depends on the organization's requirements and the effort vs. return one puts in monitoring the system. Although, it would have been great if the licensing cost could be reduced a bit.

Yes. We evaluated AppDynamics.

Go ahead if you can afford it. You won't regret the decision.

The ability to have real-time performance statistics, as we need to know if the main features of our website are working and responding fast enough to our clients' clicks.

New Relic helped us in realizing that sometimes our online service wasn't as fast and reliable as we expected it to be. With the help of New Relic tools, our organization was able to detect, track, and fix errors in our website, so we focused our efforts in these areas.

The pricing model. New Relic can be expensive for growing startups. Maybe they should think of some more choices.

I've used it for two years.

Not at all.

No, access to the New Relic website and reports was always stable. Monitoring, events and reports are always available and we didn't notice any kind of downtime.

No, our website started with a small number of users and grew to hundreds. New Relic was always working as expected.

Customer service has always answered our questions very quickly, even on weekends. It seems very effective. 10/10.

We previously tried some hosted solutions using a variety of tools to perform monitoring and reporting tasks. We decided to switch to New Relic for its simplicity on setup and maintenance. We are able to quickly deploy new servers using New Relic in zero time.

New Relic offers great tools to integrate your software stack with their tools, and everything worked like a charm.

We implemented New Relic ourselves

Pricing can be dangerous if your product grows a lot. You should start with the free lite option to see if you can find New Relic useful for your application, and then try the Pro version with one or more hosts.

No other options evaluated,

Search in the plugins repository to see if there's already a package for your CMS framework. Install que iOS/Android mobile app to monitor your sites and get alerts.

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.

The most valuable feature is the transparency into how applications are running. That’s huge because we previously didn’t have it and we had no idea what was going on. Now, we can see exactly what’s going on and are able to understand what code paths are running. That stuff is hugely beneficial to us.

The biggest thing is being able to give our customers a world-class experience. As we’re in media, this means things like hockey results, election results, favorite TV shows, etc. We’re able to cover all our bases to make sure our customers get what they love.

When I look at APM now, it’s very web-centric, but we have certain infrastructure components that are very service-based which take data from one area to another. With APM, it’s a little difficult to fit into that. So, what I’d like to see is the ability for the dashboard to be customized where it can display collection jobs and how they break out one by one.

It also needs some web UI tweaks. It’ll be interesting to see where it evolves with the “analytics everywhere” theme and incorporation of all the other items.

There are no stability problems. There have been slow points where data loads slowly, but it can be solved just by clicking refresh. No problems with agents crashing or not reporting data. So no reason for me to worry about its stability. I never have to worry about not collecting data.

It’s scaled to all our needs. We have apps for on-site and in-cloud, and it’s worked well for both.

We haven’t had to reach out yet, and hopefully things keep going smoothly.

It’s easy to use, has a low barrier of entry, you can craft custom instrumentations, and craft your own metrics to get your own details out of it.

It helps you to define the transaction percentages, average time, and highest throughput. Also, it tells us the transactions that take the most time on average. Those are the high level, most useful features.

It also tells us about every single request that comes in and how the system reacts to it. You get to see everything from the dashboard, all these breakdowns per layer of your architecture.

Error rate is the second most useful feature – there are alerts tied to that. You get paged when the error rate is above an expected percentage and that has worked very consistently and reliably for us.

The best thing is that the team has grown, and a lot of people are developing the code, but you tend to have regressions that are clearly visible in those transaction traces.

When there’s a deployment, it shows by graphing if a regression has happened, and it allows us to react. Catching regressions in performance is very important, and since we now see the breakdown in every single layer in the application, you know right away if there’s something you’re not expecting. We can then go and figure out if it’s an infrastructure or code issue. It gives you a high level view of all of the requests coming in. Error rates are a good indicator for potential rollbacks for a potential deployment – and usually it’s pretty instantaneous. At the end of the day as users, we get what we want.

For the purposes for which we’re using it, it just works. So far I don’t have any requests for new features.

Currently, it is not the only solution we have for monitoring so there are things that it’s missing – for example what Datadog does for us. Timeline series, custom timelines and graphs, and I’m not aware of those features in New Relic.

Every now and then there are little quirks, like the web site will stop refreshing by itself, or the graphs will show something that’s not happening. But in my experience just refreshing the graphs will fix it. But we’ve never had any downtime with New Relic.

We have scaled up as well in terms of number of hosts. There is some perceivable difference in performance when you’re looking at a graph versus number of hosts, but so far it has been fine. It’s definitely not the same looking at a single host versus many hosts.

The fact that I’ve never had to contact support by email or phone is a good thing. The online documentation has been fantastic. Everything you want is available in the documentation.

It was already in production. I did deployments in the staging environment, but not the first deployment. We will be doing the first deployment for mobile as well.

It was already in production. I did deployments in the staging environment, but not the first deployment. We will be doing the first deployment for mobile as well.

You need to understand what’s in their stack, what technologies, what libraries, and it takes someone who has experience with those technologies to help make the decision. It also comes down to best bang for your buck, and I’d definitely recommend New Relic APM.