JP7110762B2 - Supervisory control program, supervisory control method and information processing device - Google Patents

Description

The present invention relates to a supervisory control program, a supervisory control method, and an information processing apparatus.

From the aspect of stable operation and failure response, the system incorporates a mechanism to monitor the operation of the system. For example, monitoring software called an agent may be installed in a system to be monitored. This agent realizes system monitoring by executing a monitoring program for each item defined by the system operator or the like, such as various system resources, networks, and applications.

In this way, the monitoring program executed by the agent can be freely created by the system operator. There is also a side that occurs. In this case, as a result of the agent adversely affecting the operation of software other than the agent, the agent used in the aspect of monitoring interferes with the original task given to the system. In order to prevent this, a timeout period is set in the monitoring process executed by the monitoring program to forcibly terminate the monitoring process after a certain period of time.

JP-A-2006-338543 WO2014/054274

However, the above technique has one aspect that the timeout period for system monitoring cannot be set appropriately.

In other words, the setting of the above timeout is currently left to manual setting by the system operator or the like. Since the timeout period manually set in this way does not always correspond to the operation status of the system, it is not always possible to terminate the monitoring process at an appropriate timing.

In addition to this, although a fixed value is set for the above timeout period, the operating conditions of the system are not always constant. Therefore, even if the manually set timeout time is valid at one point in time, it may not be valid at another point in time. For example, the load state of the system changes depending on time conditions such as busy periods and off-seasons, and the time required for monitoring processing executed by the monitoring program is also affected by the load state. If a fixed timeout period is set under a situation in which the operating conditions of the system dynamically change, the timeout period may be excessive or insufficient due to changes in the operating conditions of the system. For example, if the timeout time is too short than the time required for monitoring processing, system monitoring will not function. is sometimes hindered.

In one aspect, an object of the present invention is to provide a supervisory control program, a supervisory control method, and an information processing apparatus capable of setting a timeout period according to the operation status of the system.

In one aspect, the monitoring control program executes the plurality of monitoring processes that are executed by setting a first timeout period for forcibly terminating the monitoring process for each of the plurality of monitoring processes that monitor the operational status of the system. When each time is acquired and the plurality of monitoring processes are restarted, a computer is made to execute a process of setting a second timeout time determined according to the acquired execution time to the corresponding monitoring process.

System monitoring timeouts can be set appropriately.

FIG. 1 is a diagram illustrating an example of a use case of a supervisory control program according to the first embodiment. FIG. 2 is a block diagram of an example of a functional configuration of a host according to the first embodiment; FIG. 3 is a diagram showing an example of the record file 34. As shown in FIG. FIG. 4 is a flowchart illustrating the procedure of activation processing according to the first embodiment. FIG. 5 is a flowchart illustrating the procedure of the first stop processing according to the first embodiment. FIG. 6 is a flowchart illustrating the procedure of the second stop processing according to the first embodiment. FIG. 7 is a diagram showing another example of the performance file 34. As shown in FIG. FIG. 8 is a diagram illustrating a hardware configuration example of a computer that executes the supervisory control program according to the first and second embodiments.

A supervisory control program, a supervisory control method, and an information processing apparatus according to the present application will be described below with reference to the accompanying drawings. Note that this embodiment does not limit the disclosed technology. Further, each embodiment can be appropriately combined within a range in which the contents of processing are not inconsistent.

[Example of use case]
FIG. 1 is a diagram illustrating an example of a use case of a supervisory control program according to the first embodiment. FIG. 1 shows an example of monitoring a system SYS including hardware of hosts 30-1 to 30-n, software, and networks as an example of a use case. As shown in FIG. 1, for monitoring the system SYS, the manager server 10, the operator terminal 50, and the like can be used in addition to the system SYS itself, which is shown as an example of a monitoring target. Hereinafter, the hosts 30-1 to 30-n may be referred to as "hosts 30".

Among these, the manager server 10 and the host 30 are connected via an arbitrary network. Also, the manager server 10 and the operator terminal 50 can be connected via an arbitrary network, and ports can be connected via terminals such as connectors. For example, a network corresponds to any type of communication network, whether wired or wireless, such as a local area network or a wide area network. It should be noted that the topology shown in FIG. 1 is merely schematic from the aspect of explaining the monitoring function, and the actual topology is not limited to that shown in the figure. For example, it does not prevent the host 30 and the operator terminal 50 from being connected.

