Patent Application
20130103990
The present invention relates generally to change management systems, and more specifically the present invention relates to a system and method for matching reported errors with recent software changes.
Commercial computer systems require many interdependent software programs in order to perform useful functions. These software programs include an operating system, various hardware drivers, and one or more applications. Current software programs often rely on external software components, known as shared libraries, dynamic-linked libraries, shared objects, or plug-ins, which are self-contained sets of related routines that can be accessed by software programs in order to provide functionality.
Often, the software components, collectively referred to hereinafter as shared libraries, are used by multiple software programs. This sharing of resources increases overall efficiency and performance since the computer system does not need to store many programs having overlapping functionality, and the shared libraries can be loaded and executed only when needed.
Similarly, operating systems rely on hardware drivers and helper applications to perform many of the basic functions of the operating system, including accessing network interface cards (NICs), human interface devices (e.g., keyboards, mice, touch pads, etc.), and display screens.
A benefit to the modular design of current software is the ability to periodically upgrade one portion of the software program without requiring a complete reinstallation of the software program. With respect to reinstalling an operating system, several hours may be required for the process. Such periodic upgrades can be initiated in an effort to correct software bugs, newly identified security flaws, and implement new features. As a result, bugs and security flaws can be corrected within days of a problem being identified.
However, along with the above benefits, the modularity of modern software programs also present certain disadvantages, the most significant being incompatibility with particular versions of shared libraries or drivers. These incompatibilities can lead to instability of the software program (i.e., crashes) at a minimum, and often can lead to the software program failing to execute at all.
Because a modern computer system has many software programs using a multitude of shared libraries, drivers and helper applications of one type or another, most of which remain hidden to the general computer user, it is often difficult to identify which of these components may be causing an error.
An embodiment of the present invention includes the steps of generating a database configured with fields identifying one or more component changes and potential problems associated with each one or more component changes; populating the fields of the database with information as a component change is made to a computer system; monitoring the computer system for issuance of error alerts; comparing issued error alerts against entries of potential problems in the database; and identifying a set of at least one of the component changes as a potential cause of the issued error alert based on the result of the comparing step. The component changes entered into the database include changes to hardware, security privileges, software components, database entries, and settings changes.
Additionally, an embodiment of the present invention executes a corrective process in response to the identification of the potential cause of the issued error.
Moreover, an embodiment of the present invention includes an iterative process for identifying a minimum number of component changes from the set of at least one of the component changes as a confirmed cause of the issued error.
Further, an embodiment of the present invention updates the database entry of potential problems associated with each of the minimum number of component changes to reflect the issued error as a confirmed error thereof.
These and other features, aspects, and advantages of the present invention will become better understood with regard to the following description, appended claims, and accompanying drawings wherein:
Referring to
Once the database is generated, the database is populated with the change information for the software installed on the monitored computer system in step 103. The present embodiment then proceeds to step 105 where the process waits for the next instance of a software upgrade or installation. When a software change, such as an upgrade, occurs in step 107, the present embodiment executes step 103 again.
At the same time that the present embodiment executes step 105, the present embodiment also monitors the computer system in step 109 for error alerts, or software crashes. If an error alert is detected in step 111, the present embodiment captures the error alert information, such as the text of the error alert, error code, application or service that generated the error alert, etc., in step 113. Additionally, in step 113, the captured error alert information is compared against the potential problems entries in the database. Based on the comparison conducted in step 113, the present embodiment determines if the error alert is related to a change recorded in the database in step 114. If the error alert is not related to a recorded change, the present embodiment returns to step 109 and continues monitoring for new error alerts.
Error alerts that are determined to not be related to recorded changes in step 114 are handled by the operating system in the conventional manner. The conventional error handling may include presentation of an error alert message to the user of the computer system, etc.
However, if the error alert is determined to relate to a recorded change, the present embodiment identifies one or more software entities as the potential cause of the error alert in step 115.
Additionally, in step 115, the present embodiment can be configured to provide notification to the user of the computer system that the error alert has been captured and corrective action is being taken. Further, step 115 of the present embodiment can be configured to provide the user with details relating to the cause of the error alert and the corrective action being performed. Furthermore, step 115 of the present embodiment can be configured to provide the user with an option to either have the change management system of the present embodiment perform the corrective action or abort the corrective action.
The list of one or more software entities identified as potential causes of the error alert is used by the present embodiment to update the database in step 117, to identify the error corresponding to the error alert as a known problem of the one or more software entities identified as potential causes of the error alert. Additionally, the present embodiment performs a corrective process in step 119 that includes rolling back (i.e., down-grading) the one or more software entities identified as potential causes to previously installed stable versions where possible, or quarantining or removing of the one or more software entities identified as potential causes where roll back is not feasible. Once the corrective process 119 is completed, the present embodiment returns to step 109 to continue monitoring the computer system for future error alerts.
The corrective process of step 119 can be configured to operate on all the software entities identified as potential causes of the error alert all at once. Alternatively, the corrective process process of step 119 can be configured to provide an iterative process—an example of which is shown in
It is noted that herein “roll back” is intended to encompass actual down-grading of a software change as well as any other corrective action performed in an effort to avoid future occurrences of the error alert.
If subsequent error alerts are detected in step 111 that are identical to the previous error alert, the present embodiment will roll back the next highest priority software entity on the list of potential causes in step 119. The previously, rolled back software entity will then be flagged as not the cause of the error alert, and thus allowed to be returned to its upgraded version once again. This iterative process can be repeated until the error alert in question is no longer detected. Once the error alert is no longer detected in step 111, the most recent software entity that was rolled back in connection with the error alert by step 119 is marked as the known cause of the error alert. By marking the software entity as the known, or confirmed, cause of the error alert, the software entity is prevented from being upgraded to the error-causing version in the future.
In another embodiment of the present invention, the change management is not limited to software changes. The present embodiment is configured to operate on all change categories to a computer system, including changes to databases, security privileges (e.g., user accounts), hardware (e.g., storage devices, memory, peripheral devices, etc.), configuration settings for, e.g., network services, printing, and display.
Turning to
Referring back to step 119-1, if the error has been previously tracked, and thus a list of potential causes, has already been created, the process moves to step 119-7 where any new potential causes of the error identified in step 115 are added to the list at the proper hierarchal position. The process then proceeds to step 119-9.
In step 119-9 the topmost potential cause, as listed, of the error is retrieved. Depending on the type of element referenced by the retrieved potential cause—i.e. software component, security privilege, database entry, or hardware component—an appropriate corrective action is performed at step 119-11. After performing the corrective action, the retrieved potential causes is marked in the list as having been rolled back, in step 119-13. The now-marked potential cause is moved to the bottom of the list in step 119-15. At this point the iterative roll back process terminates by returning to step 109 of
Subsequent occurrences of the error will cause the iterative roll back process to proceed directly from step 119-1 to step 119-7, and in step 119-9 the process will retrieve the new topmost potential cause of the error in the list.
The present invention can be utilized in any computer system deployment, for example the present invention is applicable for both small home office settings as well as large scale enterprise environments having fully staffed IT departments.
Additionally, a server 304 and one or more printers/copiers 306 are present. The server 304, workstations 302 and printer/copiers 306 are connected to one another by way of a router 308 utilizing any one or more communication protocols such as IEEE 802.11a/b/g/n wireless protocols, IEEE 802.3 Ethernet protocols, token ring, or other standard or proprietary communication protocols. For simplicity, the embodiment in
Also connected to the network, and in communication with all the other systems on the network, is a monitoring system 310. In the present embodiment the monitoring system is essentially a specialized workstation 302 having the necessary software programs installed thereon to perform the functions disclosed above with respect to the embodiments of
In an alternative embodiment, the software programs for performing the functions of the present invention may be installed on the server 304 (or on a second server, not shown) and executed remotely by the monitoring system 310. Additionally, the database which stores the change information can be provided either on a computer-readable storage device disposed on the server 304 or the computer-readable storage device 310b of the monitoring system 310.
An embodiment of the present invention is intended to operate from a computer operations center configured to monitor a large number of individual computer systems and terminals for error alerts. Operators viewing display screens receive notifications of error alerts issued by the monitored computer systems. The system of the present embodiment immediately flags error alerts that match changes recorded in the database and notifies the operator that corrective action is being taken by the system.
The described embodiments of the present invention are intended to be illustrative rather than restrictive, and are not intended to represent every embodiment of the present invention. Various modifications and variations can be made without departing from the spirit or scope of the invention as set forth in the following claims both literally and in equivalents recognized in law.
