Event and alert analysis in a distributed processing system

CROSS-REFERENCE TO RELATED APPLICATION

0001This application is a continuation application of and claims priority from U.S. patent application Ser. No. 14/023,849, filed on Sep. 11, 2013.

BACKGROUND

0002Field of the Invention

0003The field of the invention is data processing, or, more specifically, methods, apparatuses, and computer program products for event and alert analysis in a distributed processing system.

0004Description of Related Art

0005The development of the EDVAC computer system of 1948 is often cited as the beginning of the computer era. Since that time, computer systems have evolved into extremely complicated devices. Today's computers are much more sophisticated than early systems such as the EDVAC. Computer systems typically include a combination of hardware and software components, application programs, operating systems, processors, buses, memory, input/output devices, and so on. As advances in semiconductor processing and computer architecture push the performance of the computer higher and higher, more sophisticated computer software has evolved to take advantage of the higher performance of the hardware, resulting in computer systems today that are much more powerful than just a few years ago.

0006Modern distributed processing systems for intensive computing may have millions of devices with many processes running on each device all of which are capable of error and status reporting for automated error recovery, reporting to a systems administrator, and for other reasons. In many cases, in the case of an error for example, the sheer number of such error reports and status reports are so overwhelming that they cannot be handled in a meaningful manner. For example, a systems administrator receiving a hundred thousand error reports may be overwhelmed by the sheer number of such reports and therefore in the aggregate those reports become more and more unhelpful and irrelevant.

SUMMARY

0007Methods, apparatuses, and computer program products for event and alert analysis are provided. Embodiments include a local event analyzer embedded in an alert analyzer receiving events from an event queue. Embodiments also include the local event analyzer creating, based on the received events and local event analysis rules specific to the alert analyzer, a temporary alert for the alert analyzer. Embodiments also include the alert analyzer analyzing the temporary alert based on alert analysis rules.

0008The foregoing and other objects, features and advantages of the invention will be apparent from the following more particular descriptions of exemplary embodiments of the invention as illustrated in the accompanying drawings wherein like reference numbers generally represent like parts of exemplary embodiments of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

0009<figref idref="DRAWINGS">FIG. 1</figref> illustrates an exemplary system for event and alert analysis in a distributed processing system according to embodiments of the present invention.

0010<figref idref="DRAWINGS">FIG. 2</figref> sets forth a block diagram of automated computing machinery comprising an exemplary computer useful in event and alert analysis in a distributed processing system according to embodiments of the present invention.

0011<figref idref="DRAWINGS">FIG. 3</figref> sets forth a block diagram of an exemplary system for event and alert analysis in a distributed processing system in a distributed processing system according to embodiments of the present invention.

0012<figref idref="DRAWINGS">FIG. 4</figref> sets forth a diagram illustrating assigning events to an events pool according to embodiments of the present invention.

0013<figref idref="DRAWINGS">FIG. 5</figref> sets forth a diagram illustrating assigning alerts to an alerts pool according to embodiments of the present invention.

0014<figref idref="DRAWINGS">FIG. 6</figref> sets forth a flow chart illustrating an example method of event and alert analysis in a distributed processing system according to embodiments of the present invention.

0015<figref idref="DRAWINGS">FIG. 7</figref> sets forth a flow chart illustrating an additional method of event and alert analysis in a distributed processing system according to embodiments of the present invention.

0016<figref idref="DRAWINGS">FIG. 8</figref> sets forth a flow chart illustrating an additional method of event and alert analysis in a distributed processing system according to embodiments of the present invention.

0017<figref idref="DRAWINGS">FIG. 9</figref> sets forth a flow chart illustrating an additional method of event and alert analysis in a distributed processing system according to embodiments of the present invention.

DETAILED DESCRIPTION

0018Exemplary methods, apparatuses, and computer program products for event and alert analysis in a distributed processing system according to embodiments of the present invention are described with reference to the accompanying drawings, beginning with <figref idref="DRAWINGS">FIG. 1</figref>. <figref idref="DRAWINGS">FIG. 1</figref> illustrates an exemplary system for event and alert analysis in a distributed processing system (<b>101</b>) according to embodiments of the present invention. A distributed processing system is typically implemented as multiple autonomous or semi-autonomous computers that communicate through a computer network. In such example distributed processing systems, the computers often interact with each other in order to achieve a common goal. A computer program that runs in such an example distributed system is typically called a distributed program, and distributed programming is often used to describe the process of writing such programs.

0019In the example of <figref idref="DRAWINGS">FIG. 1</figref>, the distributed processing system (<b>101</b>) is implemented as a parallel computer (<b>100</b>), non-volatile memory for the computer in the form of data storage device (<b>118</b>), an output device for the computer in the form of a printer (<b>120</b>), and an input/output device for the computer in the form of a computer terminal (<b>122</b>). The parallel computer (<b>100</b>) in the example of <figref idref="DRAWINGS">FIG. 1</figref> includes a plurality of compute nodes (<b>102</b>). Each compute node is an automated computing device composed of one or more computer processors, its own computer memory, and its own input/output functionality. The compute nodes (<b>102</b>) are coupled for data communications by several independent data communications networks including a high speed Ethernet network (<b>174</b>), a Joint Test Action Group (‘JTAG’) network (<b>104</b>), a collective or tree network (<b>106</b>) which is optimized for collective operations, and a torus network (<b>108</b>) which is optimized for point to point operations. The tree network (<b>106</b>) is a data communications network that includes data communications links connected to the compute nodes so as to organize the compute nodes as a tree. Each data communications network is implemented with data communications links among the compute nodes (<b>102</b>). The data communications links provide data communications for parallel operations among the compute nodes of the parallel computer (<b>100</b>).

0020In addition to the compute nodes (<b>102</b>), the parallel computer (<b>100</b>) includes input/output (‘I/O’) nodes (<b>110</b>, <b>114</b>) coupled to the compute nodes (<b>102</b>) through the high speed Ethernet network (<b>174</b>). The I/O nodes (<b>110</b>, <b>114</b>) provide I/O services between the compute nodes (<b>102</b>) and I/O devices, which in this example is the data storage device (<b>118</b>), the printer (<b>120</b>) and the terminal (<b>122</b>). The I/O nodes (<b>110</b>, <b>114</b>) are connected for data communications through a local area network (‘LAN’) (<b>130</b>). The parallel computer (<b>100</b>) also includes a service node (<b>116</b>) coupled to the compute nodes (<b>102</b>) through the JTAG network (<b>104</b>). The service node (<b>116</b>) provides service common to the compute nodes (<b>102</b>), such as loading programs into the compute nodes (<b>102</b>), starting program execution on the compute nodes (<b>102</b>), retrieving results of program operations on the compute nodes (<b>102</b>), and so on. The service node (<b>116</b>) runs an event and alert analysis module (<b>124</b>) and communicates with a system administrator (<b>128</b>) through a service application interface (<b>126</b>) that runs on the computer terminal (<b>122</b>).

0021Many of the components of the distributed processing system of <figref idref="DRAWINGS">FIG. 1</figref>, that is the devices of the distributed processing system or processes running on the devices of the distributed processing system of <figref idref="DRAWINGS">FIG. 1</figref>, are capable of some form of error or status reporting through events and many of such components are also capable of receiving alerts in response to one or more of such events. Often in distributed processing systems hundreds of thousands or millions of components may provide or receive incidents, often in the form of events or alerts.

0022An incident is a generic term used in this specification to mean an identification or notification of a particular occurrence on a component of a distributed processing system such as events described below, a refined identification of an occurrence often based on events such as an alert described below, or other notifications as will occur to those of skill in the art.

0023Incidents are administered in pools for event and alert analysis according to embodiments of the present invention. A pool of incidents is a collection of incidents organized by the time of either their occurrence, by the time they are logged in an incident queue, included in the pool, or other time as will occur to those of skill in the art. Such incident pools often provide the ability to analyze a group of time related incidents. Often such incident pools are useful in identifying fewer and more relevant incidents in dependence upon multiple related incidents.

