New Relic Reviews

We are currently not using the thresholds and alerts. New Relic serves as a reactive platform. From time to time, we take a look at the metrics we have and think about how to improve.

Yes, by monitoring baselines after weekly releases, it was beneficial to see long-running queries or processes within 24-48 hours of deploy.

Our assessment shows that our DevOps organization can now deliver with maximum functionality and innovation. It is clear that we have less complexity to manage, the communication and collaboration have been improved, but also faster delivery of features has been achieved. Everybody seems to be super happy with more stable operating environments and significantly less downtime.

Since the whole company has standardized on New Relic, it's one of the first things we set up when deploying a new app. And since it's standard, as a developer it's simple to look at an existing setup as a starting place, which decreases the demand for the DevOps department's time.

Yes. New Relic helps us to quickly identify bottlenecks in applications and environments and provide logs and events that cross set thresholds.

Surely yes. I can't imagine our application without New Relic now. The time for debugging has been reduced. The features like monitor performance, visualization and dashboards tell us the errors and sort it out as soon as possible. So it surely helped us to develop our application faster and in an very efficient way.

New Relic has improved our stability by giving us detailed diagnostics of our server issues. Most notably is our database performance, which has allowed us to better construct queries and reduce the amount of data that needs to be returned. Our dashboards alert us to problem queries ane we can refine accordingly.

Our DevOps processes are greatly improved through the use of NewRelic. Through monitoring and alerting on performance issues and creating dashboards, we can catch issues before they become major problems, and we can be on top of any problems the developers are experiencing, able to hone in on where an issue is coming from much more quickly.

We have benefited from the dashboards quite a bit, if there is a production issue, it can be the default view for our DevOps team. The dashboard usually gives good insight as to what part of the stack is having issues (whether it may be poorly performing database queries or increased application errors..)

To some respect they have but the in some cases, we are not as we have PHI/PII data that cannot be processed on SaaS products. That said, those teams that were able to, used the data that New Relic was able to provide to allow them to prove certain aspects of the apps we are building and use that data as the foundational backbone for all app development going forward.

Dev Ops loved this tool at 3Form, because they were alerted when they were about to have issues.
They also used New Relic to know when they needed to add resources or beef up our servers for higher demand.

New Relic's APM helps to save time when there is some problem with applications, as you may quickly see where the problem comes from. Also, improving the performance of applications became much easier, as you can see the parts of applications that work slow, therefore, should be prioritized.

We followed an app-team/self-service model when we deployed. This is a strength for small teams/enterprises in the New Relic platform, but without the ability to do role-based access control (RBAC), managing access to data meant a lot of trial and error.

In the end, we have hundreds of sub-accounts aligned with our application support teams. Middleware teams hate it. Application teams love it. You can't make everyone happy all of the time!

Alerts and error monitoring have been extremely valuable to our dev-ops engineers and our product engineers. Alerting the appropriate people when there are problems is critical responding rapidly to incidents. Dashboards for monitoring the latency of key transactions are important for prioritizing work and understanding how to scale our infrastructure.

Our DevOps team has been able to get ahead of the curve on many server issues that in the past may have resulted in full outages. By monitoring resources on each instance and being notified when a system passes a certain threshold, it greatly increases the uptime of the system.

We use Docker, that helps our DevOps team minimize the complexity of our Drupal and Magento stacks. New Relic helps us monitoring containers and improving the overall performance of our virtual machines. One of the biggest advantages is that all members of our different teams have full visibility when an incident happens. Thanks to New Relic, we can quickly detect where the problem is. We are also using PagerDuty to manage alerts. Both products are integrated so we can create incidents based on the severity of the event.

Live/streaming data is the new standard and is necessary to keep up with the modern system. I can’t wait until other systems (like BI platforms) catchup. The proactive monitoring helps my team be responsive and the first to know, not the last.

We have devops process and build deployment and performance testing automation. Every time a build is deployed, an automation test runs. With New Relic, we get the required alerts if there are any issues and we monitor the application via a dashboard. This has helped us to ensure that production deployment is smooth.

Absolutely. New Relic has empowered my DevOps team to quickly observe health of all infrastructure.

New Relic is used by our DevOps teams as well as SRE teams for application monitoring, performance analysis and alerting. It is a key part of monitoring and alerting of our applications running on cloud and we use it for continuous monitoring and debugging.
Its reports and data are used in various dashboards for performance analysis and reporting SLAs to customers.

There are different layers of monitoring and data collection and the tool seamlessly integrates with other tools used to build, deploy, and support software, including common logging, configuration management, and incident response tools.

NR wasn't quite helpful to us in the DevOps sector. It could be because of our lack of knowledge of New Relic, but we had a hard time automating the install of NR to all our AWS instances that were created using auto-scaling groups. Then there is the matter of your instance type. Our Java application was already using the memory to its capacity of the micro instance, and there was no room for NR to run, so we had to upgrade to a small instance.