Here, the monitoring of the system SYS includes, for example, a definition file DF in which items for monitoring the host 30 are defined for each host 30, a manager 1 that provides an API (Application Programming Interface) for operating the host 30, a monitoring It is realized by providing the agent 2 that controls the programs 3a to 3n as package software. Hereinafter, the monitoring programs 3a to 3n may be referred to as "monitoring program 3".

More specifically, the definition file DF is created by the operator terminal 50 used by the operator of the system SYS. For example, the definition file DF includes items for monitoring the host 30 in units of the host 30, such as resources, networks, applications, etc., and execution conditions for executing the monitoring program 3 for executing monitoring processing corresponding to each item. is defined. The system SYS is monitored by the manager 1 operating on the manager server 10 and the agent 2 operating on the host 30 cooperating according to the definition file DF. For example, the manager 1 distributes the monitoring program 3 corresponding to the item designated to be monitored to the agent 2, and collects from the agent 2 a record file describing the monitoring results. Also, the agent 2 activates the monitoring programs 3a to 3n at the cycle defined in the definition file DF, and causes the monitoring programs 3a to 3n to perform monitoring processing.

As described above, the manager server 10 on which the manager 1 is executed, the host 30 on which the agent 2 is executed, and the operator terminal 50 used for creating the definition file DF are all labeled with labels for classifying functions. and its hardware configuration is not limited. Given that the host 30 is not limited to specific hardware, the host 30 can be a Web server, an AP (Application) server, a DB (DataBase) server, a mainframe, or a load balancer. do. Also, the operator terminal 50 corresponds to a desktop computer such as a personal computer. This is merely an example, and the operator terminal 50 may be any computer such as a laptop computer, a mobile terminal device, or a wearable terminal.

[One aspect of the challenge]
As explained in the background art section above, the monitoring program 3 executed by the agent 2 is a general-purpose monitoring program that monitors the usage of resources such as a CPU (Central Processing Unit), memory, and storage. In addition to being prepared by the providing vendor, the operator or the like can freely create a monitoring program customized according to the requirements of the system SYS such as Web and AP through the operator terminal 50 . Such customization increases the degree of freedom of monitoring, but on the other hand, the monitoring program 3 may cause an unintended failure in the host 30, or a loop may occur in the monitoring process executed by the monitoring program 3. There is one side. In this case, the agent 2 may adversely affect the operation of software other than the agent 2, such as a web service program or a web application program. become. In order to prevent this, the monitoring process executed by the monitoring program 3 is set with a timeout period for terminating the monitoring process after a certain period of time.

However, there is an aspect that it is difficult to appropriately set the timeout period for system monitoring.

One of the reasons for this is that it is entrusted to manual setting by an operator of the system SYS. With manual setting, the accuracy depends on the intuition and experience of the system SYS operator, so the time-out time is not always set to a reasonable value.

Another factor is that the timeout period is set to a fixed value. In other words, even if the manually set timeout period is a valid value at one point in time, the timeout period may not be a valid value at another point in time. For example, the load state of each host 30 changes depending on time conditions such as busy season and off-season, and the time required for monitoring processing executed by the monitoring program 3 also changes depending on the load state. If a fixed timeout period is set in such a situation that the operational status of each host 30 dynamically changes, the timeout period will be excessive or insufficient due to changes in the operational status of the system SYS. For example, if the timeout time is too short than the time required for monitoring processing, system monitoring will not function. tasks may be hindered.

[One aspect of problem-solving approach]
Therefore, when the monitoring program 3 is activated, the agent 2 according to the present embodiment obtains the measured value of the time required for the monitoring process executed by the monitoring program 3 in the past, and executes the monitoring process according to the measured value. Set timeout time for forced termination. In this manner, the actual measurement value of the required time when the monitoring program 3 normally ends the monitoring process is used for setting the timeout period, so that the set value of the timeout period can be brought closer to the operation status of the system SYS. Furthermore, since a different measured value is used to set the timeout time each time the monitoring program 3 is started, the set value of the timeout time can be made to follow changes in the operating conditions of the system SYS. Therefore, according to the agent 2 according to this embodiment, it is possible to set the timeout period in accordance with the operation status of the system SYS.

