Agile Error Determination and Reporting System

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In agile software development environments, such as IBM's Scale Out Network Attached Storage (SONAS), there is a challenge in accurately and cohesively alerting remote support of dependent and fatal errors across multiple independent systems and software tools, which has been elusive in existing solutions.

Innovation Solution

A method and system for handling errors that detect errors in a machine, determine an error ID, decide if the error should be reported to a host system, and take corresponding actions, involving error determination and action tables to send relevant information to the host system for further analysis.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple independent systems and software tools are combined to create a scalable storage system, then system scalability and functionality are improved, but error determination and reporting accuracy deteriorates

Engineering Contradiction:
Improvesystem scalabilityVSAvoiderror determination accuracy
Core Design Contradiction:
Adaptability or versatilityVSMeasurement precision

Solution Approach 1:

The patent segments the complex error determination process into distinct components: error detection modules in individual machines, error ID assignment, severity classification (dependent vs. fatal), and hierarchical reporting pathways. Each machine's error handling is segmented and can be independently configured, yet collectively they provide accurate system-wide error determination.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary error determination system that acts as a mediator between individual machines and the host system. This intermediary layer classifies errors, determines severity, and manages reporting, thereby maintaining accuracy across the distributed system architecture.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If all errors are reported to the host system, then error analysis completeness is improved, but system productivity deteriorates due to excessive notifications

Engineering Contradiction:
Improveerror analysis completenessVSAvoidsystem productivity
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

The patent applies local quality by differentiating error handling based on error type and severity. Not all errors are treated uniformly - dependent errors are handled locally or with minimal reporting, while fatal errors trigger comprehensive reporting. This selective approach maintains completeness for critical errors while preserving productivity by filtering out noise.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent implements partial action by reporting only the necessary subset of errors to the host system. Instead of reporting all errors indiscriminately, the system performs partial reporting focused on fatal and significant dependent errors, thereby maintaining error analysis completeness for critical issues while avoiding productivity loss from excessive notifications.

Inventive Principle:
Principle #16Partial or excessive action

3Stability of the object's composition

If error reporting rules are fixed, then system stability is improved, but adaptability to new error types deteriorates

Engineering Contradiction:
Improvesystem stabilityVSAvoidadaptability to new error types
Core Design Contradiction:
Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamics by making error determination rules configurable and adaptable. The system allows modification of error classification criteria, reporting thresholds, and handling procedures without requiring system redesign. This dynamic configuration enables the stable framework to adapt to new error types and changing operational requirements.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent utilizes parameter changes by allowing error determination parameters (such as severity thresholds, reporting criteria, and classification rules) to be modified. This enables the system to maintain stability through a consistent framework while adapting to new error types by changing the parameters that govern error handling behavior.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS8539285B2Systems for agile error determination and reporting and methods thereof
Publication Date: 2013.09.17 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US8539285B2 patent drawing
  • US8539285B2 patent drawing
  • US8539285B2 patent drawing

AI summary

According to one embodiment, a method for handling errors includes detecting that an error has occurred in a machine in a system, determining an error ID associated with the error, determining that the error should be reported to a host system for further analysis based on the error ID, determining that one or more actions should be taken by the system based on the error ID, and sending information corresponding to the error to the host system after it is determined that the error should be reported to the host system. In another embodiment, a system includes a processor and logic for performing the method. According to another embodiment, a computer program product includes a computer readable storage medium having computer readable code embodied therewith for performing the method. Other methods, systems, and computer program products are also described according to more embodiments.