Scenario-Based Logging for Selective Execution Data Capture
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current logging methods in software development, based solely on log levels, are inadequate for selective recording of execution information, often resulting in excessive data with noise and missed desired logs, as they do not allow for scenario-specific logging.
Innovation Solution
A computer-implemented method that determines whether an input matches a predetermined scenario, recording execution information only when the input matches the scenario, allowing for scenario-based logging to selectively record execution information at specific points of program execution.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If logging is enabled for all points of execution, then complete execution information is obtained, but data volume increases excessively and contains noise
Solution Approach 1:
The patent segments the logging process by dividing execution points into different categories based on scenario matching. Instead of uniformly logging all points, it segments logging into scenario-matched points (which are logged) and non-matched points (which are not logged), thereby reducing overall data volume while preserving critical information.
Solution Approach 2:
The patent applies local quality by making logging selective rather than uniform. Different execution points receive different logging treatments based on whether they match predetermined scenarios. This ensures that only relevant execution information is recorded, improving information quality while reducing noise and unnecessary data.
2Quantity of substance
If logging is selectively enabled based on log levels, then data volume is reduced, but desired execution information may be missed
Solution Approach 1:
The patent applies preliminary action by pre-defining scenarios and their associated execution points before program execution. This allows the system to proactively identify which execution points are relevant to specific scenarios, ensuring that desired execution information is captured without needing to log all points. The predetermined scenarios serve as a guide for selective logging.
Solution Approach 2:
The patent implements feedback by comparing actual execution inputs against predetermined scenario definitions during program execution. This feedback mechanism dynamically determines whether to log execution information at each point, ensuring that desired information is captured based on real-time execution context rather than static log level settings.
3Measurement precision
If scenario-based logging is implemented, then logging precision is improved, but system complexity increases
Solution Approach 1:
The patent reduces complexity by performing preliminary setup of scenarios and their associated execution points before runtime. By pre-configuring what to log in different scenarios, the system avoids complex real-time decision-making during execution, thereby improving logging precision while keeping the runtime overhead manageable.
Data Source
AI summary
This disclosure provides a computer implemented method comprising: determining whether an input to a program matches a predetermined scenario; and recording, at least partially in response to the determination that the input matches the predetermined scenario, execution information of execution of at least part of the program, the execution of the at least part of the program being in response to the input.