# US 2008/0288502 A1 · Storing dependency and status information with incidents

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2008/0288502 A1
- Document ID: US20080288502A1
- Status: Published application
- Kind: A1
- Application number: 11/748,602
- Filed: 2007-05-15
- Published: 2008-11-20
- Earliest claimed: 2007-05-15
- Assignees: International Business Machines Corporation
- Inventors: Brett A. Coley; Niraj P. Joshi; Kenneth J. Parzygnat; Wayne B. Riley
- Web page: https://patentgrep.com/patent/US20080288502A1

## CPC

- G06F 11/0709: {in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems}
- G06F 11/0748: {in a remote unit communicating with a single-box computer node experiencing an error/fault (remote testing G06F11/2294)}
- G06F 11/0793: {Remedial or corrective actions (recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40)}
- G06F 11/2294: {by remote test}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A method and system are disclosed for reporting incidents occurring during operation of a distributed computing environment including a multitude of hardware and software resources. The method comprises the steps of whenever a defined incident occurs, generating a respective one incident report; and keeping with each incident report, selected information relating to the incident. Preferably, this information that is kept with the incident report identifies (i) selected resources associated with the defined incident, and status of said selected resources at the time of the defined incident, (ii) dependencies among said selected resources at the time of the defined incident, and (iii) service level agreements and operating level agreements impacted by the defined incident.

## Claims

### Claim 1

A method of reporting incidents occurring during operation of a distributed computing environment including a multitude of hardware and software resources, and wherein said distributed environment provides a multitude of services to a multitude of clients pursuant to service level agreements and operating level agreements, and wherein during operation of the distributed computing environment defined incidents occur, the method comprising the steps of:
whenever one of said defined incidents occur, generating a respective one incident report; and
keeping with each incident report, information identifying selected resources associated with said one of the defined incidents, and status of said selected resources at the time of the one of said defined incidents,
dependencies among said selected resources at the time of the one of the defined incidents, and
service level agreements and operating level agreements impacted by said one of the defined incidents.

### Claim 2 (depends on 1)

A method according to claim 1, wherein the keeping step includes the step of identifying on said each incident report:
reported failing components;
candidate failing components;
actual failing components; and
impacted business systems.

### Claim 3 (depends on 2)

A method according to claim 2, comprising the further step of using relationships between incidents and resources, as reported on the incident reports, to find patterns of repeating failure of resources of the distributed computing environment.

### Claim 4 (depends on 3)

A method according to claim 3, comprising the further step of using the incident reports to identify sets of resources similar to the resources reported on the incident reports but not on the incident reports, that may be susceptible to problems.

### Claim 5 (depends on 4)

A method according to claim 4, comprising the further step of displaying said incident reports on a computer monitor.