0024An event according to embodiments of the present invention is a notification of a particular occurrence in or on a component of the distributed processing system. Such events are sent from the component upon which the occurrence occurred or another reporting component to an event and alert analysis module according to the present invention. Often events are notifications of errors occurring in a component of the data processing system. Events are often implemented as messages either sent through a data communications network or shared memory. Typical events for event and alert analysis according to embodiments of the present invention include attributes such as an occurred time, a logged time, an event type, an event ID, a reporting component, and a source component, and other attributes.

0025An alert according to embodiments of the present invention is a refined identification of an occurrence, such as an error, based upon more than one event and therefore provides an identification of the occurrence in the context of its operation in the distributed processing system. Often an alert may be a notification of a particular error type of occurrence that is identified in dependence upon the plurality of events received from one or more components of the data processing system, such as, for example, a link failure among a plurality of devices each of which are producing many events based upon the single link failure, or a power failure provoking thousands of events, and so on.

0026Alerts are often implemented as messages to be sent through a data communications network or shared memory. Typical alerts according to embodiments of the present invention have attributes attached to them based upon the attributes of the events received from which they are identified.

0027The event and alert analysis module (<b>124</b>) includes at least two incident analyzers implemented as an event analyzer and an alert analyzer capable of event and alert analysis in a distributed processing system according to embodiments of the present invention. The event and alert analysis module (<b>124</b>) is also implemented as a monitor and checkpoint manager for managing the checkpoints from the incident analyzers.

0028Specifically, the event and alert analysis module (<b>124</b>) is implemented as automated computing machinery configured to include a local event analyzer embedded in an alert analyzer. The local event analyzer is configured to receive events from an event queue. The local event analyzer creates based on the received events and local event analysis rules specific to the alert analyzer, a temporary alert for the alert analyzer. The alert analyzer is configured to analyze the temporary alert based on alert analysis rules.

0029The arrangement of nodes, networks, and I/O devices making up the exemplary distributed processing system illustrated in <figref idref="DRAWINGS">FIG. 1</figref> are for explanation only, not for limitation of the present invention. Distributed data processing systems configured to perform event and alert analysis according to embodiments of the present invention may include additional nodes, networks, devices, and architectures, not shown in <figref idref="DRAWINGS">FIG. 1</figref>, as will occur to those of skill in the art. The parallel computer (<b>100</b>) in the example of <figref idref="DRAWINGS">FIG. 1</figref> includes sixteen compute nodes (<b>102</b>). Parallel computers configured to perform event and alert analysis according to embodiments of the present invention sometimes include thousands of compute nodes. In addition to Ethernet, JTAG, collective, and point to point, networks in such data processing systems may support many data communications protocols including for example TCP (Transmission Control Protocol), IP (Internet Protocol), and others as will occur to those of skill in the art. Various embodiments of the present invention may be implemented on a variety of hardware platforms in addition to those illustrated in <figref idref="DRAWINGS">FIG. 1</figref>.

0030Event and alert analysis in a distributed processing system in accordance with the present invention is generally implemented with computers, that is, with automated computing machinery. In the system of <figref idref="DRAWINGS">FIG. 1</figref>, for example, all the service nodes, I/O nodes, compute nodes, of the parallel computer are implemented to some extent at least as computers. For further explanation, therefore, <figref idref="DRAWINGS">FIG. 2</figref> sets forth a block diagram of automated computing machinery comprising an exemplary computer (<b>252</b>) useful in performing event and alert analysis according to embodiments of the present invention. The computer (<b>252</b>) of <figref idref="DRAWINGS">FIG. 2</figref> includes at least one computer processor (<b>256</b>) or ‘CPU’ as well as random access memory (<b>268</b>) (‘RAM’) which is connected through a high speed memory bus (<b>266</b>) and bus adapter (<b>258</b>) to processor (<b>256</b>) and to other components of the computer (<b>252</b>) and through an expansion bus to adapters for communications with other components of a distributed processing system (<b>101</b>).

0031Stored in RAM (<b>268</b>) is an event and alert analysis module (<b>124</b>), a module of automated computing machinery for performing event and alert analysis according to embodiments of the present invention. The event and alert analysis module (<b>124</b>) includes two incident analyzers, a monitor (<b>204</b>), and a checkpoint manager (<b>299</b>) according to embodiments of the present invention.

0032The checkpoint manager (<b>299</b>) performs event and alert analysis according to embodiments of the present invention by processing checkpoints from the incident analyzers. The monitor (<b>204</b>) is configured to perform event and alert analysis in a distributed processing system according to embodiments of the present invention. In the example of <figref idref="DRAWINGS">FIG. 2</figref>, the monitor (<b>204</b>) receives events from components of the distributed processing system and puts the received events in an event queue. The monitor (<b>204</b>) of <figref idref="DRAWINGS">FIG. 2</figref> may receive events from components of the distributed processing system on their motion, may periodically poll one or more of the components of the distributed processing system, or receive events from components in other ways as will occur to those of skill in the art.

0033The incident analyzers include an event analyzer (<b>208</b>) and an alert analyzer (<b>218</b>). The event analyzer of <figref idref="DRAWINGS">FIG. 2</figref> is a module of automated computing machinery capable of identifying alerts in dependence upon received events. That is, event analyzers typically receive events and produce alerts. In many embodiments, event analyzers are implemented in parallel. Often such event analyzers are assigned to a particular pool of events and may be focused on events from a particular component or caused by a particular occurrence to produce a more concise set of alerts.

0034The alert analyzer (<b>218</b>) of <figref idref="DRAWINGS">FIG. 2</figref> is a module of automated computing machinery capable of identifying alerts for transmission from events and other alerts, identifying additional alerts for transmission, and suppressing unnecessary, irrelevant, or otherwise unwanted alerts identified by the event analyzer. That is, alert analyzers typically receive alerts and events and produce or forward alerts in dependence upon those alerts and events. In many embodiments, alert analyzers are implemented in parallel. Often such alert analyzers are assigned to a particular pool of alerts and may be focused on alerts with particular attributes to produce a more concise set of alerts.

0035In addition to the general functions described above, the event and alert analysis module (<b>124</b>) may be configured to perform event and alert analysis in a distributed processing system according to embodiments of the present invention. Specifically, the event and alert analysis module (<b>124</b>) is implemented as automated computing machinery configured to include a local event analyzer embedded in an alert analyzer. The local event analyzer is configured to receive events from an event queue. The local event analyzer creates based on the received events and local event analysis rules specific to the alert analyzer, a temporary alert for the alert analyzer. The alert analyzer is configured to analyze the temporary alert based on alert analysis rules.

0036Also stored in RAM (<b>268</b>) is an operating system (<b>254</b>). Operating systems useful for relevant alert delivery according to embodiments of the present invention include UNIX™, Linux™, Microsoft XP™, AIX™, IBM's i5/OS™, and others as will occur to those of skill in the art. The operating system (<b>254</b>), event and alert analysis module (<b>124</b>), the event analyzer (<b>208</b>), the alert analyzer (<b>218</b>) in the example of <figref idref="DRAWINGS">FIG. 2</figref> are shown in RAM (<b>268</b>), but many components of such software typically are stored in non-volatile memory also, such as, for example, on a disk drive (<b>270</b>).

0037The computer (<b>252</b>) of <figref idref="DRAWINGS">FIG. 2</figref> includes disk drive adapter (<b>272</b>) coupled through expansion bus (<b>260</b>) and bus adapter (<b>258</b>) to processor (<b>256</b>) and other components of the computer (<b>252</b>). The disk drive adapter (<b>272</b>) connects non-volatile data storage to the computer (<b>252</b>) in the form of disk drive (<b>270</b>). Disk drive adapters useful in computers for event and alert analysis according to embodiments of the present invention include Integrated Drive Electronics (‘IDE’) adapters, Small Computer System Interface (‘SCSI’) adapters, and others as will occur to those of skill in the art. Non-volatile computer memory also may be implemented for as an optical disk drive, electrically erasable programmable read-only memory (so-called ‘EEPROM’ or ‘Flash’ memory), RAM drives, and so on, as will occur to those of skill in the art.

