Log Data Filterability via Correlation Identifiers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current endpoint management systems face difficulties in correlating and filtering log data effectively, making troubleshooting time-consuming due to the lack of association between user-specific and event-specific logs.

Innovation Solution

A method and system that generate and filter log data by identifying pairs with user or event log chain identifiers, updating the database with corresponding user information or action types, and displaying filtered data to facilitate easier error identification and resolution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If log data is stored without correlation identifiers, then storage simplicity is maintained, but troubleshooting time increases significantly

Engineering Contradiction:
Improvetroubleshooting timeVSAvoidlog data structure complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by embedding correlation identifiers (user IDs, event log chain IDs) into log data at the time of log generation and storage, rather than adding them during troubleshooting. This preliminary enrichment of log data with identifying information enables fast filtering and correlation during issue resolution, significantly reducing troubleshooting time without requiring complex post-processing operations.

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If log data includes detailed user information and action types, then filterability improves, but data storage requirements increase

Engineering Contradiction:
Improvelog data filterabilityVSAvoiddata storage volume
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

The patent extracts and stores only the essential filtering attributes (user ID, event log chain ID, action type) from the complete log data structure. By selectively extracting only the most critical identifying fields needed for filtering and correlation, the system achieves high filterability while minimizing the additional storage overhead that would result from storing all possible log attributes.

Inventive Principle:
Principle #2Taking out (Extraction)

3Measurement precision

If error logs are correlated with user and event information, then issue identification accuracy improves, but processing complexity increases

Engineering Contradiction:
Improveerror log correlation accuracyVSAvoiddata processing complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent introduces event log chain IDs as intermediary correlation identifiers that link related log entries across different users, devices, and time periods. These chain IDs act as mediators that enable accurate error log correlation without requiring complex multi-dimensional matching algorithms. The intermediary identifiers simplify the correlation process by providing direct references between related events, thereby improving identification accuracy while keeping processing complexity manageable.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12093146B2Method and apparatus for generating log data having increased filterability
Publication Date: 2024.09.17 MALIKIE INNOVATIONS LTD
  • US12093146B2 patent drawing
  • US12093146B2 patent drawing
  • US12093146B2 patent drawing

AI summary

A method and system includes generating event logs, storing in a database log data comprising the generated event logs, identifying a first set of log data by searching the log data for a first log data type, the first log data type having a data structure that includes a generic identifier and a specific data, identifying pairs of generic identifiers and associated specific data in the first set of log data, for each generic identifier of the identified pairs identifying a second set of log data that include the generic identifier but not the specific data, wherein identifying the second set of log data is performed by searching the log data for event logs that include the generic identifier, and updating log data stored in the database by adding, for each of the event logs of the identified second set of log data, the specific data associated with the generic identifier.