WO2015155864A1

WO2015155864A1 - Information processing system and method

Info

Publication number: WO2015155864A1
Application number: PCT/JP2014/060363
Authority: WO
Inventors: 高宏漆谷
Original assignee: 富士通株式会社
Priority date: 2014-04-10
Filing date: 2014-04-10
Publication date: 2015-10-15

Abstract

The present information processing system includes a first device, and a first management device that acquires the value of a predetermined item from the first device. The first management device includes: a data storage unit that stores information indicating whether the value of the predetermined item has changed, with respect to one or a plurality of points in time; a comparison unit that compares, when the value of the predetermined item has been acquired from the first device, the acquired value of the predetermined item and the value of the predetermined item that has been previously acquired from the first device, and that stores information indicating whether the value of the predetermined item has changed in the data storage unit; and a determination unit that determines, on the basis of the information stored in the data storage unit and indicating whether the value of the predetermined item has changed, the point in time for acquiring the value of the predetermined item from the first device.

Description

Information processing system and method

Related to system management technology.

In the data center, a device (hereinafter referred to as a manager) equipped with software for managing the operation of the system is installed. The management targets of the manager are, for example, network devices, storage, system controllers, servers, OS (Operating System) on servers, physical domains separated by hardware, virtual domains virtualized on the hypervisor, and OS It is a virtual domain or the like virtualized by. The manager collects data on the status of hardware and processes from the management target, checks whether an error has occurred in the management target, and checks whether resources are being used efficiently.

By the way, with the spread of cloud computing, the scale of data centers is expanding. As the scale of the data center increases, the number of management targets increases, so the processing load for the manager to collect data increases. There is no problem if there is a contrivance to deal with the increase in manager load. However, if the manager load cannot be dealt with and the data collection process is delayed, the interval for collecting the data from the management target becomes long, and the discovery of the abnormality occurring in the management target is delayed. In such a situation, in the worst case, the system stops and the service cannot be provided.

In the prior art, a monitoring system that targets information processing devices divides monitoring targets into groups so that monitoring targets having the same performance characteristics are in the same group. In each group, the monitoring target is divided into a group monitored at a short monitoring interval and a group monitored at a long monitoring interval, thereby reducing the cost required for monitoring. However, this prior art is based on the premise that monitoring targets can be grouped according to performance characteristics.

JP 2006-338543 A

Therefore, in one aspect, an object of the present invention is to provide a technique for appropriately controlling a processing load for collecting data from a managed device.

The information processing system according to the present invention includes a first device and a first management device that acquires a value of a predetermined item from the first device. And the 1st management apparatus mentioned above acquired the value of the predetermined item from the data storage part which stores the information which shows whether the value of the predetermined item changed about one or several time points, and the 1st apparatus. A comparison unit that compares the acquired value of the predetermined item with the value of the predetermined item previously acquired from the first device and stores information indicating whether or not the value of the predetermined item has changed in the data storage unit; And a determination unit that determines a time point at which the value of the predetermined item is acquired from the first device, based on information stored in the data storage unit and indicating whether or not the value of the predetermined item has changed.

In one aspect, it is possible to appropriately control the processing load for collecting data from managed devices.

FIG. 1 is a diagram showing a system outline of the present embodiment. FIG. 2 is a diagram for explaining data collection. FIG. 3 is a functional block diagram of the proxy manager. FIG. 4 is a functional block diagram of the main manager. FIG. 5 is a diagram illustrating an example of data stored in the data storage unit of the proxy manager. FIG. 6 is a diagram illustrating an example of data stored in the history storage unit of the proxy manager. FIG. 7 is a diagram illustrating an example of data stored in the reference value storage unit of the main manager. FIG. 8 is a diagram illustrating an example of the first management table stored in the management data storage unit of the main manager. FIG. 9 is a diagram illustrating an example of the second management table stored in the management data storage unit of the main manager. FIG. 10 is a diagram illustrating a processing flow of processing in which the proxy manager collects data from the target device. FIG. 11 is a diagram illustrating a processing flow of the comparison processing. FIG. 12 is a diagram for describing a criterion for determining whether or not a value has been changed. FIG. 13 is a diagram for describing a criterion for determining whether or not a value has been changed. FIG. 14 is a diagram for describing a criterion for determining whether or not a value has been changed. FIG. 15 is a diagram illustrating a processing flow of calculation processing. FIG. 16 is a diagram for explaining calculation of the first collection interval. FIG. 17 is a diagram for explaining calculation of coefficients. FIG. 18 is a diagram illustrating a change in the collection interval. FIG. 19 is a diagram illustrating a change in the collection interval. FIG. 20 is a diagram illustrating a change in the collection interval. FIG. 21 is a diagram illustrating a processing flow of processing in which the proxy manager transmits data to the main manager. FIG. 22 is a diagram illustrating a processing flow of processing in which the main manager collects load data from the proxy manager. FIG. 23 is a diagram illustrating an example of data stored in the load data storage unit. FIG. 24 is a diagram illustrating a processing flow of processing in which the main manager transfers the target device. FIG. 25 is a diagram illustrating a processing flow of processing in which the main manager transfers the target device. FIG. 26 is a diagram illustrating an example of data stored in the transfer data storage unit. FIG. 27 is a diagram illustrating a processing flow of processing for returning the target device to which the main manager has been transferred. FIG. 28 is a diagram illustrating a processing flow of processing for returning the target device to which the main manager has been transferred. FIG. 29 is a diagram for explaining a management mode in the present embodiment. FIG. 30 is a diagram for explaining a management mode in the present embodiment. FIG. 31 is a diagram showing a list of items whose values are not changed. FIG. 32 is a functional block diagram of a computer.

