Automated Runbook Out-of-Date Detection in Workload Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The increasing complexity of modern computer systems leads to out-of-date runbooks, making it time-consuming and painful for operators to detect and update them, especially in agile development environments where thousands of alerts are defined, and runbooks can become outdated frequently.

Innovation Solution

A computer-implemented method and system that automatically generates a defect on a running workload system, obtains and parses a runbook to execute operations, and determines if the runbook is out-of-date by simulating a defect and monitoring the alert status over a predefined period, generating a runbook out-of-date signal if the alert is not solved.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If operators manually detect and update runbooks in complex workload systems, then they can maintain system reliability, but the time and effort required increases significantly

Engineering Contradiction:
Improverunbook accuracyVSAvoidtime to detect and update runbooks
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system enables automated self-detection of out-of-date runbooks by generating defects, executing runbook operations, and comparing expected versus actual outcomes. This eliminates the need for operators to manually review and update runbooks, allowing the system to self-diagnose and identify outdated documentation automatically.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary automated testing by generating test defects and executing runbook operations before actual production issues occur. This proactive approach identifies out-of-date runbooks in advance, preventing delays when real incidents need to be resolved.

Inventive Principle:
Principle #10Preliminary action

2Measurement precision

If the system automatically executes runbook operations to detect out-of-date runbooks, then the detection accuracy improves, but the complexity of the system increases

Engineering Contradiction:
Improverunbook validity detection accuracyVSAvoidautomation system complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system employs a multi-functional automated testing framework that can generate various types of defects, execute different runbook operations, and validate outcomes across diverse workload scenarios. This universal approach handles multiple detection tasks through a single integrated system, managing complexity through consolidation rather than proliferation of separate tools.

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

Solution Approach 2:

The system introduces an intermediary automated testing layer between the runbook documentation and the actual workload system. This intermediary generates controlled test defects, executes runbook operations, and compares outcomes, serving as a mediator that validates runbook accuracy without directly modifying the production system.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If operators review thousands of alerts and corresponding runbooks, then they can ensure system stability, but the productivity decreases due to the large volume of work

Engineering Contradiction:
Improvesystem stabilityVSAvoidrate of runbook validation
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system replaces the mechanical manual process of operators reviewing alerts and runbooks with an automated computational system. The automated system generates defects, executes runbook operations, and validates outcomes through programmatic means, substituting human manual labor with automated software processes that operate at much higher speeds and volumes.

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

Solution Approach 2:

The system implements periodic automated validation by scheduling regular execution of runbook operations against generated defects. This periodic action continuously validates runbook accuracy over time, maintaining system stability through repeated automated checks rather than requiring constant manual intervention.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS11561881B2Out-of-date runbook detection
Publication Date: 2023.01.24 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11561881B2 patent drawing
  • US11561881B2 patent drawing
  • US11561881B2 patent drawing

AI summary

A method, system, and computer program product for detecting out-of-date runbooks are disclosed. The method may include generating a defect corresponding to an alert on a running workload system. The method may further include, in response to generating the defect in the running workload system, automatically obtaining an identification of a runbook based on information of the alert, automatically accessing the runbook based on the identification of the runbook, the runbook including instructions for fixing the defect, automatically parsing the instructions to obtain executable operations, and automatically executing the executable operations on the running workload system. The method may further include, in response to detecting that the alert is not solved on the running workload system after a predefined period, automatically determining that the runbook is out-of-date, and automatically generating a runbook out-of-date signal.