[Configuration of host 30]
FIG. 2 is a block diagram of an example of a functional configuration of a host according to the first embodiment; For convenience of explanation, FIG. 2 shows an excerpt of the functional units related to the functions corresponding to the above-described supervisory control program. It does not prevent you from being prepared.

As shown in FIG. 2 , the host 30 has a communication I/F (InterFace) section 31 , a storage section 33 and a control section 35 . The host 30 corresponds to an example of an information processing device.

The communication I/F unit 31 is an interface that controls communication with other devices such as the manager server 10 and the like.

As one embodiment, the communication I/F unit 31 corresponds to a network interface card such as a LAN card. For example, the communication I/F unit 31 receives distribution of a monitoring program including a definition file DF from the manager server 10, or outputs a result file in which execution results of the monitoring program are recorded to the manager server 10. do.

The storage unit 33 stores various programs such as an OS (Operating System) executed by the control unit 15, application programs such as the agent 2 and the monitoring programs 3a to 3n, and data used for various programs. Corresponds to an example of storage.

As one embodiment, the storage unit 33 can be implemented as an auxiliary storage device in the host 30 . For example, an HDD (Hard Disk Drive), an optical disk, an SSD (Solid State Drive), or the like can be used as the storage unit 33 . Note that the storage unit 33 does not necessarily have to be implemented as an auxiliary storage device, and can be implemented as a main storage device in the host 30 . In this case, various semiconductor memory devices such as RAM (Random Access Memory) and flash memory can be used for the storage unit 33 .

The storage unit 33 stores performance files 34A to 34N as an example of data used for programs executed by the control unit 35. FIG. In addition to these data, the storage unit 33 may store other electronic data. For example, the storage unit 33 can also store the definition file DF corresponding to the host 30 among the definition files DF defined for each of the hosts 30-1 to 30-n.

The results files 34A to 34N are data in which the monitoring results of the monitoring programs 3a to 3n are described as results. Hereinafter, the record files 34A to 34N may be referred to as "record file 34".

As one embodiment, the result file 34 can employ data in which items such as the start date and time, the end date and time, and the execution time of the monitoring process executed by the monitoring program 3 are associated with each other. FIG. 3 is a diagram showing an example of the record file 34. As shown in FIG. FIG. 3 shows an example in which a record including the start date and time, the end date and time, and the execution time of the monitoring process is additionally described every time the monitoring program 3 executes the monitoring process. In the first line of the result file 34 shown in FIG. It ended at minute 03 seconds 03.030 milliseconds, meaning that the duration was 3006 milliseconds. In the records from the second line onward shown in FIG. 3, although the values of each field are different, the meanings of the items of start date/time, end date/time, and execution time are common. Although FIG. 3 shows an example in which the result file 34 is described in CSV (Comma-Separated Values) as an example, it may be described in another format, such as XML (Extensible Markup Language). It doesn't matter.

The control unit 35 is a processing unit that performs overall control of the host 30 .

As one embodiment, the controller 35 can be implemented by a hardware processor such as a CPU or MPU (Micro Processing Unit). Here, as examples of processors, CPUs and MPUs have been exemplified. -Purpose computing on Graphics Processing Units). Alternatively, the control unit 35 may be realized by hardwired logic such as ASIC (Application Specific Integrated Circuit) or FPGA (Field Programmable Gate Array).

The control unit 35 expands the agent 2 set as a resident program on the work area of RAM implemented as a main storage device (not shown) and executes the agent 2, thereby virtually running the monitoring control unit 300. Realize. Furthermore, the control unit 35 virtually realizes the monitoring execution units 360A to 360N by executing the monitoring programs 3a to 3n under the control of the monitoring control unit 300. FIG. Here, as an example of the program executed by the control unit 35, the agent 2 related to system monitoring and the monitoring program 3 are extracted and cited as an example. It goes without saying that application programs such as web service programs and web application programs are executed.

As shown in FIG. 2 , the monitor control unit 300 has a reference unit 310 , an acquisition unit 320 , a setting unit 330 , a start unit 340 and a stop unit 350 .

