Docs » Scenarios for troubleshooting errors and monitoring application performance using Splunk APM » Scenario: Kai troubleshoots an edge case by searching for a specific trace

Scenario: Kai troubleshoots an edge case by searching for a specific trace 🔗

Kai, the site reliability engineer at Buttercup Games, receives a ticket from a customer who reports they are getting an “Invalid request” error when redeeming a coupon on the Buttercup Games website.

To troubleshoot this issue, Kai takes the following steps:

  1. Kai reviews the services on the APM overview dashboard

  2. Kai goes to the trace view and finds the trace where the customer error occurred

  3. Kai reviews the trace and the span performance in waterfall view

  4. Kai uses data links to navigate to the relevant dashboard

Kai reviews the services on the APM overview dashboard 🔗

Kai looks at the Splunk APM Overview dashboard, seeing that all services have a minimal error rate.

Kai goes to the trace view and finds the trace where the customer error occurred 🔗

Kai selects Traces to enter the trace view powered by full-fidelity tracing to locate the specific trace corresponding to the ticket.

Kai selects the customer.id index tag under the Tags dropdown and enters the customer ID on the ticket. With the tag, Kai finds the exact trace where the error occurred.

Kai reviews the trace and the span performance in waterfall view 🔗

Kai selects Trace ID to examine the trace’s service, tags, and processes in the Waterfall view. Kai also checks the Span Performance to understand the performance of all spans within the trace.

Summary 🔗

Kai was able to use trace view to quickly navigate to a specific trace to troubleshoot an edge case issue reported by a customer.

Learn more 🔗

For more information about creating global data links, see Use Data Links to connect APM properties to relevant resources.

This page was last updated on May 26, 2023.