Log Handling Utility for Distributed Error Diagnosis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Managing and diagnosing errors in complex application log files is challenging due to the vast number of messages, with critical errors often buried among thousands of informational messages, making it difficult for users to identify and resolve issues efficiently.
Innovation Solution
A log handling utility that includes a log discovery module, extractor, parser, and dashboard user interface to collect, analyze, and filter log files, providing users with a graphical interface to search, filter, and resolve error messages, and offering a centralized location for error handling with auto-search options and customizable filtering.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If log files are generated by multiple components and processes across distributed machines, then the application can operate complex distributed systems, but the number of log files and messages increases dramatically making error diagnosis difficult
Solution Approach 1:
The patent merges multiple log files from different components and processes into a single consolidated log file. The system collects log entries from numerous distributed sources and combines them into one unified log, making error diagnosis manageable despite the distributed nature of the system.
Solution Approach 2:
The patent introduces an intermediary system that acts as a mediator between the distributed log sources and the user. This intermediary consolidates, filters, and presents log information in a manageable format, shielding users from the complexity of multiple distributed log files.
2Reliability
If all log messages are recorded including informational messages, then complete operational records are maintained, but critical error messages are buried among thousands of informational messages making them hard to discover
Solution Approach 1:
The patent extracts critical error messages from the bulk of informational messages. The system identifies and separates error-type log entries from informational entries, presenting errors prominently while maintaining the complete operational record in the background.
Solution Approach 2:
The patent applies different presentation qualities to different types of log messages. Critical errors are highlighted with special formatting, colors, or positioning, while informational messages are presented in a standard, less prominent format, allowing users to quickly identify important issues.
3Device complexity
If users manually inspect log files to diagnose problems, then no additional system complexity is introduced, but the time and effort required to identify and resolve errors increases significantly
Solution Approach 1:
The patent performs preliminary actions by automatically analyzing and organizing log messages before the user needs to diagnose problems. The system pre-processes log files, identifies errors, and prepares diagnostic information in advance, significantly reducing the time users need to spend on error diagnosis.
Solution Approach 2:
The patent implements self-service by enabling the system to automatically perform error detection and diagnosis functions. The log analysis system autonomously identifies errors, correlates them with system states, and presents diagnostic information without requiring manual log inspection, freeing users from time-consuming manual analysis.
Data Source
AI summary
An error guide including a set of error resolutions is stored. A set of log files is received which includes log entries generated by a set of processes associated with an application program. Each log entry includes a set of attributes including a first attribute specifying a message, a second attribute specifying a message identifier, a third attribute specifying process, and a fourth attribute specifying a message type. The log files are parsed based on the third and fourth attributes to identify a log entry associated with a particular process and message type. A message identifier of the log entry is compared with the error message guide to identify an error resolution that corresponds to a message of the log entry. The identified error resolution is displayed on an electronic screen.