The reference unit 310 is a processing unit that references the definition file DF.

As an embodiment, the reference unit 310 executes the following processing when the agent 2, which is a resident program, is started or restarted, or when the definition file DF set in the host 30 is updated. . That is, the reference unit 310 refers to the definition file DF corresponding to the host 30 among the definition files DF stored in the manager server 10 or a file server or the like accessible by the manager server 10 and the host 30, or refers to the definition file DF. It accepts distribution of the monitoring program 3 corresponding to the items defined in the DF.

The acquisition unit 320 is a processing unit that acquires the performance file 34 .

As one embodiment, the acquisition unit 320 executes the following process in parallel for each monitoring program 3 corresponding to the item for which execution of monitoring is defined in the definition file DF. That is, the acquisition unit 320 waits until the execution conditions of the monitoring program 3 defined in the definition file DF are satisfied. For example, if the execution condition of the monitoring program 3 is to execute the monitoring process at regular intervals, the monitoring program 3 waits until a predetermined time has elapsed since the previous activation of the monitoring program 3 . Then, when the execution condition of the monitoring program 3 is satisfied, the obtaining unit 320 obtains the result file 34 corresponding to the monitoring program 3 from among the result files 34A to 34N stored in the storage unit 33 .

Here, as an example of the execution condition, an example of executing the monitoring process at regular intervals is given, but the execution condition is not limited to this. For example, the monitoring process may be executed at a regular time, or may be executed when a request is received from the operator terminal 50 .

The setting unit 330 is a processing unit that sets a timeout period.

As one embodiment, the setting unit 330 forcibly terminates the monitoring process executed by the monitoring program 3 according to the execution time included in the result file obtained by the obtaining unit 320 every time the result file is obtained. Calculate the timeout period to be used. For example, the setting unit 330 uses a past predetermined number of execution times, for example, five execution times, among the execution times included in the performance file acquired by the acquisition unit 320, to calculate the timeout period for forcibly terminating the current monitoring process. . Various statistical processes can be used to calculate such a timeout period. For example, the setting unit 330 calculates the calculated value T _{out_Av*α} of the timeout period by multiplying the arithmetic mean value Av of the past five execution times by the safety factor α.

Then, the setting unit 330 determines whether or not the calculated value T _{out_Av*α} of the timeout period is less than the allowable limit value T _{out_max} of the timeout period permitted to be set in the monitoring process of the monitoring program 3. judge. At this time, if the calculated value T _{out_Av*α} of the timeout period is less than the allowable limit value T _{out_max} of the timeout period, the setting unit 330 sets the calculated value T out_Av* _α of the timeout period as the timeout period T _out . On the other hand, if the calculated value _{Tout_Av *α} of the timeout period is not less than the allowable limit value _{Tout_max} of the timeout period, the setting unit 330 sets the allowable limit value _{Tout_max} of the timeout period to the timeout period Tout.

For example, when the record file 34 shown in FIG. 3 is obtained, the timeout period is calculated as follows. Assume here that the safety factor α used to calculate the timeout period is 1.5 and the allowable limit is 5000 milliseconds. In the result file 34 shown in FIG. 3, the most recent five execution times are 2993 milliseconds, 3179 milliseconds, 2882 milliseconds, 3119 milliseconds, and 3006 milliseconds, respectively. In this case, by multiplying the arithmetic average value of the past five execution times "(2993+3179+2882+3119+3006)/5" by the safety factor of 1.5, the calculated timeout time _{Tout_Av*α} is 4553.7. . In this case, the calculated value T _{out_Av*α} of the timeout period <the permissible limit value T _{out_max} of the timeout period, that is, “4553.7<5000”. Therefore, the timeout period T _out is calculated as 4553.7 milliseconds.

Here, as an example of statistical processing, the case of calculating the arithmetic mean value was exemplified, but other statistical processing such as calculating the weighted average value, extracting the median, or extracting the mode is performed. It doesn't matter. Also, although an example in which the safety factor is multiplied by the arithmetic mean value is given here, the safety factor may be added, and the safety factor may not necessarily be multiplied or added.

The activation unit 340 is a processing unit that controls activation of the monitoring program 3 .

