Determining an event history for an event processed by a plurality of communicating servers via a central event data log

Patent metadata

Field	Value
Publication number	US-10148533-B1
Application number	US-201414558609-A
Country	US
Kind code	B1
Filing date	Dec 2, 2014
Priority date	Dec 2, 2014
Publication date	Dec 4, 2018
Grant date	Dec 4, 2018

Abstract

An originating server of a payment processing system comprising multiple communicating servers first processes a transaction event, generates a correlating identifier and transmits the correlating identifier and processing information to a central data log accessible by the multiple communicating servers. One or more intermediate servers and a terminating server then process the transaction event, each successive intermediate server and the terminating server receiving the transaction event and a correlation identifier associated with the transaction event generated by the previous server which processed the transaction event. Each successive intermediate server and the terminating server generates a correlation identifier, and transmits both the received and generated correlation identifiers to the central transaction log. A query comprising a correlation identifier associated with the transaction event is received. The payment processing system extracts successive sets of entries from the central data log by matching corresponding correlation identifiers and generates a transaction event history.

First claim

What is claimed is:

1. A computer-implemented method to determine status information for events processed by multiple processors, comprising:
receiving, by a computing device and from a first processor in response to processing an event by the first processor, first data associated with the event, the first data comprising a first correlation identifier associated with the event and the first processor;
storing, by the computing device, the first data associated with the event as a first entry in a central data log of a tracing repository;
receiving, by the computing device and from a second processor, in response to processing the event by the second processor at a first time after processing the event by the first processor, second data associated with the event, the second data comprising a second correlation identifier associated with the event and the second processor and further comprising at least one primary data element in common with the first data;
storing, by the computing device, the second data associated with the event as a second entry in the central data log of the tracing repository, the stored second data being associated with the stored first data based on the at least one primary data element of the second data in common with the first data;
receiving, by the computing device and from a third processor in response to processing the event by the third processor at a second time after processing the event by the first processor and after processing the event by the second processor, third data associated with the event, the third data comprising a third correlation identifier associated with the event and the third processor and further comprising at least one secondary data element in common with the second data without having any data elements in common with the first data;
storing, by the computing device, the third data associated with the event as a third entry in the central data log of the tracing repository, the stored third data being associated with the stored second data based on the at least one secondary data element of the third data in common with the second data, and the stored third data being thereby associated with the stored first data based on the association of the second data with the first data and based on the association of the third data with the second data;
receiving, by the computing device, a query;
based on the query, generating, by the computing device, an event status comprising the first entry, the second entry, and the third entry from the central data log; and
outputting, by the computing device, the generated event status.

2. The method of claim 1 , wherein the query comprises the first correlation identifier and further comprising:
identifying, by the computing device and from the central data log, the first entry and the second entry of the central data log based on the first correlation identifier, the first data associated with the event, and the second data associated with the event; and
identifying, by the computing device and from the central data log, the third entry based on the second data associated with the event and the third data associated with the event.

3. The method of claim 1 , wherein the query comprises the second correlation identifier and further comprising:
identifying, by the computing device and from the central data log, the second entry and the third entry of the central data log based on the second correlation identifier, the second data associated with the event, and the third data associated with the event; and
identifying, by the computing device and from the central data log, the first entry based on the first data associated with the event and the second data associated with the event.

4. The method of claim 1 , wherein the query comprises the third correlation identifier and further comprising:
identifying, by the computing device and from the central data log, the third entry of the central data log based on the third correlation identifier, the second data associated with the event, and the third data associated with the event;
identifying, by the computing device and from the central data log, the second entry based on the second data associated with the event and the third data associated with the event; and
identifying, by the computing device and from the central data log, the first entry based on the first data associated with the event and the second data associated with the event.

5. The method of claim 1 , wherein one or more of the first processor, the second processor, and the third processor are associated with a payment processing system.

6. The method of claim 1 , wherein a single computing device comprises the first processor and at least one of the second processor and the third processor.

7. The method of claim 1 , wherein the first processor and at least one of the second processor and the third processor execute in distinct computing devices.

8. A computer-implemented method to determine status information for events processed by multiple processors, comprising:
receiving, by one or more computing devices associated with a tracing repository, a query for an event comprising a first correlation identifier;
extracting, by the one or more computing devices and from a central event log stored in the tracing repository, one or more first entries comprising the first correlation identifier, the first correlation identifier having been generated by a first processor for the event in response to the first processor processing the event;
identifying, by the one or more computing devices and from the one or more extracted first entries, one or more second correlation identifiers, the one or more second correlation identifiers having been generated by one or more second processors for the event in response to the one or more second processors processing the event at one or more corresponding times after the first processor processed the event;
extracting, by the one or more computing devices and from the central event log stored in the tracing repository, one or more second entries comprising the one or more second correlation identifiers;
generating, by the one or more computing devices, an event status comprising extracted event status entries comprising the extracted one or more first entries and the extracted one or more second entries, wherein the extracted event status entries each comprise timestamps and processing details, and wherein the extracted event status entries are organized according to timestamp; and
outputting, by the one or more computing devices, the generated event status.

9. The method of claim 8 , wherein a single computing device comprises the first processor and at least one of the one or more second processors.

10. The method of claim 8 , wherein the first processor and at least one of the one or more second processors execute in distinct computing devices.

11. The method of claim 8 , further comprising:
at a time before generating the event status, identifying, by the one or more computing devices and from the one or more second extracted entries comprising the one or more second correlation identifiers, one or more third correlation identifiers, the one or more third correlation identifiers having been generated by one or more third processors for the event in response to the one or more third processors processing the event at one or more corresponding times after the one or more second processors processed the event and at a time after the first processor processed the event; and
extracting, by the one or more computing devices and from the central event log stored in the tracing repository, one or more third entries comprising the one or more third

Assignees

• Google Inc
• Google Llc

Inventors

• Hull David Morris
• Linck Michael

Classifications

• G06F11/3476

  Data logging (G06F11/14, G06F11/2205 take precedence) · CPC title

• G06F2201/87

  Monitoring of transactions · CPC title

• G06F11/3068

  where the reporting involves data format conversion · CPC title

• G06F11/3006

  where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems (multiprogramming arrangements G06F9/46; allocation of resources G06F9/50) · CPC title

• H04L43/0864

  Round trip delays · CPC title