JP2002278798A - Fault monitoring apparatus and method, and storage medium - Google Patents

Abstract

(57) [Summary] [Problem] To prevent a failure from being overlooked by notifying the failure level explicitly by selecting a notification method according to the failure of the device, and also explicitly reporting the location of the failure. thing. SOLUTION: A log from each computer is referred to (S
602), an error is determined at the software level (S603). In the case of an error, the error level is specified (S609), an error notification method based on the error level is specified (S610), and the error is notified by the specified notification method (S611). Further, the generated error is written in the failure / request log (S612). On the other hand, an error is determined at the network level by referring to NOS (S604). In the case of an error, the processing shifts to S609. On the other hand, error detection at the hardware level is performed by referring to the OS (S606). In the case of an error, the processing shifts to S609.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a fault monitoring apparatus for monitoring a network to which a device storing software is connected, a method thereof, and a storage medium.

[0002]

2. Description of the Related Art In a network environment in which a plurality of client PCs and a plurality of servers are connected via a network, if a problem such as an error, a failure, or an abnormal termination of processing occurs in these client PCs or a server, the client PC or the server may fail. The generated result is recorded in each log of the server.

Specifically, the problem at the hardware level is the OS, and the problem at the network level is NOS.
In (network OS), problems at the software level are logged in each software.

[0004]

However, heretofore, there have been the following problems.

[0005] (1) Since problems at all levels are written in a log, if a failure occurs in a client PC or server, conversely, from the log, whether the failure is at the hardware level, the network level, or the software It takes time to judge whether it is the level.

(2) There is a case where a failure to respond to a failure or a request for repair for the failure is overlooked and the response is delayed only by being recorded in the log. As a result, the process proceeds as it is, and even a situation where even a long time and effort is required to recover from the failure may be caused. Further, even when a request for repairing a failure is displayed on the management PC, for example, the management PC
If it is located at a location distant from C, the occurrence of a failure or request may be overlooked and the response may be delayed.

[0007] When the processing is abnormally terminated due to a data exception, it takes time and effort to find out where the problem exists in the file to be processed.

SUMMARY OF THE INVENTION The present invention has been made in view of the above-mentioned problems, and a method of notifying according to a failure of a device is selected so that the level of the failure is specified and the location of occurrence of the failure is also specified. The purpose is to prevent failures from being overlooked.

[0009]

In order to achieve the object of the present invention, for example, a fault monitoring device of the present invention has the following configuration. That is, a fault monitoring device that monitors a network to which a device that stores software is connected, and a device that is connected to the network, software that the device stores, a status monitoring unit that monitors a status of the network, When a failure is detected by the state monitoring unit, a failure level identification unit that identifies the level of the failure based on a code that identifies the failure identified from the detection target, and the failure that is identified by the failure level identification unit Notification method selecting means for selecting the notification method of the failure based on the level of the information, notification means for notifying the failure based on the notification method selected by the notification method selection means, and a log relating to the failure in a predetermined storage means Recording means for recording in

[0010] Further, there is provided recording means for recording a log relating to the failure in a predetermined storage means.

[0011] Further, the fault monitoring means may detect a fault of software stored in a device connected to the network.
If the error is detected by the log of the device, a first part that identifies a corresponding location of the failure in the intermediate file of the software is specified.
Fault location identifying means, second failure location identifying means for identifying a corresponding location of the failure in the log relating to the failure by the recording means, the first failure location identifying means, the second failure location identifying means,
Display means for displaying a list of applicable locations of the respective faults by the fault location specifying means.

[0012] The apparatus further comprises a level table storage means for storing a table in which a code for specifying a fault assigned in advance and a level of the code is stored.

[0013] Further, there is provided a notifying method table storing means for storing a table in which a fault level and a fault notifying method corresponding to the level are stored.

[0014]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention will be described below in detail according to preferred embodiments with reference to the accompanying drawings.