0038The example computer (<b>252</b>) of <figref idref="DRAWINGS">FIG. 2</figref> includes one or more input/output (‘I/O’) adapters (<b>278</b>). I/O adapters implement user-oriented input/output through, for example, software drivers and computer hardware for controlling output to display devices such as computer display screens, as well as user input from user input devices (<b>281</b>) such as keyboards and mice. The example computer (<b>252</b>) of <figref idref="DRAWINGS">FIG. 2</figref> includes a video adapter (<b>209</b>), which is an example of an I/O adapter specially designed for graphic output to a display device (<b>180</b>) such as a display screen or computer monitor. The video adapter (<b>209</b>) is connected to processor (<b>256</b>) through a high speed video bus (<b>264</b>), bus adapter (<b>258</b>), and the front side bus (<b>262</b>), which is also a high speed bus.

0039The exemplary computer (<b>252</b>) of <figref idref="DRAWINGS">FIG. 2</figref> includes a communications adapter (<b>267</b>) for data communications with other computers (<b>282</b>) and for data communications with a data communications network (<b>200</b>). Such data communications may be carried out serially through RS-232 connections, through external buses such as a Universal Serial Bus (‘USB’), through data communications data communications networks such as IP data communications networks, and in other ways as will occur to those of skill in the art. Communications adapters implement the hardware level of data communications through which one computer sends data communications to another computer, directly or through a data communications network. Examples of communications adapters useful for event and alert analysis according to embodiments of the present invention include modems for wired dial-up communications, Ethernet (IEEE 802.3) adapters for wired data communications network communications, and 802.11 adapters for wireless data communications network communications.

0040For further explanation, <figref idref="DRAWINGS">FIG. 3</figref> sets forth a block diagram of an exemplary system for event and alert analysis and relevant alert delivery in a distributed processing system (<b>102</b>) according to embodiments of the present invention. The system of <figref idref="DRAWINGS">FIG. 3</figref> includes an event and alert analysis module (<b>124</b>). The event and alert analysis module (<b>124</b>) of <figref idref="DRAWINGS">FIG. 3</figref> receives in an event queue (<b>306</b>) a plurality of events (<b>302</b>) from one or more components of a distributed processing system (<b>102</b>). A component of a distributed processing system according to embodiments of the present invention may be a device of the distributed processing system or a process running on a device of the distributed processing. Such components are often capable of some form of event transmission, often for error or status reporting.

0041An event according to embodiments of the present invention is a notification of a particular occurrence in or on a component of the distributed processing system. Such events are sent from the component upon which the occurrence occurred or another reporting component to an event and alert analysis module according to the present invention. Often events are notifications of errors occurring in a component of the data processing system. Events are often implemented as messages either sent through a data communications network or shared memory. Typical events for event and alert analysis according to embodiments of the present invention include attributes such as an occurred time, a logged time, an event type, an event ID, a reporting component, and a source component, and other attributes. An occurred time is the time at which the event occurred on the component. A logged time is the time the event was included in the event queue (<b>306</b>) and is typically inserted into the event by a monitor. An event type is a generic type of event such as for example, power error, link failure error, errors related to not receiving messages or dropping packets and so on as will occur to those of skill in the art. An event ID is a unique identification of the event. A reporting component is an identification of the component that reported the event. A source component is an identification of the component upon which the event occurred. In many cases, but not all, the reporting component and source component are the same component of the distributed processing system.

0042The event and analysis module (<b>124</b>) of <figref idref="DRAWINGS">FIG. 3</figref> also includes a checkpoint manager (<b>299</b>) that is configured to perform event and alert analysis in a distributed processing system according to embodiments of the present invention. In the example of <figref idref="DRAWINGS">FIG. 3</figref>, the monitor (<b>204</b>) receives events from components of the distributed processing system and puts the received events (<b>302</b>) in the event queue (<b>306</b>). The monitor (<b>204</b>) of <figref idref="DRAWINGS">FIG. 3</figref> may receive events from components of the distributed processing system on their motion, may periodically poll one or more of the components of the distributed processing system, or receive events from components in other ways as will occur to those of skill in the art.

0043The system of <figref idref="DRAWINGS">FIG. 3</figref> also includes an event analyzer (<b>208</b>). The event analyzer (<b>208</b>) of <figref idref="DRAWINGS">FIG. 3</figref> is a module of automated computing machinery configured to identify alerts in dependence upon received events. That is, event analyzers typically receive events and produce alerts. In many embodiments, multiple event analyzers are implemented in parallel. Often event analyzers are assigned to a particular pool of events and may be focused on events from a particular component or caused by a particular occurrence to produce a more concise set of alerts.

0044As mentioned above, in some embodiments of the present invention, more than one event analyzer may operate in parallel. As such, each event analyzer may maintain one or more events pools for performing event and alert analysis according to embodiments of the present invention. Assigning by the event analyzer the events to an events pool may therefore include selecting only events from one or more particular components. In such embodiments, particular components may be selected for a particular events pool to provide events associated with a particular period of time from a particular set of one or more components.

0045Assigning by the event analyzer the events to an events pool may also be carried out by selecting only events of a particular event type. In such embodiments, particular events may be selected for a particular events pool to provide events associated with a particular period of time from a particular set of event types. The event analyzer (<b>208</b>) in the example of <figref idref="DRAWINGS">FIG. 3</figref> identifies in dependence upon the event analysis rules (<b>310</b>) and the events assigned to the events pool, one or more alerts (<b>314</b>). Event analysis rules (<b>310</b>) are a collection of predetermined rules for meaningfully parsing received events to identify relevant alerts in dependence upon the events.

0046The event analysis rules (<b>310</b>) of <figref idref="DRAWINGS">FIG. 3</figref> include event arrival rules (<b>330</b>), events pool operation rules (<b>332</b>), event suppression rules (<b>334</b>), and events pool closure rules (<b>336</b>). The event arrival rules (<b>330</b>) are configurable predetermined rules for identifying alerts in dependence upon events in real time as those events are assigned to the events pool. That is, the event arrival rules (<b>330</b>) identify alerts in dependence upon events before closing the events pool. Such rules are typically predetermined to identify particular alerts in dependence upon attributes of those events. Event arrival rules may for example dictate identifying a particular predetermined alert for transmission to a systems administrator in dependence upon a particular event type or component type for the event or other attribute of that event. Such rules are flexible and may be tailored to a particular distributed computing system and its functions.

0047An alert according to embodiments of the present invention is a refined identification of an occurrence, such as an error based upon more than one event, and therefore provides an identification of the occurrence in the context of its operation in the distributed processing system. Often an alert may be a notification of a particular error type of occurrence that is identified in dependence upon the plurality of events received from one or more components of the data processing system, such as, for example, a link failure among a plurality of devices each of which are producing many events based upon the single link failure, or a power failure provoking thousands of events, and so on.

0048Alerts are often implemented as messages to be sent through a data communications network or shared memory. Typical alerts according to embodiments of the present invention have attributes attached to them based upon the attributes of the events received from which they are identified.

0049The events pool operation rules (<b>332</b>) are configurable predetermined rules for controlling the operations of the events pool. Such rules includes rules identifying the initial predetermined period of time for each events pool, rules dictating the length of time extended to the pool upon the assignment of each new event to the pool, rules dictating the minimum time an event must be in a pool before that event is included in a collection of events when the pool is closed, rules dictating the amount to extend the initial predetermined period of time based on an arrival rate of events assigned to an events pool, rules governing the closing of an events pool, and others as will occur to those of skill in the art. Such rules are flexible and may be tailored to a particular distributed computing system and its functions.

0050The event suppression rules (<b>334</b>) are configurable predetermined rules for suppressing one or more events in a closed pool of events used in identifying alerts. That is, often events in the closed events pool may be duplicate events, redundant events, or otherwise unnecessary or unhelpful events in identifying alerts. Such suppression rules are typically predetermined to delete, drop, or otherwise ignore those suppressed events. Event suppression rules may for example dictate that more than a threshold number of events of a particular event type or component type are to be suppressed. Such rules are also flexible and may be tailored to a particular distributed computing system and its functions.

0051The events pool closure rules (<b>336</b>) are configurable predetermined rules for identifying alerts in dependence upon unsuppressed events in the closed events pool and alerts identified by the event arrival rules. That is, events pool closure rules identify new alerts in dependence upon one or more or even all of the unsuppressed events in the closed events pool. The events pool closure rules also identify alerts in dependence upon the alerts identified by the event arrival rules (<b>330</b>) or a combination of the alerts identified by the event arrival rules (<b>330</b>) and one or more of the unsuppressed events in the closed events pool.

