JP2007005905A - Monitor object terminal, and monitoring program, system and method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To eliminate omission in the notification of trouble information when the trouble information cannot be notified due to some trouble by resuming the transmission of the trouble information automatically after recovery, and to reduce a load caused by the retransmission of unnecessary trouble information. <P>SOLUTION: Various device monitoring programs acquire states of a device at constant intervals using a device control API and records the information of a trouble in a monitor information log at a trouble information storage section 140 when a trouble is detected. A log monitor section 150 monitors the monitor information log continuously and when trouble information is recorded in the log, notifies the trouble information to a log monitor control section 171 through a WAN 190. An understanding confirmation section 151 and a confirmation response section 172 confirm mutual safety at a constant interval and the transmission of trouble information is stopped when the confirmation of safety stops. When safety is confirmed again, the transmission of the trouble information is resumed. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a monitoring target terminal device, a monitoring program, a monitoring system, and a monitoring method. In particular, it relates to a device monitoring system for special terminals.

In the conventional information processing device failure notification method, if a failure occurs in the device, the failure details cannot be reported to the maintenance center for some reason by writing the failure content in the log medium and sending the log to the maintenance center. In such a case, a method has been proposed in which the failure of the apparatus is reliably notified by retransmitting the log information (see, for example, Patent Document 1).
Japanese Patent Laid-Open No. 5-113909 (first page, FIG. 1)

  In the conventional failure notification method, when the network is disconnected, the failure information continues to be re-notified at regular intervals, or after repeated retransmission for a certain time, the failure information notification is stopped (timed out), so the load is high. Or there is a problem of failure to notify failure information.

  In the present invention, for example, when failure information notification from the terminal side to the maintenance center cannot be performed due to some failure, the failure of notification of failure information of the terminal is prevented by automatically restarting transmission of monitoring contents after recovery. An object of the present invention is to reduce a CPU (Central Processing Unit) load and a network load by eliminating unnecessary and unnecessary failure information. Also, for example, by automatically setting the device monitoring interval on the terminal side to an appropriate value, the CPU load and memory usage of the terminal are adjusted, and a monitoring method that does not affect the performance of other applications is realized. For the purpose.

The monitoring target terminal device of the present invention communicates with a monitoring server device that monitors a peripheral device via a network and connects the peripheral device,
A peripheral device monitoring unit that monitors a state of the peripheral device and detects a failure of the peripheral device;
A failure information storage unit that stores failure information related to a failure detected by the peripheral device monitoring unit;
A communication confirmation unit that determines that communication with the monitoring server device is possible when an inquiry is transmitted to the monitoring server device and a response to the inquiry is received from the monitoring server device;
If the communication confirmation unit determines that communication with the monitoring server device is possible and failure information to be transmitted is stored in the failure information storage unit, the failure to be transmitted to the monitoring server device And a failure information transmission unit for transmitting information.

  In the present invention, the failure information transmission unit of the monitoring target terminal device is determined by the communication confirmation unit to be able to communicate with the monitoring server device, and the failure information to be transmitted is stored in the failure information storage unit. In this case, when failure information notification from the terminal side to the server side becomes impossible due to failure by sending failure information to be sent to the monitoring server device, the failure information notification of the terminal is eliminated and It is possible to reduce CPU load, network load, and the like due to retransmission of necessary failure information.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  FIG. 1 is a diagram illustrating an example of a hardware configuration of a monitoring target terminal device according to the following embodiment.

  In FIG. 1, a monitoring target terminal device 100 is, for example, a computer, and includes a CPU 911 that executes a program. The CPU 911 includes a ROM 913, a RAM 914, a communication board 915, a CRT (Cathode Ray Tube) display device 901, a keyboard (K / B) 902, a mouse 903, an FDD (Flexible Disk Drive) 904, a magnetic disk device 920, via a bus 912. A compact disk device (CDD) 905, a scanner device 110, a printer device 120, and a card reader device 130 are connected.

  The RAM 914 is an example of a volatile memory. The ROM 913, the FDD 904, the CDD 905, and the magnetic disk device 920 are examples of nonvolatile memories. These are examples of a storage device or “˜storage unit”.

  The communication board 915 is connected to a local area network (LAN) or the like.

  For example, the communication board 915 is an example of “˜receiving unit” or “˜transmitting unit”. Further, for example, the K / B 902, the scanner device 110, the card reader device 130, the FDD 904, and the like are examples of “˜input unit”. For example, the printer device 120, the CRT display device 901, and the like are examples of “˜output unit”.

  Here, the communication board 915 is not limited to the LAN, and may be connected to a WAN (wide area network) 190 such as the Internet or ISDN (Integrated Services Digital Network), not only via the LAN.

  The magnetic disk device 920 stores an operating system (OS) 160, a window system 922, a program group 923, and a file group 924. The program group 923 is executed by the CPU 911, the OS 160, and the window system 922.

  The program group 923 stores programs that execute functions described as “˜units” in the description of the embodiments described below. The program is read and executed by the CPU 911.

  In the file group 924, what is described as “determination result of”, “calculation result of”, and “processing result of” in the description of the embodiment described below is stored as “˜file”. Yes.

  In addition, the arrow portion of the flowchart described in the description of the embodiment described below mainly indicates input / output of data, and for the input / output of the data, the data is a magnetic disk device 920, an FD (Flexible Disk), an optical disk. , CD (compact disc), MD (mini disc), DVD (Digital Versatile Disk) and other recording media. Alternatively, it is transmitted through a signal line or other transmission medium.

  In addition, what is described as “unit” in the description of the embodiment described below may be realized by firmware stored in the ROM 913. Alternatively, it may be implemented by software alone, hardware alone, a combination of software and hardware, or a combination of firmware.

  In addition, a program that implements the embodiment described below may be stored using a recording device using another recording medium such as a magnetic disk device 920, FD, optical disk, CD, MD, or DVD.

