Dynamic Runtime Logging Control via User Review Analysis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems for collecting runtime statistics of applications lack efficient mechanisms to dynamically control logging, leading to unnecessary data overhead and resource consumption, especially when only specific code components are defective.
Innovation Solution
A computer program product that analyzes user reviews to identify defective code components within applications, enabling dynamic control of logging to selectively turn on/off logging for these components, reducing data transmission and resource usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all runtime statistics are logged and pushed to server, then complete monitoring data is obtained, but CPU/network overhead and memory usage increase
Solution Approach 1:
The patent applies local quality by selectively enabling logging only for defective code components identified through user reviews, rather than uniformly logging all application components. This targeted approach reduces the volume of logged data and associated CPU/network overhead while maintaining monitoring effectiveness for problematic areas.
Solution Approach 2:
The system dynamically adjusts logging behavior based on runtime conditions, specifically turning on logging only when defective code components are detected through user review analysis. This dynamic control allows the system to adapt logging intensity to actual needs, reducing unnecessary resource consumption during normal operation.
2Loss of information
If comprehensive logging is performed for all code components, then complete troubleshooting information is available, but data transmission overhead increases
Solution Approach 1:
The patent extracts and isolates logging operations to only those specific code components that have been identified as defective through user review analysis. This extraction principle separates necessary logging from unnecessary logging, reducing data transmission overhead while ensuring complete troubleshooting information is captured for problematic components.
3Reliability
If logging is continuously enabled for all components, then all runtime issues are captured, but memory usage increases
Solution Approach 1:
The system applies local quality by concentrating memory resources on storing logs for only the defective code components identified through user reviews, rather than uniformly allocating memory for all application components. This selective approach reduces overall memory usage while maintaining comprehensive issue detection capability for problematic areas.
Data Source
AI summary
Runtime system statistics logging is dynamically controlled at code and application levels, based on user reviews. Logging of specific code components in specific application instances, identified based on user reviews, is automatically turned on, based on the user reviews indicating defects. Logging for other components or application instances, however, remains off or is automatically turned off.