0052The event analyzer (<b>208</b>) in the example of <figref idref="DRAWINGS">FIG. 3</figref> sends all the alerts (<b>314</b>) identified by the event analyzer (<b>208</b>) to an alert analyzer (<b>218</b>). The alert analyzer of <figref idref="DRAWINGS">FIG. 3</figref> is a module of automated computing machinery capable of identifying alerts for transmission from events and other alerts, identifying additional alerts for transmission, and suppressing unnecessary, irrelevant, or otherwise unwanted or unhelpful alerts identified by the event analyzer. That is, alert analyzers typically receive alerts and events and produce or forward alerts in dependence upon those alerts and events. In many embodiments, alert analyzers are implemented in parallel. The alerts (<b>316</b>) in the example of <figref idref="DRAWINGS">FIG. 3</figref> are sent from the event analyzer (<b>208</b>) to the alert analyzer (<b>218</b>) through an alerts queue (<b>316</b>).

0053The alert analyzer (<b>218</b>) of <figref idref="DRAWINGS">FIG. 3</figref> assigns each of the identified alerts (<b>314</b>) to an alerts pool (<b>324</b>). An alerts pool is a collection of alerts organized by the time of one or more the events causing the alert to be identified, the time the alert is identified, or other time as will occur to those of skill in the art. That is, alerts pools are a collection of alerts organized by time. Such alerts pools often provide the ability to analyze groups alerts identified and included in the alerts pool according to some time. Often such alerts pools are useful in identifying fewer and more relevant alerts in dependence upon multiple related events and multiple related alerts.

0054The alert analyzer (<b>218</b>) of <figref idref="DRAWINGS">FIG. 3</figref> determines in dependence upon alert analysis rules (<b>322</b>) and the alerts in the alerts pool whether to suppress any alerts. Suppressing an alert is typically carried out by dropping the alert, deleting the alert or otherwise ignoring or not transmitting the suppressed alert to a component of the distributed processing system.

0055The alert analysis rules (<b>322</b>) are a collection of rules for suppressing one or more alerts to provide a more relevant set of alerts for transmission to a component of the distributed processing system, such as for example, for display to a systems administrator and to identify additional alerts for transmission to one or more components of the distributed processing system. Alert analysis rules for example may dictate that duplicate alerts are to be suppressed, alerts of a particular type for transmission to a particular component are to be suppressed, alerts of a particular type be transmitted to a particular component are to be suppressed and so on as will occur to those of skill in the art. Such alerts may be more meaningful to a component of the distributed processing system for automated error recovery or for a systems administrator who may otherwise be less informed by a number of raw unanalyzed alerts.

0056The alert analyzer (<b>218</b>) of <figref idref="DRAWINGS">FIG. 3</figref> also has access to the events queue (<b>306</b>). The alert analyzer (<b>218</b>) of <figref idref="DRAWINGS">FIG. 3</figref> in dependence upon the alert analysis rules may, in some embodiments select events from the events queue and determine whether to suppress any alerts in dependence upon the selected events. That is, alert analysis rules may also take into account events and their attributes for suppressing alerts and for identifying additional alerts for transmission to one or more components. Such events may be related to the alerts in the alerts pool or independent from such alerts.

0057The alert analyzer (<b>218</b>) of <figref idref="DRAWINGS">FIG. 3</figref> transmits the unsuppressed alerts to one or more components of the distributed processing system. The alert analyzer may transmit the unsuppressed alerts to one or more components of the distributed processing system by sending the alert as a message across a data communications network, through shared memory, or in other ways as will occur to those of skill in the art. In the example of <figref idref="DRAWINGS">FIG. 3</figref>, the unsuppressed alerts (<b>320</b>) are transmitted to the terminal (<b>122</b>) for display to the systems administrator (<b>128</b>).

0058The alert analyzer (<b>218</b>) of <figref idref="DRAWINGS">FIG. 3</figref> is also configured to identify in dependence upon alert analysis rules (<b>322</b>), the alerts in the alerts pool (<b>324</b>), and selected events (<b>306</b>) one or more additional alerts and transmitting the one or more components of the distributed processing system. The additional alerts may include one or more alerts not identified by the event analyzer. Such additional alerts may provide additional information to a component of the distributed processing system of a systems administrator.

0059The alert analyzer (<b>218</b>) of <figref idref="DRAWINGS">FIG. 3</figref> also includes a local event analyzer (<b>399</b>) embedded in the alert analyzer (<b>218</b>). The local event analyzer (<b>399</b>) is configured to receive events from the event queue (<b>306</b>) and create based on the received events and local event analysis rules specific to the alert analyzer (<b>218</b>), a temporary alert for the alert analyzer (<b>218</b>). The alert analyzer (<b>218</b>) is configured to analyze the temporary alert based on the alert analysis rules (<b>322</b>).

0060In the system of <figref idref="DRAWINGS">FIG. 3</figref>, events (<b>302</b>) are received and analyzed by event analyzers (<b>208</b>) with event analysis rules (<b>310</b>). Based on the event analysis rules (<b>310</b>), the event analyzers (<b>208</b>) generate the alerts (<b>314</b>). These alerts may be sent to a delivery queue (<b>399</b>) for immediate delivery to the system administrator (<b>128</b>) and the distributed processing system (<b>102</b>). These alerts may also be sent to alert analyzers (<b>218</b>) for further processing and generation of additional alerts (<b>320</b>), which may also be provided to the delivery queue (<b>399</b>). The event and alert analysis module (<b>124</b>) also includes an alert database (<b>397</b>) for recording alerts that have generated by the event and alert analysis module (<b>124</b>).

0061The event and alert analysis module (<b>124</b>) is also configured to receive a plurality of events from one or more components of the distributed processing system and determine that an arrival attribute of the plurality of events exceeds an arrival threshold. The event and alert analysis module is also configured to adjust, in response to determining that the arrival attribute of the plurality of events exceeds the arrival threshold, a clock speed of at least one of the event and alert analysis module and a component of the distributed processing system.

0062As mentioned above, event and alert analysis according to embodiments of the present invention may include assigning events to an events pool and those pools are administered according to embodiments of the present invention. For further explanation, <figref idref="DRAWINGS">FIG. 4</figref> sets forth a diagram illustrating assigning events to an events pool according to embodiments of the present invention. An events pool (<b>312</b>) is a collection of events organized by the time of either their occurrence, by the time they are logged in the event queue, included in the events pool, or other time as will occur to those of skill in the art. That is, events pools are a collection of events organized by time. Such events pools often provide the ability to analyze a group of time related events and to identify alerts in dependence upon them. Often such events pools are useful in identifying fewer and more relevant alerts in dependence upon multiple related events.

0063Events pools according to embodiments of the present invention are typically operated according to events pool operation rules which are themselves often included in event analysis rules. Such events pool operation rules are configurable predetermined rules for controlling the operations of the events pool. Such rules includes rules identifying the initial predetermined period of time for each events pool, rules dictating the length of time extended to the pool upon the assignment of each new event to the pool, rules dictating the minimum time an event must be in a pool before that event is included in a collection of events when the pool is closed, rules dictating the amount to extend the initial predetermined period of time based on an arrival rate of events assigned to an events pool, rules governing the closing of an events pool, and others as will occur to those of skill in the art. Such rules are flexible and may be tailored to a particular distributed computing system and its functions.

0064Events are often assigned to an events pool according to their logged time. That is, events are typically inserted into the events pool in the order that they are received in the event queue. In the example of <figref idref="DRAWINGS">FIG. 4</figref>, the timing of the events pool (<b>312</b>) is initiated when the first event ‘Event 0’ (<b>400</b>) is assigned to the events pool (<b>312</b>) at time t₀. The events pool of <figref idref="DRAWINGS">FIG. 4</figref> is initiated for a predetermined initial period of time from t₁to t_f. That is, upon receiving the first event ‘Event 0’ (<b>400</b>) the events pool of <figref idref="DRAWINGS">FIG. 4</figref> has a predetermined initial period of time beginning at t₁and ending at t_f. The predetermined initial period of time may be configured in dependence upon a number of factors as will occur to those of skill in the art such as, the number of components in the distributed processing system, the frequency of receiving events, the types of events typically received and so on as will occur to those of skill in the art.

