JP3157763B2 - Failure notification management device and recording medium storing failure notification management program - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a failure report management apparatus and a recording medium storing a failure report management program, and more particularly to a failure report management apparatus for reporting failure information generated in a computer system to a system administrator. The present invention relates to a device and a recording medium on which a failure notification management program is recorded.

[0002]

2. Description of the Related Art Conventionally, in computer systems,
Various problems occur every day, and some problems are expected to develop into serious obstacles depending on the contents. In order to operate the computer system safely, it is necessary to monitor the occurrence of such various problems, and to report the occurrence of any such problems to the system administrator promptly, and to deal with them. Has been provided as.

[0003] In order to continue operating the computer system safely, it is important for the fault report management device to detect a sign of a fault as soon as possible and to report information that enables preventive maintenance before a serious fault occurs. It is. For this reason, the events detected by the fault notification management device have become diverse, and the amount of information has increased in order to notify all of them to the system administrator.

In order to prevent a system administrator from overlooking the most important problem, a conventional fault report management device uses:
By controlling only the first occurrence of the same problem that occurs within a certain time,
The same content was prevented from being reported over and over again.

As a result, there has been a problem that it is not possible to correctly report a symptom in which the number of occurrences is more important than the occurrence of an event.

A problem in which the number of occurrences of an event is important is a disk device. The disk device operates normally by retrying several times even if one read / write fails when the device itself deteriorates. If such a state continues, reading and writing cannot be performed normally even after many retries, and important data can be expected to be lost.

[0007]

As described above, in the conventional fault report management device, when a problem in which the number of occurrences is more important than the occurrence of a certain event, a notification within a predetermined time is issued. There is a problem that it is not possible to apply the function of disabling and to notify all occurrence events to the system administrator, so that the amount of reports cannot be reduced.

[0008] In addition, there is another problem in system management that the billing is expensive because billing is generated for each report.

[0009] An object of the present invention is to predict the occurrence of an important failure by notifying the occurrence history within a predetermined time when the number of occurrences is more important than the occurrence of a certain event, and An object of the present invention is to provide a fault report management device that reduces the amount of reports and reduces billing.

[0010]

According to the present invention, there is provided a fault report management apparatus for setting a time period for not reporting a predetermined event among events occurring in a monitored device ,
When the first occurrence occurs, a notification is issued; when the occurrence occurs again , the first occurrence
The first occurrence after the birth time when the above-mentioned notification is not passed
It is characterized in that the history of the previously specified event that occurred within the time from the time until the time when the notification is not passed elapses is reported in a lump.

The fault notification management device according to the present invention includes a fault monitoring means for detecting an event occurring in a device to be monitored, and a notification of the occurrence of the event from the fault monitoring means. When an outbreak occurs,
At the time of reoccurrence , the preset time for not reporting is set to 1
After the time of the first occurrence, the above
Said occurred within the time period until the end of the time that does not broadcast Oh
A report event management means for giving an instruction to collectively report the history of events specified in advance; and a report management means for receiving a report instruction from the report event management means and reporting to an administrator using a report device. May be provided.

[0012] The trouble report management device of the present invention further comprises a report event management table for managing a report event occurring in the monitored device and a processing method when the report event occurs, wherein the report event management table is provided. The means may collect information from the report event management table and issue a report instruction.

In the fault report management apparatus according to the present invention, the report event management table may include a report event identifier, a report means, a report destination, a non-report time, and a batch report flag.

[0014] The fault report management device of the present invention may further include a collective report management area for managing report events that have occurred and report events that have re-occurred within a period during which no report is made.

According to the recording medium of the present invention, among events that occur in the monitored device, a pre-specified event is reported at the first occurrence, and is reported at the first occurrence .
The previously set non-reporting time has passed since the first occurrence.
After a while, the time for not reporting has passed since the first occurrence
A program for causing the data processing apparatus to execute a process of collectively reporting the history of the previously specified event that occurred within the time required for the data processing device to be recorded.

[0016]

Embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a block diagram showing a configuration of the first exemplary embodiment of the present invention.

Referring to FIG. 1, a first embodiment is similar to the first embodiment.
A monitoring target device 10 to be monitored for a failure such as a disk device or a network connection device, a data processing device 20 operated by program control, a storage device 30 for storing information, and a reporting device 40 for reporting failure information And a storage device 50 that manages the batch report event.

