New Relic Reviews

The ability to do layered reporting quickly and in real-time on stats is the most valuable feature to us.

It makes my executives happy because it allows me to provide them with usage statistics. We have three types of users: customer, internal, and vendor. We can see who’s logged on, when, how long, what views they’re using, what data elements they’ve updated and how often, and which features of all reports that customers retrieve and use the most. And management knows who’s doing work and who’s not, and who's doing what they’re supposed to be doing.

I'd like to be able to do visual selection of fields, so that executives who don’t enter queries and select what they want, but they’ve already announced that -- all that's now available. The only limitation we experience is with Insights query limit of 1,000 transactions. If there was an ability to do a “true” 4 weeks of transactions either by running Asynchronously in the background and returning an excel dump or by paging/tabbing the 1,000 transactions per window view, it too, would be perfect.

It has a limit of only 1000 records. I can run a query, and it will only give me feedback on 1000 regardless of the filters I use. Some users are heavy users and have more transactions. I’d like the ability to do 10,000.

I would like more than 1000 views.

First time we tried to do dashboard with nested queries, we had trouble getting syntax correct with tags. Tech support was very supportive with three one-hour sessions with my developers. Since then, it’s never been an issue. They literally hand-held them to get them to put the tags within our code to get the right results.

There were no problems.

If you invest in it and take the time to set it up correctly within the application, the sales and marketing information of the product will pay for itself within the first day or two.

Transactions overview - we can track the slowest ones to see where the problems occur. It’s the first place we look for problems.

Both developers and operations people can look at the same data, and that’s a great benefit. Operations can monitor, as they’re also in charge of the website, and developers can use it to see code changes.

It could be faster, but they’re already working on making this.

Quite stable. There have been some times where it failed to record something, but those were rare. Pretty reliable.

No performance issues when scaling. We don’t need to care about scaling it as it monitors our system. You just put an agent in the server and New Relic takes care of the scaling to provide you with the data.

Haven’t had to use it as the product is quite easy to use. Also, the documentation is also very clear in how to use the API, etc.

Just do it.

It's schema-less and unconstrained to queries. And although NRQL isn’t as expressive as SQL, we're able to implement a solution that uses New Relic's API to provide data so the project manager can query it using NRQL.

They announced that they’re expanding a GUI to make NRQL even less technical.

Helped us understand that we had a professional group of our users that we didn’t even know about.

It identified mechanized behavior (e.g. bots) and then blocked them.

Raw transaction didn’t give us data that we needed. We needed user information so we needed to supply the data with an API.

It’s built to stay up. We starting sending a ton of data to them. They were able to deal with it on their end given their internal architecture. We had a marketing partnership with them.

It’s responsive. When I have had questions, we used the forum. As a big customer, we get a response within a few hours.

Our CTO came back from a conference last year and we were trying to solve a problem using DynamoDB, S3 and Redis (trying to solve the user segmentation question and analyze user behavior). Within a few hours of implementing the API, I was able to query for what we needed. You could do a lot with elastic search, but that needs a team of three people.

No complexity. Just an API call.

They charge by the number of events and for the retention.

It shows you what’s going on, but we had to do custom instrumentation ourselves.

• Debugging response time is less
• Alert notifications and alert summaries

• I wish it had more insight into what might be causing a particular slowness issue. It finds the function, but it would be great to have insight into what’s slow.
• More instrumentation.
• Also, it would be good to compare machine state to machine state (compare versions of UNIX, Ruby, and libraries) and be able to perform auditing of machines.

Never needed it.

The decision was why not to have it (cost?) not why to have it.

New Relic is great for DevOps and for a company that expects developers to do their own operations. For specialists they tend to have their own instrumentation tools.

It is easy to set up from scratch, as you don’t need resources.

Also, the response time and PHP are valuable.

From an ops standpoint, we can know and pinpoint what the problem is. We're excited by down-to-the-server performance, as this was missing before.

If they added the monitoring to the ops-server side, it would be better.

We're using it alongside Insights for about three years, and heavily for the past two years. We had logic monitor that helped us at server level.

We're moving our infrastructure to AWS, as they are integrated with it.

No issues with tech support.

It was easy.

It's easy to deploy and maintain, and all bugs can be handled.

• It integrates everything, which is awesome.
• The level of detail and customization, and integrating Insights with an application.
• Using analytics as an application database.
• DevOps for marketing.

Error handling and reporting is a little lackluster, but they're announcing a whole new analytics approach.

We have a big deployment and use all of their product offerings except Mobile and Plugins. We use APM, Browsers, and Insights.

No issues. It’s expected since they’re cloud based.

They’ve been friendly and responsive.

We compared them to others, but they seem to be pumping out more features. Insights has no competition. They pump APM and browser data automatically so that it’s all seamlessly integrated into their insights.

This is an awesome APM, and solves a lot of the problems that were in the interactions between system components and micro services, to see how the system between the backend, middle tier, and front-end works. 

It provides diverse middle-tier Insights through the entire execution landscape and actionable data. Some give you alerts and logs, but to figure out what to do with that is New Relics strength.

The browser functionality gives view activity on the client, JS errors, in the same view as the rest of the APM allows us to solve these things quickly.

One issue is cost.

We looked into other solutions. SumoLogic does other kinds of log aggregation. Maybe Splunk. LogAnalytics. Rigor is a competitor to their Synthetic.

Because they have a lot of new functionality, to get an ROI we use an open source solution that they give us, GA monitor.

They have a price desk who can be negotiated with.

• The monitoring and alerts for servers
• Memory
• Disk space
• CPU

We use it at our clients' sites. We own all our dev servers, and then hand them off to our clients. 

Then, with our micro-services, we have basic analytics. It is super simple to set up.

If we can find a way to communicate the need to use it, we use it, but we want a way to hand it off to our clients easily. There are other solutions out there.