[First Embodiment] FIG. 1 shows a schematic configuration example of a network system including an electronic form management console 106 as a failure monitoring device according to the present embodiment.
The LAN 108 includes a host computer 101, an electronic form server 102, a CD-R creation server 103, a client computer 104, a host management console 10
5, the electronic form management console 106 and the patrol lamp are connected and can communicate with each other. An operator (not shown) normally operates the host management console 105.
Is operating the console 105. Further, the host computer 101, the electronic form server 10
2. Each memory in the CD-R creation server 103 has an OS
Are stored in respective memories, and when an error occurs at the hardware level, the OS stores an error code or an error and specifies the hardware or the like that caused the error later. can do. In addition, logs (LOG) of the computer 101 and the servers 102 and 103 storing the respective programs are transmitted to the electronic form management console 106 at regular time intervals (settings can be changed). The respective programs including the OS and the NOS (network OS) are stored in an external storage device (not shown) in each of the computers 101 and the servers 102 and 103. Loaded in the memory, each computer 101, server 102, 10
3 are read and executed by respective CPUs (not shown).

On the other hand, a memory in the electronic form management console 106 stores a management (monitoring) program 106a for executing the procedure shown in the flowchart of FIG. 6, and is read by the CPU in the console as necessary. Issued and executed. Also, such programs include NOS
It is included. The NOS serves to monitor the network level. The management program monitors the status of each unit at regular time intervals (settings can be changed). That is,
Resident program (host computer 101, electronic form server 102, resident program of CD-R creation server 103), network, hardware (electronic form server 102), job (host computer 101, electronic form server 102, CD-R creation server) The status of each job (103) is monitored.

When monitoring software such as resident programs and jobs, the monitoring method refers to logs transmitted from the computer 101 and the servers 102 and 103 described above. As a result, if an error occurs at the software level, the error code, computer name, server name, software name, and the like described in this log can be specified.

When monitoring a network, reference is made to a NOS (network OS). As a result, if an error occurs at the network level, the error code, the network in which the error occurred, and the like can be specified by referring to the NOS. In addition, for example, “Ping 10
9.57.32.1 ”etc.
Within a certain period of time, the (IP) address “109.57.32.
If there is no response from the device specified by “1”, it can be estimated that there is a failure in the network for this device.

When monitoring hardware, the OS is referred to. As a result, when an error occurs at the hardware level, the error code, the hardware that caused the error, and the like can be specified by referring to the OS.

Then, a message based on the error specified by the above-described monitoring method by the management program 106a in the electronic form management console 106 is notified by the program 106a. The notification method will be described later.

FIG. 2 shows an example of the arrangement of each computer described above.

The floor 201 is divided into two rooms 201a and 202b by a wall 202, and each room can be opened and closed by opening a door 203. As described above, since the operator is usually in front of the host management console 105 and working, the electronic form management console 106 outputs a message based on the error identified as described above to the electronic form management console 106, for example. The operator does not notice even if it is displayed on the illustrated display.

Therefore, as described above, the management program 106a
When an error is detected, an error notification method is determined according to the error level. Here, it is necessary to assign an error level to each error code (error type) in advance, and create a table (error level table) in which the error codes are associated with the levels. FIG. 3 shows an example of the error level table.

Reference numeral 302 denotes a column where an error code is described.
Reference numeral 301 denotes a column in which an error level corresponding to each error code is described. By referring to this table 300,
The error level corresponding to each error code is known. In addition,
The contents of the table shown in the figure can be arbitrarily set as needed.

Next, as described above, a method of notifying a message (warning) according to the error level is determined. For determining the notification method, a table (notification method determination table) shown in FIG. 4 is referred to as an example. The table 400 in FIG.
This is a table when the minimum error level is 1 and the maximum error level is 100.

Reference numeral 401 denotes a column in which an error level area is described; and 402, a column in which an error notification method is described.
In the figure, when the error level is 1 to 30, an e-mail having a content corresponding to the error level is transmitted to the host management console 105 as a message notification method. Further, since the meaning of the error code is described in the content of the e-mail, a table (conversion table) for converting the error code into a word having the meaning of the error code is required. FIG. 5 shows an example of this conversion table.