The storage device 30 includes a report event management table 3 for recording a report event processing method. The storage device 50 includes the collective report management area 5.

The notification event management table 3 stores in advance methods of processing various notification events occurring on the monitored device 10 and the data processing device 20. The storage contents include a report event identifier, a report means, a report destination, a report non-reporting time, a batch report flag, and the like. The report event identifier stores an ID that uniquely specifies various report events. The notifying unit stores a unit for making a notification using the notifying device 40. The report destination stores the report destination when reporting. Examples of the report destination include a telephone number and an e-mail address. The non-reporting time is a positive integer including 0, and stores a time interval during which no reporting process is performed. The batch notification flag stores ON and OFF states.

The collective report management area 5 is an area for managing report events that have occurred and report events that have reoccurred within a time period during which no report is made. The contents to be managed include a report event identifier that uniquely identifies a report event that has occurred, a report time, a plurality of pieces of history information, and the like.

The data processing device 20 includes the monitoring target device 10
Monitoring means 1 for monitoring the operating state of the server, a notification event management means 2 for managing a fault that has occurred in response to a failure notification from the failure monitoring means 1, and a notification instruction from the notification event management means 2 for controlling the notification device 40. And a report management means 4 for making a report in accordance with the above.

The failure monitoring means 1 constantly monitors the monitoring target device 10 and, when an abnormality or a problem occurs, notifies the notification event management means 2 of a failure. The notification event management function 2 that has received the failure notification searches the notification event management table 3 using the notification event identifier, reads out the processing method of the corresponding event, and determines the notification processing method. If the non-reporting time is 0, the event is instructed to the report management means 4 together with the information of the report means and the report destination. However, if it is other than 0, first, the collective report management area 5 is searched for the same report event identifier. When the same report event identifier does not exist, a report instruction is issued to the report management unit 4 together with information on the report unit, report destination, and the like. Further, a value obtained by adding the report event identifier, the current time and the time during which the report is not performed is additionally registered as the report time. If the same report event identifier exists, history information is additionally registered when the collective report flag is ON. The history information may include not only the occurrence time but also supplementary information. For example, in the case of a disk device, it is information of a failed area, and in the case of a network connection device, it is information of a communication partner or the like in which a failure has occurred.

The report event management means 2 traverses the collective report management area 5 at regular intervals, compares the report time of each report event identifier with the current time, and determines whether the report time has elapsed. If it has passed, the batch report flag is checked, and if it is OFF, the report event identifier is deleted.
However, in the case of ON, it is checked whether or not there is additionally registered history information, and if there is, after requesting the report management function 4 to report all the information collectively, the report identifier and the history information are deleted. However, when there is no additional registered history information, the report identifier is deleted.

When receiving the notification instruction from the notification event management means 2, the notification management means 4 uses the notification device 40 to connect to the notification destination specified by the specified notification means, and then receives the notification event and the history information. If such is the case, the notification is made in one communication.

Next, the operation will be described with reference to FIGS. FIG. 2 is a flowchart showing the operation of the notification event management means 2.

When a problem or a failure occurs on the monitoring target device 10 or the data processing device 20, the failure monitoring function 1 notifies the event to the notification event management means 2 of the event. The notification event management means 2 (step A1) that has received the failure notification searches the notification event management table 3 by the notification event identifier, reads out the processing method of the corresponding event (step A2), and checks the non-reporting time (step A3). ). If the non-reporting time is 0, the event is instructed to the report management means 4 together with information on the report means, report destination, etc. (step A6). However, if it is other than 0, first, the collective report management area 5 is searched for the same report event identifier (step A4). If the same notification event identifier does not exist, the notification event identifier, a value obtained by adding the current time and the time during which no notification is performed is additionally registered as the notification time (step A5). A report instruction is issued together with information such as a report means and a report destination (step A).
6). If the same report event identifier exists, the batch report flag is checked (step A7), and if it is ON, history information is additionally registered (step A8).

The report event management means 2 patrolls the collective report management area 5 at regular intervals (step B1), compares the report time of each report event identifier with the current time, and passes the report time. Is determined (step B2). If it has elapsed, and if the history information has been added, it instructs the report management means 4 to report (step B3) and deletes the report event identifier (step B4).

