Docs » Example: Finding the Root Cause of a Problem

Example: Finding the Root Cause of a Problem

The following example shows one way in which SignalFx µ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.

../../_images/event-feed.png

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

../../_images/clicked-event.png

The Traces page will open with a time range that encompasses the time when the alert was triggered. You can similarly carry over the time context from any chart you have on a dashboard by opening the chart’s menu and selecting View traces from this time window.

../../_images/traces-time-range.png

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.

../../_images/narrow-time-range.png

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

../../_images/trace-error.png

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

../../_images/trace-error-expanded.png

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

../../_images/click-span.png

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.

../../_images/span-details.png

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 SignalFx µAPM UI, see Using the µAPM User Interface. To get started implementing µAPM, see µAPM Quick Start Guide.