Automated Error Log Analysis for Root Cause Determination

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current management application suites, such as OpenManage Integration, face challenges in efficiently determining the root cause of issues in server troubleshooting logs due to the large size and complexity of Bundle Troubleshoot Logs, which are difficult and time-consuming to analyze manually.

Innovation Solution

A management suite error log analysis system that modifies the Bundle Troubleshoot Log to include a Hierarchical StackTrace, generates error-only logs, gathers software and firmware versions, and executes Perl scripts to analyze errors, determine root causes, and suggest solutions, utilizing a Knowledge Base search for efficient troubleshooting.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If manual analysis of Bundle Troubleshoot Log is performed, then comprehensive error detection is achieved, but analysis time and complexity increase significantly

Engineering Contradiction:
Improveerror detection completenessVSAvoidanalysis time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent introduces an intermediary tool (error log analysis system) that sits between the raw Bundle Troubleshoot Log and the analyst. This system automatically processes the log, extracts errors, generates hierarchical stack traces, and presents structured findings, thereby maintaining comprehensive error detection while dramatically reducing manual analysis time.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces the mechanical manual analysis process with an automated computational system. Instead of manually examining log entries, the system uses scripts and algorithms to automatically parse logs, identify errors, generate stack traces, and search knowledge bases, substituting human mechanical effort with automated processing.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Loss of information

If complete Bundle Troubleshoot Log is collected, then all error information is captured, but log size and processing complexity increase

Engineering Contradiction:
Improveerror information completenessVSAvoidlog processing complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent extracts only the essential error information from the complete Bundle Troubleshoot Log. The system identifies and extracts error entries, their hierarchical stack traces, and relevant contextual information, separating these from the rest of the log data. This extraction maintains information completeness for error analysis while reducing overall processing complexity.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments the large Bundle Troubleshoot Log into manageable error units. Each error is treated as a separate entity with its own hierarchical stack trace and metadata. This segmentation allows the system to process and analyze errors individually rather than dealing with the log as one monolithic structure, reducing processing complexity.

Inventive Principle:
Principle #1Segmentation

3Measurement precision

If detailed log analysis is performed to determine root cause, then accurate diagnosis is achieved, but support efficiency decreases

Engineering Contradiction:
Improveroot cause accuracyVSAvoidsupport efficiency
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The patent performs preliminary actions by automatically generating hierarchical stack traces and organizing error information before the analyst begins root cause analysis. The system pre-processes the log data, structures errors hierarchically, and prepares diagnostic information in advance, so that when the analyst reviews the case, the foundational analysis work is already complete, improving both accuracy and efficiency.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback mechanisms where the analysis system searches knowledge bases using extracted error information and provides suggested solutions back to the analyst. This feedback loop allows the system to learn from known issues and provide guided recommendations, improving root cause accuracy while maintaining high support efficiency through automated assistance.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9645874B2Analyzing OpenManage integration for troubleshooting log to determine root cause
Publication Date: 2017.05.09 DELL PROD LP
  • US9645874B2 patent drawing
  • US9645874B2 patent drawing
  • US9645874B2 patent drawing

AI summary

A system, method, and computer-readable medium for enhancing troubleshoot log analysis. More specifically, in certain embodiments, a management suite error log analysis system enables users, including engineers and technical support personnel to quickly and effectively determine a root cause of an error and to suggest possible solutions to the error.