When the report management means 4 receives a report instruction from the report event management means 2, after using the report device 40 to connect to the report destination designated by the designated report means, the report event and the history information are checked. If such is the case, the notification is made in one communication.

Next, a second embodiment of the present invention will be described. FIG. 3 is a block diagram showing the configuration of the second embodiment.

Referring to FIG. 3, the second embodiment is similar to the first embodiment.
Programs corresponding to the failure monitoring function 1, the notification event management means 2, and the notification management means 4 described in the first embodiment;
And a recording medium 6 that records data corresponding to the notification event management table 3 referred to by the notification event management means 2 to determine a notification method. This recording medium may be a magnetic disk, a semiconductor memory, or another recording medium.

The programs corresponding to the fault monitoring means 1, the report event management means 2, and the report management means 4 are read from the recording medium 6 into the data processing device 20, and control the operation of the data processing device 20. The notification event management table 3 may exist on the recording medium 6 or a copy thereof may exist on the recording device 30.

The data processing device 20 executes data processing of fault monitoring, report event management, and report management, similarly to the processing in the first embodiment.

[0033]

As described above, according to the present invention, when the same notification event occurs in a short time, a notification is made for the first time, but thereafter, within a predetermined non-reporting time. By reporting only the history of reoccurring events, frequent reporting occurs, which has the effect of preventing a system administrator or system maintenance person from overlooking a more important failure.

Also, for a report event that occurred within a predetermined non-reporting time period, the history is collectively reported, so that the system administrator or system maintenance staff can receive all the histories that have occurred. There is.

Furthermore, instead of reporting each time a reporting event occurs, events that occur within a time period during which no reporting event occurs are delayed and collectively reported, so that the number of reporting times can be reduced and communication costs can be reduced. There is.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a configuration of a first exemplary embodiment of the present invention.

FIG. 2 is a flowchart showing an operation of a report event management unit.

FIG. 3 is a block diagram showing a configuration of a second exemplary embodiment of the present invention.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 Fault monitoring means 2 Report event management means 3 Report event management table 4 Report management means 5 Batch report management area 6 Recording medium 10 Monitored device 20 Data processing device 30 Storage device 40 Report device 50 Storage device

──────────────────────────────────────────────────続 き Continuation of front page (56) References JP-A-7-13810 (JP, A) JP-A-6-168160 (JP, A) JP-A-5-233376 (JP, A) JP-A-3-3 219335 (JP, A) JP-A-3-150643 (JP, A) JP-A-8-25766 (JP, A) JP-A-5-324367 (JP, A) (58) Fields investigated (Int. ⁷ , DB name) G06F 11/30

Claims (6)

(57) [Claims] 1. Among events that occur in a monitoring target device, a time when a predetermined event is not reported is set.
Set it up, report when it occurs for the first time , and 1 when it occurs again
One time after the time during which the notification is not made has passed since the time of the first occurrence
A failure report management device, which collectively reports the history of the previously specified event that has occurred within a period of time from the occurrence of an eye to the lapse of the non-reporting time . 2. A failure monitoring means for detecting an event occurring in a monitoring target device, and receiving notification of the occurrence of the event from the failure monitoring means, and reporting a predetermined event at the first occurrence. , When reoccurring , set in advance
After the time when the notification was not made after the first occurrence,
A report event management means for issuing an instruction to collectively report the history of the previously specified events that have occurred within a time period from the first occurrence to the time when the notification is not performed, and the report event management means And a report management means for receiving a report instruction from the user and reporting to a manager using a report device. 3. A notification event management table for managing a notification event occurring in the monitored device and a processing method when the notification event occurs, wherein the notification event management unit includes the notification event management unit. 3. The fault report management device according to claim 2, wherein information is collected from the table to issue a report instruction. 4. The fault report management device according to claim 3, wherein the report event management table includes a report event identifier, a report unit, a report destination, a time at which report is not performed, and a batch report flag. 5. The fault report management according to claim 3, further comprising a collective report management area for managing a report event that has occurred and a report event that has reoccurred within a time period during which no report is made. apparatus. 6. Among the events occurring in the monitored device, a predetermined event is notified when the event occurs for the first time , and a predetermined notification is issued when the event occurs again.
The first occurrence after no time has elapsed since the first occurrence
A recording medium on which a program for causing a data processing device to execute a process of collectively reporting the history of the previously specified event that has occurred within a period from time to when the non-reporting time has elapsed is recorded.