US 11,789,804 B1
Identifying the root cause of failure observed in connection to a workflow
Gergely Danyi, Cupertino, CA (US); Sakshi Garg, San Francisco, CA (US); Maxime Petazzoni, San Mateo, CA (US); Sahinaz Safari Sanjani, San Mateo, CA (US); Timothy Matthew Robin Williamson, Santa Barbara, CA (US); and Eric Wohlstadter, Atherton, CA (US)
Assigned to SPLUNK Inc., San Francisco, CA (US)
Filed by Splunk Inc., San Francisco, CA (US)
Filed on Jan. 31, 2022, as Appl. No. 17/589,556.
Claims priority of provisional application 63/257,056, filed on Oct. 18, 2021.
Int. Cl. G06F 11/00 (2006.01); G06F 11/07 (2006.01)
CPC G06F 11/079 (2013.01) [G06F 11/0751 (2013.01); G06F 11/0778 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A method of identifying a root cause of a failure for a trace within a microservices-based application, the method comprising:
determining if a root span of the trace is an error span resulting in an error experienced by a user at a front end of the microservices-based application;
responsive to a determination that the root span of the trace is the error span, analyzing a plurality of spans comprising the trace to determine if the trace comprises at least one leaf error span that is a last error span of a chain of unbroken error spans starting at the root span;
responsive to a determination that the trace comprises the at least one leaf error span, attributing the root cause of the failure in the trace to a service associated with the at least one leaf error span; and
responsive to a determination that the trace comprises multiple leaf error spans, attributing the root cause of the failure in the trace to a service associated with a leaf error span of the multiple leaf error spans that comprises a latest starting timestamp.