Dynamic Code Tracing Module Selection for Error Analysis

Solution Overview

Problem

Managing code-tracing data is challenging due to the large volume of data generated, which consumes storage space and slows down software operation, and reducing tracing levels can obscure error identification.

Innovation Solution

A method and system that analyze log data to identify error modules, activate high-detail tracing in those modules, and create profiles for specific error types, dynamically adjusting tracing levels based on error patterns and absence of errors to optimize data collection.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If code-tracing is activated at a high detail level in all modules, then error identification capability is improved, but storage space consumption increases and software operation speed decreases

Engineering Contradiction:

Improveerror identification capabilityVSAvoidsoftware operation speed

Core Design Contradiction:

Measurement precisionVSProductivity

Solution Approach 1:

The patent applies local quality by enabling high-detail code-tracing only in specific modules where errors are detected or suspected, rather than uniformly across all modules. The trace manager dynamically adjusts tracing detail levels based on error patterns, applying intensive tracing locally to problematic areas while maintaining lower tracing levels in normal-operating modules, thus preserving overall system performance.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

The patent implements dynamics by making the code-tracing detail level adjustable and adaptive rather than static. The trace manager continuously monitors error patterns and dynamically modifies which modules operate at high tracing detail levels. This allows the system to transition between different tracing intensities based on runtime conditions, optimizing the balance between error detection capability and system performance.

Inventive Principle:

Principle #15Dynamics

2Measurement precision

If code-tracing is activated at a high detail level in all modules, then error identification capability is improved, but storage space consumption increases

Engineering Contradiction:

Improveerror identification capabilityVSAvoidstorage space consumption

Core Design Contradiction:

Measurement precisionVSQuantity of substance

Solution Approach 1:

The patent applies local quality by enabling high-detail code-tracing only in specific modules where errors are detected or suspected, rather than uniformly across all modules. The trace manager dynamically adjusts tracing detail levels based on error patterns, applying intensive tracing locally to problematic areas while maintaining lower tracing levels in normal-operating modules, thus preserving overall system performance.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

The patent implements dynamics by making the code-tracing detail level adjustable and adaptive rather than static. The trace manager continuously monitors error patterns and dynamically modifies which modules operate at high tracing detail levels. This allows the system to transition between different tracing intensities based on runtime conditions, optimizing the balance between error detection capability and system performance.

Inventive Principle:

Principle #15Dynamics

3Quantity of substance

If the level of tracing is reduced to decrease storage consumption, then storage space efficiency is improved, but information completeness for error identification deteriorates

Engineering Contradiction:

Improvestorage space efficiencyVSAvoidinformation completeness for error identification

Core Design Contradiction:

Quantity of substanceVSLoss of information

Solution Approach 1:

The patent applies local quality by enabling high-detail code-tracing only in specific modules where errors are detected or suspected, rather than uniformly across all modules. The trace manager dynamically adjusts tracing detail levels based on error patterns, applying intensive tracing locally to problematic areas while maintaining lower tracing levels in normal-operating modules, thus preserving overall system performance.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

The patent implements feedback by using detected error patterns to inform and adjust the code-tracing configuration. The trace manager monitors runtime behavior and error occurrences, then uses this feedback to dynamically modify which modules receive high-detail tracing. This closed-loop approach ensures that tracing resources are allocated to the modules most likely to provide useful error identification information.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS8874967B2Managing code-tracing data

Publication Date: 2014.10.28 NCR ATLEOS CORP

AI summary

A method of managing code-tracing data is described. The method comprises the steps of: analyzing a log of code-tracing data to identify a module in which an error occurred; activating code-tracing at a high detail level in that module; identifying modules associated with that module; and activating code-tracing at a high detail level in those identified modules.