State based configuration failure detection using checkpoint comparison
First Claim
1. A system for determining a root cause for configuration failure of an application, the system including:
- a narrow-down component configured to compare a plurality of checkpoints, each checkpoint being any configuration data saved at different points in a machine history, record configuration file accesses, and track change frequencies of configuration file values;
a solution query component coupled to the narrow-down component, the solution query component configured to record actions of the user interface and configuration file modifications and to search one or more databases for information related to the configuration failure, the solution query phase, the narrow-down component and the solution query component operative to determine a deviation from known operation of the application without requiring the application to specify configuration settings that control the deviation.
2 Assignments
0 Petitions
Accused Products
Abstract
A system and method for determining configuration failure root cause of an application uses persistent-state checkpoints. Checkpoints are periodic snapshots of configuration data saved at different points in a machine'"'"'s history. One component in the system compares checkpoints, records configuration file accesses, and tracks change frequencies of configuration file values. Another component is configured to record actions of a user interface and configuration file modifications and to search one or more databases for information related to the configuration failure. The components determine a deviation from known operation of the application without the application specifying configuration settings that control the deviation. The method includes identifying a set of configuration data modified since a last known working state of the application, intersecting the set of configuration data with data associated with access by the application, removing frequently changing configuration data from the intersection, and ranking each entry by likelihood of each entry being the cause of the failure.
-
Citations
30 Claims
-
1. A system for determining a root cause for configuration failure of an application, the system including:
-
a narrow-down component configured to compare a plurality of checkpoints, each checkpoint being any configuration data saved at different points in a machine history, record configuration file accesses, and track change frequencies of configuration file values;
a solution query component coupled to the narrow-down component, the solution query component configured to record actions of the user interface and configuration file modifications and to search one or more databases for information related to the configuration failure, the solution query phase, the narrow-down component and the solution query component operative to determine a deviation from known operation of the application without requiring the application to specify configuration settings that control the deviation. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11)
-
-
12. A method for determining a cause for failure of an application on a machine, the method comprising:
-
identifying a set of configuration data modified since a last known working state of an application;
intersecting the set of configuration data with a second set of configuration data including data associated with access by the application;
removing frequently changing configuration data from the intersection to provide a reduced set of configuration data; and
ranking each entry in the reduced set of configuration data by likelihood of each entry being the cause of the failure. - View Dependent Claims (13, 14, 15, 16, 17, 18, 19, 20, 21, 22)
-
-
23. A computer readable medium having computer-executable instructions to perform acts for determining a cause for failure of an application on a machine, the acts comprising:
-
identifying a set of configuration data modified since a last known working state of an application;
intersecting the set of configuration data with a second set of configuration data including data associated with access by the application;
removing frequently changing configuration data from the intersection to provide a reduced set of configuration data; and
ranking each entry in the reduced set of configuration data by likelihood of each entry being the cause of the failure. - View Dependent Claims (24, 25, 26, 27, 28, 29, 30)
-
Specification