0065In the example <figref idref="DRAWINGS">FIG. 4</figref>, the initial period of time is extended for each new event assigned to the events pool during the predetermined initial period from t₁to t_fby a particular period of time assigned to the event. In the example of <figref idref="DRAWINGS">FIG. 4</figref> upon assigning ‘Event 1’ (<b>402</b>) to the events pool (<b>312</b>) the predetermined initial period of time t₀-t_fis extended by ‘Extension 1’ (<b>406</b>) having a time of e1 thereby creating a new time for closing the events pool (<b>312</b>) at t_f+e1if no other events are assigned to the pool before t_f+e1. Similarly, in the example of <figref idref="DRAWINGS">FIG. 4</figref> upon assigning ‘Event 2’ (<b>404</b>) to the events pool having a time of e2, the now extended period of time from t₀-t_f+e1is extended again by extension 2 (<b>408</b>) thereby establishing a new time for closing the pool at time t_f+e1+e2if no other events are assigned to the pool before t_f+e1+e2or before some maximum time for the events pool has expired. In this manner, the events pool is extended with each received event until a collection of events that may be usefully used to identify alerts is assigned to the events pool. According to embodiments of the present invention, the predetermined initial period of time may be extended based on an arrival rate at which events are assigned to an events pool.

0066In typical embodiments of the present invention, events pools may have a maximum duration that can no longer be extended. In such cases, a requirement may exist that an event that has not resided in the events pool for a threshold period of time be moved to a next events pool. In some embodiments, the attributes of such an event that is moved to the next events pool are used for relevant alert delivery with the initial events pool and in other embodiments; the attributes of such an event are used for relevant alert delivery with the next events pool to which that event is moved.

0067In the example of <figref idref="DRAWINGS">FIG. 4</figref>, when conditions are met to close the pool an events analyzer determines for each event (<b>400</b>, <b>402</b>, <b>404</b>) in the events pool (<b>312</b>) whether the event has been in the pool for its predetermined minimum time for inclusion in a pool. If the event has been in the pool for its predetermined minimum time, the event is included in the closed pool for event analysis for relevant alert delivery. If the event has not been in the pool for its predetermined minimum time, the event is evicted from the closed pool and included a next pool for event analysis for relevant alert delivery.

0068In many embodiments, a plurality of events pools may be used in parallel and one or more of such events pools are assigned to a particular events analyzer. In such embodiments, events analyzers may be directed to events in events pools having particular attributes.

0069As mentioned above, event and alert analysis according to embodiments of the present invention may include assigning alerts to an alerts pool and those pools are administered according to embodiments of the present invention. For further explanation, <figref idref="DRAWINGS">FIG. 5</figref> sets forth a diagram illustrating assigning alerts to an alerts pool according to embodiments of the present invention. The alerts pool (<b>324</b>) of <figref idref="DRAWINGS">FIG. 5</figref> operates in a manner similar to the events pool of <figref idref="DRAWINGS">FIG. 4</figref>. That is, the alerts pool according to the example of <figref idref="DRAWINGS">FIG. 5</figref> includes alerts and the timing of the alerts pool begins with the first alert ‘Alert 0’ (<b>500</b>) at time t₀and is configured to have a predetermined initial period of time t₀-tf. In the example of <figref idref="DRAWINGS">FIG. 5</figref>, the initial period of time is extended for each new alert assigned to the alerts pool in the predetermined initial period from t₁to t_fby a particular period of time assigned to the alert. In the example of <figref idref="DRAWINGS">FIG. 5</figref>, upon assigning ‘Alert 1’ (<b>502</b>) to the alerts pool (<b>324</b>) the predetermined initial period of time t₀-t_fis extended by ‘Extension 1’ (<b>506</b>) having a time of e1 thereby creating a new time for closing the alerts pool (<b>324</b>) at t_f+e1if no other alerts are assigned to the pool before t_f+e1. Similarly, in the example of <figref idref="DRAWINGS">FIG. 5</figref> upon assigning ‘Alert 2’ (<b>504</b>) to the alerts pool having a time of e2, the now extended period of time from t₀-t_f+e1is extended again by ‘Extension 2’ (<b>508</b>) thereby establishing a new time for closing the pool at time t_f+e1+e2if no other alerts are assigned to the pool before t_f+e1+e2or before some maximum time for the alerts pool has expired. According to embodiments of the present invention, the predetermined initial period of time may be extended based on an arrival rate at which alerts are assigned to an alerts pool.

0070In typical embodiments of the present invention, alerts pools may have a maximum duration that can no longer be extended. In such cases, a requirement may exist that an alert that has not resided in the alerts pool for a threshold period of time be moved to a next alerts pool. In some embodiments, the attributes of such an alert that is moved to the next alerts pool are used for relevant alert delivery according to embodiments of the present invention with the initial alerts pool and in other embodiments, the attributes of such an alert are used for relevant alert delivery with the next alerts pool to which that alert is moved.

0071In the example of <figref idref="DRAWINGS">FIG. 5</figref>, when conditions are met to close the pool an alerts analyzer determines for each alert (<b>500</b>, <b>502</b>, <b>504</b>) in the pool (<b>324</b>) whether the alert has been in the pool for its predetermined minimum time for inclusion in a pool. If the alert has been in the pool for its predetermined minimum time, the alert is included in the closed pool for alert analysis for relevant alert delivery according to embodiments of the present invention. If the alert has not been in the pool for its predetermined minimum time, the alert is evicted from the closed pool and included a next pool for alert analysis for relevant alert delivery according to embodiments of the present invention.

0072In many embodiments, a plurality of alerts pools may be used in parallel and one or more of such alerts pools are assigned to a particular alerts analyzer. In such embodiments, alerts analyzers may be directed to alerts in alerts pools having particular attributes.

0073As mentioned above, event and alert analysis according to embodiments of the present invention may include the administration of one or more pools of incidents such as events, alerts or other incidents as will occur to those of skill in the art. For further explanation, <figref idref="DRAWINGS">FIG. 6</figref> sets forth a flow chart illustrating an example method of performing event and alert analysis for incident analysis in a distributed processing system in a distributed processing system according to embodiments of the present invention. The method of <figref idref="DRAWINGS">FIG. 6</figref> includes receiving (<b>602</b>) in an event queue a plurality of events (<b>302</b>) from one or more components of a distributed processing system. Attributes of events useful in performing event and alert analysis for incident analysis in a distributed processing system according to embodiments of the present invention may include an occurred time, a logged time, an event type, an event ID, a reporting component, and a source component.

0074Receiving (<b>602</b>) in an event queue a plurality of events (<b>302</b>) from one or more components of a distributed processing system may be carried out by receiving an event initiated by one or more components of the data processing system and storing the event in the event queue according to the time in which the event occurred or according to the time the event was received. Receiving (<b>602</b>) in an event queue a plurality of events (<b>302</b>) from one or more components of a distributed processing system also may be carried out by polling a component for status and receiving in response an event and storing the event in the event queue according to the time in which the event occurred or according to the time the event was received.

0075The method of <figref idref="DRAWINGS">FIG. 6</figref> also includes assigning (<b>604</b>) by an event analyzer each received event to an events pool (<b>312</b>). In some embodiments of the present invention, assigning (<b>604</b>) by an event analyzer each received event (<b>302</b>) to an events pool (<b>312</b>) may be carried out by assigning (<b>632</b>) events to the events pool according to the logged time. Assigning (<b>604</b>) by an event analyzer each received event (<b>302</b>) to an events pool (<b>312</b>) may also be carried out in dependence upon attributes of the event. Such attributes may include an identification or type of the component upon which an occurrence occurred to create the event, the reporting component of the event, the event ID, the event type, and so on as will occur to those of skill in the art.

0076An events pool according to the method of <figref idref="DRAWINGS">FIG. 6</figref> includes events occurring during a predetermined initial period of time and in the example of <figref idref="DRAWINGS">FIG. 6</figref> assigning (<b>604</b>) by the event analyzer each received event to an events pool includes extending (<b>626</b>) for each event assigned to the events pool the predetermined initial period of time by a particular period of time assigned to the event.