As one embodiment, the activation unit 340 activates the monitoring program 3 for which the timeout period is set by the setting unit 330 . As a result, the monitoring execution unit 360 starts executing the monitoring program 3, thereby starting the monitoring process.

The stopping unit 350 is a processing unit that controls stopping of the monitoring program 3 .

As one aspect, the stopping unit 350 executes the following processing in parallel for each monitoring program 3 being executed started by the starting unit 340 . For example, the stopping unit 350 measures the elapsed time after the monitoring program 3 is activated as the execution time of the monitoring process. Then, if the monitoring program 3 is normally terminated before the execution time of the monitoring process passes the timeout time, the stopping unit 350 stores a record including the start date and time, the end date and time, and the execution time of the monitoring process in the result file. Add to 34. On the other hand, if the monitoring program 3 is not terminated normally before the monitoring process execution time elapses, the suspending unit 350 forcibly terminates the monitoring program 3, and then suppresses execution on a work area (not shown). The identification information of the monitoring program 3, such as the process name, is registered in the list. Execution of the monitoring program 3 having an entry in the execution suppression list is suppressed until the entry is deleted. Here, as an example, an example in which the agent 2 executes the recording to the result file 34 has been described, but the monitoring program 3 may execute the recording.

As another aspect, the stopping unit 350 also controls the stopping of Agent2. For example, the stopping unit 350 monitors updates to an execution inhibition list saved in a work area (not shown). At this time, if the execution suppression list is updated, the stopping unit 350 determines whether or not the number of monitoring programs 3 having entries in the execution suppression list is equal to or greater than a predetermined threshold Th. Here, if the number of monitoring programs 3 having entries in the execution suppression list is equal to or greater than the threshold value Th, a failure or failure that affects the monitoring process, which has a lighter processing load than the original task assigned to the host 30, is executed. A high load may be occurring on the host 30 . In this case, the stopping unit 350 forcibly terminates the agent 2 in order to reduce the processing load of the original task given to the host 30 .

[Process flow]
Next, the processing flow of the host 30 according to this embodiment will be described. Note that here, (1) start processing, (2) first stop processing, and (3) second stop processing executed by the host 30 will be described in this order.

(1) Activation Processing FIG. 4 is a flowchart illustrating the procedure of activation processing according to the first embodiment. As an example, this process is executed in parallel for each monitoring program 3 corresponding to an item for which execution of monitoring is defined in the definition file DF. By way of example only, when the monitoring program 3 is activated last time and a predetermined condition, such as an operation interval or a regular time, is satisfied, the activation process of the monitoring program 3 is started.

As shown in FIG. 4, the acquisition unit 320 acquires the result file 34 corresponding to the monitoring program 3 from among the result files 34A to 34N stored in the storage unit 33 (step S101). Subsequently, the setting unit 330 calculates a statistical value of execution times for a predetermined number of times in the past among the execution times included in the performance file acquired in step S101 (step S102).

Then, the setting unit 300 determines whether or not the calculated value _{Tout_Av*α} of the timeout period obtained by multiplying the statistical value of the execution time calculated in step S102 by the safety factor is less than the permissible limit value _{Tout_max} of the timeout period. Determine (step S103).

Here, if the calculated value T _{out_Av*α} of the timeout period is less than the permissible limit value T _{out_max} of the timeout period (Yes in step S103), the setting unit 330 sets the calculated value T _{out_Av*α} of the timeout period to the timeout period T _out . Set (step S104).

On the other hand, if the calculated value T _{out_Av*α} of the timeout time is not less than the allowable limit value T _{out_max} of the timeout time (No at step S103), the allowable limit value T _{out_max} of the timeout time is set to the timeout time T _out (step S105).

After either the timeout period T _out is set in step S104 or step S105 in this way, the activation unit 340 activates the monitoring program 3 for which the timeout period T _out is set (step S106), and terminates the process. do.

(2) First Stop Processing FIG. 5 is a flowchart showing the procedure of the first stop processing according to the first embodiment. As an example, this processing is executed in parallel for each monitoring program 3 being executed by the monitoring execution unit 360 by being activated by the activation processing shown in FIG.

