New Relic Reviews

Mainly our developers use this solution, and the executive management. They love seeing all the reports and dashboards. There are two things: your current features, how many people are using them, and that also gives us the sense of what people really want.

It’s like a marketing opportunity also. It gives something more which adds value. From a developer’s standpoint, we can practically put customer attributes for every transaction. We just keep pushing data, different customer attributes, into New Relic, and we can understand quickly what happened in a time frame, plus all of the dashboard views, drill-down reports – you can have multiple reports. The good part is that we don’t have to implement anything on our side – we just use the features.

Every action we have certain attributes that we keep pushing data and we don’t have to worry about it. It captures everything, which we can send to executive management. We can put a feature out and see how people respond to it, and that can go into a release which will help make money for the company and add value for the customer.

Probably make the query language a little bit easier. Improved documentation. The reasons we had to call them (they were super helpful) is because we couldn’t find the documentation. It would really help if they were to come up with some online help where you just type something in and get the answers.

In the last year, I’ve never seen Insights go down. In the first couple of months we had a little bit of trouble understanding it, but that’s OK. The query language is a little bit different. It never breaks.

I’ve spoken to them about 20 times after we started using Insights, and they were just brilliant. No doubt about it. Even the account manager could help direct resources to us to help solve issues. All we do is call the account manager and he would get us the correct person; we like to send all of the questions in an email in advance and we’d make arrangements to go through the issues or questions immediately in a meeting.

I was the one who recommended Insights. We implemented a trial for 60 days and we ended up saying yes. We love it. We do a lot of dashboard stuff. Especially the executive management, they just want to see what happened in a given week or time. What did the vendors do? What did the customers do? Who’s working on what?

It was pretty straightforward. We just put the DLLs into the solutions, make a couple of config changes for New Relic so it detects the name of the product or web app or whatever it’s trying to monitor, and just keep pushing customer attributes or whatever you want. It was very simple. Within 30 minutes you see customer attributes in the environment and it starts capturing.

I think we also looked at one or two. The first one we tried was New Relic. The reputation of the vendor – we decided to give New Relic a try after hearing about how it was used to fix the Affordable Care Act implementation. That’s how we heard about New Relic. We needed to set up monitoring and alert – when we saw New Relic we liked it and its ease of setup. We gave it a 30-day trial and after that there was no looking back.

I really love it. I’m not a developer, but I can just walk up to a developer and ask them to push some data so I can see what’s going on. It’s very easy. The whole ease part; once the code is pushed I just wait to see what events occurred.

If they don’t want to build something on their own (and it all depends on company size resources, etc.) an APM solution is the right answer. Given we have only one infrastructure guy and he can manage all of this, and a small team, everyone can use it all for different purposes. Stress testing, load testing, and evaluating performance. Each team has different ideas about how to use the reports, so it’s good for everybody. Different skill set people can use the entire NR suite for different reasons. It’s the whole package.

The most valuable features for us are:

• Application performance index score
• Error rate
• Transaction traces

When an app goes down, we can get insights into the issue with New Relic. It tells us what the problem is. For example, if there is an issue in the code, we see a spike in the error rate in the applications. The load environment lets us stress test our application to find the bottlenecks in the code.

They already have everything we need, so I can't suggest an improvement.

I was not involved with deployment.

Very stable. No problems.

No problems.

One issue – there is no option for live chat or phone support. We can go to the community forum to post a question and wait for the answer.

The solution was already in production when I got to the company.

New Relic is the right solution in my opinion. The light version of server monitoring is free with New Relic, and application performance index and error rate are the key features to look into.

Debugging tools, as we’re huge on this. Being able to drill down into what’s actually going on with our stack, being able to see the performance issues, where our bottlenecks are.

We do continuous deployment and delivery. One of the things that’s useful is to be able to detect when we deploy bugs and issues into the live platform – error reports are hugely useful.

Throughput, apex, those kinds of things, so we can always see what’s going on. The New Relic Browser also gives us the front-end reporting, versus APM on the back-end.

Speed to issue resolution – making sure our stack is healthy. If someone reports an issue we’ll always go to New Relic first; that’s where it becomes a good product in and of itself. It gives us all the information we need in one place.

We have custom insights dashboards – massive screens with all this information aggregated.

A few issues in the past; there were some CSS issues where sometimes the CSS wasn’t rendering, but they seem to have overcome those. I’ve never experienced downtime which is impressive.

We use the APM scalability tools; more so in the past. Now we’re in the cloud we can see how the stack performs. We use some of the graphing to see at what point we’ll hit bottlenecks, and the in-depth reporting to identify weak points.

We’ve used it a couple of times. They’re great. They follow up with us as well, which is nice and quite unusual.

It was already in production, but I have done it in the past elsewhere. It’s so straightforward it’s ridiculous.

I like the solution so much I haven’t necessarily tried other products and don’t need or want to. Ask if the solution has the main features your stack needs. Does it support your languages, frameworks?

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.

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.

Dashboards let us monitor applications. We can see exactly what the problem is and where we need to go to troubleshoot it to solve the problem. Most of the time it tells us what the problem is. When you see it up in the application you put it exactly where you need it; we can troubleshoot simply by looking.

If something goes bad, we can resolve it faster and in the proper way, rather than spending a lot of time just trying to understand what’s going on. We can see easily what’s working and not, so there’s less downtime.

It’s really powerful with a lot of features, but some training and documentation from New Relic would be useful.

We had some problems at the beginning, but we may not have set it up properly. It’s not clear if it was stability problem in New Relic or in our application, and it was just at the beginning.

Our stack is fixed, so we only scale within the set number of servers.

I wasn’t on the implementation team.

Sometimes we just don’t know how to maximize the use of its features. If we had some additional training, that would help.

The main APM page with the graphs. We leave that up on our wall and we can tell pretty quickly if something is about to go wrong, or if the response time slows down. Database queries are really helpful as they helps to figure out where the low hanging fruit is in terms of making the site faster on the database site. 

I use key transactions a lot when I’m tweaking the resources for the site. There are certain transactions that I care about more than the rest. 

I use the throughput numbers a lot, especially working on workers as opposed to web. If I’m going to add more workers, first I want to know if there will be a bottleneck somewhere.

It saves time and engineering resources in terms of making things faster and diagnoses problems. For us, engineering uses it but no one else even knows what it is. Overall, it improves the experience of the customers and site users.

It’s pretty solid. Sometimes they have downtime – for the most part the New Relic site is up all the time, but once in a while the data is delayed on the graph (like every month or two), but other than that it works!

It’s scalable – thumbs up. We turn on new servers and New Relic just works.

It was already in production when I joined.

All the information is there, but sometimes it’s hard to figure out what it means. You have to have used it a number of times in order to understand where to look. It doesn’t tell you the whole story, it just gives you pieces.