# US 2023/0409350 A1 · Generating log timeline data structures based on the hierarchical data structure

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2023/0409350 A1
- Document ID: US20230409350A1
- Status: Published application
- Kind: A1
- Application number: 18/459,282
- Filed: 2023-08-31
- Published: 2023-12-21
- Earliest claimed: 2022-03-24
- Assignees: Oracle International Corporation
- Applicants: Oracle International Corporation
- Inventors: Nagarajan Muthukrishnan; Ravi Shankar Thammaiah; Sumanta Kumar Chatterjee; Binoy Sukumaran
- Web page: https://patentgrep.com/patent/US20230409350A1

## CPC

- G06F 9/44526: {Plug-ins; Add-ons}
- G06F 11/0775: {Content or structure details of the error report, e.g. specific table structure, specific error fields}
- G06F 11/323: {Visualisation of programs or trace data}
- G06F 11/327: {Alarm or error message display}
- G06F 11/3476: {Data logging (G06F11/14, G06F11/2205 take precedence)}
- G06F 2201/86: Event-based monitoring
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Plugins that are independently written are executed in a collaborative manner to analysis a log. A plugin executing with respect to a particular node of a hierarchical data structure determines values for a set of keys based on information of the particular node and/or any ancestor nodes, and information stored in a shared repository. The plugin stores the values for the keys as additional information of the particular hierarchical node and/or into the shared repository. The plugin does not access information of non-ancestor nodes when executing with respect to the particular hierarchical node. Each plugin writes into and retrieves from the shared repository using the shared naming convention, thereby sharing information. The sequence of execution of the plugins is not dependent on dependencies amongst the plugins. If a dependent plugin requiring an output from a requisite plugin is first executed, the dependent plugin is flagged as pending and subsequently re-executed.

## Claims

### Claim 1

One or more non-transitory computer-readable media storing instructions that, when executed by one or more processors, cause performance of operations comprising:
obtaining a first hierarchical data structure that represents a first log;
determining that a first timeline plugin, in a pool of timeline plugins configured to generate timelines for respective log types, is relevant to the first log;
identifying, at least by executing the first timeline plugin, first node data of the first hierarchical data structure that corresponds to a first event of a first event type associated with the first timeline plugin;
generating, based at least on the first node data, a first timeline data structure for the first event of the first event type;
storing the first timeline data structure in a timeline repository.

### Claim 2 (depends on 1)

The one or more non-transitory computer-readable media of claim 1, the operations further comprising:
determining that a second timeline plugin, in the pool of timeline plugins configured to generate timelines for respective log types, is relevant to the first log;
identifying, at least by executing the second timeline plugin, second node data of the first hierarchical data structure that corresponds to a second event of a second event type associated with the second timeline plugin;
generating, based at least on the second node data, a second timeline data structure for the second event of the second event type;
storing the second timeline data structure in the timeline repository.

### Claim 3 (depends on 1)

The one or more non-transitory computer-readable media of claim 1, the operations further comprising:
obtaining a second hierarchical data structure that represents a second log;
determining that a second timeline plugin, in the pool of timeline plugins configured to generate timelines for respective log types, is relevant to the second log;
identifying, at least by executing the second timeline plugin, second node data of the second hierarchical data structure that corresponds to a second event of a second event type associated with the second timeline plugin;
generating, based at least on the second node data, a second timeline data structure for the second event of the second event type;
storing the second timeline data structure in the timeline repository.

### Claim 4 (depends on 1)

The one or more non-transitory computer-readable media of claim 1, wherein identifying the first node data of the first hierarchical data structure that corresponds to the first event of the first event type associated with the first timeline plugin comprises:
determining, for each hierarchical node in a plurality of hierarchical nodes of the first hierarchical data structure, whether data of the hierarchical node matches one or more event attributes specified by the first timeline plugin.

### Claim 5 (depends on 1)

The one or more non-transitory computer-readable media of claim 1, the operations further comprising:
identifying a target component for which to generate a timeline report;
identifying, in the timeline repository, a plurality of timeline data structures associated with a time period of interest;
generating the timeline report based on the plurality of timeline data structures.

### Claim 6 (depends on 5)

The one or more non-transitory computer-readable media of claim 5, wherein generating the timeline report based on the plurality of timeline data structures comprises:
identifying a plurality of hierarchical nodes referenced respectively by the plurality of timeline data structures;
for each particular hierarchical node in the plurality of hierarchical nodes, if (a) node data of the particular hierarchical node, or (b) node data of any ancestor of the particular hierarchical node, is associated with the target component: using the node data to generate the timeline report.

### Claim 7 (depends on 5)

The one or more non-transitory computer-readable media of claim 5, the operations further comprising:
presenting the timeline report in a user interface.

### Claim 8

A system comprising:
one or more hardware processors;
one or more non-transitory computer-readable media; and
program instructions stored on the one or more non-transitory computer readable media which, when executed by the one or more hardware processors, cause the system to perform operations comprising:
obtaining a first hierarchical data structure that represents a first log;
determining that a first timeline plugin, in a pool of timeline plugins configured to generate timelines for respective log types, is relevant to the first log;
identifying, at least by executing the first timeline plugin, first node data of the first hierarchical data structure that corresponds to a first event of a first event type associated with the first timeline plugin;
generating, based at least on the first node data, a first timeline data structure for the first event of the first event type;
storing the first timeline data structure in a timeline repository.