Fig. 1 shows the system outline of this embodiment. For example, in the network 7 that is a LAN (Local Area Network), for example, the target devices 51 to 56, the main manager 1 that collects data from the target devices 51 to 56, and the proxy managers 31 to 33, and the collected data are browsed. Is connected to a user terminal 9 which is a terminal. There are no limitations on the number of proxy managers, target devices, and user terminals.

In the present embodiment, data collection is performed in two stages. For example, target devices managed by the proxy manager 31 are

target devices

51 and 52, target devices managed by the proxy manager 32 are

target devices

53 and 54, and target devices managed by the proxy manager 33 are

target devices

55 and 56. Suppose that In this case, as shown in FIG. 2, the proxy manager 31 collects the data of the

target devices

51 and 52, the proxy manager 32 collects the data of the

target devices

53 and 54, and the proxy manager 33 collects the data of the

target devices

55 and 56. Collect data. Further, the main manager 1 collects data of the

target devices

51 and 52 from the proxy manager 31, collects data of the

target devices

53 and 54 from the proxy manager 32, and collects data of the

target devices

55 and 56 from the proxy manager 33. To do. In this way, the manager layer to which the main manager 1 and the proxy managers 31 to 33 belong has a hierarchical structure.

FIG. 3 shows a functional block diagram of the proxy manager 31. The proxy manager 31 includes a reception unit 310, a comparison unit 311, a data storage unit 312, a queue 313, a history storage unit 314, a calculation unit 315, and a transmission unit 316.

The receiving unit 310 collects data from the target device and outputs it to the comparison unit 311. Note that data collection is performed by, for example, telnet (TEL communication NETwork) or ssh (Secure SHell). The comparison unit 311 determines whether the value of the item has been changed using the data received from the reception unit 310 and the data stored in the data storage unit 312. The comparison unit 311 stores the item value in the queue 313 and the data storage unit 312 when the item value is changed. The comparison unit 311 manages data stored in the history storage unit 314. Based on the data stored in the history storage unit 314, the calculation unit 315 calculates a time point at which data is next collected, and stores data indicating the next data collection time point in the history storage unit 314. The transmission unit 316 transmits the data stored in the queue 313 to the main manager 1.

Note that the functional block diagrams of the

proxy managers

32 and 33 are the same as the functional block diagram of the proxy manager 31, and the description thereof will be omitted.

FIG. 4 shows a functional block diagram of the main manager 1. The main manager 1 includes a communication unit 10, a load data collection unit 11, a load data storage unit 12, a transfer unit 13, a reference value storage unit 14, a management data storage unit 15, a transfer data storage unit 16, Data storage unit 17.

The communication unit 10 receives data from the proxy managers 31 to 33 and stores the data in the data storage unit 17. The load data collection unit 11 receives the load data from the proxy managers 31 to 33 and stores the load data in the load data storage unit 12. The transfer unit 13 is stored in the data stored in the load data storage unit 12, the data stored in the reference value storage unit 14, the data stored in the management data storage unit 15, and the transfer data storage unit 16. The process of transferring the target device is performed using the existing data.

The user terminal 9 receives an instruction from the user via a web browser or the like, and displays data held by the main manager 1 and the proxy managers 31 to 33 in the manager layer on a display device (for example, a display) based on the instruction. Further, the user terminal 9 receives an instruction from a user who has confirmed the data displayed on the display device via a web browser or the like, and controls the target devices 51 to 56 based on the instruction.

The data collected from the target devices 51 to 56 includes various item values. In the present embodiment, the values of items related to hardware components (for example, serial number, part number, model name, etc.) and the values of items acquired by the OS of the target device (for example, CPU usage rate, free memory) Capacity, disk usage, and operation process information).

FIG. 5 shows an example of data stored in the data storage unit 312 of the proxy manager 31. In the example of FIG. 5, the target device name of the transmission source, the item name, and the item value are stored. Note that data is also stored in the data storage unit 17 of the main manager 1 in the same format.

FIG. 6 shows an example of data stored in the history storage unit 314 of the proxy manager 31. In the example of FIG. 6, a target device name, an item name, data indicating the next collection point, a change history, and a collection flag are stored. When the collection flag is “On”, data collection is being executed, and when the collection flag is “Off”, data collection is not being executed.

FIG. 7 shows an example of data stored in the reference value storage unit 14 of the main manager 1. In the example of FIG. 7, an upper limit value and a lower limit value are stored for each item related to the load.

FIG. 8 shows an example of the first management table stored in the management data storage unit 15 of the main manager 1. In the example of FIG. 8, the name of the target device and the name of the proxy manager that manages the target device are stored.

FIG. 9 shows an example of the second management table stored in the management data storage unit 15 of the main manager 1. In the example of FIG. 9, the target device name and the name of the proxy manager that can manage the target device are stored. A proxy manager that cannot manage a target device is, for example, a proxy manager that cannot access the target device due to a network configuration.