0077The event analyzer includes event analysis rules (<b>310</b>) including, event arrival rules, events pool operation rules, event suppression rules, and events pool closure rules. Event arrival rules are configurable predetermined rules for identifying alerts in dependence upon events in real time as those events are assigned to the events pool. That is, event arrival rules identify alerts in dependence upon events before closing the events pool. Such rules are flexible and may be tailored to a particular distributed computing system and its functions.

0078An alert according to embodiments of the present invention is a refined identification of an occurrence, such as an error based upon more than one event, and therefore provides an identification of the occurrence in the context of its operation in the distributed processing system. Often an alert may be a notification of a particular error type of occurrence that is identified in dependence upon the plurality of events received from one or more components of the data processing system, such as, for example, a link failure among a plurality of devices each of which are producing many events based upon the single link failure, or a power failure provoking thousands of events, and so on.

0079Alerts are often implemented as messages to be sent through a data communications network or shared memory. Typical alerts according to embodiments of the present invention have attributes attached to them based upon the attributes of the events received from which they are identified.

0080Events pool operation rules are configurable predetermined rules for controlling the operations of the events pool. Such rules includes rules identifying the initial predetermined period of time for each events pool, rules dictating the length of time extended to the pool upon the assignment of each new event to the pool, rules dictating the minimum time an event must be in a pool before that event is included in a collection of events when the pool is closed, rules governing the closing of an events pool, and others as will occur to those of skill in the art. Such rules are flexible and may be tailored to a particular distributed computing system and its functions.

0081Event suppression rules are configurable predetermined rules for suppressing one or more events in a closed pool of events used in identifying alerts. That is, often events in the closed events pool may be duplicate events, redundant events, or otherwise unnecessary or unhelpful events in identifying alerts. Such suppression rules are typically predetermined to delete, drop, or otherwise ignore those suppressed events. Event suppression rules may for example dictate that more than a threshold number of events of a particular event type or component type are to be suppressed. Such rules are also flexible and may be tailored to a particular distributed computing system and its functions.

0082Events pool closure rules are configurable predetermined rules for identifying alerts in dependence upon unsuppressed events in the closed events pool and alerts identified by the event arrival rules. That is, events pool closure rules identify new alerts in dependence upon one or more or even all of the unsuppressed events in the closed events pool. The events pool closure rules also identify alerts in dependence upon the alerts identified by the event arrival rules or a combination of the alerts identified by the event arrival rules and one or more of the unsuppressed events in the closed events pool.

0083The method of <figref idref="DRAWINGS">FIG. 6</figref> also includes identifying (<b>610</b>) by the event analyzer in dependence upon the event arrival rules and the events assigned to the events pool one or more alerts (<b>314</b>). Identifying (<b>610</b>) by the event analyzer in dependence upon the event arrival rules and the events assigned to the events pool one or more alerts (<b>314</b>) may be carried out by identifying alerts in dependence upon one or more attributes of the events as that event is assigned to the events pool. Identifying (<b>610</b>) by the event analyzer in dependence upon the event arrival rules and the events assigned to the events pool one or more alerts (<b>314</b>) may be carried by comparing the attributes of the events to the event arrival rules and identifying as a result of the comparison one or more alerts. Such attributes may include the type of component from which the event was received, the type of component creating the event, the identification of the component creating the event, the time the event was created or received, an error reported in the event, and many others as will occur to those of skill in the art.

0084The method of <figref idref="DRAWINGS">FIG. 6</figref> also includes closing (<b>612</b>), by the event analyzer in dependence upon the events pool operation rules, the events pool (<b>312</b>). Closing (<b>612</b>), by the event analyzer in dependence upon the events pool operation rules, the events pool (<b>312</b>) may be carried out by determining that conditions dictated by the events pool operation rules have been met to stop assigning new events to the events pool and identifying in dependence upon those events pool operation rules the particular events that are included in the closed pool of events.

0085Closing the events pool may be carried out by determining that the initial period of time for the events pool and any particular periods of time for events received in the events pool extended to the initial period of time have expired. In such cases, if no new events are received prior to the expiration of the initial period of time for the events pool and any particular periods of time for events received in the events pool extended to the initial period of time the pool is closed.

0086Closing the events pool may also be carried out by determining that a maximum duration for the events pool has expired. In such cases, regardless of the number of new events being received after a maximum duration for the events pool has expired the pool is closed. In such embodiments, a maximum duration for the events pool prevents the events pool from including more events than are useful for relevant alert delivery according to embodiments of the present invention.

0087The method of <figref idref="DRAWINGS">FIG. 6</figref> also includes determining (<b>614</b>), by the events analyzer in dependence upon the event suppression rules, whether to suppress one or more events in the closed events pool (<b>312</b>). Determining (<b>614</b>), by the events analyzer in dependence upon the event suppression rules, whether to suppress one or more events in the closed events pool (<b>312</b>) may be carried out by determining in dependence upon the attributes of one or more events in the closed pool whether to delete, drop, or otherwise ignore one or more of the events in the closed pool.

0088The method of <figref idref="DRAWINGS">FIG. 6</figref> includes identifying (<b>616</b>) by the event analyzer in dependence upon the events pool closure rules and any unsuppressed events assigned to the events pool, one or more additional alerts (<b>617</b>). Identifying (<b>616</b>) by the event analyzer in dependence upon the events pool closure rules and any unsuppressed events assigned to the events pool, one or more additional alerts (<b>617</b>) may be carried out by identifying alerts in dependence upon one or more attributes of the events as that event is assigned to the events pool. Identifying (<b>616</b>) by the event analyzer in dependence upon the events pool closure rules and any unsuppressed events assigned to the events pool, one or more additional alerts (<b>617</b>) may be carried out by selecting the unsuppressed events for the events pool, comparing the attributes of the unsuppressed events of the events pool to the pool closure rules, and identifying as a result of the comparison one or more additional alerts. Such attributes may include the type of component from which one or more of the unsuppressed events are received, the type of components creating the unsuppressed events, the identification of the component creating the unsuppressed events, the time the events were created or received, one or more errors reported by the events event, the number of events in the pool, and many others as will occur to those of skill in the art.

0089The method of <figref idref="DRAWINGS">FIG. 6</figref> includes sending (<b>618</b>) by the event analyzer to an alert analyzer all the alerts identified by the event analyzer. Sending (<b>618</b>) by the event analyzer to an alert analyzer all the alerts (<b>314</b>) identified by the event analyzer may be carried out by sending a message containing the alerts from the event analyzer to the alert analyzer. Such a message may be sent from the event analyzer to the alert analyzer across a network, through shared memory, or in other ways as will occur to those of skill in the art.

0090The method of <figref idref="DRAWINGS">FIG. 6</figref> includes assigning (<b>620</b>) by the alert analyzer the identified alerts to an alerts pool (<b>324</b>). An alerts pool according to the method of <figref idref="DRAWINGS">FIG. 6</figref> has a predetermined initial period of time and in the example of <figref idref="DRAWINGS">FIG. 6</figref> assigning (<b>620</b>) by the alert analyzer the identified alerts to an alerts pool (<b>324</b>) includes extending for each alert assigned to the alerts pool the predetermined initial period of time by a particular period of time assigned to the alert. Assigning (<b>620</b>) by the alert analyzer the identified alerts to an alerts pool (<b>324</b>) also may be carried out in dependence upon attributes of the alerts. Such attributes may include an identification or type of the component upon which an occurrence occurred to create the event that was used to identify the alert, the alert ID, the alert type, and so on as will occur to those of skill in the art.

0091The method of <figref idref="DRAWINGS">FIG. 6</figref> includes determining (<b>622</b>) by the alert analyzer in dependence upon alert analysis rules (<b>322</b>) and the alerts in the alerts pool whether to suppress (<b>624</b>) any alerts. Determining (<b>622</b>) by the alert analyzer in dependence upon alert analysis rules (<b>322</b>) and the alerts in the alerts pool whether to suppress any alerts may be carried out in dependence upon one or more attributes of the alerts. Such attributes may include an identification or type of the component upon which an occurrence occurred to create the event that was used to identify the alert, the alert ID, the alert type, and so on as will occur to those of skill in the art. In such embodiments, determining (<b>622</b>) by the alert analyzer in dependence upon alert analysis rules (<b>322</b>) and the alerts in the alerts pool whether to suppress any alerts may be carried out by comparing the attributes of the alerts in the alerts pool to the alert analysis rules and identifying as a result of the comparison one or more alerts for suppression according to the event analysis rules.