As shown in FIG. 5, the stopping unit 350 measures the elapsed time after the monitoring program 3 is activated as the execution time of the monitoring process (step S201). If the monitoring program 3 is normally terminated before the execution time of the monitoring process elapses (Yes in step S202), the stopping unit 350 includes the start date/time, the end date/time, and the execution time of the monitoring process. The record is added to the result file 34 (step S203), and the process is terminated.

On the other hand, if the monitoring program 3 does not end normally before the execution time of the monitoring process passes the timeout time (No in step S202 and No in step S204), the stopping unit 350 forcibly terminates the monitoring program 3 (step S205). . Then, the stopping unit 350 registers the identification information of the monitoring program 3, for example, the process name, in an execution suppression list on a work area (not shown) (step S206), and terminates the process.

(3) Second Stop Processing FIG. 6 is a flowchart showing the procedure of the second stop processing according to the first embodiment. This process is continuously executed from the start of the agent 2 until it is terminated. As shown in FIG. 6, the stopping unit 350 monitors updates to an execution inhibition list stored in a work area (not shown) (step S301).

At this time, if there is an update to the execution suppression list (step S302 Yes), the stopping unit 350 determines whether or not the number of monitoring programs 3 having entries in the execution suppression list is equal to or greater than a predetermined threshold Th (step S303).

If the execution inhibition list is not updated (No at step S302), or if the number of monitoring programs 3 having entries in the execution inhibition list is less than the predetermined threshold value Th (No at step S303), the process returns to step S301 and the execution inhibition list is updated. wait for an update to

Here, if the number of monitoring programs 3 with entries in the execution suppression list is equal to or greater than the threshold Th (Yes in step S303), it affects the monitoring process with a lighter processing load than the original task given to the host 30. There is a possibility that a failure or a high load of this magnitude has occurred in the host 30 . In this case, from the aspect of reducing the processing load of the original task given to the host 30, the stopping unit 350 forcibly terminates the agent 2 (step S304), and terminates the process.

[One aspect of the effect]
As described above, when the monitoring program 3 is activated, the agent 2 according to the present embodiment acquires the measured value of the time required for the monitoring process executed by the monitoring program 3 in the past, and set the timeout period to forcibly terminate the monitoring process. In this manner, the actual measurement value of the required time when the monitoring program 3 normally ends the monitoring process is used for setting the timeout period, so that the set value of the timeout period can be brought closer to the operation status of the system SYS. Furthermore, since a different measured value is used to set the timeout time each time the monitoring program 3 is started, the set value of the timeout time can be made to follow changes in the operating conditions of the system SYS. Therefore, according to the agent 2 according to this embodiment, it is possible to set the timeout period in accordance with the operation status of the system SYS.

Although embodiments of the disclosed apparatus have been described so far, the present invention may be embodied in various forms other than the embodiments described above. Therefore, other embodiments included in the present invention will be described below.

[Timeout period]
In the above-described first embodiment, an example was described in which the execution time for the last predetermined number of times was used as the execution time for the predetermined number of times in the past to calculate the timeout period. is not limited to For example, the setting unit 330 can use the timing for calculating the timeout period and the time condition, for example, the execution period with a similar day of the week and time to calculate the timeout period.

FIG. 7 is a diagram showing another example of the performance file 34. As shown in FIG. In FIG. 7, assuming that the timeout period is calculated at 13:00:00 on April 8, 2018, the records whose day of the week and time match the timeout period calculation point are indicated by hatching. ing. That is, as shown in FIG. 7, for calculating the timeout period, the start time is 13:00:00:024 milliseconds on Mar. 4, 2018 and 13:00:00:032 on Mar. 11, 2018. milliseconds, 13:00:00019 ms on Mar 18, 2018, 13:00:00:041 ms on Mar 25, 2018, 13:00:00 on Apr 1, 2018 A run time of 5 records of 018 milliseconds is used. The execution times for these five records are 2993 milliseconds, 3179 milliseconds, 2882 milliseconds, 3119 milliseconds, and 3006 milliseconds in descending order from the time at which the timeout time was calculated. In this case, by multiplying the arithmetic mean value of the five execution times "(2993+3179+2882+3119+3006)/5" by the safety factor of 1.5, the calculated timeout time _{Tout_Av*α} is calculated as 4553.7. .

In this way, by using execution times with similar time conditions to calculate the timeout period, actual values of samples with similar system operating conditions are used to calculate the timeout period. can be calculated.