Next, processing performed in the system shown in FIG. 1 will be described with reference to FIGS. First, a process in which the proxy managers 31 to 33 collect data from the target devices 51 to 56 will be described.

First, the comparison unit 311 of the proxy manager (here, the proxy manager 31) specifies one row to be processed from the history storage unit 314 (FIG. 10: step S1). When the process of step S1 is executed for the first time, the line to be processed is the first line. When the process of step S1 is not executed for the first time, it is the line next to the line specified last time. However, if the previously identified line is the last line, the line to be processed is the first line.

The comparison unit 311 obtains the current time from, for example, the system clock, and determines whether the “next collection time point” in the line to be processed has elapsed (step S3). If it has not elapsed (step S3: No route), data is not collected, and the process returns to step S1. On the other hand, when it has elapsed (step S3: Yes route), the comparison unit 311 determines whether the collection flag in the line to be processed is “On” (step S5).

If it is “On” (step S5: Yes route), the processing to be collected is already being executed, so the processing returns to step S1. On the other hand, when it is not “On” (step S5: No route), the comparison unit 311 sets the collection flag in the row to be processed to “On” (step S7).

And the comparison part 311 performs a comparison process (step S9). The comparison process will be described with reference to FIGS.

First, the comparison unit 311 specifies a target device and an item from the line to be processed, and transmits an acquisition request for requesting the target device to acquire the value of the item. Then, the comparison unit 311 acquires the value of the item from the target device that is the transmission destination of the acquisition request (FIG. 11: Step S21).

The comparison unit 311 reads the value of the item acquired last time from the target device from the data storage unit 312 (step S23). Then, the comparison unit 311 compares the current value acquired in step S21 with the value read in step S23, and determines whether the value has been changed (step S25).

The determination in step S25 will be described with reference to FIGS. In the present embodiment, when the change in value is equal to or greater than a predetermined reference, data is transmitted to the main manager 1 to suppress an increase in the load on the main manager 1 and the proxy manager. 12 to 14, parentheses at the end of “value examples” represent data types.

FIG. 12 shows the criteria for items related to the CPU. As shown in FIG. 12, regarding the frequency and the CPU temperature, it is determined that the value has been changed when there is a difference that exceeds a predetermined reference.

Fig. 13 shows the criteria for items related to memory. As shown in FIG. 13, it is determined that the values have been changed when the free capacity, the used capacity, and the total capacity are different from a predetermined reference.

Fig. 14 shows the criteria for items related to fans. As shown in FIG. 14, it is determined that the values of the fan speed and the fan temperature have been changed when there is a difference greater than a predetermined reference.

As described above, it is possible to suppress unnecessary data transfer by introducing a mechanism for ignoring a slight difference. Thereby, the data transfer amount in the network 7 can be reduced, and an increase in the load on the main manager 1 can be suppressed.

Note that, for example, even when the item disappears due to the removal of hardware or the number of items increases due to the addition of hardware, data is transmitted to the main manager 1 as in the case where the value is changed. Like that.

Returning to the explanation of FIG. 11, when the value has not been changed (step S25: No route), the process proceeds to step S31. On the other hand, when the value is changed (step S25: Yes route), the comparison unit 311 overwrites the value of the previous item in the data storage unit 312 with the value of the current item (step S27). When the comparison unit 311 overwrites the item value, the format may be changed. However, the description is omitted because it is not related to the main part of the present embodiment.

The comparison unit 311 adds an entry including the target device name and the value of the current item to the queue 313 (step S29). Note that when entries for the same target device and the same item are already stored in the queue 313, the entry is an old entry that does not need to be transmitted to the main manager 1. Therefore, the comparison unit 311 overwrites the old entry with the current entry. In this way, the size of the queue 313 does not increase infinitely.

The comparison unit 311 updates the change history stored in the history storage unit 314 (step S31). Specifically, delete the data in the “5 times ago” column in the change history, move the data in the “4 times ago” column to the “5 times ago” column, Move the data to the “4 times ago” column, move the data from the “2 times ago” column to the “3 times ago” column, and move the data from the “1 time ago” column to the “2 times ago” column. Move to the column. Then, the result of determination (with or without change) in step S25 is stored in the “one time before” field.

The comparison unit 311 requests the calculation unit 315 to execute the calculation process. In response to this, the calculation unit 315 executes a calculation process (step S33). The calculation process will be described with reference to FIGS.

First, the calculation unit 315 counts the number of target devices managed by the proxy manager 31 by counting the target device names stored in the history storage unit 314 (FIG. 15: step S41).

The calculation unit 315 calculates a basic collection interval from the number counted in step S41 (step S43). In the present embodiment, the basic collection interval becomes longer as the number of target devices increases, thereby suppressing an increase in the processing load of the proxy manager when the number of target devices increases. For example, as shown in FIG. 16, the basic collection interval is calculated by a linear function whose slope and intercept are positive. In FIG. 16, the horizontal axis represents the number of target devices, and the vertical axis represents the basic collection interval. It is to be noted that appropriate control can be performed when the slope value is set to 0.8 and the intercept value is set to 600, for example. However, it is not necessarily limited to such a value.

15, the calculation unit 315 reads the change history from the history storage unit 314 (step S45). Then, the calculation unit 315 calculates a coefficient from the change history (step S47).

