New Relic Reviews

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

• On-demand profiling – This gives us the ability to execute a thread profiler on demand and get a very in depth view of call costs
• ApDex/Error monitoring – As a dev-ops solution, this is a great tool because we’re able to help predict issues before the end-user starts notifying us. We can set thresholds that are based on our metrics

We are now able to quickly identify how our product behaves in production. Before New Relic APM, we would push a build, and try to dig through a plethora of information (event logs, error messages, customer feedback, etc) to find problem spots. Instead, we now publish and can see all the key stats (apdex, response time, error rate, etc.) and quickly drill into what’s causing an issue.

More configurability through the dashboard, for example, being able to ignore transactions without the need to update the config or code.

I've been using it for two years and alongside Insights for one year.

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 minute 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 demoing the product, we were already learning more about our application than we expected.

• It provides information on where time is spent overall in server requests.
• It performs database query time analysis.

New Relic APM generates weekly performance reports, but they aren't really actionable.

No, but it was deployed before I arrived at the organization.

No, the service appears very stable. We get occasional 503 errors when pushing data to New Relic, but it's fairly infrequent.

No issues encountered.

We haven't had to interact with customer service at all.

I haven't had to use technical support.

We've always used New Relic.

It was done in-house.

We never quantified this.

New Relic was the market leader at the time. It still is, although there are more competitors now (AppNeta, sysdig).

At the moment, I think the aspect of their product is the most useful to us: server monitoring. We actually display the status of our servers continually in our dashboard (using https://Screensaver.Ninja) because that's a critical aspect of our operation. This is only true because our most used product is not gaining new features as we are re-writing it from scratch, but while we were developing new features, their performance report on which controllers are taking the longest and which parts of the application are consuming the most resources is incredibly useful.

Very simple, using server monitoring. I saw over a period of time our disk usage increase until some servers went into yellow alert (above 70%). Then we started working on this issue without a rush because we knew we had time, and instead of increasing the size of our servers and thus having extra cost, we managed to find how to reduce our storage footprint to fit within our current servers. Constantly seeing the green status of all my servers makes me sleep well at night.

I think their dev packages for server monitoring could handle configuration a bit better. We install upgrades and patches every day and their packages seems to require manual intervention due to the configuration file more often than other packages. Since we use Puppet, it's trivial for us to deal with it, but sometimes we do have to look at the configuration file to figure out whether something really changed or not. To be fair, this hasn't happened in a while, so maybe they improved it already.

I've used it for five years over multiple projects in multiple companies.

No issues encountered.

No issues encountered.

No issues encountered.

I don't think I ever needed it, no.

I don't think I ever needed it, no.

I don't think New Relic has a lot of competition. We also use Linode to monitor our servers (but not our app).

I think this is one of the aspects in which New Relic shines. They designed the product to be easy to install and integrate, it's part of their guiding philosophy and probably what made me try it in the first place.

I implemented it myself.

We are happy with the free version, so I never properly evaluated this.

New Relic is not cheap, but I have a few colleagues that need the paid accounts, and although it hurts, generally not having New Relic hurts more.

Not really.

Just go ahead and try it.

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.

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.

I find the error monitoring of IIS web applications to be extremely useful. Being able to filter errors by URL, server, and period of time has been extremely helpful in quickly isolating and fixing problems. Being able to see a list of slow transactions is also very helpful in identifying the root cause of application performance problems.

In one case, a developer had an end-user report a recurring issue with a web application after a new release. I was able to use New Relic to find the error and provide the developer with the exact line of code that was causing the error within minutes of the issues being reported.

I can't say as I haven't used all of the features.

I've used it for one year.

No issues encountered.

No issues encountered.

No issues encountered.

I haven't had to contact customer service.

I haven't had to contact technical support.

We didn't have a solution in place prior to deploying New Relic.

It was straightforward.

We didn't install it through a vendor.

• APM
• Synthetics
• Blazemeter integration

This tool has really helped us in monitoring our production apps and also to diagnose the errors coming in using APM and synthetics modules.

I have logged a bug in their Ping Monitor within Synthetics and I need more improvement in this area.

I've used it for two years.

No issues encountered.

No issues encountered.

No issues encountered.

9/10.

9/10.

No previous solution used,

It was quite simple.

We implemented it in-house.

We are getting a very good ROI as out production quality has gone up with more issues getting detected on local environments.

• Gomez by Compuware
• AppDynamics

It is very simple to implement and it adds great value.