0092The method of <figref idref="DRAWINGS">FIG. 6</figref> includes delivering (<b>628</b>) the unsuppressed alerts to one or more components of the distributed processing system. Delivering (<b>628</b>) the unsuppressed alerts to one or more components of the distributed processing system may be carried out by sending a message containing the alert to one or more components of the distributed processing system. In many cases, an alert may be sent as a message to a systems administrator advising the systems administrator of one or more occurrences within the distributed processing system.

0093As mentioned above, alert analysis rules may select additional alerts or suppress alerts in dependence upon events. In such embodiments, determining whether to suppress any alerts includes selecting events and determining whether to suppress any alerts in dependence upon the selected events. The method of <figref idref="DRAWINGS">FIG. 6</figref> therefore also includes identifying (<b>626</b>) by the alert analyzer in dependence upon alert analysis rules (<b>322</b>), the alerts in the alerts pool (<b>324</b>), and any selected events one or more additional alerts and in the method of <figref idref="DRAWINGS">FIG. 6</figref>, delivering (<b>628</b>) the unsuppressed alerts also includes delivering (<b>630</b>) any additional alerts to one or more components of the distributed processing system.

0094For further explanation, <figref idref="DRAWINGS">FIG. 7</figref> sets forth a flow chart illustrating an exemplary method of event and alert analysis in a distributed processing system according to embodiments of the present invention. The method of <figref idref="DRAWINGS">FIG. 7</figref> includes a local event analyzer (<b>700</b>) that is embedded in an alert analyzer (<b>701</b>). The method of <figref idref="DRAWINGS">FIG. 7</figref> includes the local event analyzer (<b>700</b>) receiving (<b>702</b>) events (<b>750</b>) from an event queue (<b>741</b>).

0095An event according to embodiments of the present invention is a notification of a particular occurrence in or on a component of the distributed processing system. Such events are sent from the component upon which the occurrence occurred or another reporting component to an event and alert analysis module according to the present invention. Often events are notifications of errors occurring in a component of the data processing system. Events are often implemented as messages either sent through a data communications network or shared memory. Typical events for event and alert analysis according to embodiments of the present invention include attributes such as an occurred time, a logged time, an event type, an event ID, a reporting component, and a source component, and other attributes.

0096An alert according to embodiments of the present invention is a refined identification of an occurrence, such as an error, based upon more than one event and therefore provides an identification of the occurrence in the context of its operation in the distributed processing system. Often an alert may be a notification of a particular error type of occurrence that is identified in dependence upon the plurality of events received from one or more components of the data processing system, such as, for example, a link failure among a plurality of devices each of which are producing many events based upon the single link failure, or a power failure provoking thousands of events, and so on.

0097Alerts are often implemented as messages to be sent through a data communications network or shared memory. Typical alerts according to embodiments of the present invention have attributes attached to them based upon the attributes of the events received from which they are identified.

0098An event analyzer is a module of automated computing machinery capable of identifying alerts in dependence upon received events. That is, event analyzers typically receive events and produce alerts. In many embodiments, event analyzers are implemented in parallel. Often such event analyzers are assigned to a particular pool of events and may be focused on events from a particular component or caused by a particular occurrence to produce a more concise set of alerts.

0099An alert analyzer is a module of automated computing machinery capable of identifying alerts for transmission from events and other alerts, identifying additional alerts for transmission, and suppressing unnecessary, irrelevant, or otherwise unwanted alerts identified by the event analyzer. That is, alert analyzers typically receive alerts and events and produce or forward alerts in dependence upon those alerts and events. In many embodiments, alert analyzers are implemented in parallel. Often such alert analyzers are assigned to a particular pool of alerts and may be focused on alerts with particular attributes to produce a more concise set of alerts.

0100The example of <figref idref="DRAWINGS">FIG. 7</figref> includes a plurality of event analyzers (<b>760</b>) and the local event analyzer (<b>700</b>). Both the local event analyzer (<b>700</b>) and the plurality of event analyzers (<b>760</b>) receive events (<b>750</b>) from an event queue (<b>741</b>). The plurality of event analyzers (<b>760</b>) are configured to process the events (<b>750</b>) according to each of the event analyzer's event analysis rules and to generate alerts (<b>758</b>). The generated alerts (<b>758</b>) are written to an alert queue (<b>740</b>) for transmission to the alert analyzer (<b>701</b>).

0101Event analysis rules are a collection of predetermined rules for meaningfully parsing received events to identify relevant alerts in dependence upon the events. Event analysis rules may include a plurality of different subsets of event processing rules, such as event arrival rules, events pool operation rules, event suppression rules, events pool closure rules, and others as will occur to one of skill in the art.

0102The local event analyzer (<b>700</b>) differs from the plurality of event analyzers (<b>760</b>) in that the local event analyzer (<b>700</b>) is embedded in the alert analyzer (<b>701</b>) as opposed to being outside of an alert analyzer. The local event analyzer (<b>700</b>) is also different because the local event analyzer is configured to process the events (<b>750</b>) based on local event analysis rules (<b>770</b>) that are specific to the alert analyzer (<b>701</b>) as opposed to event analysis rules that are not specific to the alert analyzer. The local event analyzer (<b>700</b>) is also different from each of the event analyzers of the plurality of event analyzers (<b>760</b>) in that the local event analyzer (<b>700</b>) is configured to generate temporary alerts specifically for the alert analyzer (<b>701</b>). A temporary alert is an alert that is visible to one or more specific alert analyzers. Restricting visibility to only an alert analyzer that contains the local event analyzer means that that nothing needs to be done to prevent the temporary alerts from being inadvertently reported to end users or consumed by another alert analyzer. For example, in the method of <figref idref="DRAWINGS">FIG. 7</figref>, the local event analyzer (<b>700</b>) is configured to create (<b>704</b>), based on the received events (<b>750</b>) and local event analysis rules (<b>770</b>) specific to the alert analyzer (<b>701</b>), a temporary alert (<b>749</b>) for the alert analyzer (<b>701</b>).

0103Local event analysis rules are a collection of predetermined rules for meaningfully parsing received events to identify relevant temporary alerts in dependence upon the events and the needs of the alert analyzer that includes the local event analyzer. In a particular embodiment, processing events based on local event analysis rules enables the temporary alerts to have times that are consistent with the alerts from an alert queue being processed by the alert analyzer. Creating (<b>704</b>), based on the received events (<b>750</b>) and local event analysis rules (<b>770</b>) specific to the alert analyzer (<b>701</b>), a temporary alert (<b>749</b>) for the alert analyzer (<b>701</b>) may be carried out by identifying temporary alerts based the received events.

0104The method of <figref idref="DRAWINGS">FIG. 7</figref> also includes the alert analyzer (<b>701</b>) analyzing (<b>706</b>) the temporary alert (<b>749</b>) based on alert analysis rules (<b>781</b>) and analyzing (<b>708</b>) the alerts (<b>758</b>) based on the alert analysis rules (<b>781</b>). Alert analysis rules are a collection of rules for suppressing one or more alerts to provide a more relevant set of alerts for transmission to a component of the distributed processing system, such as for example, for display to a systems administrator and to identify additional alerts for transmission to one or more components of the distributed processing system. Alert analysis rules for example may dictate that duplicate alerts are to be suppressed, alerts of a particular type for transmission to a particular component are to be suppressed, alerts of a particular type be transmitted to a particular component are to be suppressed and so on as will occur to those of skill in the art. Such alerts may be more meaningful to a component of the distributed processing system for automated error recovery or for a systems administrator who may otherwise be less informed by a number of raw unanalyzed alerts.

