Accelerate troubleshooting using Business Workflows on Tag Spotlight 🔗
Deepu, the payment service owner at Buttercup Games, wants to understand how errors in the payment service impact business KPIs. Deepu clicks the paymentservice node on the service map, and then selects Tag Spotlight to look at errors and latency for the Workflow tag.
Deepu notices that the requests of the frontend:/cart/checkout workflow return a majority of root cause errors. Because APM supports infinite cardinality, Deepu selects the frontend:/cart/checkout workflow and applies filters to show only data from traces. Deepu filters version to
v350.10 and Kind to
SERVER to view the tags to examine the subset of traces where the most errors occur:
Because Splunk APM stores all traces without sampling, Deepu clicks the peak of errors on the chart to see example traces of those tag combinations at that timestamp. Deepu finds that the requests from checkoutservice to paymentservice are failing.
Deepu remembers that version 350.10 of the payment service recently deployed a backwards incompatible change to its API. Because Deepu enabled Related Content in Splunk APM, Deepu can click Logs for payment service to switch to Splunk Log Observer to investigate whether the deployment causes the error.
For details about business workflows, see Correlate traces to track Business Workflows.
For details about using Related Content, see Enable Related Content in Splunk Observability Cloud.
For more information about using Splunk Log Observer to detect the source of problems, see Introduction to Splunk Log Observer.