Embodiment 1 FIG.
FIG. 2 is a block diagram showing a configuration of the monitoring system according to the present embodiment.

  In FIG. 2, a monitoring target terminal device 100 is a special terminal to be monitored, and a plurality of monitoring target terminal devices 100 are connected to a WAN 190 (an example of a network). A plurality of devices (examples of peripheral devices) necessary for business such as a scanner device 110, a printer device 120, and a card reader device 130 are connected to the monitoring target terminal device 100. The monitoring target terminal device 100 includes an OS 160 that can control these devices, device drivers such as a scanner control device driver 111, a printer control device driver 121, and a card reader control device driver 131, and a scanner control API (Application). (Program Interface) 112, a printer control API 122, a card reader control API 132, and other device control APIs.

  The monitoring target terminal device 100 also includes device monitoring programs (an example of a peripheral device monitoring unit) such as a scanner monitoring program 113, a printer monitoring program 123, a card reader monitoring program 133, and the like. The device status is acquired using APIs such as the control API 112, the printer control API 122, and the card reader control API 132.

  Furthermore, the monitoring target terminal device 100 includes a failure information storage unit 140 and a log monitoring unit 150 that store a monitoring information log (an example of failure information). The log monitoring unit 150 includes a communication confirmation unit 151 and a failure information transmission unit. 152.

  In FIG. 2, the monitoring server device 170 is connected to the WAN 190 and can communicate with the monitoring target terminal device 100. The monitoring server device 170 includes a log monitoring control unit 171, and the log monitoring control unit 171 includes a confirmation response unit 172, a failure information receiving unit 173, and a failure information output unit 174. The monitoring terminal device 180 includes a monitoring result notification unit 181.

  Next, the operation will be described.

  FIG. 3 is a flowchart showing the operation of the monitoring system according to the present embodiment.

  The scanner monitoring program 113 uses the scanner control API 112 to acquire the status of the scanner device 110 at regular intervals (step S110). When a failure is detected (step S111), the scanner monitoring program 113 is stored in the failure information storage unit 140. The information is recorded in the monitored information log (step S112). Similarly, the printer monitoring program 123 uses the printer control API 122 to acquire the status of the printer device 120 at regular intervals (step S120). When a failure is detected (step S121), the printer monitoring program 123 stores the status in the failure information storage unit 140. The information is recorded in the stored monitoring information log (step S122). Similarly, the card reader monitoring program 133 acquires the status of the card reader device 130 at regular intervals using the card reader control API 132 (step S130), and stores a failure information storage when a failure is detected (step S131). The information is recorded in the monitoring information log stored in the unit 140 (step S132). Although the scanner device 110, the printer device 120, and the card reader device 130 have been described here, the same applies to other devices (for example, a CRT display device 901, a K / B 902, a mouse 903, an FDD 904, a magnetic disk device 920, and a CDD 905). It is.

  The log monitoring unit 150 constantly monitors the monitoring information log. When failure information is recorded in the log, the failure information transmission unit 152 causes the failure of the log monitoring control unit 171 operating on the monitoring server device 170 through the WAN 190. The information reception unit 173 is notified of the information (step S152).

  In the monitoring terminal device 180, the monitoring result notification unit 181 operates (step S171), and notifies the failure information notified to the failure information reception unit 173 of the log monitoring control unit 171 to a system administrator or the like (step S180).

  The communication confirmation unit 151 in the log monitoring unit 150 and the confirmation response unit 172 in the log monitoring control unit 171 confirm each other's life and death at regular intervals (step S150 and step S170), and the life / death confirmation is lost. In that case, the failure information transmission unit 152 of the log monitoring unit 150 stops transmission of the failure information (step S151). When the life / death confirmation is obtained again, the transmission of the fault information is resumed from the place where the previous transmission of the monitoring information log was interrupted (step S152).

  Thus, in the present embodiment, in the monitoring system (or monitoring method), the monitoring target terminal device 100 (or a device or computer that executes a monitoring program) connects peripheral devices, and the monitoring server device 170 is a network. The peripheral device connected to the monitoring target terminal device 100 is monitored via the.

  In the monitoring target terminal device 100, the peripheral device monitoring unit monitors the state of the peripheral device and detects a failure of the peripheral device (steps S110, S111, S120, S121, S130, S131: peripheral device monitoring step (processing) )). The failure information storage unit 140 stores failure information related to the failure detected by the peripheral device monitoring unit (steps S112, S122, and S132: failure information storage step (process)). If the communication confirmation unit 151 transmits an inquiry to the monitoring server device 170 and receives a response to the inquiry from the monitoring server device 170, the communication confirmation unit 151 determines that communication with the monitoring server device 170 is possible (steps S150 and S151: communication). Confirmation step (processing)). The failure information transmission unit 152 determines that communication with the monitoring server device 170 is possible by the communication confirmation unit 151 and the failure information storage unit 140 stores the failure information to be transmitted. The failure information to be transmitted is transmitted to 170 (step S152: failure information transmission step (process)).

  In the monitoring server device 170, the confirmation response unit 172 returns a response to the inquiry transmitted by the communication confirmation unit 151 of the monitoring target terminal device 100 (step S170: confirmation response step (process)). The failure information receiving unit 173 receives the failure information transmitted by the failure information transmitting unit 152 of the monitoring target terminal device 100 (step S171: failure information receiving step (process)). The failure information output unit 174 outputs the failure information received by the failure information reception unit 173 (failure information output step (process)). In the monitoring terminal device 180, the monitoring result notification unit 181 receives the failure information output by the failure information output unit 174 of the monitoring server device 170 via the network, and displays the received failure information on a screen, for example. The system administrator or the like is notified by sending it by e-mail (step S180: monitoring result notifying step (process)).

  As described above, according to the present embodiment, when a failure occurs in the communication path or the like and the failure information of the terminal cannot be transmitted, the failure information transmission is stopped once and the failure information is restored after the failure is recovered. Transmission can be automatically resumed, and failure to notify failure information can be eliminated. In addition, system load such as CPU load, memory usage, and network load due to repeated retransmission of failure information is reduced.

