# US 2012/0239982 A1 · Methods for diagnosing entities associated with software components

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

- Number: US 2012/0239982 A1
- Document ID: US20120239982A1
- Status: Published application
- Kind: A1
- Application number: 13/484,200
- Filed: 2012-05-30
- Published: 2012-09-20
- Earliest claimed: 2010-10-07
- Assignees: International Business Machines Corporation
- Inventors: John M. Clifton; Matthew J. Fairhurst
- Web page: https://patentgrep.com/patent/US20120239982A1

## CPC

- G06F 11/302: {where the computing system component is a software system}
- G06F 11/0727: {in a storage system, e.g. in a DASD or network based storage system (drivers for digital recording or reproducing units G06F3/06; circuits for error detection or correction within digital recording or reproducing units G11B20/18; for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS], H04L67/1097)}
- G06F 11/079: {Root cause analysis, i.e. error or fault diagnosis (in a hardware test environment G06F11/22; in a software test environment G06F11/36)}
- G06F 11/3409: {for performance assessment}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

In one embodiment, a method includes recording event history information for one or more events associated with an entity; evaluating the event history information for each of the one or more events associated with the entity against a symptom rule, wherein the symptom rule defines a validity state of a diagnosis; issuing a subscription to one or more subscribers, wherein the subscription enables the one or more subscribers to receive diagnosis information; and indicating the validity state of the diagnosis to the subscriber, wherein the recording and the evaluating are performed independently such that the issuing and the event history information and the are substantially decoupled. Other methods are also described, according to various embodiments.

## Claims

### Claim 1

A method, comprising:
recording event history information for one or more events associated with an entity;
evaluating the event history information for each of the one or more events associated with the entity against a symptom rule, wherein the symptom rule defines a validity state of a diagnosis;
issuing a subscription to one or more subscribers, wherein the subscription enables the one or more subscribers to receive diagnosis information; and
indicating the validity state of the diagnosis to the subscriber,
wherein the recording and the evaluating are performed independently such that the issuing and the event history information and the are substantially decoupled.

### Claim 2 (depends on 1)

The method as recited in claim 1, wherein the event history information is provided to the one or more subscribers as trace information for a problem diagnosis.

### Claim 3 (depends on 1)

The method as recited in claim 1, wherein the symptom rule comprises one or more event history conditions relating to at least one of:
a type of events; and
a frequency of events.

### Claim 4 (depends on 1)

The method as recited in claim 1, wherein the recording, the evaluating and the indicating are each performed independently and are interoperable via at least one of:
an application programming interface; and
a shared data interface comprising the event history information.

### Claim 5 (depends on 1)

The method as recited in claim 1, further comprising:
analyzing an event profile comprising one or more events associated with the entity; and
determining whether the one or more events associated with the entity are to be recorded to the event history information.

### Claim 6 (depends on 1)

The method as recited in claim 1, further comprising:
analyzing an event profile comprising one or more events associated with the entity; and
determining whether the one or more events associated with the entity are to be recorded to the event history information,
wherein the event history information is provided to the one or more subscribers as trace information for a problem diagnosis,
wherein the symptom rule comprises one or more event history conditions relating to at least one of:
a type of events; and
a frequency of events,
wherein the recording, the evaluating and the indicating are each performed independently and are interoperable via at least one of:
an application programming interface; and
a shared data interface comprising the event history information,
wherein the recording and the evaluating are performed independently, and
wherein the entity is a storage device in a redundant array of independent disks (RAID).
