New Relic Reviews

We use it for application performance monitoring. It helps us to track down the bottlenecks in the application, whether it is in the database or the front-end. It is helpful for our developers when they are tracking down issues.

We are concerned about our application's print and load times. It should be faster for the end user's experience. New Relic has helped us in terms of the optimizing our print and loading times.

It has solved many of our performance issues.

The deep insights, which will give you the metrics (not a high level), so we can build out at the database level where the bottleneck is. This has been pretty helpful.

The stability is good. We haven't had any issues with New Relic. We load test for about 10,000 users accessing the application for every five minutes. This is our use case, and New Relic was used to monitor how the application is performing.

We use SaaS, so we don't really manage New Relic in any of the boxes.

The scalability is good, because it is already running on AWS.

We have not used technical support.

The integration and configuration of this product in our AWS environment was very easy.

We have plans to integrate with other products going forward.

It has saved on our developers' time when digging into performance issues.

The pricing model is a little confusing for beginners. They find it a little expensive, and if you are using it already, then that is not good.

Purchasing from the AWS Marketplace is very straightforward. When you buy it from AWS Marketplace, you can go with both options: URL SSL license and On Demand. So, when you are building, it is part of AWS, and this is convenient for end users.

We deploy everything on AWS. Purchasing the product on AWS Marketplace made it easier for us.

The pricing is okay comparatively their competitors. The only concern was whether it should be purchased on demand or bring your own license, and which way passes some savings onto the end customers.

We evaluated a couple of other vendors: AppDynamics and Datadog. They were quite a few other players as well, but we are happy with New Relic because it is simple to use and the developers can use it in their development.

Evaluate it, because it supports almost all the popular run times. Most of the popular languages support this, like Java. So, it makes it adaptable and easy to use.

I work predominantly on AWS.

We use it for server monitoring and strictly for our EC2 instances.

It has helped us maintain a much higher uptime than we had previously.

It fulfills the need that we had for the product.

Server uptime is its most valuable feature.

We have had issues with our agents going offline.

The stability has been fine.

Our environment has 25 servers.

The help from the technical support has always been good.

We have to install an agent on each of our instances.

New Relic was the main product that we looked at.

If you are looking for this specific type of application to keep a record of your inventory, then it does exactly what it is supposed to do.

We use their cloud version of it.

The New Relic toolset has become part of our SDLC -- reviewing the changes we made for impact to the production environment. It's been a valuable asset to identify areas for improvement in our application.

We utilize the APM, BROWSER, and INSIGHTS dashboards on a daily basis to monitor the health and performance of our application.

We really love the INSIGHTS query and dashboarding capabilities. It would be great to see this expand even further with more options for querying.

None at all.

No.

Customer Service:

10 -- New Relic has been very responsive and helpful when we've had to contact them.... and it was mostly about 'how do I do xxx' and not related to product problems.

Technical Support:

10/10

No.

Very easy -- install the agent and reload the dashboard!

In-house

Improved product performance and customer satisfaction.

Don't be hesitant to reach out to New Relic in the pre-sales process to ask questions for help.

I've found the most valuable feature to be--

• Being able to drill down to see data, and
• Being able to capture all the timing information and different functions.

It comes in as part of the regular process for every application roll-out. We have a standard visibility process for any application that rolls out. It gives us the ability to train our people and provide a more responsive application. We used to have many tools with many different functions, and now APM allows us to consolidate a lot of it.

The mapping between applications to servers is not very intuitive.

Another thing we come across is that our technology just doesn’t have reporting to New Relic, but that can be addressed with a plugin/SDK. However, we can’t really make the case to put in the investment to have that happen yet.

Another thing is that we’re micro-service based, and the New Relic interface only gives us views into the top 100 services out of 50,000. Typically when we monitor our system, we use a heat map, and New Relic only provides us the second-level view of that. Ideally, it would also provide us the first-level view. Eventually, we’d like New Relic to step up to do that.

Finally, it should ideally do two things -

1. Isolate the problem right away without the user having to do a lot of analysis. Right now, New Relic provides a lot of data points that require me to go in to understand.
2. It has its own dashboard, and I’d like to be able to bring that/integrate it into our own system (use an API to pull out data).

Sometimes when we pull data from New Relic, we time-out or drop data, and we can see when that happens, but we're not sure if it’s us or them.

Also, the alerting system has trouble with large alerts that come up slowly, requiring the operator to know the system well (yellow, red, orange) and to know what the alerts mean.

It hasn’t scaled quite right now. We use another tool for out-of-gate view. Currently, we manage about 60,000 servers in total and we don’t have a good roll-up view of the entire system. The application on the server side is OK. We use other tools to monitor the environment.

So far, the interactions have been good, and they keep us in the loop as to what’s been done. In terms of the solution, it’s just OK.

I wasn't involved in the setup.

Engage the development community within the company early, and request an integration tool to make implementation easy.

The way some transactions are recorded, you can dig through and see what’s going on with the request, how many times you’re making a certain call. That’s the biggest part – almost like application profiling.

We get greater insight into what our application is doing once it’s in production. We can identify issues faster, and being able to identify issues before they become a big problems is an improvement. We use it in load testing to identify inefficient query patterns.

At times some of the data can be opaque. Some of the aggregates over time tend to become more vague, so you lose resolution. Greater resolution going further back in time would be nice. If I start going back a month or two, the resolution is a lot lower, which is kind of challenging and makes it harder to do in-depth historical analysis.

Alongside APM, we're using New Relic servers, plugins, and pretty much everything else except Insights, Synthetics, or the mobile product.

Pretty stable. Sometimes the charts will fail to load or there are some random errors. But because of the way we use APM, there’s no significant impact.

Our use doesn’t really push the limits of New Relic, but it looks like it will scale just fine.

It was already in production when I joined the company.

I don’t see us being able to operate without New Relic. It’s important to collect a lot of metrics, but it’s more important to identify the ones that are essential to your business purposes. Know which data are really important and what you should keep an eye on.

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.

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.

We are using the SLA reporting, server monitoring and alerting, however the main and most important feature for Mangocam is the real time application performance and capacity reporting. We are also using plugins for memcached and database monitoring and alerting.

New Relic has changed the way we are dealing with application problems. It's the first place for our administrators to check if we encounter issues. In most cases, New Relic can immediately pinpoint the root cause of the issue, be it application errors, slow transactions, external services, database throughput or high transaction count. New Relic can monitor thresholds and alert if required. We are also using New Relic to help understand performance tests and bottlenecks.

Some of the 3rd party plugins could be improved - especially the requirement for java to monitor simple network services is not ideal. Also the pricing / plans may need restructuring as there is a big gap between the free offering and the first paid tier.

About three years for Mangocam.com, also at two other companies as IT consultant for the last 4 years.

We have used the PHP and Java monitoring modules as well as the server monitoring service without many problems. There was an initial glitch with the javascript injection on parts of our site, which has been sorted out quickly with the help of the New Relic support.

None so far. The service is very mature and very stable.

None so far. However, the amount of servers and services connected is limited.

We only had to contact the support twice and in both cases the response time and professionalism were exceptional.

The quality and expertise of the email support was very high, we have no complaints.

We have tried different services in the past, which only offered part of the features, but again New Relic is very different - complete product that just works.

Setting up New Relic is very easy and well documented. It's using the standard operating system packaging tools and is straightforward.

We implemented it in-house.

There is no measurable ROI as we are currently utilising the free plan / option.