As described above, in the present embodiment,
Devices (peripheral devices) such as printers, scanners, card readers, TV (video) phones connected to special terminals (monitored terminal devices) such as unmanned contract machines such as financial institutions, ATMs (Automated Teller Machines) and window terminals ) On a special terminal in a remote monitoring system
(A) Various device monitoring mechanisms (peripheral device monitoring unit)
(B) Monitoring information log (failure information storage unit)
(C) Log monitoring mechanism (log monitoring unit)
(D) Communication confirmation mechanism (communication confirmation unit)
On the monitoring server (monitoring server device)
(E) Log monitoring control mechanism (log monitoring control unit)
(F) Communication confirmation mechanism (confirmation response unit)
When (a) outputs monitoring information (failure information) to (b) and (c) outputs the monitoring result of (b) to (e), the result cannot be output due to a failure such as a communication error. In this case, the device monitoring method has been described, in which the communication state is grasped by (d) and (f), and re-notification can be surely performed after the failure is resolved.

Embodiment 2. FIG.
FIG. 4 is a block diagram showing a configuration of the monitoring system according to the present embodiment.

  In FIG. 4, the CPU usage rate measuring unit 191 measures the CPU load (usage rate) of the OS 160. The CPU usage rate threshold setting unit 193 sets a CPU load threshold. The monitoring interval control units 195 to 197 set the monitoring interval of each device monitoring program. In addition, about the component same as FIG. 1, the same code | symbol is attached | subjected and the overlapping description is abbreviate | omitted.

  Next, the operation will be described.

  FIG. 5 is a flowchart showing the operation of the monitoring system according to the present embodiment.

  The CPU usage rate measurement unit 191 constantly measures the CPU load on the OS 160 and transmits the measured value to the CPU usage rate threshold setting unit 193 (step S190). Further, the CPU usage rate threshold setting unit 193 sets a threshold value (upper limit of CPU usage rate) in advance. When the CPU usage rate measured by the CPU usage rate measuring unit 191 reaches the set threshold value, the CPU usage rate threshold value setting unit 193 instructs the monitoring interval control units 195 to 197 to widen the monitoring interval, and performs monitoring. The interval control units 195 to 197 increase the monitoring interval of each device monitoring program (steps S191 and S192). When the measured value of the CPU load falls below the threshold value, the monitoring interval is narrowed in the same manner as described above. The other operations are the same as those shown in FIG.

  As described above, in the present embodiment, in the monitoring target terminal device 100, the CPU usage rate measuring unit 191 measures the usage rate of the CPU and outputs the measured value (step S190: CPU usage rate measuring step (processing) )). The CPU usage rate threshold setting unit 193 sets a CPU usage rate threshold value in advance. The monitoring interval control units 195 to 197 compare the measurement value output from the CPU usage rate measuring unit 191 with the threshold value set by the CPU usage rate threshold setting unit 193, and the peripheral device monitoring unit determines whether the peripheral device monitoring unit is in accordance with the comparison result. The interval for monitoring the state of the peripheral device is controlled (steps S191 and S192: monitoring interval control step (process)).

  As described above, according to the present embodiment, the monitoring interval of various device monitoring programs is set in accordance with the system load such as the CPU usage rate to perform device monitoring. The performance of other applications is not affected, and device monitoring can be performed at an optimal monitoring interval for maintaining the throughput of business applications.