The calculation of the coefficient will be described with reference to FIG. The coefficient calculated in step S47 is a coefficient for calculating the final collection interval. The coefficient decreases as the frequency of the item value changes, and decreases as the time when the item value is changed later. For example, as shown in FIG. 17, the weight is determined, and when there is a change, the weight is multiplied by 1, and when there is no change, the weight is multiplied by 0. Then, the coefficient is obtained by subtracting the total of the calculated values from 1.0. For example, in the case of the fan temperature of the target apparatus 1, the coefficient is 1− (0.3 * 1 + 0.2 * 1 + 0.1 * 0 + 0.05 * 1 + 0.03 * 0 + 0.01 * 0) = 1−0.55. = 0.45. By doing so, the collection interval becomes smaller as the frequency of the item value is changed, and becomes smaller as the time when the item value is changed later.

15, the calculation unit 315 calculates the collection interval by multiplying the basic collection interval by the coefficient calculated in step S47 (step S49).

For example, the calculation unit 315 acquires the current time from the system clock (step S51), calculates the next collection time from the current time and the collection interval calculated in step S49 (step S53), and stores the history. Stored in the unit 314. Then, the process returns to the calling process. The next collection time is the time when the collection interval has elapsed from the current time.

If the above processing is executed, data can be collected at an appropriate interval reflecting the number of target devices managed by the proxy manager and the change history.

18 to 20 show an example of the change in the collection interval. FIG. 18 shows a change in the collection interval when no change is detected. The axis in FIG. 18 is a time axis. In the example of FIG. 18, the collection interval is gradually increased, and when a certain point in time is reached, the collection interval does not change.

Fig. 19 shows changes in the collection interval when changes are detected each time. The axis in FIG. 19 is a time axis. In the example of FIG. 19, the collection interval is gradually shortened, and when a certain point in time is reached, the collection interval does not change.

Fig. 20 shows changes in the collection interval when a change is detected once. The axis in FIG. 20 is a time axis. In the example of FIG. 20, the change is not detected until the third time, but the change is detected at the fourth time, and the change is not detected after the fifth time. In this case, the collection interval is gradually increased until a change is detected. When a change is detected for the fourth time, the collection interval is shortened. The collection interval gradually increases with time.

Returning to the description of FIG. 11, the comparison unit 311 sets the collection flag in the line to be processed to “Off” (step S35). Then, the process returns to the calling process.

Returning to the description of FIG. 10, the comparison unit 311 determines whether there is an end instruction (for example, an instruction to turn off the power) (step S <b> 11). When there is no end instruction (step S11: No route), the process returns to step S1. On the other hand, if there is an end instruction (step S11: Yes route), the process ends.

As described above, basically, an increase in the load of processing to be collected can be suppressed by increasing the interval as the number of target devices increases. Further, by shortening the interval when the value is changed, it is possible to shorten the time during which the difference is generated between the value held in the manager layer and the actual value. Further, since the interval is set for each item, it is possible to suppress an increase in load by shortening the item unnecessarily.

Note that, as described above, even if the value suddenly starts to fluctuate, the collection interval can be greatly shortened when the fluctuation is first detected. Lee can be captured. Even when the value fluctuates temporarily, data is collected at a relatively short collection interval for a while after the value fluctuates, and thereafter the collection interval gradually becomes longer. Therefore, the change frequency = the number of changes / the number of collections is obtained, and it becomes possible to flexibly cope with the fluctuation of the value as compared with the method of simply determining the collection interval using the change frequency.

Next, a process in which the proxy managers 31 to 33 transmit data to the main manager 1 will be described with reference to FIG.

First, the transmission unit 316 of the proxy manager (here, the proxy manager 31) determines whether there is an entry in the queue 313 (FIG. 21: step S61). When there is no entry (step S61: No route), the transmission unit 316 waits for a predetermined time (step S63), and returns to the process of step S61.

On the other hand, when there is an entry in the queue 313 (step S61: Yes route), the transmission unit 316 transmits an acquisition request for requesting acquisition of load data to the main manager 1 (step S65). The load data is data including values of items related to loads (for example, CPU usage rate, I / O (Input / Output) usage rate, memory usage rate, power consumption, etc.).

The communication unit 10 of the main manager 1 receives the acquisition request from the proxy manager 31 (step S67), and acquires the value of the item related to the load from the OS, for example. And the communication part 10 transmits the load data containing the acquired value to the proxy manager 31 (step S69).

The transmission unit 316 of the proxy manager 31 receives load data from the main manager 1 (step S71).

The transmission unit 316 determines whether or not the load value included in the load data is equal to or greater than a predetermined reference value (step S73). In step S73, for example, it is determined whether any of the load values included in the load data is greater than or equal to a predetermined reference value. If the load value is equal to or greater than the predetermined reference value (step S73: Yes route), data cannot be transmitted to the main manager 1, and the process returns to step S61.

On the other hand, when the load value is not equal to or greater than the predetermined reference (step S73: No route), the transmission unit 316 takes out the first entry in the queue 313. Then, the transmission unit 316 transmits the extracted entry to the main manager 1 (step S75).