Reference numeral 501 denotes a column in which an error code is described.
Reference numeral 502 denotes a column in which a sentence interpreting the content of the error code is described. In the conversion table 500, if the error code is 0C7, the interpreted sentence is “error due to writing”. When the electronic form management console 106 detects the error code of this value (0C7), it converts this error code. The issuing computer can determine that an “error due to writing” has occurred.

As described above, the interpreted sentence corresponding to the error code can be specified by referring to the table 500. Therefore, when the management program 106a detects the error code, the management program 106a refers to the conversion table 500 to detect the error code. The interpreted sentence corresponding to the code is specified, and the specified interpreted sentence is used for the content of the e-mail.

When the error level is 31 to 60, the host management console 105 is used as a message notification method.
A pop-up window is displayed on a display (not shown), and the content of the above-mentioned e-mail is described in the window. This notification method is a more urgent error notification method because the notification timing is real-time than the method using electronic mail. Since the interpreted text of the error code is also described in this window, the interpreted text corresponding to the error code is specified using the table 500, and the specified interpreted text is used.

When the error level is 61 to 100, as a message notification method, an operation signal is sent to the patrol lamp 107, and the lighting section rotates while the patrol lamp is lit. This notification method is a more urgent error notification method than the method using the pop-up window. In the case where the error level is 61 to 100, the highest urgency is required for the error notification method. Therefore, in addition to the notification using a patrol lamp, which is a visual notification method, for example, an auditory A buzzer or the like, which is a typical notification method, may be used. In that case, table 400
Column 402 when the error level is 61 to 100
Inside is "buzzer alert". The table 40
Using 0, a notification method according to the error level is selected.

FIG. 6 shows a flowchart of each process in the electronic form management console 106 described above. It should be noted that the flowchart shown in FIG.
The data is stored in a memory (not shown) in the CPU 06 and is read and executed by the CPU as necessary.

First, a monitoring interval time is set (step S601). Then, monitoring is performed every interval time. First, monitor the software.
As described above, the log transmitted from each computer is referred to (step S602), and it is determined whether an error has occurred at the software level (step S603).
If an error has occurred, the process proceeds to step S609, and the error level is specified with reference to the table 300 (step S609). Next, an error notification method based on the specified error level is specified by referring to the table 400 (step S610). Then, an error is notified using the specified notification method (step S6).
11). At this time, the interpretation of the error code is specified using the table 500 as necessary. Further, the generated error is written in the failure and request log (step S612). Note that the processing of steps S609 to S611 and step S612
May be reversed.

On the other hand, if no error is detected in step S603, the process moves to step S604 to monitor the network.

As described above, the network monitoring is performed by the NOS
, An error is detected at the network level (step S604). If an error is detected, the process proceeds to step S609, and the process as described above is performed. If no error is detected,
The process shifts to step S606 to monitor the hardware (electronic form server 102).

As described above, the hardware monitoring detects an error at the hardware level by referring to the OS (step S606). If an error is detected, the process proceeds to step S609, and the process as described above is performed. If no error has been detected, the process proceeds to step S608, and it is determined whether or not it is time to perform monitoring based on the set interval time (step S608). If it is time to perform monitoring, the process proceeds to step S602, and the above-described processes are executed.

As described above, the fault monitoring apparatus according to the present embodiment can monitor three units of software, hardware, and a network, and can provide a notification method according to an error level detected as a result of monitoring. Could choose.

In the present embodiment, the error notification method is specified according to the error level. However, an error notification method may be specified according to, for example, the type of error.

[Second Embodiment] In this embodiment, after the electronic form management console 106 detects and reports an error, a description will be given of a countermeasure for the error. More specifically, if the electronic form server 102 terminates abnormally due to a data exception when the operator registers the electronic form in the external storage device (not shown) using the electronic form server 102, a countermeasure against this error is taken. Will be described.

