What is your primary use case for New Relic APM?

We use New Relic for collecting the metrics on microservices and databases.

Our primary use case for the solution is notification, customization, and everything from New Relic. Before adding a monitoring tool to New Relic APM, we need to add a subscription and specify the target we want to add, and this is a blank dashboard where we have to select, step by step, which modelling we want to understand. The solution is very similar to Azure monitor.

We used New Relic APM for monitoring our data.

We do have a couple of applications for one of our customers. We are involved in performance testing and engineering of those applications. We use New Relic in multiple areas. It's used to monitor infrastructure in this use case. We capture the metrics around the utilizations on the infrastructure. We do also identify bottlenecks of the services or the calls, which are causing high response times. Those are two key areas where we have been using New Relic. We have been able to identify calls that are causing a lot of performance issues in the overall application, and then that, in turn, helps us to see what can be tuned to bring the performance to a better state.

The primary use case is for synthetic monitoring of all the APIs. It helps to detect if any APIs are failing before a customer detects an issue. The solution was deployed on cloud. There were 15 people using this solution. They worked on the configurations and setting alerts for new environments and customers. The solution was used on a daily basis. At my previous organization, they were planning to replace New Relic with Google Apigee. That was only to be done in conjunction with the cloud migration from the in-house hosted apps.

We use New Relic APM to gather performance monitoring metrics such as thread count, CPU, response time, JVMs, and DB connectivity. New Relic APM is an observability tool.

New Relic APM is an application monitoring tool.

We use this solution to provide insight into how the UI is performing.

The use case for this solution is the same as Azure Monitor. They have the same coverage for the use case. In the end, we switched to Azure Monitor. It is for the application quality process and the live system support monitoring.

We have our current parameters and our current dashboards. Our main purpose is to continue to migrate and get the same metrics in New Relic. We will prepare another secondary dashboard between the parameters. And we will do a lot of monitoring on it as it is mainly used for monitoring purposes.

We are using New Relic APM to monitor our production application and to get some insight into performance.

Basically, I'm helping a customer of mine to set up monitoring items. What I'm doing is comparing solutions in order to create a document that I can give them so that they can pick one final solution.

We are basically testing three products before going live with the new release of the software. We are also using it to monitor our production.

We use New Relic APM to monitor our public cloud-hosted application and infrastructure.

We primarily use the solution for watching user behavior, among other use cases.

We were using New Relic to build performance, application monitoring, security aspects, infrastructure, exporting from databases, lower-performance tips, and trying to identify deadlocks.

I'm working with a banking client. Apart from a uniform monitoring platform experience, they are looking for a solution that is scalable and also ready for cloud services monitoring and container-based workloads.

The primary uses case was to monitor all the front end servers, code, and query optimization for code and DB to enhance the performance, detect and remove anomalies which cause a long time to process the functions.

Our primary use case is for application performance management (APM. We use New Relic to monitor API performance on the servers. It is a safety monitor for the performance.

We use it for application and infrastructure monitoring. It covers all of our systems, including our main eCommerce system.

We use it for application performance monitoring.

* Infrastructure management * Application management

It monitors all of our services that are running. It also monitors our infrastructure. Therefore, we use it for monitoring, identifying when services go down, or when they are outside of what we would consider normal operations.

I use the product for monitoring many types of metrics, e.g., availability and comparing numbers in relation to products. I evaluate the response time of servers and the product to determine the health of the servers.

We use New Relic for monitoring and alerts.

We use this for application monitoring of our product.

The primary use case is monitoring.

We are monitoring our server database to see if there are any anomalies or problems with the servers and databases.

We use it for server monitoring and strictly for our EC2 instances.

Monitoring the health of our infrastructure.

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

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.

* Mostly monitoring * Analytics * Troubleshooting * PagerDuty

The primary use is for data application monitor, we used to add some backlogs into the application to see where the progress or the border makes in the process. So far, it is a good program.