The communication unit 10 of the main manager 1 receives the entry from the proxy manager 31 and stores it in the data storage unit 17 (step S77). And the communication part 10 transmits the completion notification which shows completion of storage to the proxy manager 31 (step S78).

The transmission unit 316 of the proxy manager 31 receives a completion notification from the main manager 1 (step S79). Then, the process returns to step S61.

If the above processing is executed, it is possible to suppress the load value of the main manager 1 from exceeding the reference value. In addition, by making the manager layer have a hierarchical structure, it is possible to cope with an increase in the number of target devices.

Next, a process in which the main manager 1 collects load data from the proxy managers 31 to 33 will be described with reference to FIGS.

First, the load data collection unit 11 identifies one row to be processed from the load data storage unit 12 (FIG. 22: step S81). When the process of step S81 is executed for the first time, the line to be processed is the first line. When the process of step S81 is not executed for the first time, it is the line next to the line specified last time. However, if the previously identified line is the last line, the line to be processed is the first line.

FIG. 23 shows an example of data stored in the load data storage unit 12. In the example of FIG. 23, the proxy manager name, CPU usage rate, I / O usage rate, memory usage rate, and power consumption are stored.

The load data collection unit 11 identifies the proxy manager name included in the line to be processed (step S83). Then, the load data collection unit 11 transmits an acquisition request for requesting acquisition of load data to the proxy manager (in this case, the proxy manager 31) having the specified proxy manager name (step S85).

The reception unit 310 of the proxy manager 31 receives the acquisition request from the main manager 1 (step S87), and acquires the value of the item related to the load from the OS, for example. Then, the receiving unit 310 transmits load data including the acquired value to the main manager 1 (step S89).

The communication unit 10 of the main manager 1 receives the load data from the proxy manager 31 and outputs it to the load data collection unit 11. The load data collection unit 11 stores the received load data in the load data storage unit 12 (step S91). Then, the process returns to step S81.

If the above processing is executed, the main manager 1 can monitor the loads of the proxy managers 31 to 33.

Next, a process in which the main manager 1 transfers the target device will be described with reference to FIGS.

First, the transfer unit 13 identifies one row to be processed from the load data storage unit 12 (FIG. 24: step S101). When the process of step S101 is executed for the first time, the line to be processed is the first line. When the process of step S101 is not executed for the first time, it is the line next to the line specified last time. However, if the previously identified line is the last line, the line to be processed is the first line.

The transfer unit 13 determines whether any of the load values included in the row to be processed exceeds the upper limit stored in the reference value storage unit 14 (step S103). When the upper limit is not exceeded (step S103: No route), the transfer unit 13 waits for a predetermined time (step S105) and returns to the process of step S101.

On the other hand, when the upper limit is exceeded (step S103: Yes route), the transfer unit 13 determines from the first management table in the management data storage unit 15 the proxy manager (in this case, the proxy manager name) included in the row to be processed. The target device managed by the manager 31 is specified. Then, the transfer unit 13 specifies one target device to be transferred (here, the target device 51) from the specified target devices (step S107). In step S107, for example, a target device to be transferred is specified at random.

The transfer unit 13 uses the load data storage unit 12 to determine whether there is a proxy manager whose load value is smaller than the upper limit stored in the reference value storage unit 14 (step S109).

If there is no proxy manager whose load value is smaller than the upper limit stored in the reference value storage unit 14 (step S109: No route), the process cannot be transferred, and the process returns to step S105. On the other hand, when there is a proxy manager whose load value is smaller than the upper limit stored in the reference value storage unit 14 (step S109: Yes route), the transfer unit 13 is stored in the management data storage unit 15 Using the second management table, it is determined whether or not the target device 51 can be transferred to the proxy manager (in this case, the proxy manager 32) (step S111). In step S111, the proxy manager 32 determines whether the target device 51 can be managed.

If transfer is not possible (step S111: No route), the process returns to step S105. On the other hand, when transfer is possible (step S111: Yes route), the transfer part 13 transmits the transfer request | requirement which requests | requires transfer of the object apparatus 51 to the proxy manager 32 (step S113). In response to this, the reception unit 310 of the proxy manager 32 receives the transfer request (step S115) and outputs it to the comparison unit 311. The processing shifts to the processing in FIG. 25 via terminals A and B.

25, the comparison unit 311 starts managing the target device (here, the target device 51) specified in the transfer request (FIG. 25: step S117). Specifically, the comparison unit 311 adds an entry for the target device 51 to the history storage unit 314.

The comparison unit 311 determines whether to wait for completion of acquisition of the item value (step S119). When waiting for the completion of the acquisition of the item value (step S119: Yes route), the comparison unit 311 waits until the item value is acquired from the target device 51 (step S121). On the other hand, when not waiting for the completion of the acquisition of the item value (step S119: No route), the comparison unit 311 transmits a completion notification indicating the completion of the transfer to the main manager 1 (step S123).

The communication unit 10 of the main manager 1 receives the completion notification from the proxy manager 32 (step S125) and outputs it to the transfer unit 13. The transfer unit 13 transmits a stop request for requesting stop of management of the target device 51 to the proxy manager 31 (step S127).

The reception unit 310 of the proxy manager 31 receives a stop request from the main manager 1 (step S129), and outputs the received stop request to the comparison unit 311. The comparison unit 311 stops management of the target device (here, the target device 51) specified in the stop request (step S131). Specifically, the comparison unit 311 deletes the entry of the target device 51 from the history storage unit 314. Then, the comparison unit 311 transmits a stop notification indicating the completion of the stop to the main manager 1 (step S135).

