Contextual Drill Back to Source Code from Log Data
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current log files are cumbersome and time-consuming to parse, requiring extensive expertise to identify error causes and solutions, as they contain numerous irrelevant messages, making it difficult for developers and support personnel to pinpoint issues in source code and access relevant resources.
Innovation Solution
Embedding developer URLs and support URLs directly in log messages, which link to specific source code locations and support resources, allowing direct access to diagnostic information and solutions, thereby streamlining the debugging process and reducing human error.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If log files record detailed events during software execution, then the audit trail and diagnostic information are improved, but the log file size and complexity increase, making parsing difficult
Solution Approach 1:
The patent segments the log file into structured records with distinct fields (timestamp, event type, message, stack trace, etc.). Each log entry is divided into manageable components that can be independently parsed and processed, reducing the overall complexity of analyzing large log files while preserving all diagnostic information.
Solution Approach 2:
The patent introduces an intermediary processing layer that automatically parses log files, extracts relevant diagnostic information, and presents it in a structured format. This intermediary tool mediates between the raw complex log data and the user, handling the complexity of parsing while delivering simplified diagnostic insights.
2Loss of information
If log files contain hundreds of messages during a single session, then the record of transactions is improved, but the time required to parse and identify errors increases
Solution Approach 1:
The patent performs preliminary actions by pre-processing log files during or immediately after generation, organizing messages into structured formats with indexed fields. Error patterns and critical information are pre-identified and tagged, so when analysis is needed, the structured organization allows rapid retrieval without manual parsing of hundreds of individual messages.
Solution Approach 2:
The patent replaces the mechanical process of manually parsing log messages with automated computational processing. Software tools automatically scan, parse, and analyze the structured log data, substituting human effort with machine processing that can handle hundreds of messages instantaneously, dramatically reducing error identification time.
3Ease of manufacture
If simple text strings are used in log messages, then the ease of generation is improved, but the sufficiency of detail for identifying error causes deteriorates
Solution Approach 1:
The patent creates a universal log message structure that serves multiple functions simultaneously. The standardized format with fields for timestamp, event type, message, stack trace, and contextual data allows a single log entry to provide comprehensive diagnostic information. This multi-functional structure maintains ease of generation through template-based messaging while ensuring sufficient detail for error cause identification.
Solution Approach 2:
The patent changes the parameters of log messages from simple text strings to structured records with multiple defined parameters or fields. Each log entry includes standardized parameters such as event type, severity level, contextual data, and stack trace information. This parameter-based approach maintains ease of generation through structured templates while providing comprehensive detail for diagnosing error causes.
Data Source
AI summary
A system receives real-time log messages from an executing process that experiences a runtime error. Information such as a filename and line number for the underlying source code may be embedded in the log messages using compiler macros. When the log messages are received, a developer URL may be generated that links a developer workstation directly to the underlying source code file and line number in a source code repository. A support URL may also be generated with a link to a support center and an embedded search string that retrieves resources that are known to address the process error.