New Relic Reviews

Monitoring the health of our infrastructure.

It has given us better insight into the performance of the system, allowing us to prepare things, if necessary. It has been helpful to patch things before they are a problem.

We are able to drill down and see what is going on in the system.

The price needs improvement.

Three to five years.

It is on our production workload, so we put a fair amount of stress on it. However, it is sort of self-contained. We do not really have to do much with it.

Size of the environment is 30 VMs which are instrumented with New Relic. 

I haven't had any scaling problems with it.

We receive technical support as part of our subscription.

The integration and configuration of the product into our AWS environment was extremely easy.

The pricing and licensing are too high.

We evaluated Dynatrace and a few others. These competitors did not provide as much in-depth information, but they were considered because they were far more cost-effective.

We went with New Relic because it was best of breed.

I would recommend to go with New Relic.

It integrated well with Docker. They have Lambda support now, so it has been fairly seamless.

I have only used the AWS version.

The primary use is for data application monitor, we used to add some backlogs into the application to see where the progress or the border makes in the process. So far, it is a good program.

I think it is the possibility to see the application flow, and gives us suggestions how to manage it. We have a mode we call "influx" where we can see statistics, traffic jams or other important information.

I think the APM mode can be improved. 

In addition, its difficult to have a predictive tool to see how the application would behave in the future when it basically only shows the historical data.

The solution is very stable.

The solution is very sclable.

We looked at Dynatrace. We analyzed the differences between New Relic and Dynatrace and we realized that New Relic was easier to implement and that our Miami office had experience to do so. They had already started using it there, in the Operations office. So, we went with New Relic.

In my opinion, New Relic is a good tool, and if a colleague was asking my opinion, I would say "Go ahead and use it!" It is a good solution.

We are a web development agency, focused on Drupal CMS. As New Relic is already integrated with Drupal, we can get our projects done with best practice and with the best value that we believe in. New Relic provides deep analysis for data and server health so it lets us know of network bottlenecks before we deliver the project to enhance our product. Therefore, we can be sure that we deliver the best value for our customers.

In our experience, the Server Insights are valuable.

Some of our customers see New Relic as a promising product to have, and we would like to deliver it to them. The only way we would be able to do that would be if we had server appliance for clients that we could install in their data centres.

We had no issues with the performance.

It's been able to scale for our needs.

9/10

It was easy and we documented all the steps that we took to make it easy for everyone. You need to be a server admin of course to do it, but you don't need much experience to install and run New Relic.

We did it in-house, you just have to follow the documentation.

It would be nice if we could buy it annually instead of monthly.

We evaluated many products, and chose New Relic because of its deep integration with Drupal.

If you are using Drupal you should get New Relic. I would say that even if you don't use Drupal, you should get it. New Relic helps us to improve our team quality and to get our projects done with best practices. It will help you get to know everything about your infrastructure.

• 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.

• Custom instrumentation/events. We use this tool are additional analytics and debugging.
• With limited code, we can create and report on custom metrics or events in real-time. This allows us to quickly identify success rates of our efforts.

Joining datasets. Currently, it’s only possible to pull data from a single event type. It would be nice to do more of a SQL-like join, for example, CheckOut events with ItemsAddedToCartEvent.

I've been using it for one year, and alongside their APM, which I've been using for two years.

No issues encountered.

No issues encountered.

No issues encountered.

Really high. While we’ve never had any major issue, the ticket I’ve opened have received responses within a couple hours with quality answers.

We didn’t use any other solutions prior to this.

It was straightforward. On each of our servers, we installed the agent, added our key to a config, and then within minutes we were seeing metrics on our site.

In-house. Always start with your development or QA environment. While we had no issues, it’s best to take a dry run, and get a feel for how the app affects performance to see if the data is what you’re looking for.

I have no hard numbers detailing how much we get back for what we pay. However, as a dev-ops tool, it has been priceless. We are now able to pinpoint issues much quicker and can significantly reduce our downtime.

We did evaluate one additional tool but the install and integration was significantly more cumbersome.

The core reason we chose New Relic was the ease of us and the quality of the metrics it gave us. Within hours of demo-ing the product, we were already learning more about our application than we expected.

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.

From operationally rich, to developer deep. Invites dev and ops to work together, most operational APM tools don't invite the dev. Most easily adopted APM tool. For innovators first, then the rest of the Org will start to "Get It".

It is a SaaS service and this creates internal friction that needs innovative solutions (but you have to own that).ROI is very high because a single SKU product is rare in APM today, and the ability to move licenses anywhere is an amazing agility quotient.

ROI - found key issues in the first month in the biggest Alexa-rated site that we own.

New Relic APM can improve the information when we dig deeper to check a problem. There should be more detailed information provided.

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

The stability of New Relic APM is very good.

The scalability of New Relic APM is good. We have not had any issue with scalability when we use different types of loads, it worked very well.

The technical support from New Relic APM is very good.

The ROI from using New Relic APM is good.

I rate New Relic APM an eight out of ten.