Embodiment 3 FIG.
In FIG. 4, in the second embodiment, the CPU usage rate measurement unit 191 measures the CPU load of the system. However, in this embodiment, the CPU usage rate measurement unit 191 measures the device monitoring program (scanner monitoring program 113). , Printer monitoring program 123, card reader monitoring program 133) Measure the CPU load of each. The CPU usage rate threshold setting unit 193 sets a CPU usage rate that can be used by the entire device monitoring program. The configuration of the monitoring system according to the present embodiment is the same as that shown in FIG.

  Next, the operation will be described.

  A CPU usage rate that can be used by the entire device monitoring program is set in the CPU usage rate threshold setting unit 193. The CPU usage rate measuring unit 191 measures the load of each device monitoring program (scanner monitoring program 113, printer monitoring program 123, card reader monitoring program 133), and notifies the CPU usage rate threshold setting unit 193 of the load. When the total CPU usage rate of each device monitoring program exceeds the threshold, an instruction to increase the monitoring interval of each device monitoring program is transmitted to any (or a plurality) of the monitoring interval control units 195 to 197. When the CPU load falls below the set threshold, the monitoring interval is shortened in the same manner as described above.

  Thus, in the present embodiment, in the monitoring target terminal device 100, the CPU usage rate measuring unit 191 measures the CPU usage rate by each peripheral device monitoring unit. The CPU usage rate threshold setting unit 193 sets a threshold value that is a sum of the CPU usage rates by the peripheral device monitoring units. The monitoring interval control units 195 to 197 compare the total measurement value of each peripheral device monitoring unit output from the CPU usage rate measuring unit 191 with the threshold set by the CPU usage rate threshold setting unit 193, and the comparison result In response to this, each peripheral device monitoring unit controls the interval at which the status of each peripheral device is monitored.

  As described above, according to the present embodiment, the CPU usage rate measurement unit 191 measures the CPU usage rate for each device monitoring program, and the CPU usage rate threshold setting unit 193 can use the CPU for the entire device monitoring program. By setting the rate, the CPU usage rate that can be used by the device monitoring program can be strictly set, and the load control of the device monitoring program can be performed more finely.

  In the present embodiment, the CPU usage rate threshold setting unit 193 sets a threshold value that is the sum of the CPU usage rates by the peripheral device monitoring units, but the threshold value for the CPU usage rate by the peripheral device monitoring units. May be set separately. At this time, the monitoring interval control units 195 to 197 correspond to the measured values of the peripheral device monitoring units output from the CPU usage rate measuring unit 191 and the peripheral device monitoring units set by the CPU usage rate threshold setting unit 193. The threshold is compared, and the interval at which each peripheral device monitoring unit monitors the state of each peripheral device is controlled according to the comparison result.

