New Relic Reviews

We were using New Relic Synthetics to test our application, which retrieved data from the web on a daily basis. Our second use case was that it helped us to isolate any bad code.

You put the hooks in for the website as a database, and you can drill down into all of the offending code. You can even go down into the SQL. We were running an Oracle database and I was the DBA, so the SQL level was my responsibility.

The most valuable feature was drill-downs. I was able to use it to drill-down into the SQL, get the response time, as well as the allocation based on IO, CPU, and the other resources attached to the SQL queries.

We were able to integrate with the messaging tool, Slack, which meant that we got notifications whenever something was not quite right.

There are certain features that are not supported in New Relic, such as CATSEARCH, which allows you to do a full-text search. Certain things like this would have helped me a little bit.

We used New Relic Synthetics for at least a year, up until the end of 2019.

It's a stable solution and we never had a problem with it.

Prior to New Relic, we were using some Oracle tools such as AWR. Although they were useful, they were not really proactive. New Relic is a more proactive tool, as it were.

I was not involved in the initial setup, but it was done in-house by one person. It took at least half a week to complete it. This included setting up the service, and Slack integration. It took a nice amount of time, in total.

I loved this product, but we can no longer afford it, so we dropped it.

Honestly, at first, I was very hesitant about using this product. My advice is to learn to use it and learn all of the features because it has many of them, not all of which are documented, but they work wonders. For us, they really helped a lot.

I would rate this solution an eight out of ten.

We use it for monitoring the CPU, memory, services, email rates, etc.

We monitor the Internet daily, or every few days. Then, every time there is a crisis, high traffic, or if we see a problem with a server, we go to New Relic and monitor it to determine the cause.

• The APM
• Monitoring
• The capabilities which allow you to easily see whatever you are looking for.

• I would like to be able to invest less time in IT and ad hocs. We should be concentrating on other issues.
• I would like more deep dive monitoring into services and being able to install it on some apps.

It is stable. We don't have any issues.

The scalability is good. We have a few thousand servers, and it is up and down based on the traffic and need. We have New Relic on all of our servers.

We don't use the technical support.

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

We have it integrated mostly with our physical servers.

The product saves time and money.

Purchasing through the AWS Marketplace was easy. The product is easy to deploy and manage, which is why our company purchased through the AWS Marketplace.

The pricing could be better. We did not purchase the full version. Maybe if we applied all the other features of the full version of New Relic, we could get all the features that we feel are missing.

In addition to New Relic, we evaluated Monitis and Dynatrace. We chose New Relic because it was cheaper for us as a startup, and it is also faster and more user-friendly.

Go with it. It is a good product. It gives us the visibility that we need in monitoring.

The AWS version is easier to deploy than the on-premise version.

We used it more heavily before Synthetics came, but it’s kind of like Synthetics, but used domestically.

It allows us to perform threshold testing to see how quickly transactions are getting out to customers, providing us with data such as response time and adequacy.

Our software does significant data queries, so we throttle performance according to region just to keep the application up. Now we can open it up completely because of New Relic tools.

Ability to quickly identify different browser usage performance issues across our application functions. Again saves time in coding to enhance the end user experience.

It enables us to fine-tune our application quicker. It's also better if we find issues in our application than if our customers find it.

It also prevents performance issues because we're able to see potential issues before they cause real problems.

I can't recommend any improvements to Browser. I really can’t find anything that I don’t like about these apps.

Deployment was very simple.

We've encountered no issues with stability.

Scaling has not been a problem.

I've not had to use technical support.

We had no problems setting it up.

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.

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.