We use New Relic APM for application monitoring, so if the application goes down, we do the root-cause analysis of why it went down. Was it the database? Was it the middle tier? We try to find out where it is and determine why the component went down.

We also use New Relic APM for its self-healing mechanism, which helps us determine the application's needs if it goes down. What data does it require? What was missing? Was the application able to send an email or a text alert?

We also have contractors responsible for the upkeep of the application. We have service-level agreements with these vendors, so we try to figure out how to incentivize or disincentivize the vendor. We try to measure their KPIs and SLAs, so New Relic APM tells us the uptime for the application for a month, a quarter, and a year.

These are our use cases for the solution.

We use New Relic APM. We use New Relic synthetic monitors to monitor around 3,600 websites that we host for clients. We also use a scripted browser to automate some of the scripting browser tests that we run. The APM is there and we use basic monitoring with all the metrics, et cetera.

The New Relic APM basically helps us understand how the application is functioning at a very in-depth level. The APM helps us bring in observability, which is the next part of monitoring. It tells us about every database query, long-running query, website response time, page load times, and everything in very good detail that normal, basic monitoring cannot provide. APM is really important to every organization out there.

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 use New Relic for collecting the metrics on microservices and databases.

Our use cases were varied. We had front-facing applications, message brokers, API gateways, legacy applications running on RPC, and platforms. We used New Relic for instrumentation, and we discovered different metrics using it.

My primary use case for this solution is to see the application's performance and alert the reiteration of any performance.

We use the solution to ensure the applications perform at the accepted performance level. The application must not have any bugs or problems. It must also have no bottlenecks in the volume of the transactions. We use the tool before we deploy an application to production and during the first part of the deployment to ensure that the application will perform properly.

Regarding use cases, we use it for app support. So basically, we use the APM module, and we also use it for monitoring.

We recently purchased the Splunk SAM module and are exploring whether it is worth integrating the ITSM module. We are deciding if we can have a proper platform or if we should go with features that New Relic offers.

I used it in another organization. I had a project where we were using New Relic for monitoring APIs and utilization of nodes or hosts. It was a standard implementation that involved getting the statistics and configuring New Relic agents on the application servers. The data was sniffed from the network based on the configuration and then it was saved. We were using the out-of-the-box capability of New Relic. We didn't do any customization on New Relic.

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 it to monitor servers. It's just a log in New Relic. I set the start and end times, and then I just pull down the server metrics.

It's not the New Relic APM, it's just the New Relic. There is the one that is New Relic, and then is New Relic APM. It's a bit confusing.

Normally when I use it, it takes me 20 minutes to pull all the data, and I use it maybe once or twice in a month.

We would run a low test, and then after the test, we would log into New Relic and then look at things, including: what are the top five slowest interactions on the servers? What are the slowest database calls? Then, we just pull the graphs from New Relic, and then we give it to the customer and show them here are the calls are being made the most, and that correlates to a slow response time. Then they'll be able to focus on it and try to maybe fix it.

The main purpose we are using New Relic is to enable application backend and frontend performance monitoring. We enable synthetic monitoring for the application team and for the business owners of the applications. Additionally, we
on-host integration for different DBs, SQL, and Oracle.

We used New Relic APM for monitoring our data.

The solution is an APM monitoring tool.

We will be monitoring all kinds of server details, including how the application is handling things and any threat count, as well as if there are any network utilization failures or problems with DNA instance ports.

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.

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

The primary use case is 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 use it for application performance monitoring.

• Mostly monitoring
• Analytics
• Troubleshooting
• PagerDuty

The primary use case of the solution is to monitor, log, and investigate incidents.

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.

We use New Relic as an infrastructure management tool. 

We are currently in the POC phase with New Relic APM and are looking at using it mainly for analytics.

We integrated the library within our backend service to see the throughput and to monitor latency. We also created a few dashboards in the New Relic dashboard section to observe the traffic and monitor how the system performs during the day.

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.

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.

We have both the mobile and web applications which use the APIs in the back end. The New Relic Browser also monitors all our review servers and has mobile and browser compatibility. Most of our stakeholders view the data on mobile and don't need to open their laptops.

Stakeholders can install New Relic on a mobile device, whether iOS or Android and monitor the enrolment. It is more compatible with the mobile device, but we can view it on the web browser, and the same features are supported for both. In addition, stakeholders can access the system 24-7 and can monitor it from anywhere, anytime.

Our company uses the solution for time series analysis. 

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

We use New Relic to generate log management, like the different kinds of logs and alarms, and automate the same easily.

If we receive errors or exceptions, or we need to check the load we use New Relic.

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

New Relic APM is an application monitoring tool.

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 use the Synthetics component to evaluate load balancing and monitor the average throughput of data on the system.

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

We primarily use the solution to optimize web pages and to track user behavior.

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.

I used New Relic Insights to create dashboards, to receive some metrics regarding performance, and alerts regarding any kind of issues with the performance. Additionally, we used it for SQL and Oracle to receive metrics related to performance, such as CPU and memory.

Depending on the type of dashboards we wait for some time and then we build alerts in New Relic Insights for the metrics to prevent issues.

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 are using New Relic APM to monitor our production application and to get some insight into performance.

Monitoring the health of our infrastructure.

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.

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.

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

We use New Relic for monitoring and alerts. 

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 use it for server monitoring and strictly for our EC2 instances.

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 it for application and infrastructure monitoring. It covers all of our systems, including our main eCommerce system.

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

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. 

We use this for application monitoring of our product.

• Infrastructure management
• Application management

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.