Distributed and integrated
Also, each component of each illustrated device may not necessarily be physically configured as illustrated. In other words, the specific form of distribution and integration of each device is not limited to the one shown in the figure, and all or part of them can be functionally or physically distributed and integrated in arbitrary units according to various loads and usage conditions. Can be integrated and configured. For example, one of the functional units included in the monitor control unit 300 may be connected to the host 30 via a network as an external device. In addition, another device has one of the functional units included in the monitoring control unit 300, and is connected to the network to cooperate with each other, thereby realizing the functions of the host 30 described above. good too.

[Monitoring control program]
Moreover, various processes described in the above embodiments can be realized by executing a prepared program on a computer such as a personal computer or a work station. Therefore, an example of a computer that executes a supervisory control program having functions similar to those of the above embodiments will be described below with reference to FIG.

FIG. 8 is a diagram illustrating a hardware configuration example of a computer that executes the supervisory control program according to the first and second embodiments. As shown in FIG. 8, the computer 100 has an operation unit 110a, a speaker 110b, a camera 110c, a display 120, and a communication unit . Furthermore, this computer 100 has a CPU 150 , a ROM 160 , an HDD 170 and a RAM 180 . Each part of these 110 to 180 is connected via a bus 140 .

As shown in FIG. 8, the HDD 170 stores a monitor control program 170a that exhibits the same functions as the monitor control unit 300 shown in the first embodiment. This monitor control program 170a may be integrated or separated like each component of the monitor control unit 300 shown in FIG. That is, the HDD 170 does not necessarily store all the data shown in the first embodiment, and the HDD 170 only needs to store data used for processing.

Under such an environment, the CPU 150 reads the supervisory control program 170 a from the HDD 170 and loads it into the RAM 180 . As a result, the supervisory control program 170a functions as a supervisory control process 180a, as shown in FIG. The supervisory control process 180a deploys various data read from the HDD 170 in an area assigned to the supervisory control process 180a among the storage areas of the RAM 180, and executes various processes using the deployed various data. For example, examples of processing executed by the supervisory control process 180a include the processing shown in FIGS. 4 to 6. FIG. Note that the CPU 150 does not necessarily have to operate all the processing units described in the first embodiment, as long as the processing units corresponding to the processes to be executed are virtually realized.

Note that the monitor control program 170a described above does not necessarily have to be stored in the HDD 170 or the ROM 160 from the beginning. For example, the supervisory control program 170a is stored in a “portable physical medium” such as a flexible disk inserted into the computer 100, so-called FD, CD-ROM, DVD disk, magneto-optical disk, IC card, or the like. Then, the computer 100 may acquire and execute the monitoring control program 170a from these portable physical media. Alternatively, the monitor control program 170a is stored in another computer or server device connected to the computer 100 via a public line, the Internet, LAN, WAN, etc., and the computer 100 acquires the monitor control program 170a from these. You can also run

The following notes are further disclosed with respect to the embodiments including the above examples.

(Appendix 1) Acquiring the execution time of each of the plurality of monitoring processes executed by setting a first timeout period for forcibly terminating the monitoring process for each of the plurality of monitoring processes for monitoring the operational status of the system. ,
When starting the plurality of monitoring processes again, setting a second timeout period determined according to the acquired execution time to the corresponding monitoring process;
A monitor control program characterized by causing a computer to execute processing.

(Appendix 2) Cause the computer to further execute a process of stopping the monitoring control program that manages a plurality of monitoring processes according to the number of monitoring processes forcibly terminated after reaching the set second timeout time. The monitor control program according to Supplementary Note 1, characterized by:

(Supplementary note 3) In the setting process, a statistic value of execution times for a predetermined number of times in the past going back from the setting of the second timeout period is set as the second timeout period. The supervisory control program described in .

(Supplementary Note 4) The setting process includes setting the statistical value of the execution time with similar time conditions including at least one of the day of the week and time between the setting of the second timeout period and the second timeout period. 3. The monitor control program according to appendix 3, characterized by setting the timeout time.

