Preventing and servicing system errors with event pattern correlation

US9652316B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9652316-B2
Application numberUS-201514674780-A
CountryUS
Kind codeB2
Filing dateMar 31, 2015
Priority dateMar 31, 2015
Publication dateMay 16, 2017
Grant dateMay 16, 2017

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A method includes receiving historical monitoring data for components of a system, the historical monitoring data comprising a plurality of events, each triggered by an associated component, and a plurality of alarms, each triggered by detection of a particular type of condition in the components. The method also includes determining common event sequences in the plurality of events, each event sequence culminating in one of the plurality of alarms. The method further includes correlating the common event sequences into an event pattern. The method also includes receiving a plurality of real-time events triggered by the components. The method additionally includes detecting the event pattern in the plurality of real-time events to predict a potential future instance of the particular type of condition in the components of the system.

First claim

Opening claim text (preview).

What is claimed is: 1. A method, comprising: receiving historical monitoring data for components of a system, the historical monitoring data comprising a plurality of events, each triggered by an associated component, and a plurality of alarms, each triggered by detection of a particular type of condition in the components; determining common event sequences in the plurality of events, each event sequence culminating in one of the plurality of alarms; correlating the common event sequences into an event pattern; for each event sequence, determining a relationship between a common system component and each component that generated each event in the event sequence; receiving a plurality of real-time events triggered by the components; detecting the event pattern in the plurality of real-time events to predict a potential future instance of the particular type of condition in the components of the system; and determining a root cause component based on each determined relationship as applied to the detected event pattern. 2. The method of claim 1 , further comprising: determining a root cause inference regarding the particular type of condition based on the associated components for each event in the common event sequences; and in response to detecting the event pattern in the real-time events, mitigating a root cause of the particular type of condition based on the root cause inference to prevent the potential future instance of the particular type of condition. 3. The method of claim 1 , further comprising: determining a root cause inference regarding the particular type of condition based on the associated components for each event in the common event sequences; receiving a real time alarm triggered by detection of a first error in the components; and mitigating a root cause of the first error based on the root cause inference. 4. The method of claim 2 , wherein the root cause comprises a configuration setting for a first component, and wherein addressing the root cause comprises modifying the configuration setting. 5. The method of claim 1 , wherein the historical monitoring data further comprises information regarding relationships between the components of the system, and wherein the common event sequences are determined based on the relationships between the components. 6. The method of claim 1 , wherein the historical monitoring data further comprises attributes for each event in the plurality of events, the attributes comprising an event type, a trigger time, a severity level, an impact level, and an associated component, and wherein the common event sequences are determined based on matching event attributes between each common event sequence. 7. The method of claim 1 , wherein the plurality of events in the historical monitoring data are discovered using a component monitoring system. 8. The method of claim 1 , further comprising: accessing a database of predetermined event patterns with associated root cause inferences regarding the particular type of condition; and modifying the event pattern based on the predetermined event patterns. 9. A computer configured to access a storage device, the computer comprising: a processor; and a non-transitory, computer-readable storage medium storing computer-readable instructions that when executed by the processor cause the computer to perform: receiving historical monitoring data for components of a system, the historical monitoring data comprising a plurality of events, each triggered by an associated component, and a plurality of alarms, each triggered by detection of a particular type of condition in the components; determining common event sequences in the plurality of events, each event sequence culminating in one of the plurality of alarms; correlating the common event sequences into an event pattern; for each event sequence, determining a relationship between a common system component and each component that generated each event in the event sequence; receiving a plurality of real-time events triggered by the components; detecting the event pattern in the plurality of real-time events to predict a potential future instance of the particular type of condition in the components of the system; and determining a root cause component based on each determined relationship as applied to the detected event pattern. 10. The computer of claim 9 , wherein the computer-readable instructions further cause the computer to perform: determining a root cause inference regarding the particular type of condition based on the associated components for each event in the common event sequences; and in response to detecting the event pattern in the real-time events, mitigating a root cause of the particular type of condition based on the root cause inference to prevent the potential future instance of the particular type of condition. 11. The computer of claim 9 , wherein the computer-readable instructions further cause the computer to perform: determining a root cause inference regarding the particular type of condition based on the associated components for each event in the common event sequences; receiving a real time alarm triggered by detection of a first error in the components; and mitigating a root cause of the first error based on the root cause inference. 12. The computer of claim 10 , wherein the root cause comprises a configuration setting for a first component, and wherein addressing the root cause comprises modifying the configuration setting. 13. The computer of claim 9 , wherein the historical monitoring data further comprises information regarding relationships between the components of the system, and wherein the common event sequences are determined based on the relationships between the components. 14. The computer of claim 9 , wherein the historical monitoring data further comprises attributes for each event in the plurality of events, the attributes comprising an event type, a trigger time, a severity level, an impact level, and an associated component, and wherein the common event sequences are determined based on matching event attributes between each common event sequence. 15. The computer of claim 9 , wherein the plurality of events in the historical monitoring data are discovered using a component monitoring system. 16. The computer of claim 9 , wherein the computer-readable instructions further cause the computer to perform: accessing a database of predetermined event patterns with associated root cause inferences regarding the particular type of condition; and modifying the event pattern based on the predetermined event patterns. 17. A computer program product comprising: a non-transitory computer-readable storage medium having computer-readable program code embodied therewith, the computer-readable program code comprising: computer-readable program code configured to receive historical monitoring data for components of a system, the historical monitoring data comprising a plurality of events, each triggered by an associated component, and a plurality of alarms, each triggered by detection of a particular type of condition in the components; computer-readable program code configured to determine common event sequences in the plurality of events, each event sequence culminating in one of the plurality of alarms; computer-readable program code configured to correlate the common event sequences into an event pattern; computer-readable program code configured to determine a relationship between a common system component and each component that generated each event in the e

Assignees

Inventors

Classifications

  • Reliability or availability analysis · CPC title

  • by exceeding a count or rate limit, e.g. word- or bit count limit · CPC title

  • in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems · CPC title

  • to enhance reliability, e.g. reduce downtime · CPC title

  • by exceeding limits · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9652316B2 cover?
A method includes receiving historical monitoring data for components of a system, the historical monitoring data comprising a plurality of events, each triggered by an associated component, and a plurality of alarms, each triggered by detection of a particular type of condition in the components. The method also includes determining common event sequences in the plurality of events, each event…
Who is the assignee on this patent?
Gamage Nimal K K, Whitner Richard Bennett, Ca Inc
What technology area does this patent fall under?
Primary CPC classification G06F11/079. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue May 16 2017 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).