Docs » µAPM PG Example: Finding the Root Cause of a Problem

µAPM PG Example: Finding the Root Cause of a Problem 🔗

Site map for µAPM Previous Generation documentation

The following example shows one way in which µAPM can help you quickly narrow in on the cause of a problem.

Suppose you are looking at a dashboard containing an event feed chart, and you see that an alert was triggered.


Click on the event to open the alert details page. Click View more details if necessary, then click View traces from this time window.


The Traces page will open with a time range that encompasses the time when the alert was triggered with the same cluster, service, and endpoint carried forward. If the alert is for an APM error rate detector, the trace filter will default to showing only traces containing error spans for the alerted endpoint. You can similarly carry over filters from any chart you have on a dashboard by opening the Actions menu on a chart and selecting View traces from this time window.


As you navigate through the page, scroll down to the Errors/Requests chart. You can see that there are errors. Click and drag across the highlighted area to narrow down the time range even further. Depending on the starting time range, you may have to narrow down the time range more than once to get to a granular enough view.


You see there is an endpoint with at least one error.


Click the caret to expand the endpoint and view its traces.


Click the error trace to display it in the View a trace page, then click on one of the error spans.


The span details on the right provide information on problem area in your code, including information about the service, operation, component, HTTP status, and other useful data.


From here, you have a good idea where to look in your code to diagnose and fix the problem, and prevent this error from occurring again.

For more information on working with each part of the µAPM UI, see Using the µAPM PG User Interface. To get started implementing µAPM, see µAPM PG Getting Started.