In 3 minutes we’re gonna show you how to stay on top of your overall application health.
The application performance monitoring (APM) summary tiles provide a comprehensive picture of the service’s most important health indicators all in one place so you can identify emerging issues and troubleshoot faster.
Troubleshoot faster with an at-a-glance view of critical health indicators for your service
Troubleshoot with the summary page
Our APM tools can help you resolve incidents when you have limited time. With the APM summary page, you can see an overview potential failures in your apps and get important metrics about each of your services. It’s the first place you’ll go to check the health of your service, understand any problems within a larger context, and take the necessary steps to resolve the issue.
This doc walks you through a fictional example of how to use New Relic’s APM tools to determine the root cause of service degradation. You’re going to explore a situation where you work for a fictional e-commerce company that sells shoes. You are an engineering manager for the checkout team. Customers have been complaining they have to wait too long to check out.
After a customer puts a pair of shoes in their cart and decides it’s time to check out, they will hit the Pay Now button. Checkout-service is the entity that manages the functionality of the Pay Now button.
To figure out why customers can’t click the Pay Now button, open APM and select your Checkout-service.
STEP 1 OF 3 — Review these key metrics
Is there a problem with your Checkout-service? Which systems are affected and how?
Apdex
Web transactions
Throughput
Errors
STEP 2 OF 3 Locate the problem in a larger context
Which parts of your stack are in trouble?
Was the problem caused by changes in entities that call your service, or are called by your service?
Logs
Distributed tracing
Infrastructure
