US 12,443,966 B2
Distributed tracing techniques for acquiring business insights
Premkumar Manivannan, Phoenix, AZ (US); Patrick Vondette, Detroit, MI (US); Timothy Edwards, Charlotte, NC (US); and Spencer Cremers, Detroit, MI (US)
Assigned to Ally Financial Inc., Detroit, MI (US)
Filed by Ally Financial Inc., Detroit, MI (US)
Filed on Jun. 9, 2021, as Appl. No. 17/342,735.
Prior Publication US 2022/0398603 A1, Dec. 15, 2022
Int. Cl. G06Q 30/0201 (2023.01); G06F 16/23 (2019.01); G06F 16/28 (2019.01); G06Q 10/0639 (2023.01); G06Q 30/016 (2023.01); G06Q 40/02 (2023.01)
CPC G06Q 30/0201 (2013.01) [G06F 16/2379 (2019.01); G06F 16/284 (2019.01); G06Q 10/06393 (2013.01); G06Q 30/016 (2013.01); G06Q 40/02 (2013.01)] 18 Claims
OG exemplary drawing
 
1. A method, comprising:
generating, for a user journey initiated by a source device via an application, trace data for one or more spans corresponding to respective portions of the user journey, wherein each span of the one or more spans is associated with a respective service of a plurality of services of the application;
collecting diagnostic information and user-specific transaction information associated with the user journey based at least in part on the trace data, wherein the diagnostic information and the user-specific transaction information is collected for each service of the plurality of services, wherein the user-specific transaction information comprises an account balance;
generating trace context information for the one or more spans, the trace context information associated with the diagnostic information and the user-specific transaction information;
propagating the trace context information across the plurality of services based at least in part on one or more trace headers, wherein the trace context information is propagated in accordance with a B3 propagation scheme;
storing the diagnostic information and the user-specific transaction information based at least in part on generating the trace data for the user journey, wherein one or more logs associated with the user-specific transaction information are stored in a first database and one or more tags associated with the one or more logs are stored in a second database, and wherein the second database is indexed according to a hash index associated with the user-specific transaction information; and
retrieving, as part of a troubleshooting operation, the diagnostic information using the hash index and retrieving the user-specific transaction information using the hash index in response to determining that the account balance exceeds a minimum account balance threshold, wherein retrieving the diagnostic information and the user-specific transaction information and collecting the diagnostic information and the user-specific transaction information occurs in approximate real time.