The communication unit 10 of the main manager 1 receives the stop notification from the proxy manager 31 (step S137) and outputs it to the transfer unit 13. The transfer unit 13 adds data indicating the contents of the transfer to the transfer data storage unit 16 (step S139). The processing returns to step S101 in FIG.

FIG. 26 shows an example of data stored in the transfer data storage unit 16. In the example of FIG. 26, the name of the target device to be transferred, the name of the proxy manager that managed the target device before the transfer, and the name of the proxy manager that manages the target device after the transfer are stored. .

If the above processing is executed, the load can be distributed among the proxy managers.

Next, a process for returning the transferred target device to the original will be described with reference to FIGS. 27 and 28. FIG.

First, the transfer unit 13 determines whether there is data in the transfer data storage unit 16 (FIG. 27: step S141). When there is no data in the transfer data storage unit 16 (step S143: No route), the transfer unit 13 waits for a predetermined time (step S145) and returns to the process of step S141. On the other hand, when there is data in the transfer data storage unit 16 (step S143: Yes route), the transfer unit 13 specifies one row of data from the transfer data storage unit 16 (step S147). When the process of step S147 is executed for the first time, the specified line is the first line. When the process of step S147 is not executed for the first time, it is the line next to the line specified last time. However, if the previously identified line is the last line, the line to be processed is the first line.

The transfer unit 13 determines whether any of the load values of the proxy manager (here, the proxy manager 31) whose management has been stopped in step S131 is smaller than the lower limit stored in the reference value storage unit 14 (step S149). ). If it is equal to or greater than the lower limit (step S149: No route), the process returns to step S145. On the other hand, if it is smaller than the lower limit (step S149: Yes route), a start request for requesting to start management of the target device (here, the target device 51) is transmitted to the proxy manager 31 (step S151).

The reception unit 310 of the proxy manager 31 receives a start request from the main manager 1 (step S153) and outputs the request to the comparison unit 311. The processing shifts to the processing in FIG. 28 via terminals D and E.

28, the comparison unit 311 starts managing the target device (here, the target device 51) specified in the start request (FIG. 28: step S155). Specifically, the comparison unit 311 adds an entry for the target device 51 to the history storage unit 314.

The comparison unit 311 determines whether to wait for the completion of the acquisition of the item value (step S157). When waiting for the completion of the acquisition of the item value (step S157: Yes route), the comparison unit 311 waits until the item value is acquired from the target device 51 (step S159). On the other hand, when the acquisition of the value of the item is not waited (step S157: No route), the comparison unit 311 transmits a start notification indicating the start of management to the main manager 1 (step S161).

The communication unit 10 of the main manager 1 receives the start notification from the proxy manager 31 (step S163) and outputs it to the transfer unit 13. The transfer unit 13 transmits a stop request for requesting stop of management of the target device 51 to the proxy manager 32 (step S165).

The reception unit 310 of the proxy manager 32 receives a stop request from the main manager 1 (step S167), and outputs the received stop request to the comparison unit 311. The comparison unit 311 stops management of the target device (here, the target device 51) specified in the stop request (step S169). Specifically, the comparison unit 311 deletes the entry of the target device 51 from the history storage unit 314. Then, the comparison unit 311 transmits a stop notification indicating the completion of the stop to the main manager 1 (step S171).

The communication unit 10 of the main manager 1 receives the stop notification from the proxy manager 32 (step S173) and outputs it to the transfer unit 13. The transfer unit 13 deletes the data added in step S139 from the transfer data storage unit 16 (step S175). The processing returns to step S141 in FIG.

If the processing as described above is executed, the proxy manager that should originally manage the transferred target device can be managed again. For example, when a proxy manager that has been in an idle state is temporarily used, the proxy manager can be returned to an idle state and used for other purposes.

Hereinafter, the management mode in the present embodiment will be described more specifically.

FIG. 29 shows an example in which one proxy manager manages all target devices. In the system shown in FIG. 29, the main manager 1,

proxy managers

31 and 32, target devices 51 to 53, and the user terminal 9 are connected via a network 7. When the user operates an input device (for example, a keyboard) of the user terminal 9, setting is performed so that the proxy manager 31 manages the target devices 51 to 53. In this case, since the load is concentrated on the proxy manager 31, when the load value exceeds the upper limit, one of the target devices 51 to 53 is transferred to the proxy manager 32. However, when the value of the item is not changed in the target apparatuses 51 to 53, as described with reference to FIG. 18, the collection interval becomes longer, and the load on the proxy manager 31 is reduced accordingly. In such a case, transfer is not performed. Further, even when the number of target devices decreases, the load on the proxy manager 31 decreases, so that transfer is not performed.

Here, it is assumed that the number of target devices increases as shown in FIG. In the system shown in FIG. 30, the main manager 1,

proxy managers

