Correlating different types of data of a distributed ledger system

Patent metadata

Field	Value
Publication number	US-11269859-B1
Application number	US-201916419835-A
Country	US
Kind code	B1
Filing date	May 22, 2019
Priority date	May 22, 2019
Publication date	Mar 8, 2022
Grant date	Mar 8, 2022

Abstract

Systems and methods are described to correlate different types of data obtained from a distributed ledger system. The distributed ledger system can generate transaction notifications, log data, and/or metrics data. At least some of the data generated by the distributed ledger system can be obtained by a data intake and query system via a distributed ledger system monitor. The data from the distributed ledger system can be stored in the data intake and query system and correlated. Based on the correlation, the data intake and query system can determine a history of a transaction in the distributed ledger system, relationships between components of the distributed ledger system, and/or an architecture of the distributed ledger system.

First claim

What is claimed:

1. A computer-implemented method, comprising:
receiving a query at a computing device of a data intake and query system, the query identifying a set of data associated with a distributed ledger system;
identifying as at least a portion of the set of data, a first set of events corresponding to transaction notification events generated by one or more nodes of the distributed ledger system and a second set of events corresponding to log data generated by a plurality of nodes of the distributed ledger system;
identifying, in the first set of events, a particular transaction notification event generated by a particular node of the plurality of nodes;
correlating the particular transaction notification event with the log data, wherein a result of the correlating traces a history of a transaction processed by the plurality of nodes of the distributed ledger system; and
outputting the result as a response to the query.

2. The method of claim 1 , wherein the correlating the particular transaction notification event with the log data is based on a transaction identifier associated with the particular transaction notification event.

3. The method of claim 1 , further comprising:
extracting a transaction identifier from of the particular transaction notification event using a regular expression rule.

4. The method of claim 1 , further comprising:
reading a transaction identifier from an inverted index, wherein the transaction identifier is associated with the particular transaction notification event.

5. The method of claim 1 , wherein the particular transaction notification event is associated with a node of the distributed ledger system and a portion of the log data is associated with the node of the distributed ledger system.

6. The method of claim 1 , further comprising identifying a node type of a node associated with the particular transaction notification event.

7. The method of claim 1 , wherein correlating the particular transaction notification event with the log data is based on a transaction identifier associated with the particular transaction notification event and a node identifier associated with a portion of the log data.

8. The method of claim 1 , wherein the particular transaction notification event is associated with a first node of the distributed ledger system and a portion of the log data is associated with a second node of the distributed ledger system.

9. The method of claim 1 , wherein the particular transaction notification event is associated with a first node of the distributed ledger system implemented as a first isolated execution environment and a portion of the log data is associated with a second node of the distributed ledger system implemented as a second isolated execution environment.

10. The method of claim 1 , further comprising correlating the particular transaction notification event with metrics data.

11. The method of claim 1 , further comprising correlating the particular transaction notification event with metrics data based on a timestamp associated with the particular transaction notification event and a timestamp associated with the metrics data.

12. The method of claim 1 , further comprising correlating the particular transaction notification event with metrics data, wherein the particular transaction notification event is associated with a node of the distributed ledger system, the log data is associated with the node, and the metrics data is associated with the node.

13. The method of claim 1 , wherein the correlating the particular transaction notification event with the log data comprises correlating an event of the first set of events with one or more events of the second set of events.

14. The method of claim 1 , wherein the transaction notification events are obtained from a publication-subscription messaging system implemented by a node of the distributed ledger system.

15. The method of claim 1 , wherein the transaction notification events are obtained from a node of the distributed ledger system using a distributed ledger system monitor.

16. The method of claim 1 , wherein the second set of events are generated based on the log data, and wherein each event of the second set of events includes at least a portion of the log data associated with a timestamp.

17. The method of claim 1 , wherein the particular transaction notification event is correlated with the log data using an inverted index.

18. The method of claim 1 , wherein the history of the transaction indicates a block of a blockchain that includes the particular transaction notification event.

19. The method of claim 1 , wherein the history of the transaction includes a plurality of processing tasks performed by a node of the distributed ledger system on the transaction.

20. The method of claim 1 , wherein the history of the transaction includes an endorsement of the transaction by the particular node of the distributed ledger system and a validation of the transaction by the particular node.

21. The method of claim 1 , further comprising generating a visualization of the result.

22. The method of claim 1 , further comprising identifying one or more relationships between components of the distributed ledger system based on the correlating.

23. A computing system of a data intake and query system, the computing system comprising:
memory; and
one or more processing devices coupled to the memory and configured to:
receive a query, the query identifying a set of data associated with a distributed ledger system;
identify as at least a portion of the set of data, a first set of events corresponding to transaction notification events generated by one or more nodes of the distributed ledger system and a second set of events corresponding to log data generated by a plurality of nodes of the distributed ledger system;
identify, in the first set of events, a particular transaction notification event generated by a particular node of the plurality of nodes;
correlate the particular transaction notification event with at least a portion of the log data, wherein a result of the correlation traces a history of a transaction processed by the plurality of nodes of the distributed ledger system; and
output the result as a response to the query.

24. The system of claim 23 , wherein the particular transaction notification event is associated with a node of the distributed ledger system and the at least a portion of the log data is associated with the node of the distributed ledger system.

25. The system of claim 23 , wherein the particular transaction notification event is associated with a first node of the distributed ledger system and the at least a portion of the log data is associated with a second node of the distributed ledger system.

26. The system of claim 23 , wherein the history of the transaction includes an endorsement of the transaction by the particular node of the distributed ledger system and a validation of the transaction by the particular node.

27. Non-transitory computer-readable media comprising computer-executable instructions that, when executed by a computing system of a data intake and query system, cause the computing system to:
receive a query, the query identifying a set of data associated with a distributed ledger system;
identify as at least a portion of the set of data, a first set of events corresponding to transaction notification

Assignees

• Splunk Inc

Inventors

• Luedtke Stephen Robert
• Mckervey Nathaniel Gerard
• Moore Ryan Russell
• Wu Jeffrey Yung

Classifications

• G06F16/27

  Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor · CPC title

• G06F16/245 Primary

  Query processing · CPC title

• G06F16/2379 Primary

  Updates performed during online database operations; commit processing · CPC title

• G06F16/248

  Presentation of query results · CPC title