Action Pattern Database for Faster Computing Failure Remediation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for addressing computing system failures are inefficient and time-consuming, particularly as the volume of knowledge and complexity of systems increase, leading to prolonged downtime and reduced reliability.

Innovation Solution

A database of failure patterns and remediation actions is constructed, allowing for the identification of relevant log files and extraction of debugging data, which is then sent to an external system for instructions on failure resolution, with preprocessing to remove sensitive information and enhance informativeness.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If traditional manual methods are used to address computing system failures, then system administrators can manually diagnose and resolve issues, but the process becomes inefficient and time-consuming as system complexity and knowledge volume increase

Engineering Contradiction:
Improvefailure resolution efficiencyVSAvoidsystem downtime
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by building a comprehensive database of failure patterns and associated remediation actions before failures occur. The database is pre-populated with knowledge from multiple sources including log files, error messages, and expert systems, enabling rapid matching and resolution when failures actually occur, thus reducing both resolution time and downtime.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates copies of failure patterns and remediation knowledge from various sources (log files, expert systems, external databases) and stores them in a standardized database format. When a failure occurs, the system copies relevant patterns from the database to diagnose and resolve the issue, eliminating the need to manually recreate diagnostic procedures each time.

Inventive Principle:
Principle #26Copying

2Measurement precision

If comprehensive debugging data is collected and sent to external systems for failure analysis, then more accurate diagnoses can be achieved, but data security and privacy concerns increase

Engineering Contradiction:
Improvefailure diagnosis accuracyVSAvoiddata security risk
Core Design Contradiction:
Measurement precisionVSObject-affected harmful factors

Solution Approach 1:

The system extracts only the specific debugging data and failure patterns that are directly relevant to diagnosing the current failure, rather than transmitting comprehensive system data. The database is queried to extract only matching failure patterns and associated log files, minimizing data transmission while maintaining diagnostic accuracy.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system introduces an intermediary layer between the internal system and external analysis systems. The database acts as an intermediary that pre-processes and filters failure information, presenting only relevant, anonymized data to external systems while protecting sensitive internal information.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If a detailed database of failure patterns and action patterns is built, then more accurate matching and remediation can be achieved, but the complexity of building and maintaining the database increases

Engineering Contradiction:
Improvefailure remediation accuracyVSAvoiddatabase construction complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The database structure is designed to be universal and multi-functional, accommodating multiple types of failure patterns, log file formats, and remediation actions within a single standardized framework. This universal structure reduces complexity by providing a consistent methodology for building and maintaining the database across different system configurations and failure types.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS20250355758A1Failure remedy in computing systems using action pattern database
Publication Date: 2025.11.20 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US20250355758A1 patent drawing
  • US20250355758A1 patent drawing
  • US20250355758A1 patent drawing

AI summary

A method for operating a first computer system is provided. The method includes: building a database comprising entries, each entry indicating a failure in one or more second computer systems and an action pattern to remedy the failure, the action pattern indicating log files to be accessed to remedy the failure. In response to detecting a failure in the first computer system, one or more entries of the database that match the detected failure may be identified. The one or more action patterns associated with the identified one or more entries may be used for extracting debugging data representing the detected failure. At least part of the debugging data may be sent to an external system. In response to the sending, instructions to remedy the detected failure may be received from the external system.