Embodiment 4 FIG.
FIG. 6 is a block diagram showing the configuration of the monitoring system according to the present embodiment.

  In FIG. 6, the memory usage measuring unit 192 measures the memory usage of the OS 160. The memory usage threshold setting unit 194 sets a memory usage threshold. The monitoring interval control units 195 to 197 set the monitoring interval of each device monitoring program. In addition, about the component same as FIG. 1, the same code | symbol is attached | subjected and the overlapping description is abbreviate | omitted.

  FIG. 7 is a flowchart showing the operation of the monitoring system according to the present embodiment.

  The memory usage measuring unit 192 constantly measures the memory usage on the OS 160 and transmits the measured value to the memory usage threshold setting unit 194 (step S193). Also, the memory usage threshold setting unit 194 sets a threshold (an upper limit of the memory usage) in advance. When the memory usage measured by the memory usage measuring unit 192 reaches the set threshold, the memory usage threshold setting unit 194 instructs the monitoring interval control units 195 to 197 to increase the monitoring interval, The monitoring interval control unit lengthens the monitoring interval of each device monitoring program (steps S194 and S195). When the measured value of the memory usage is below the threshold, the monitoring interval is shortened in the same manner as described above. The other operations are the same as those shown in FIG.

  Thus, in the present embodiment, in the monitored terminal device 100, the memory usage measuring unit 192 measures the memory usage and outputs the measured value (step S193: memory usage measuring step (processing) )). The memory usage threshold setting unit 194 sets a memory usage threshold in advance. The monitoring interval control units 195 to 197 compare the measurement value output from the memory usage amount measuring unit 192 with the threshold value set by the memory usage amount threshold setting unit 194, and the peripheral device monitoring unit determines whether the peripheral device monitoring unit is in accordance with the comparison result. The interval for monitoring the state of the peripheral device is controlled (steps S194 and S195: monitoring interval control step (process)).

  As described above, according to the present embodiment, the monitoring interval of various device monitoring programs is set in accordance with the system load such as the memory usage and the device monitoring is performed. The performance of other applications is not affected, and device monitoring can be performed at an optimal monitoring interval for maintaining the throughput of business applications.

