DETERMINING AND ANALYZING A ROOT CAUSE INCIDENT IN A BUSINESS SOLUTION

• US 20080256395A1
• Filed: 04/10/2007
• Published: 10/16/2008
• Est. Priority Date: 04/10/2007
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Schneider, Juergen, Biazetti, Ana C., Feridun, Metin, Araujo, Carlos C., Kim, Harrison H.
• Application Number:
  US11/733,391
• Publication Number:
  US 20080256395A1
• Time in Patent Office: Days
• US Class Current: 714/43
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

A method, system and computer program product for analyzing a state changing event are disclosed. According to an embodiment, a method for analyzing a state changing event comprises: detecting a state changing event of a first resource; tracing a dependence link beginning at the first resource to a resource that the first resource depends on until finding a second resource having a state changing event that is not dependent on any resource with a state changing event; and identifying the state changing event of the second resource as a root cause incident for analysis.

Claims

1. A method for analyzing a state changing event, the method comprising:

detecting a state changing event of a first resource;

tracing a dependence link beginning at the first resource to a resource that the first resource depends on until finding a second resource having a state changing event that is not dependent on any resource with a state changing event; and

identifying the state changing event of the second resource as a root cause incident for analysis.

2. The method of claim 1, further comprising tracing a dependence link beginning at the first resource to a third resource that depends on the first resource and has a state changing event.

3. The method of claim 2, in response to a root cause incident being previously established for the state changing event of the third resource, further comprising deleting the previous root cause incident.

4. The method of claim 1, in response to the second resource being the first resource itself, further comprising performing another tracing after a preset period of time.

5. The method of claim 1, further comprising analyzing an impact of the root cause incident by tracing a dependence link beginning at the second resource to a process depending on the second resource.

6. The method of claim 1, in response to multiple processes depending on the second resource, further comprising integrating impacts of the root cause incident on the multiple processes by assigning weights to the multiple processes.

7. The method of claim 1, wherein the dependency link and a latest state of a resource are queried from a relationship database, the latest state of the resource being used to determine a state changing event of the resource.

8. A system for analyzing a state changing event, comprising:

means for detecting a state changing event of a first resource;

means for tracing a dependence link beginning at the first resource to a resource that the first resource depends on until finding a second resource having a state changing event that is not dependent on any resource with a state changing event; and

means for identifying the state changing event of the second resource as a root cause incident for analysis.

9. The system of claim 8, further comprising means for tracing a dependence link beginning at the first resource to a third resource that depends on the first resource and has a state changing event.

10. The system of claim 9, in response to a root cause incident being previously established for the state changing event of the third resource, the third resource tracing means further deletes the previous root cause incident.

11. The system of claim 8, in response to the second resource being the first resource itself, the tracing means further performs another tracing after a preset period of time.

12. The system of claim 8, further comprising means for analyzing an impact of the root cause incident by tracing a dependence link beginning at the second resource to a process depending on the second resource.

13. The system of claim 8, in response to multiple processes depending on the second resource, further comprising means for integrating impacts of the root cause incident on the multiple processes by assigning weights to the multiple processes.

14. The system of claim 8, further comprising a relationship database to store the dependence link and a latest state of a resource, the latest state of the resource being used to determine a state changing event of the resource.

15. A computer program product for analyzing a state changing event, the computer program product comprising:

computer usable program code which, when executed by a computer system, enables the computer system to;

receive data of a detected state changing event of a first resource;

trace a dependence link beginning at the first resource to a resource that the first resource depends on until finding a second resource having a state changing event that is not dependent on any resource with a state changing event; and

identify the state changing event of the second resource as a root cause incident for analysis.

16. The program product of claim 15, wherein the program code is further configured to enable the computer system to trace a dependence link beginning at the first resource to a third resource that depends on the first resource and has a state changing event.

17. The program product of claim 16, wherein, in response to a root cause incident being previously established for the state changing event of the third resource, the program code is further configured to enable the computer system to delete the previous root cause incident.

18. The program product of claim 15, wherein, in response to the second resource being the first resource itself, the program code is further configured to enable the computer system to perform another tracing after a preset period of time.

19. The program product of claim 15, wherein the program code is further configured to enable the computer system to analyze an impact of the root cause incident by tracing a dependence link beginning at the second resource to a process depending on the second resource, and in response to multiple processes depending on the second resource, the program code is further configured to enable the computer system to integrate impacts of the root cause incident on the multiple processes by assigning weights to the multiple processes.

20. The program product of claim 15, wherein the program code is configured to enable the computer system to query a relationship database to obtain the dependency link and a latest state of a resource, and to use the latest state of the resource to determine a state changing event of the resource.