New Relic

New Relic helped us identify RDS lock wait timeouts for a clients high load e-commerce store. With the help of New Relic Application Performance Monitoring we were able to pin point the root cause and made changes to the table configurations of DB which helped us solve the degraded site performance.

We use New Relic for backend, frontend and synthetics observability. We need to know when our website for the users is performing.

After GA4 retired the page speed reports, we installed New Relic on our site to make sure we didn't lose visibility into page load times. We quickly realized that it has a lot more capabilities than we were using or would ever use. It's a very powerful tool, but more for technical users.

Our scope of new relic was to identify the bottleneck services which we were using to find out why some of our APIs were taking longer time. After integrating with new relic, we identified few anomalies, which we were unaware of like un-instrumented time and uneven distribution of response time of internal service APIs. We integrated new-relic in our downstream services as well with same new relic account, it gives the picture of how APIs are flowing from 1 service to another.

We use New Relic's APM product primarily for visibility of our PHP Web applications.
It is our eyes to detect errors, performance losses, anomalies, distributed transactions, database performance, external services.
We also use Synthetic Monitoring, Infrastructure, Logs and all proactive alerts and event correlators.
We have been using New Relic for 7 years

I primarily use New Relic's APM product to find the cause of slow-running PHP apps. The transaction tracer allows me to drill down to individual function calls to find bottlenecks, fix them and then verify the results using deployment tracking. The database query and external services logging also helps me keep track of any performance drains.

We use New Relic for monitoring back-end / front-end performance and synthetic monitoring. It gives us insight using custom dashboards, connections to other services and gives teams opportunity to focus on their part as well as giving them insight on the whole. Also it gives us the alerting to pro-actively act on possible issues before they become problematic.

New Relic is primarily a DevOps tool that helps us identify issues in our web app. We use it optimize our hosting environment and code. It saves us lots of time by pinpointing where the bottlenecks are in our website performance.

NR is used as a monitoring and optimisation tool at our organisation. It integrates with several of our key other services such as AWS and helps development and support teams keep on top of their applications through the monitoring options and alerting / notification features. Lots of great visualisation options and customisation abilities to make it fit exactly what you do at your company. It helps us reduce MTTR and often catch issues before they become incidents which is very valuable for a company like ours when any amount of downtime can have a big knock on effect to our customers.

New Relic is used as a full-stack monitoring tool. It is used by various application teams within our organization for monitoring their application, server infrastructure, end-user, and synthetics. We have also started to leverage it for monitoring other cloud entities like lambda, RDS, etc along with Kubernetes clusters. It helps with monitoring and alerting mechanics and helps various notification methods.

Observability and monitoring of our customer facing systems

We use New Relic across the whole organization to gather data from our hosts: - Alert in case of performance degradation - Understand the call stack and find where performance issues come from - Link services between them

we are using many new relic sub products for our many use cases we are using it as APM tools, infrastructure monitoring tool in order to monitor our large number of server fleet, Database monitoring, Kubernetes Cluster monitoring, track bugs and issues in application code, alerts and warnings for uptime of our application or to get the overall idea on how our product is performing under certain circumstances and for better scaling and resources optimisations.

New Relic is tightly integrated into our SDLC process and giving us feedback in not only how our application is performing, but how it is being used by our customers. Starting with onboarding our engineers can see how our application functions through our API calls, what services are used and how a request spans multiple services (both internally and externally). We can then use it in the application development phase in our lower level environments. Allowing engineers and QA easily identify errors or performance issues before it ever reaches our Production environment. Then finally in the Production environment, New Relic gives you an X-Ray machine into your application performance and monitoring. Understanding your transactions, where a bottleneck might lay within a specific API call because of a database call, or external call. The tool is used in every cycle of our SDLC for every engineer in our company. It is then heavily used by our SRE team for alerting and monitoring too.

The Tech department uses new relics in general, and much more on customer-facing systems, since their load changes drastically.

We use New Relic for a wide range of monitoring and observability needs. We don't just gather system metrics, but also performance metrics and customer experience data from many different applications. Our ability to reference data collected from any number of systems has proven to be an invaluable troubleshooting tool. It also helps us with plotting growth, and planning for future capacity.

We use New Relic to get stats on page hits and performance metrics of our website, hosted on Acquia. We use it to monitor slow SQL queries and also page load times and get statistics on browser types as well as what device is accessing our site's pages. It is also the default performance monitoring tool for Acquia sites.

It's being used by the developers working on the application. New Relic helps the team to find bottlenecks and performance problems introduced with the changes. It also helps to break the request flow into several steps so we can understand how the application works under the hood and how we have to tackle problems.

It is used across the whole organization. We use APM to monitor customers' applications, Infrastructure to review the infrastructure behaviors, Synthetics to check the availability of the customer's sites, and logs to review in a friendly way all those logs that are recorded from the app/infra. New Relic has become something basic in my day-to-day.

New Relic is being used by the University of South Australia (UniSA) Information Technology Unit to provide detailed insight into the end-user performance, availability, and error rate of the University's applications. The Unit supports critical systems that serve over 32,000 students.

We have used a couple of different tiers of New Relic. Our Dev Ops manager first used it to track all bugs, issues, and uptime, giving us alerts and warnings to help us proactively manage our applications. Now we use it more as a traffic monitoring tool, helping us know how our server is performing against traffic and demand.

Our solution hosts thousands of PHP applications in AWS cloud across multiple regions. We installed the PHP NewRelic agent and we set up each application to use a different newrelic_set_appname among with several newrelic_add_custom_parameter, like the database identifier where the site is in, the Autoscaling group where the site is running on, etc., that way we could identify which clients had the most traffic in a specific database server or Autoscaling group. To do that, we used Dashboards with queries to retrieve that data. NewRelic APM helped us a lot to identify why a site was slow when loading in the browser or when processing a specific php script. With Transactions and Databases features, we could even identify which specific php function of the code was stuck or which specific database query was taking too long. With External Services, we could detect when there was a delay connecting, for example, to Microsoft auth, Google auth, or even to another AWS service. In general, for us, it was a great tool to troubleshoot application slowness issues.

• Infrastructure Monitoring and Alerting
• Application Performance Monitoring and Alerting
• Tracking business and product related KPI's and metrics.
• Dashboards for NOC and the customer facing teams.

New Relic is the de-facto KPI tracking and dash-boarding tool for us. Apart from the APM - which is the USP of New Relic - even the technical and product KPIs are plotted on New Relic. It is used the tool for handshake and exchange of data between the various groups within the organisation.

New Relic is being used in our Organization for monitoring everything literally. All our devices & instances, whether they are present in AWS, GCP, or On-premises, are being monitored in New relic. New Relic has helped in making sure that all aspects of an instance are being monitored, and whenever something goes wrong, New Relic sends out an alert over email or any chosen platform.

We have used New Relic for application performance monitoring. Our product being B2C, we need to monitor the performance 24 * 7 for the best experience for our customers. At the same time, when a customer faces any issue, our Technology team requires all the necessary details to assess, debug and identify the root cause. New Relic has assisted in both the ways to proactively monitor and provide finer details to assist during an issue as well.