Embodiment 5. FIG.
In FIG. 6, in the fourth embodiment, the memory usage measuring unit 192 measures the memory usage of the system. However, in this embodiment, the memory usage measuring unit 192 uses the device monitoring program (scanner monitoring program). 113, printer monitoring program 123, card reader monitoring program 133), each memory usage is measured. The memory usage threshold setting unit 194 sets a memory usage that can be used by the entire device monitoring program. The configuration of the monitoring system according to the present embodiment is the same as that shown in FIG.

  Next, the operation will be described.

  The memory usage threshold setting unit 194 sets the memory usage available for the entire device monitoring program. The memory usage measuring unit 192 measures the memory usage of each device monitoring program (scanner monitoring program 113, printer monitoring program 123, card reader monitoring program 133) and notifies the memory usage threshold setting unit 194. . When the total memory usage of each device monitoring program exceeds the threshold, an instruction to increase the monitoring interval of each device monitoring program is transmitted to any (or a plurality) of the monitoring interval control units 195 to 197. If the memory usage is below the set threshold, the monitoring interval is shortened in the same manner as described above.

  Thus, in the present embodiment, in the monitoring target terminal device 100, the memory usage measuring unit 192 measures the memory usage by each peripheral device monitoring unit. The memory usage threshold value setting unit 194 sets a threshold value that is a sum of the memory usage amounts of the peripheral device monitoring units. The monitoring interval control units 195 to 197 compare the sum of the measurement values of each peripheral device monitoring unit output from the memory usage measuring unit 192 with the threshold set by the memory usage threshold setting unit 194, and the comparison result In response to this, each peripheral device monitoring unit controls the interval at which the status of each peripheral device is monitored.

  As described above, according to the present embodiment, the memory usage measuring unit measures the memory usage for each device monitoring program, and the memory usage threshold setting unit determines the memory usage that can be used by the entire device monitoring program. By setting, it is possible to strictly set the memory usage that can be used by the device monitoring program, and it is possible to more finely control the load of the device monitoring program.

  In this embodiment, the memory usage threshold value setting unit 194 sets a threshold value that is the sum of the memory usage amounts by the peripheral device monitoring units. However, the threshold values for the memory usage amounts by the peripheral device monitoring units are set separately. May be set. At this time, the monitoring interval control units 195 to 197 correspond to the measured values of the peripheral device monitoring units output from the memory usage measuring unit 192 and the peripheral device monitoring units set by the memory usage threshold setting unit 194. The threshold is compared, and the interval at which each peripheral device monitoring unit monitors the state of each peripheral device is controlled according to the comparison result.

Embodiment 6 FIG.
The monitoring system according to the present embodiment is a combination of the second or third embodiment and the fourth or fifth embodiment. In the present embodiment, the monitoring target terminal device 100 includes a CPU usage rate measuring unit 191 and a CPU usage rate threshold setting unit 193 shown in FIG. 4, a memory usage measuring unit 192, and a memory usage threshold value shown in FIG. A setting unit 194. Other configurations are the same as those in FIGS. 4 and 6.

  Further, the operation of the monitoring system according to the present embodiment is the same as that of the second to fifth embodiments.

  According to the present embodiment, the monitoring interval of various device monitoring programs is set corresponding to both the CPU usage rate and the memory usage amount to monitor the device, so the load control of the device monitoring program is performed more accurately. It becomes possible to do.

As described above, in the present embodiment, in the same system as in the first embodiment, on the special terminal,
(G) CPU load measurement mechanism (CPU usage rate measurement unit)
(H) Memory usage measurement mechanism (memory usage measurement unit)
(I) CPU load threshold detection mechanism (CPU usage rate threshold setting unit)
(J) Memory usage threshold detection mechanism (memory usage threshold setting unit)
(K) Monitoring interval measurement mechanism (monitoring interval control unit)
(G) (h) constantly measures the CPU load (usage rate) and memory usage, and (k) monitors various device monitoring mechanisms corresponding to the threshold values set in (i) and (j). A device monitoring method characterized by adjusting the interval has been described.

  Further, in the device monitoring method according to the present embodiment, as in the third embodiment, the CPU usage rate that can be used by various device monitoring mechanisms is set for the CPU load threshold detection mechanism, and the set CPU usage is set. It may be configured to operate so as not to exceed the rate.

  In addition, the device monitoring method according to the present embodiment enables and sets the memory usage amount that can be used by the various device monitoring mechanisms for the memory usage threshold detection mechanism as in the fifth embodiment. It may be configured to operate so as not to exceed the memory usage.