0105Analyzing (<b>706</b>) the temporary alert (<b>749</b>) and the alerts (<b>758</b>) based on alert analysis rules (<b>781</b>) may be carried out by identifying duplicate alerts; identifying alerts of a particular type for transmission to a particular component; identifying alerts of a particular type be transmitted to a particular component; and suppressing the identified alerts. Suppressing an alert is typically carried out by dropping the alert, deleting the alert or otherwise ignoring or not transmitting the suppressed alert to a component of the distributed processing system. Analyzing (<b>706</b>) the temporary alert (<b>749</b>) and the alerts (<b>758</b>) based on alert analysis rules (<b>781</b>) may be carried out by generating one or more additional alerts. The additional alerts may include one or more alerts not identified by the event analyzer. Such additional alerts may provide additional information to a component.

0106The alert analyzer (<b>701</b>) may also be configured to transmit the unsuppressed alerts to one or more components of the distributed processing system. The alert analyzer may transmit the unsuppressed alerts to one or more components of the distributed processing system by sending the alert as a message across a data communications network, through shared memory, or in other ways as will occur to those of skill in the art.

0107For further explanation, <figref idref="DRAWINGS">FIG. 8</figref> sets forth a flow chart illustrating an additional method of event and alert analysis in a distributed processing system according to embodiments of the present invention. The method of <figref idref="DRAWINGS">FIG. 8</figref> is similar to the method of <figref idref="DRAWINGS">FIG. 7</figref> in that the method of <figref idref="DRAWINGS">FIG. 8</figref> also includes receiving (<b>702</b>) events (<b>750</b>) from an event queue (<b>741</b>); creating (<b>704</b>), based on the received events (<b>750</b>) and local event analysis rules (<b>770</b>) specific to the alert analyzer (<b>701</b>), a temporary alert (<b>749</b>) for the alert analyzer (<b>701</b>); and analyzing (<b>706</b>) the temporary alert (<b>749</b>) based on alert analysis rules (<b>781</b>).

0108In the example of <figref idref="DRAWINGS">FIG. 8</figref>, the local event analyzer (<b>701</b>) is capable of creating one or more events pools, such as a local events pool (<b>850</b>). An events pool is a collection of events organized by the time of either their occurrence, by the time they are logged in the event queue, included in the events pool, or other time as will occur to those of skill in the art. That is, events pools are a collection of events organized by time. Such events pools often provide the ability to analyze a group of time related events and to identify alerts in dependence upon them. Often such events pools are useful in identifying fewer and more relevant alerts in dependence upon multiple related events.

0109Events pools according to embodiments of the present invention are typically operated according to events pool operation rules and events pool closure rules which are themselves often included in event analysis rules. Such events pool operation rules are configurable predetermined rules for controlling the operations of the events pool. Such rules includes rules identifying the initial predetermined period of time for each events pool, rules dictating the length of time extended to the pool upon the assignment of each new event to the pool, rules dictating the minimum time an event must be in a pool before that event is included in a collection of events when the pool is closed, rules dictating the amount to extend the initial predetermined period of time based on an arrival rate of events assigned to an events pool, rules governing the closing of an events pool, and others as will occur to those of skill in the art. Such rules are flexible and may be tailored to a particular distributed computing system and its functions.

0110The events pool closure rules are configurable predetermined rules for identifying alerts in dependence upon unsuppressed events in the closed events pool and alerts identified by the event arrival rules. That is, events pool closure rules identify new alerts in dependence upon one or more or even all of the unsuppressed events in the closed events pool. The events pool closure rules also identify alerts in dependence upon the alerts identified by the event arrival rules or a combination of the alerts identified by the event arrival rules and one or more of the unsuppressed events in the closed events pool.

0111The method of <figref idref="DRAWINGS">FIG. 8</figref> includes the alert analyzer (<b>701</b>) controlling (<b>802</b>) the local events pool (<b>850</b>) of the local event analyzer (<b>700</b>). Controlling (<b>802</b>) the local events pool (<b>850</b>) of the local event analyzer (<b>700</b>) may be carried out by forcing closure of the local events pool, modifying duration of the events pool, changing the local events pool configuration, or a variety of other actions associated with operation and closure of a local events pool.

0112In the example of <figref idref="DRAWINGS">FIG. 8</figref>, the local event analyzer (<b>701</b>) is configured to utilize a local event analyzer checkpoint (<b>861</b>). The method of <figref idref="DRAWINGS">FIG. 8</figref> also includes the alert analyzer (<b>701</b>) controlling (<b>804</b>) the local event analyzer checkpoint (<b>861</b>). A checkpoint is some indication of a restart point for event analysis and processing. For example, a checkpoint may indicate an event having the oldest identification number still in analysis by the local event analyzer at the time associated with the checkpoint. A checkpoint may also include additional information such a state of the event analyzer (e.g., running, failed, or shutdown); a last event ID used in an events pool; a list of event IDs that were moved forward to a next event pool; a list of event IDs that were suppressed events; and a minimum time need for each moved event in the next pool. Controlling (<b>804</b>) the local event analyzer checkpoint (<b>861</b>) may be carried out by identifying outdated event analyzer checkpoints that the alert analyzer no longer needs; and abandoning the identified event analyzer checkpoints.

0113In the method of <figref idref="DRAWINGS">FIG. 8</figref>, controlling (<b>804</b>) the local event analyzer checkpoint (<b>861</b>) optionally may be carried out by coordinating (<b>806</b>) the local event analyzer checkpoint (<b>861</b>) with an alert analyzer checkpoint (<b>862</b>) of the alert analyzer (<b>701</b>). Coordinating (<b>806</b>) the local event analyzer checkpoint (<b>861</b>) with an alert analyzer checkpoint (<b>862</b>) of the alert analyzer (<b>701</b>) may be carried out by examining both the local event analyzer checkpoint and the alert analyzer checkpoint to identify the best restart point for event and alert analysis.

0114For further explanation, <figref idref="DRAWINGS">FIG. 9</figref> sets forth a flow chart illustrating an additional method of event and alert analysis in a distributed processing system according to embodiments of the present invention. The method of <figref idref="DRAWINGS">FIG. 9</figref> is similar to the method of <figref idref="DRAWINGS">FIG. 7</figref> in that the method of <figref idref="DRAWINGS">FIG. 9</figref> also includes the local event analyzer (<b>700</b>) embedded in the alert analyzer (<b>701</b>) receiving (<b>702</b>) events (<b>750</b>) from an event queue (<b>741</b>); creating (<b>704</b>), based on the received events (<b>750</b>) and local event analysis rules (<b>770</b>) specific to the alert analyzer (<b>701</b>), a temporary alert (<b>749</b>) for the alert analyzer (<b>701</b>); and analyzing (<b>706</b>) the temporary alert (<b>749</b>) based on alert analysis rules (<b>781</b>).

0115In the method of <figref idref="DRAWINGS">FIG. 9</figref>, however, the distributed processing system includes a plurality of alert analyzers (<b>901</b>) and each of the alert analyzers includes an instance of the local event analyzer (<b>900</b>). That is, each alert analyzer of the plurality of alert analyzers (<b>901</b>) has its own local event analyzer. Each instance of the local event analyzer may perform according to the methods described in <figref idref="DRAWINGS">FIGS. 7-8</figref>.

0116For example, the method of <figref idref="DRAWINGS">FIG. 9</figref> includes each instance of the local event analyzer (<b>900</b>), receiving (<b>902</b>) the events (<b>750</b>) from the event queue (<b>741</b>). The method of <figref idref="DRAWINGS">FIG. 9</figref> also includes each instance of the local event analyzer (<b>900</b>), creating (<b>904</b>) a temporary alert for the alert analyzer in which the instance of the local event analyzer is embedded.

0117Each instance of the local event analyzer (<b>900</b>) may also include its own local event analyzer configuration (<b>950</b>). The local event analyzer configuration for a particular instance of the local event analyzer may be specifically configured for the alert analyzer in which the local event analyzer is embedded. For example, each local event analyzer configuration may have its own unique event analysis rules.

0118As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.

0119Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

0120A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

0121Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing. Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

0122Aspects of the present invention are described below with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

0123These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.

0124The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

0125The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

0126It will be understood from the foregoing description that modifications and changes may be made in various embodiments of the present invention without departing from its true spirit. The descriptions in this specification are for purposes of illustration only and are not to be construed in a limiting sense. The scope of the present invention is limited only by the language of the following claims.