31 and 32, target devices 51 to 53, target devices 54 to 56 to be newly managed, and the user terminal 9 are connected to the network 7. Connected through. When the user operates an input device (for example, a keyboard) of the user terminal 9, settings are made so that the proxy manager 31 manages the target devices 51 to 56. However, since the load value of the proxy manager 31 exceeds the upper limit, the target devices 55 to 56 are transferred to the proxy manager 32 in order one by one. Further, it is assumed that the load value of the main manager 1 temporarily exceeds a predetermined reference value due to an increase in the number of target devices. In this case, the

proxy managers

31 and 32 do not transmit the data acquired from the target device to the main manager 1 until the load value of the main manager 1 becomes smaller than a predetermined reference value. When the load value of the main manager 1 becomes smaller than a predetermined reference value, the

proxy managers

31 and 32 resume data transmission. Further, when the value of the item is not changed in the target devices 51 to 54, the collection interval becomes longer as described with reference to FIG. 18, and the load on the proxy manager 31 is reduced accordingly. Then, when the load value of the proxy manager 31 becomes smaller than the lower limit, the target devices transferred to the proxy manager 32 are transferred to the proxy manager 31 one by one.

As described above, according to the present embodiment, a larger amount of data can be collected and stored without causing a problem such as a system stoppage, and more target devices can be managed as a whole system. It becomes like this.

Although one embodiment of the present invention has been described above, the present invention is not limited to this. For example, the functional block configurations of the proxy manager 31 and the main manager 1 described above may not match the actual program module configuration.

In addition, the configuration of each table described above is an example, and it does not have to be the configuration described above. Further, in the processing flow, the processing order can be changed if the processing result does not change. Further, it may be executed in parallel.

Note that, for items whose values are not changed, for example, a list as shown in FIG. 31 may be prepared. In addition, by acquiring values only for the first time for the items included in the list of FIG.

In addition, the number of hierarchies in the manager layer is not limited to two above, and may be three or more.

The main manager 1, the proxy managers 31 to 33, the target devices 51 to 56, and the user terminal 9 described above are computer devices, and as illustrated in FIG. 32, a memory 2501 and a CPU (Central Processing Unit). 2503, a hard disk drive (HDD: Hard Disk Drive) 2505, a display control unit 2507 connected to the display device 2509, a drive device 2513 for the removable disk 2511, an input device 2515, and a communication control unit 2517 for connecting to the network. Are connected by a bus 2519. An operating system (OS: Operating System) and an application program for performing the processing in this embodiment are stored in the HDD 2505, and are read from the HDD 2505 to the memory 2501 when executed by the CPU 2503. The CPU 2503 controls the display control unit 2507, the communication control unit 2517, and the drive device 2513 according to the processing content of the application program, and performs a predetermined operation. Further, data in the middle of processing is mainly stored in the memory 2501, but may be stored in the HDD 2505. In the embodiment of the present invention, an application program for performing the above-described processing is stored in a computer-readable removable disk 2511 and distributed, and installed in the HDD 2505 from the drive device 2513. In some cases, the HDD 2505 may be installed via a network such as the Internet and the communication control unit 2517. Such a computer apparatus realizes various functions as described above by organically cooperating hardware such as the CPU 2503 and the memory 2501 described above and programs such as the OS and application programs. .

The embodiments of the present invention described above are summarized as follows.

The information processing system according to the first aspect of the present embodiment includes (A) a first device and (B) a first management device that acquires a value of a predetermined item from the first device. The first management device described above includes (b1) a data storage unit that stores information indicating whether or not a value of a predetermined item has changed for one or more time points, and (b2) a predetermined value from the first device. When the value of the item is acquired, the acquired value of the predetermined item is compared with the value of the predetermined item previously acquired from the first device, and information indicating whether or not the value of the predetermined item has changed is stored in the data storage unit. And (b3) determining when to acquire the value of the predetermined item from the first device, based on the information stored in the data storage unit and indicating whether the value of the predetermined item has changed. And a determination unit.

∙ For items whose values do not change, it is not preferable to acquire values frequently. Therefore, as described above, it is possible to appropriately control the load of the process for acquiring the value.

Further, the determination unit described above calculates (b31) a first interval that is an interval for acquiring the value of the predetermined item from the first device from the number of devices managed by the first management device, and (b32) A coefficient is calculated based on the information stored in the data storage unit and indicating whether or not the value of the predetermined item has changed. (B33) The second interval is calculated by multiplying the first interval by the coefficient, (B34) The time point at which the value of the predetermined item is acquired from the first device may be determined using the time point at which the value of the predetermined item was previously acquired from the first device and the second interval. In this way, the process of acquiring a value can be performed at an appropriate time.

Further, the determination unit described above (b35) may calculate the first interval so that the first interval becomes longer as the number of devices managed by the first management device increases. If it does in this way, it will become possible to suppress that the load of a management apparatus increases with the increase in the number of the apparatuses to manage.

Further, the determination unit described above (b36) is such that the coefficient becomes smaller as the frequency of the value of the predetermined item changes, and the coefficient becomes smaller as the time when the value of the predetermined item changes later. A coefficient may be calculated. In this way, it is possible to suppress an increase in the period from when the value changes until it is acquired.

In addition, the comparison unit described above (b21), when the difference between the acquired value of the predetermined item and the value of the predetermined item previously acquired from the first device satisfies the condition for the change of the value of the predetermined item. It may be determined that the value of the predetermined item has changed. Thereby, for example, when the difference is slight, it is possible to prevent the value from being acquired.

