Automatic Logging Level Adjustment for Electronic Device Failure Events
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional methods for troubleshooting electronic devices require manual adjustment of logging levels, which is time-consuming and inefficient, especially when only specific modules are involved in an error, leading to excessive data capture and resource utilization.
Innovation Solution
An electronic device capable of automatically adjusting its logging level to DEBUG mode upon detecting a failure event, enabling logging only for affected modules and disabling it when the issue is resolved, thereby reducing unnecessary data capture and resource usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If manual adjustment of logging level is required for troubleshooting, then logging can be enabled for detailed analysis, but the process becomes time-consuming and inefficient
Solution Approach 1:
The system automatically detects failure events and enables DEBUG logging level without requiring manual user intervention. The logging system serves itself by monitoring its own state and adjusting logging levels autonomously based on detected failures, eliminating the need for users to manually configure logging settings during troubleshooting.
Solution Approach 2:
The system pre-configures a mapping between failure event types and corresponding logging levels. When a failure is detected, the system immediately applies the pre-determined logging level (DEBUG) without requiring manual configuration. This preliminary preparation of logging configurations resolves the time loss issue by eliminating manual setup steps.
2Loss of information
If DEBUG logging level is enabled to capture all log entries, then comprehensive data is obtained for troubleshooting, but excessive data capture consumes CPU resources
Solution Approach 1:
The logging level is dynamically adjusted based on the detected failure event. Instead of maintaining a static DEBUG logging level that captures all entries regardless of context, the system transitions to a dynamic state where logging intensity is modulated according to actual failure conditions, capturing detailed data only when and where needed.
Solution Approach 2:
The system applies DEBUG logging level selectively to specific modules or components associated with the detected failure event, rather than enabling DEBUG level globally for all modules. This localized approach ensures comprehensive data capture for troubleshooting while minimizing CPU resource consumption by limiting intensive logging to only the affected areas.
3Loss of information
If DEBUG logging level is manually enabled for troubleshooting, then detailed log data can be captured, but the user must manually reproduce the error and monitor until resolved
Solution Approach 1:
The system automatically detects failure events, identifies the relevant modules, enables appropriate logging levels, captures log data, and monitors until resolution without requiring manual user intervention. This self-service capability eliminates the burden of manual error reproduction and monitoring from the user.
Solution Approach 2:
The system continuously monitors system events and provides feedback by automatically adjusting logging levels based on detected failures. When a failure is detected, the system responds by enabling detailed logging and continues monitoring until the failure is resolved, creating a closed-loop feedback mechanism that eliminates manual user involvement.
4Loss of information
If logging level is set to capture all module entries, then complete system data is obtained, but unnecessary data from unrelated modules increases data volume
Solution Approach 1:
The system applies selective logging by identifying the specific module or modules associated with the detected failure event and enabling detailed logging only for those modules. This local quality approach ensures that complete data is captured for the affected areas while filtering out unnecessary data from unrelated modules, thereby reducing overall data volume.
Solution Approach 2:
The system extracts and focuses logging attention on the specific subset of modules relevant to the detected failure, separating the needed detailed data from the unnecessary data generated by other modules. This extraction process allows the system to obtain complete troubleshooting information for the affected area while minimizing the quantity of data that needs to be processed and analyzed.
Data Source
AI summary
An apparatus, method, and computer-readable recording medium for automatically adjusting a logging level for an electronic device. The electronic device includes a plurality of software modules, each software module controlling functions of the electronic device. Each of a plurality of failure events are associated in advance with one or more of the software modules. A current event is detected on the electronic device that corresponds to a matching failure event of the plurality of failure events. A predetermined logging level is automatically enabled for the one or more of the software modules associated with the matching failure event at the time of the detected current event. Log messages are captured at the predetermined logging level for the one or more of the software modules for which the predetermined logging level has been automatically enabled. The predetermined logging level is automatically disabled when the current event has ended.