FIG. 7 shows an example of the configuration of a system for dealing with errors performed by the electronic form server 102 and the host computer 101, and a method thereof. Host computer 1
01 includes an electronic form data extraction program 101b. The details of the electronic form data extraction program 101b will be described later.

Reference numeral 701 denotes an external storage device for storing the failure / request log described in the first embodiment. Reference numeral 702 denotes an external storage device for storing electronic form data (intermediate files) registered up to that time when the electronic form server 102 abnormally ends, and 703 an external storage for storing a library management table having various functions. 704 in the storage device
Is an external storage device for storing the source of the program 101b. Of these, the external storage devices 701 and 702 are connected to the electronic form server 102, and the external storage devices 702 and 70
3 is connected to the host computer 101. Note that the external storage device 701 may be connected to the host computer 101. Note that predetermined memories may be used instead of the external storage devices 701 to 704. Alternatively, the respective information stored in the external storage devices 701 to 704 may be stored in different areas in the same memory.

The electronic form server 102 that has received an error code indicating “abnormal termination due to a data exception” from the electronic form management console 106 is a failure stored in the external storage device 701. From the request log, the log 701a at the corresponding location where the error has occurred is specified. And the specified log 7
The intermediate file corresponding to 01a is specified from the external storage device 702. In this case, the specified log 701a
Specify based on the content described in.

The specified intermediate file 702a is read by the electronic form data extraction program 101b included in the program 101a, and the library 703a that specifies the program that created the intermediate file 702a is specified by searching the external storage device 703. Then, the source 704a of the program that created the intermediate file 702a is specified by the specified library 703a.

The source 704a is transmitted to the electronic form server 102 via the host computer 101 and displayed on a display (not shown) of the electronic form server 102. FIG. 8 shows a display example of the display.

Reference numeral 800 denotes a window displayed on the display, which is used to make corrections described below in order to deal with the above-mentioned errors. In the window 800, a display area for displaying each information is provided, and 801 is a log display area for displaying the contents of the log 701a. Reference numeral 802 denotes data of an electronic form input when an error occurred (data of an intermediate file)
Is a data file display area for displaying. A display area 803 displays a program for correcting the data file of the electronic form displayed in the area 802. This window is also a window for correcting a data file processing program of an electronic form, and is also a window for correcting a master maintenance program and the like. That is, the target displayed in the area 803 is the content (source) of the program, and is a display area for loading, displaying, and correcting the program presumed to be the cause of the error.

The operator makes each correction while referring to each of the above-mentioned areas in the window 800. The modified program is compiled and executed. As a result, the above-mentioned error can be dealt with by the corrected program. FIG. 9 shows a flowchart of error handling in this embodiment, which will be described below. Note that in the flowchart in FIG.
Each process in 909 and S912 is a manual operation, and the process in step S910 is a process for the operator to see and confirm. Other processing is performed on the electronic form server 1
02. Steps S907 and S9
Programs according to the respective processes except for 09 and S912 are included in the program 101a.

First, the screen example including the log shown in FIG. 8 is displayed (step S902). The log is displayed in the area 801 as described above. Next, as described above, an intermediate file is searched based on the contents of the log (step S903), and a corresponding portion of the file is displayed in the area 802 (step S904). Here, the process branches as to the cause of the data exception. That is, the process branches depending on whether or not the file in which the data exception has occurred is the master file (step S905).

If the file in which the data exception has occurred is a master file, the process shifts to step S911 to load the master maintenance program and display it in the area 803 (step S911). Then, maintenance is manually performed using the master maintenance program displayed in the area 803 (step S91).
2).

On the other hand, if the file in which the data exception has occurred is not the master file, a file correction program is loaded and displayed in the area 803, and the file in which the data exception has occurred is corrected using this program.
Next, the file processing program is displayed in the area 803, and the file processing program is corrected and compiled.