The information processing system may further include (C) an information processing device that manages the first management device. The first management device acquires (b4) the load value of the information processing device from the information processing device, and if the acquired load value is smaller than the first reference value, the acquired value of the predetermined item is You may further have a transmission part which transmits to a processing apparatus. In this way, it is possible to suppress an increase in the processing load for the information processing apparatus to acquire a value.

The information processing system may further include (D) a second management device managed by the information processing device. The information processing apparatus described above includes (c1) a second acquisition unit that acquires load values of the first management apparatus and the second management apparatus, and (c2) the load value of the first management apparatus is first. A transfer unit that transfers the second device among the devices managed by the first management device to the second management device when the load value of the second management device is smaller than the first reference value. You may have. In this way, it is possible to distribute the processing load for acquiring values.

The second acquisition unit described above may acquire the load value of the first management device after (c11) transferring the second device to the second management device. The transfer unit described above is (c21) when the load value of the first management device is smaller than the second reference value, the second management device manages the second device among the devices managed by the second management device. May be transferred. In this way, the management form can be returned to the original state.

In the information processing method according to the second aspect of the present embodiment, when the value of the predetermined item is acquired from the managed device (E), the acquired value of the predetermined item and the previous value from the managed device are acquired. The value of the predetermined item is compared, information indicating whether or not the value of the predetermined item has changed is stored in the data storage unit, and (F) whether the value of the predetermined item stored in the data storage unit has changed Based on the information indicating whether or not, a process of determining a time point at which the value of the predetermined item is acquired from the management target device is included.

A program for causing a computer to perform the processing according to the above method can be created. The program can be a computer-readable storage medium such as a flexible disk, a CD-ROM, a magneto-optical disk, a semiconductor memory, or a hard disk. It is stored in a storage device. The intermediate processing result is temporarily stored in a storage device such as a main memory.

Claims

A first device;
A first management device for obtaining a value of a predetermined item from the first device;
Have
The first management device is
A data storage unit that stores information indicating whether or not the value of the predetermined item has changed for one or more time points;
When the value of the predetermined item is acquired from the first device, the acquired value of the predetermined item is compared with the value of the predetermined item previously acquired from the first device, and the value of the predetermined item changes. A comparison unit for storing in the data storage unit information indicating whether or not
A determination unit configured to determine a time point at which the value of the predetermined item is acquired from the first device, based on information stored in the data storage unit and indicating whether or not the value of the predetermined item has changed;
An information processing system.
The determination unit is
From the number of devices managed by the first management device, a first interval that is an interval for obtaining the value of the predetermined item from the first device is calculated,
A coefficient is calculated based on information stored in the data storage unit and indicating whether or not the value of the predetermined item has changed,
Calculating a second interval by multiplying the first interval by the factor;
The information according to claim 1, wherein a time point at which the value of the predetermined item is acquired from the first device is determined using a time point at which the value of the predetermined item was acquired from the first device last time and the second interval. Processing system.
The determination unit is
The information processing system according to claim 2, wherein the first interval is calculated so that the first interval becomes longer as the number of devices managed by the first management device increases.
The determination unit is
The coefficient is calculated so that the coefficient decreases as the frequency of the value of the predetermined item changes, and the coefficient decreases as the time when the value of the predetermined item changes later. 3. The information processing system according to 3.
The comparison unit includes:
The value of the predetermined item has changed when a difference between the acquired value of the predetermined item and the value of the predetermined item previously acquired from the first device satisfies a condition for a change in the value of the predetermined item. The information processing system according to any one of claims 1 to 4.
An information processing device for managing the first management device;
The first management device includes:
A transmission for acquiring a load value of the information processing apparatus from the information processing apparatus and transmitting the acquired value of the predetermined item to the information processing apparatus when the acquired load value is smaller than a first reference value. Part,
The information processing system according to any one of claims 1 to 5, further comprising:
A second management device managed by the information processing device;
The information processing apparatus includes:
A second acquisition unit that acquires load values of the first management device and the second management device;
If the load value of the first management device is greater than or equal to the first reference value and the load value of the second management device is smaller than the first reference value, the device managed by the first management device Among them, a transfer unit that transfers the second device to the second management device,
The information processing system according to claim 6.
The second acquisition unit includes
After transferring the second device to the second management device, obtain a load value of the first management device,
The transfer section is
The information according to claim 7, wherein when the load value of the first management device is smaller than a second reference value, the second device among devices managed by the second management device is transferred to the first management device. Processing system.
When the value of the predetermined item is acquired from the management target device, the acquired value of the predetermined item is compared with the value of the predetermined item previously acquired from the management target device, and the value of the predetermined item changes. Store in the data storage unit information indicating whether or not
Based on information stored in the data storage unit and indicating whether or not the value of the predetermined item has changed, the time point at which the value of the predetermined item is acquired from the managed device is determined.
An information processing method in which processing is executed by a computer.
When the value of the predetermined item is acquired from the management target device, the acquired value of the predetermined item is compared with the value of the predetermined item previously acquired from the management target device, and the value of the predetermined item changes. Store in the data storage unit information indicating whether or not
Based on information stored in the data storage unit and indicating whether or not the value of the predetermined item has changed, the time point at which the value of the predetermined item is acquired from the managed device is determined.
A program that causes a computer to execute processing.