Further, when the present embodiment is implemented by a program, the program executed on the monitoring target terminal device is:
A monitoring mechanism for various devices;
Monitoring information log,
A log monitoring mechanism;
A communication confirmation mechanism;
CPU load measurement mechanism,
A memory usage measurement mechanism;
A CPU load threshold detection mechanism;
A memory usage threshold detection mechanism;
A program for causing a computer to execute a monitoring interval measurement mechanism.

The figure which shows an example of the hardware constitutions of the monitoring object terminal device in Embodiment 1-6. 1 is a block diagram illustrating a configuration of a monitoring system according to Embodiment 1. FIG. FIG. 3 is a flowchart showing the operation of the monitoring system according to the first embodiment. FIG. 4 is a block diagram showing a configuration of a monitoring system according to Embodiments 2 and 3. FIG. 6 is a flowchart showing the operation of the monitoring system according to the second and third embodiments. FIG. 6 is a block diagram showing a configuration of a monitoring system according to Embodiments 4 and 5. FIG. 6 is a flowchart showing the operation of the monitoring system according to the fourth and fifth embodiments.

Explanation of symbols

  100 Monitoring target terminal device, 110 Scanner device, 111, 121, 131 Device driver, 112 Scanner control API, 113 Scanner monitoring program, 120 Printer device, 122 Printer control API, 123 Printer monitoring program, 130 Card reader device , 132 Card reader control API, 133 Card reader monitoring program, 140 Fault information storage unit, 150 Log monitoring unit, 151 Communication confirmation unit, 152 Fault information transmission unit, 160 OS, 170 Monitoring server device, 171 Log monitoring control unit 172 Confirmation response unit 173 Fault information receiving unit 174 Fault information output unit 180 Monitoring terminal device 181 Monitoring result notification unit 190 WAN 191 CPU usage rate measuring unit 192 Memory usage measuring unit 193 C U usage rate threshold setting unit, 194 memory usage threshold setting unit, 195, 196, 197 monitoring interval control unit, 901 CRT display device, 902 K / B, 903 mouse, 904 FDD, 905 CDD, 911 CPU, 912 bus, 913 ROM, 914 RAM, 915 communication board, 920 magnetic disk drive, 922 window system, 923 program group, 924 file group.

Claims (8)