Then, the operator confirms whether or not all the data exception occurrence locations have been handled, and if not completed, the process proceeds to step S902; otherwise, the process ends.

In the system having the above configuration, even when the electronic form server 102 is abnormally terminated due to a data exception, the corresponding location of the log and the corresponding location of the intermediate file can be displayed simultaneously by comparing them. Each error can be corrected by referring to. In the present embodiment, a method for dealing with an error in the case of abnormal termination due to a data exception has been described using the electronic form server 102 as an example, but the method for dealing with an error in the present embodiment is not limited to the electronic form server 102.

[Other Embodiments] An object of the present invention is to supply a storage medium (or a recording medium) storing a program code of software for realizing the functions of the above-described embodiments to a system or an apparatus, System or device computer (or CPU or MPU)
Can also be achieved by reading and executing the program code stored in the storage medium. In this case, the program code itself read from the storage medium implements the functions of the above-described embodiment, and the storage medium storing the program code constitutes the present invention. When the computer executes the readout program codes, not only the functions of the above-described embodiments are realized, but also an operating system (OS) running on the computer based on the instructions of the program codes. It goes without saying that a case where some or all of the actual processing is performed and the functions of the above-described embodiments are realized by the processing is also included.

Further, after the program code read from the storage medium is written into a memory provided in a function expansion card inserted into the computer or a function expansion unit connected to the computer, based on the instruction of the program code. , The CPU provided in the function expansion card or the function expansion unit performs part or all of the actual processing,
It goes without saying that a case where the function of the above-described embodiment is realized by the processing is also included.

When the present invention is applied to the storage medium, the storage medium stores program codes corresponding to the above-described flowcharts (shown in FIG. 6 and / or FIG. 9).

[0054]

As described above, according to the present invention, the level of the failure is explicitly specified by selecting the notification method according to the failure of the device, and the location of the occurrence of the failure is also explicitly reported. Failures can be prevented from being overlooked.

[Brief description of the drawings]

FIG. 1 is a block diagram illustrating a schematic configuration example of a network system including an electronic form management console 106 as a failure monitoring device according to a first embodiment of the present invention.

FIG. 2 is a diagram illustrating an example of the arrangement of each computer according to the first and second embodiments of the present invention.

FIG. 3 is a diagram illustrating an example of an error level table.

FIG. 4 is a diagram illustrating an example of a notification method determination table.

FIG. 5 is a diagram illustrating an example of a conversion table.

FIG. 6 is a flowchart of each process in the electronic form management console 106 according to the first embodiment of the present invention.

FIG. 7 is a diagram illustrating an example of a configuration of an error handling system performed by an electronic form server 102 and a host computer 101 and a method thereof according to a second embodiment of the present invention.

FIG. 8 is a diagram showing an example of an error correction screen.

FIG. 9 is a flowchart of an error handling process according to the second embodiment of the present invention.

 ──────────────────────────────────────────────────続 き Continued on the front page F term (reference) 5B042 GA12 GA21 GA39 GB09 GC08 GC10 JJ02 JJ03 KK13 LA20 MA08 MA14 MC15 NN02 NN04 NN56 5B085 AC11 AC14 BG07 5B089 GA11 GB02 JA35 JB17 KA12 MC03 MC18

Claims (17)

