Determining a number of unique incidents in a plurality of incidents for incident processing in a distributed processing system

• US 9,348,687 B2
• Filed: 06/09/2014
• Issued: 05/24/2016
• Est. Priority Date: 01/07/2014
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Boger, Lynn A.
• Primary Examiner(s): Patel, Kamini
• Application Number:
  US14/299,311
• Publication Number:
  US 20150195165A1
• Time in Patent Office: 715 Days
• Field of Search: 714/20
• US Class Current: 1/1
• CPC Class Codes: G06F 11/0709 in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
• CPC Class Codes: G06F 11/0748 in a remote unit communicating with a single-box computer node experiencing an error/fault remote testing G06F11/2294
• CPC Class Codes: G06F 11/0775 Content or structure details of the error report, e.g. specific table structure, specific error fields
• CPC Class Codes: G06F 11/0781 Error filtering or prioritizing based on a policy defined by the user or on a policy defined by a hardware/software module, e.g. according to a severity level
• CPC Class Codes: G06F 11/0787 Storage of error reports, e.g. persistent data storage, storage using memory protection
• CPC Class Codes: G06F 11/3006 where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems multiprogramming arrangements G06F9/46; allocation of resources G06F9/50
• CPC Class Codes: G06F 11/3072 where the reporting involves data filtering, e.g. pattern matching, time or event triggered, adaptive or policy-based reporting
• CPC Class Codes: G06F 11/34 Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
• CPC Class Codes: H04L 41/0618 based on the physical or logical position
• CPC Class Codes: H04L 43/08 Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters

Abstract

Methods, apparatuses, and computer program products for determining a number of unique incidents in a plurality of incidents for incident processing in a distributed processing system are provided. Embodiments include an incident analyzer identifying within the plurality of incidents, attribute combination entries of location identifications and incident types and analyzing each location identification in each attribute combination entry according to a sequence of the attribute combination entries including creating attribute pairs. The incident analyzer is also configured to count the attribute pairs. The number of attribute pairs is the number of unique incidents in the plurality of incidents.

Claims

1. A method of determining a number of unique incidents in a plurality of incidents for incident processing in a distributed processing system, the method comprising:

identifying within the plurality of incidents, by an incident analyzer, attribute combination entries of location identifications and incident types, wherein each attribute combination entry has one location identification and a set of unique incident types corresponding to the location identification;

analyzing each location identification in each attribute combination entry according to a sequence of the attribute combination entries including for each location identification of each attribute combination entry;

determining whether the set of unique incident types within the attribute combination entry includes an incident type not selected for pairing with another location identification in an attribute pair;

if the set of unique incidents types includes an incident type not selected for pairing with another location identification in an attribute pair, selecting the incident type for pairing with the location identification in an attribute pair and creating an attribute pair of the selected incident type and the location identification; and

counting the attribute pairs;

wherein the number of attribute pairs is the number of unique incidents in the plurality of incidents.

2. The method of claim 1 further comprising creating the sequence of the attribute combination entries;

wherein creating the sequence of the attribute combination entries includes sorting the attribute combination entries based on one of a number of incident types within each set of unique incident types and a number of location identifications.

3. The method of claim 1 wherein determining whether the set of unique incident types corresponding to the location identification within the attribute combination entry includes an incident type not selected for pairing with another location identification in an attribute pair further comprises:

maintaining a list of selected incident types that have already been selected for pairing with a location identification in an attribute pair; and

comparing the set of unique incident types to the list of selected incident types.

4. The method of claim 1 further comprising:

identifying attribute combination entries having identical sets of incident types; and

merging the identified attribute combination entries.

5. The method of claim 1 further comprising:

determining that the number of unique incidents is greater than or equal to a predetermined number; and

executing an action in response to determining that the number of unique incidents is greater than or equal to the predetermined number.

6. The method of claim 1 wherein executing an action includes at least one of creating an alert and suppressing an incident.