In the monitoring target terminal device that communicates with the monitoring server device that monitors the peripheral device via the network and connects the peripheral device,
A peripheral device monitoring unit that monitors a state of the peripheral device and detects a failure of the peripheral device;
A failure information storage unit that stores failure information related to a failure detected by the peripheral device monitoring unit;
A communication confirmation unit that determines that communication with the monitoring server device is possible when an inquiry is transmitted to the monitoring server device and a response to the inquiry is received from the monitoring server device;
If the communication confirmation unit determines that communication with the monitoring server device is possible and failure information to be transmitted is stored in the failure information storage unit, the failure to be transmitted to the monitoring server device A monitoring target terminal device comprising: a failure information transmission unit that transmits information. The monitored terminal device has a CPU (Central Processing Unit), and
CPU usage rate measurement unit that measures the usage rate of the CPU and outputs the measured value;
CPU usage rate threshold setting section for setting a CPU usage rate threshold in advance;
The measurement value output by the CPU usage rate measurement unit is compared with the threshold value set by the CPU usage rate threshold setting unit, and the peripheral device monitoring unit monitors the state of the peripheral device according to the comparison result. The monitoring target terminal device according to claim 1, further comprising a monitoring interval control unit that controls the interval. The monitored terminal device has a memory, and
A memory usage measuring unit for measuring the memory usage and outputting the measured values;
A memory usage threshold value setting unit for setting a memory usage threshold value in advance;
The measurement value output from the memory usage measuring unit is compared with the threshold set by the memory usage threshold setting unit, and the peripheral device monitoring unit monitors the state of the peripheral device according to the comparison result. The monitoring target terminal device according to claim 1, further comprising a monitoring interval control unit that controls the interval. The monitored terminal device is:
A plurality of peripheral devices are connected, and the peripheral device monitoring unit is provided for each peripheral device,
The CPU usage rate measurement unit measures the CPU usage rate by each peripheral device monitoring unit,
The CPU usage rate threshold setting unit sets a threshold value of the total CPU usage rate by each peripheral device monitoring unit,
The monitoring interval control unit
The total of the measurement values of each peripheral device monitoring unit output by the CPU usage rate measuring unit is compared with the threshold value set by the CPU usage rate threshold setting unit, and each peripheral device monitoring unit determines whether or not the comparison result is the result. The monitoring target terminal device according to claim 2, wherein an interval for monitoring a state of each peripheral device is controlled. The monitored terminal device is:
A plurality of peripheral devices are connected, and the peripheral device monitoring unit is provided for each peripheral device,
The memory usage measuring unit measures the memory usage by each peripheral device monitoring unit,
The memory usage threshold setting unit sets a threshold of a value obtained by summing the memory usage by each peripheral device monitoring unit,
The monitoring interval control unit
The total of the measurement values of each peripheral device monitoring unit output by the memory usage measuring unit is compared with the threshold value set by the memory usage threshold setting unit, and each peripheral device monitoring unit responds according to the comparison result. The monitoring target terminal device according to claim 3, wherein an interval for monitoring a state of each peripheral device is controlled. In a monitoring program executed by a monitoring target terminal device that communicates with a monitoring server device that monitors a peripheral device via a network and connects the peripheral device,
A peripheral device monitoring process for monitoring a state of the peripheral device and detecting a failure of the peripheral device;
A fault information storage process for storing fault information relating to a fault detected by the peripheral device monitoring process;
A communication confirmation process for determining that communication with the monitoring server device is possible when an inquiry is transmitted to the monitoring server device and a response to the inquiry is received from the monitoring server device;
When it is determined that communication with the monitoring server device is possible by the communication confirmation processing, and failure information to be transmitted is stored in the monitored terminal device, the failure to be transmitted to the monitoring server device A monitoring program for causing a computer to execute failure information transmission processing for transmitting information. In a monitoring system comprising a monitoring target terminal device that connects a peripheral device and a monitoring server device that monitors the peripheral device connected to the monitoring target terminal device via a network,
The monitored terminal device is:
A peripheral device monitoring unit that monitors a state of the peripheral device and detects a failure of the peripheral device;
A failure information storage unit that stores failure information related to a failure detected by the peripheral device monitoring unit;
A communication confirmation unit that determines that communication with the monitoring server device is possible when an inquiry is transmitted to the monitoring server device and a response to the inquiry is received from the monitoring server device;
If the communication confirmation unit determines that communication with the monitoring server device is possible and failure information to be transmitted is stored in the failure information storage unit, the failure to be transmitted to the monitoring server device A failure information transmission unit for transmitting information,
The monitoring server device
A confirmation response unit that returns a response to the inquiry transmitted by the communication confirmation unit of the monitoring target terminal device;
A failure information receiving unit for receiving the failure information transmitted by the failure information transmitting unit of the monitored terminal device;
A monitoring system comprising: a failure information output unit that outputs the failure information received by the failure information receiving unit. In a monitoring method using a monitoring system comprising a monitoring target terminal device that connects a peripheral device and a monitoring server device that monitors the peripheral device connected to the monitoring target terminal device via a network,
The peripheral device monitoring step in which the monitoring target terminal device monitors the state of the peripheral device and detects a failure of the peripheral device;
A failure information storage step in which the monitored terminal device stores failure information relating to a failure detected by the peripheral device monitoring step;
When the monitoring target terminal device transmits an inquiry to the monitoring server device and receives a response to the inquiry from the monitoring server device, a communication confirmation step of determining that communication with the monitoring server device is possible;
A confirmation response step in which the monitoring server device returns a response to the inquiry transmitted in the communication confirmation step;
When it is determined that the monitoring target terminal device can communicate with the monitoring server device by the communication confirmation step, and failure information to be transmitted is stored in the monitoring target terminal device, the monitoring server A failure information transmission step of transmitting the failure information to be transmitted to a device;
A failure information receiving step in which the monitoring server device receives the failure information transmitted in the failure information transmitting step;
The monitoring method comprising: a failure information output step for outputting the failure information received by the failure information receiving step.

Images