[Claims] 1. A fault monitoring device for monitoring a network to which a device storing software is connected, comprising: a device connected to the network, software stored by the device, and a status monitoring means for monitoring a status of the network. And, when a fault is detected by the state monitoring unit, based on a code specifying the fault specified from the detection target,
Fault level specifying means for specifying the level of the fault; notification method selecting means for selecting a fault notification method based on the fault level specified by the fault level specifying means; selection by the notification method selecting means And a notifying means for notifying a fault based on the notified notifying method. 2. The apparatus according to claim 1, further comprising recording means for recording a log relating to the failure in a predetermined storage means.
The fault monitoring device according to claim 1. 3. The state monitoring means, when monitoring the state of a device connected to the network, checks the status of the device.
The fault monitoring device according to claim 1, wherein S is referred to. 4. The apparatus according to claim 1, wherein when monitoring the status of software stored in the device connected to the network, the status monitoring unit refers to a log of the device transmitted from the device. The fault monitoring device according to claim 1. 5. The fault monitoring device according to claim 1, wherein the status monitoring unit refers to a network OS when monitoring the status of the network. 6. A level table storing means for storing a table which associates a level of a code specified in advance with a level of a fault and a level of the code, wherein the fault level specifying means stores the level table storing means. The fault monitoring device according to claim 1, wherein a level of the fault according to the code that specifies the fault is specified by referring to the fault. 7. A notifying method table storing means for storing a table in which a fault level and a fault notifying method corresponding to the level are stored, wherein the notifying method selecting means refers to the notifying method table storing means. 2. The fault monitoring device according to claim 1, wherein the fault monitoring method selects a fault notification method according to the fault level by the fault level specifying unit. 8. The failure monitoring method according to claim 7, wherein the notification method table storage means stores a notification method with a higher urgency as the level of the failure increases. apparatus. 9. The fault monitoring device according to claim 1, wherein the notification unit includes an e-mail, a pop-up window, and a patrol lamp. 10. When the failure monitoring means detects a failure of software stored in a device connected to the network by using a log of the device, the failure monitoring unit specifies a location of the failure in an intermediate file of the software. A first fault location specifying means, a second fault location specifying means for specifying a relevant location of the fault in the log relating to the fault by the recording means, a first fault location specifying means, and the second fault 3. The fault monitoring device according to claim 2, further comprising: display means for displaying a list of the locations of the faults by the location specifying means. 11. The fault monitoring device according to claim 10, wherein the fault of the software includes an abnormal stop of a device due to a data exception. 12. A fault monitoring method for monitoring a network to which a device storing software is connected, comprising: a device connected to the network, software stored by the device, and a status monitoring step of monitoring a status of the network. When a failure is detected in the state monitoring step, a failure level identification step of identifying the level of the failure based on a code identifying the failure identified from the detection target, and the failure level identification step is performed in the failure level identification step. A notification method selecting step of selecting the notification method of the failure based on the level of the failure, and a notification step of notifying the failure based on the notification method selected in the notification method selection step. Fault monitoring method. 13. The failure monitoring method according to claim 12, further comprising a recording step of recording a log relating to the failure in a predetermined storage unit. 14. When a failure of software stored in a device connected to the network is detected by the log of the device in the failure monitoring step, a corresponding location of the failure is specified in an intermediate file of the software. A first fault location specifying step, a second fault location specifying step for specifying a relevant location of the fault in the log relating to the fault in the recording step, a first fault location specifying step, and the second fault The failure monitoring method according to claim 13, further comprising: a display step of displaying a list of respective locations of the failures in the location specifying step. 15. A storage medium for storing a program code of a fault monitoring process for monitoring a network to which a device for storing software is connected, wherein the device is connected to the network, software stored by the device, and the network. A failure level identification that identifies the level of the failure based on a program code of a status monitoring step that monitors the status of the failure and a code that identifies the failure identified from the detection target when the failure is detected in the status monitoring step A program code of a process; a program code of a notification method selection step of selecting the notification method of the failure based on the failure level specified in the failure level specification step; and a notification method selected in the notification method selection step. And a program code for a notification process for notifying a failure based on the And the storage medium. 16. The storage medium according to claim 15, further comprising a program code of a recording step of recording a log relating to a failure in a predetermined storage means. 17. When a failure of software stored in a device connected to the network is detected by a log of the device in the failure monitoring step, a location of the failure is specified in an intermediate file of the software. A program code for a first fault location specifying step, a program code for a second fault location specifying step for specifying a location of the fault in a log relating to the fault in the recording step, and a first fault location specifying step. 17. The storage medium according to claim 16, further comprising: a program code for a display step of displaying a list of the locations of the respective faults in the second fault location specifying step.