### Claim 9 (depends on 8)

The system of claim 8, the operations further comprising:
determining that a second timeline plugin, in the pool of timeline plugins configured to generate timelines for respective log types, is relevant to the first log;
identifying, at least by executing the second timeline plugin, second node data of the first hierarchical data structure that corresponds to a second event of a second event type associated with the second timeline plugin;
generating, based at least on the second node data, a second timeline data structure for the second event of the second event type;
storing the second timeline data structure in the timeline repository.

### Claim 10 (depends on 8)

The system of claim 8, the operations further comprising:
obtaining a second hierarchical data structure that represents a second log;
determining that a second timeline plugin, in the pool of timeline plugins configured to generate timelines for respective log types, is relevant to the second log;
identifying, at least by executing the second timeline plugin, second node data of the second hierarchical data structure that corresponds to a second event of a second event type associated with the second timeline plugin;
generating, based at least on the second node data, a second timeline data structure for the second event of the second event type;
storing the second timeline data structure in the timeline repository.

### Claim 11 (depends on 8)

The system of claim 8, wherein identifying the first node data of the first hierarchical data structure that corresponds to the first event of the first event type associated with the first timeline plugin comprises:
determining, for each hierarchical node in a plurality of hierarchical nodes of the first hierarchical data structure, whether data of the hierarchical node matches one or more event attributes specified by the first timeline plugin.

### Claim 12 (depends on 8)

The system of claim 8, the operations further comprising:
identifying a target component for which to generate a timeline report;
identifying, in the timeline repository, a plurality of timeline data structures associated with a time period of interest;
generating the timeline report based on the plurality of timeline data structures.

### Claim 13 (depends on 12)

The system of claim 12, wherein generating the timeline report based on the plurality of timeline data structures comprises:
identifying a plurality of hierarchical nodes referenced respectively by the plurality of timeline data structures;
for each particular hierarchical node in the plurality of hierarchical nodes, if (a) node data of the particular hierarchical node, or (b) node data of any ancestor of the particular hierarchical node, is associated with the target component: using the node data to generate the timeline report.

### Claim 14 (depends on 12)

The system of claim 12, the operations further comprising:
presenting the timeline report in a user interface.

### Claim 15

A method comprising:
obtaining a first hierarchical data structure that represents a first log;
determining that a first timeline plugin, in a pool of timeline plugins configured to generate timelines for respective log types, is relevant to the first log;
identifying, at least by executing the first timeline plugin, first node data of the first hierarchical data structure that corresponds to a first event of a first event type associated with the first timeline plugin;
generating, based at least on the first node data, a first timeline data structure for the first event of the first event type;
storing the first timeline data structure in a timeline repository;
wherein the method is performed by at least one device including a hardware processor.

### Claim 16 (depends on 15)

The method of claim 15, further comprising:
determining that a second timeline plugin, in the pool of timeline plugins configured to generate timelines for respective log types, is relevant to the first log;
identifying, at least by executing the second timeline plugin, second node data of the first hierarchical data structure that corresponds to a second event of a second event type associated with the second timeline plugin;
generating, based at least on the second node data, a second timeline data structure for the second event of the second event type;
storing the second timeline data structure in the timeline repository.

### Claim 17 (depends on 15)

The method of claim 15, further comprising:
obtaining a second hierarchical data structure that represents a second log;
determining that a second timeline plugin, in the pool of timeline plugins configured to generate timelines for respective log types, is relevant to the second log;
identifying, at least by executing the second timeline plugin, second node data of the second hierarchical data structure that corresponds to a second event of a second event type associated with the second timeline plugin;
generating, based at least on the second node data, a second timeline data structure for the second event of the second event type;
storing the second timeline data structure in the timeline repository.

### Claim 18 (depends on 15)

The method of claim 15, wherein identifying the first node data of the first hierarchical data structure that corresponds to the first event of the first event type associated with the first timeline plugin comprises:
determining, for each hierarchical node in a plurality of hierarchical nodes of the first hierarchical data structure, whether data of the hierarchical node matches one or more event attributes specified by the first timeline plugin.

### Claim 19 (depends on 15)

The method of claim 15, the operations further comprising:
identifying a target component for which to generate a timeline report;
identifying, in the timeline repository, a plurality of timeline data structures associated with a time period of interest;
generating the timeline report based on the plurality of timeline data structures, at least by:
identifying a plurality of hierarchical nodes referenced respectively by the plurality of timeline data structures;
for each particular hierarchical node in the plurality of hierarchical nodes, if (a) node data of the particular hierarchical node, or (b) node data of any ancestor of the particular hierarchical node, is associated with the target component: using the node data to generate the timeline report.

### Claim 20 (depends on 19)

The method of claim 19, further comprising:
presenting the timeline report in a user interface.
