Software Stability Diagnosis via Fleet Configuration Comparison
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing system management tools face challenges in identifying and addressing stability changes in computer systems, particularly in virtual machines, due to the dynamic nature of software installations and updates, which can lead to instability and performance issues.
Innovation Solution
A method that detects stability changes in a computer system by comparing the software applications installed on that system with those on other systems, identifying a second system with the same applications except for a specific software application, and attributing the stability change to that application, allowing for the removal or updating of the identified software to stabilize the system.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If software applications are continuously installed and updated to maintain system capabilities, then system functionality is improved, but system stability deteriorates due to potential faults and errors
Solution Approach 1:
The system performs preliminary actions by proactively monitoring and detecting stability changes before they manifest as critical failures. The management module continuously compares software configurations across multiple systems and identifies potential instability sources through pattern recognition, allowing preventive maintenance before actual system failures occur.
Solution Approach 2:
The invention implements feedback mechanisms by continuously monitoring system stability metrics and using this information to guide software update decisions. The management module collects stability data from multiple systems, analyzes correlations between software changes and stability variations, and uses this feedback to determine whether to proceed with, delay, or rollback software updates across the fleet.
2Loss of information
If system management tools detect failures and trigger log collection, then diagnostic information is obtained, but identification of the specific causing software application becomes complex and time-consuming
Solution Approach 1:
The system creates and maintains copies of software configuration data across multiple systems in a centralized management module. By comparing these copied configuration datasets, the system can rapidly identify which specific software application differs between stable and unstable systems without manually examining each system's complete software inventory, significantly reducing identification complexity.
Solution Approach 2:
The management module performs multiple functions simultaneously: it stores software configuration data, detects stability changes, compares configurations across systems, and identifies problematic software applications. This multi-functional approach consolidates what would otherwise require separate tools and processes into a single unified system.
3Measurement precision
If administrative personnel manually access logs to determine problem causes, then detailed analysis is possible, but time and productivity are reduced due to manual investigation requirements
Solution Approach 1:
The system enables self-service by automatically detecting stability changes, comparing software configurations across multiple systems, and identifying the specific application causing instability without requiring manual log analysis. The management module autonomously performs the diagnostic work that would otherwise require administrative personnel time, while maintaining high precision through systematic comparison methods.
Solution Approach 2:
Instead of requiring complete manual analysis of all log data across all systems, the invention performs partial action by focusing specifically on comparing software configuration data between stable and unstable systems. This targeted approach achieves sufficient diagnostic precision without the excessive time investment required for comprehensive manual log review.
Data Source
AI summary
A computer program product including computer usable program code embodied on a tangible computer usable storage medium, includes: computer usable program code for detecting a stability change in a first computer system; computer usable program code for comparing a first set of software applications installed on the first computer system to each set of software applications installed on a plurality of other computer systems in communication with a management module; computer usable program code for identifying a second computer system from among the plurality of other computer systems, wherein the set of software applications installed on the second computer system includes all of the first set of software applications except for a given software application; and computer usable program code for identifying the given software application as the cause of the stability change in the first computer system.