(Appendix 5) Acquiring the execution time of each of the plurality of monitoring processes executed by setting a first timeout period for forcibly terminating the monitoring process for each of the plurality of monitoring processes for monitoring the operational status of the system. ,
When starting the plurality of monitoring processes again, setting a second timeout period determined according to the acquired execution time to the corresponding monitoring process;
A supervisory control method characterized in that the processing is executed by a computer.

(Appendix 6) The computer further executes a process of stopping the monitoring control program that manages a plurality of monitoring processes according to the number of monitoring processes forcibly terminated after reaching the set second timeout time. The monitoring control method according to appendix 5, characterized by:

(Supplementary note 7) In the setting process, a statistic value of a predetermined number of execution times in the past going back from the setting of the second timeout period is set as the second timeout period. The supervisory control method described in .

(Supplementary Note 8) The setting process includes setting the statistical value of the execution time with similar time conditions including at least one of the day of the week and time between the setting of the second timeout period and the second timeout period. The supervisory control method according to appendix 7, characterized by setting a timeout period.

(Appendix 9) Acquiring the execution time of each of the plurality of monitoring processes executed by setting a first timeout period for forcibly terminating the monitoring process for each of the plurality of monitoring processes for monitoring the operating status of the system. an acquisition unit;
a setting unit that sets a second timeout period determined according to the acquired execution time to the corresponding monitoring process when restarting the plurality of monitoring processes;
An information processing apparatus characterized by comprising:

(Supplementary Note 10) The method further includes a stopping unit that stops the monitoring control program that manages a plurality of monitoring processes according to the number of monitoring processes forcibly terminated due to reaching the set second timeout time. The information processing device according to appendix 9.

(Supplementary Note 11) According to Supplementary note 9, the setting unit sets the statistical value of execution times for a predetermined number of times in the past going back from the setting of the second timeout period to the second timeout period. The information processing device described.

(Supplementary note 12) The setting unit sets the statistical value of the execution time with similar time conditions including at least one of the day of the week and the time between when the second timeout period is set to the second timeout period. 12. The information processing apparatus according to appendix 11, wherein the setting is made at time.

1 manager 2 agent 3 monitoring program 10 manager server 30 host 31 communication I/F section 33 storage section 34 result file 35 control section 300 monitoring control section 310 reference section 320 acquisition section 330 setting section 340 start section 350 stop section 360 monitoring execution Part 50 operator terminal

Claims (5)

Acquiring each execution time of the plurality of monitoring processes executed by setting a first timeout period for forcibly terminating the monitoring process for each of the plurality of monitoring processes for monitoring the operation status of the system;
setting a second timeout period determined according to the acquired execution time to the corresponding monitoring process when restarting the plurality of monitoring processes ;
stopping the monitoring control program that manages the plurality of monitoring processes according to the number of monitoring processes that are forcibly terminated after reaching the set second timeout period;
A monitor control program characterized by causing a computer to execute processing. 2. The method according to claim 1 , wherein in the setting process, a statistical value of execution times for a predetermined number of times in the past going back from the setting of the second timeout period is set as the second timeout period. Supervisory control program. In the setting process, a statistic value of execution times with similar time conditions including at least one of day of the week and time between when the second timeout period is set is set as the second timeout period. 3. The supervisory control program according to claim 2 , wherein: Acquiring each of the execution times of the plurality of monitoring processes executed by setting a first timeout period for forcibly terminating the monitoring process for each of the plurality of monitoring processes for monitoring the operation status of the system;
setting a second timeout period determined according to the obtained execution time to the corresponding monitoring process when starting the plurality of monitoring processes again ;
stopping the monitoring control program that manages the plurality of monitoring processes according to the number of monitoring processes that have reached the set second timeout time and have been forcibly terminated;
A supervisory control method characterized in that the processing is executed by a computer. an acquisition unit configured to acquire an execution time of each of the plurality of monitoring processes executed by setting a first timeout period for forcibly terminating the monitoring process for each of the plurality of monitoring processes for monitoring the operational status of the system;
a setting unit that sets a second timeout period determined according to the acquired execution time to the corresponding monitoring process when restarting the plurality of monitoring processes;
a stopping unit that stops a monitoring control program that manages the plurality of monitoring processes according to the number of monitoring processes forcibly terminated after reaching the set second timeout period;
An information processing apparatus characterized by comprising:

Images