JP6364203B2 - Monitoring server for monitoring system operating status and monitoring server control method - Google Patents

Description

  The present invention relates to a monitoring server that monitors the operating state of a system constructed using a cloud computing service, and a monitoring server control method.

  As a background art in this technical field, there is JP-A-2001-298454 (Patent Document 1). Patent Document 1 states that “a monitoring computer is installed and information is sent and received between the monitoring computer and the monitoring center computer via the network, and the performance and operating status of the monitoring target network are monitored at a remote monitoring center. Provides a network monitoring system, a monitoring computer, a monitoring center computer, and a recording medium that can be grasped quickly and accurately. "

  Moreover, there exists Unexamined-Japanese-Patent No. 2012-015762 (patent document 2). Patent Document 2 discloses that in a remote monitoring system in which an agent is installed in a customer system or the like, a lack of processing performance of the agent caused by an increase in the number of devices to be monitored, a router existing between the agent and the devices to be monitored, It provides a method for avoiding communication shielding by a firewall. "

  Further, there is US2012 / 0159232A1 (Patent Document 3). Patent Document 3 describes that “the information processing service in which a failure has occurred can be immediately recovered without clustering information processing devices that provide the information processing service”.

JP 2001-298454 A JP 2012-015762 A US2012 / 0159232A1

  When monitoring the operating status of the system, it is necessary to install and set up agent software having a monitoring function in the environment where the system to be monitored is constructed, and to activate the function.

  However, when building a standby system to be monitored on a data center that provides a cloud service where service usage costs are incurred due to the number of CPUs (Central Processing Units) and virtual machines used, the monitoring function can be used from the standby state. Introducing a system that does not require monitoring when it is not in operation will incur resource usage costs for running the monitoring function.

  Also, if the network line between the environment where the monitored system is built and the monitoring center where the integrated monitoring server that collects monitoring logs is installed is a shared line, the system that is not in operation and does not require monitoring For this reason, if the network line resources are secured, the utilization efficiency of the shared line is deteriorated.

  In addition, when the integrated monitoring server that collects monitoring logs is operated on a data center that provides a cloud service that is charged according to the amount of storage used, the monitoring function operates while the monitored system is in the standby state. If the monitoring log is notified through the network and the monitoring log is accumulated, an extra storage usage cost occurs because the system is not in operation and does not require monitoring.

  The present invention has been made in view of the circumstances as described above, and an object of the present invention is to reduce resource consumption and resource utilization costs associated with monitoring the operating status of a system constructed using a cloud computing service. And

  In view of the above problems, when the monitoring server in the present embodiment detects a configuration change of a system constructed using data center resources, the monitoring server newly detects a portion that needs to be monitored due to the configuration change. Deploy agent software for monitoring parts, and establish a logical network to collect monitoring information from the deployed agent software. Specifically, the operating state of the application constituting the system connected to one or more data centers via a network line and constructed on one or more computers in the one or more data centers. When the monitoring server that monitors the application detects an increase in the number of operating applications or a change in the location of the application, the agent software for monitoring the operating status of the application is installed on the computer where the changed or increased applications are installed. Deploy to computers in the center. Then, the monitoring server opens a logical network on the network line to be used for receiving the monitoring information of the operating state of the changed or increased application from the deployed agent software.

  This makes it possible to reduce the cost of using resources necessary for monitoring the operating status of the system and to effectively use the resources.

It is an example of a block diagram of a monitoring system. It is an example of the sequence diagram explaining the flow of processing of the monitoring system. It is an example of a block diagram of a monitoring server. It is an example of the block diagram of the apparatus which deploys the monitoring agent and a configuration change monitoring function. It is an example of the flowchart explaining the process of a dynamic deployment function part. It is an example of the flowchart explaining the process of the monitoring function introduction part. It is an example of a switching system management table. It is an example of a monitoring object management table. It is an example of a monitoring network management table. It is an example of the figure which shows the structural example of the monitoring system of Example 2. FIG. FIG. 10 is an example of a diagram illustrating a configuration example of a monitoring target management table according to the second embodiment. 10 is an example of a flowchart illustrating monitoring agent control processing of a dynamic deployment function unit according to the second embodiment. It is an example of a figure which shows the structural example of a monitoring agent management table. 12 is an example of a flowchart for explaining processing of a dynamic deployment function unit according to a third embodiment. It is an example of the figure which shows the structural example of a structure change notification message.

  Hereinafter, examples will be described with reference to the drawings.

In this embodiment, an example of monitoring a system that performs system switching to a standby system when an operating system stops due to a disaster or failure, such as a DR (Disaster Recovery) system or an HA (High Availability) system. Will be described.
FIG. 1 is an example of a configuration diagram of the configuration change tracking type monitoring system according to the present embodiment, and FIG. 2 is an example of a sequence diagram illustrating a processing flow of the configuration change tracking type monitoring system according to the present embodiment. In this example, the operating system 6 is constructed on one or more computers of the customer site 1, and the monitoring agent 10 a of the customer site 1 that monitors the operating system transmits the acquired monitoring log via the wide area network 2. And sent to the integrated monitoring server 8 installed in the monitoring center 3 and stored in the monitoring log collection function unit 11. The monitoring agent 10a only needs to be arranged in the computer at the customer site 1, and may be arranged in a single computer or a plurality of computers.

  On the other hand, the standby system 7 is constructed in one or more computers of the public cloud 5 which is a data center that provides a public cloud service. The status of the operating system 6 and the switching opportunity are monitored by the configuration change monitoring function 12 of the public cloud 5. The configuration change monitoring function 12 monitors the system switching trigger of the operating system 6 of the DR system or the HA system (S20), and notifies the configuration change notification to the dynamic deployment function 13 of the integrated monitoring server 8 when the system switching occurs. Send (S21). This configuration change notification includes identifier information for making it possible to determine which system configuration change has occurred. The system switching trigger may be in a form in which the configuration change monitoring function 12 actively monitors, or in a passive form in which notifications from the DR system or the HA system are monitored. Upon receiving the configuration change notification, the dynamic deployment function 13 introduces the monitoring agent 10b for monitoring the standby system 7 into the public cloud 5 in which the standby system 7 is prepared (S23).

  The dynamic deployment function 13 that has received the configuration change notification opens a monitoring logical network 14 on the shared dedicated line 4 between the public cloud 5 and the monitoring center 3 (S22). The monitoring logical network 14 serves as a communication line for the standby system 7 to switch from the standby state to the operating state and for the monitoring agent 10 b to send the monitoring log to the monitoring log collection function unit 11 of the integrated monitoring server 8.

  The dynamic deployment function 13 that has received the configuration change notification secures a monitoring log storage area of the monitoring log collection function unit 11 in order to accumulate the monitoring log of the system 7 that switches from the standby state to the operating state.

  In addition, the said structural example is one Embodiment to the last, It is not limited to the said structural example, Various modifications are included. For example, although the configuration change monitoring function 12 seems to be installed at the customer site 1 in FIG. 1, it may be installed at the monitoring center 3 side to remotely monitor the monitoring target. The method of grasping the trigger of the configuration change may also be a Push type monitoring method that receives a notification from the monitoring target system, or a Pull type monitoring method that periodically polls and monitors the operating state of the monitoring target system.

  Further, in the above configuration example, the form in which the operating system 6 is constructed at the customer site 1 has been described. However, the operating system 6 is different from the public cloud 5 in which the standby system 7 is constructed in terms of the operator and geographical location. It may be configured in a different public cloud.

  FIG. 3 is an example of a configuration diagram of the integrated monitoring server device 8 of the present embodiment. Although the hardware configuration is not shown in the drawing, it includes components that are generally provided in a server device such as a CPU (Central Processing Unit), memory, and storage device, and can be connected from an external terminal device as necessary, or can be connected to a display or keyboard Hardware devices that can be directly connected to input / output devices such as mice are used. The integrated monitoring server device 8 includes a monitoring log collection function 11 and a dynamic deployment function 13. In the configuration example of FIG. 3, a form in which both functions operate on the same hardware device is shown, but a form in which the functions operate on physically different hardware devices may be used. Further, even when operating on the same hardware device, it may be configured to operate in different user spaces 44 on the hypervisor 41 as shown in FIG.

  FIG. 4 is an example of a configuration diagram of a device to which the monitoring agent 10 and the configuration change monitoring function 12 are deployed, that is, a computer at the customer site 1 and the public cloud 5. Further, as described above, it is also an example of a configuration diagram of the integrated management server that operates the monitoring log collection function 11 and the dynamic deployment function 13. In this apparatus, a hypervisor 41 is mounted on the hardware 40, and a driver 42 and an OS (Operating System) 43 are placed on an area virtually divided on the hypervisor 41 to generate a user space 44. When the monitoring agent 10, the configuration change monitoring function 12, the monitoring log collection function 11, and the dynamic deployment function 13 are introduced, the user space 44 is also introduced. The deployment destination of the monitoring agent 10 and the configuration change monitoring function 12 may be the same as the computer in which the operating system 6 or the standby system 7 is constructed, or may be a different computer.

  Returning to FIG. 3, the monitoring log collection function 11 will be described. The monitoring log sent from the monitoring agent 10 is received via the input interface 30 such as a communication interface and sent to the monitoring log collecting function unit 31. The monitoring log collection function unit 31 classifies the received monitoring log for each monitoring target system and records it in the monitoring log storage unit 33. The monitoring log storage unit 33 is configured by a recording device such as a database or storage, and may be physically configured as a separate device. The collected monitoring log is subjected to data analysis such as threshold monitoring in the log analysis function unit 34 as necessary, and then sequentially output to an external terminal device or a directly connected display device via the output interface 31.

  Next, the dynamic deployment function 13 will be described with reference to the flowcharts of FIGS. 5 and 6 and the table configuration diagrams of FIGS.

  The execution opportunity monitoring unit 37 that has received the configuration change notification from the configuration change monitoring function 12 via the input interface 30 such as a communication interface (S50), the identifier information 70 included in the received configuration change notification, or the occurrence of configuration change. Based on the address information 71 of the original active system 6, the switching system management table 300 is searched to identify the address information 72 of the system (standby system 7) to be newly monitored (S 51). When a new monitoring target system is known, a series of function introductions and settings necessary for collecting monitoring logs are performed (S52). The switching system management table 300 may be implemented as a component of the integrated monitoring server 8 or may be implemented in a database device different from the integrated monitoring server 8.

  A configuration example of the configuration change notification message is shown in FIG. The configuration shown in FIG. 15 shows the contents stored in the body part of the communication packet, and the description regarding the header part is omitted. As in this embodiment, when changing the monitoring target due to system switching, “switch” is designated as the command 150, and the configuration change is made by including the identifier 70 of the target system or the address information 71 of the operating system in 151. Configure notification messages.

  Details of the processing (S52) of the monitoring function introduction unit will be described with reference to FIG. The procedure for introducing the monitoring agent 10b for monitoring the standby system 7 to be newly monitored is as follows. The monitoring agent deploying function unit 39 refers to the monitoring target management table 36 (S60), and is a monitoring log notification destination host (in this embodiment, an integrated monitoring server, particularly a server on which the monitoring log collection function is operating). ) Address information 82, notification period 83, threshold information 81 required for alert notification, and the like, information necessary for setting the monitoring agent 10 b is extracted, and the monitoring target address 80 (in this embodiment, Based on the address information 72 of the standby system, the monitoring agent 10b is deployed (S61).

  The procedure for opening the monitoring logical network 14 is as follows. The monitoring network setting function 38 refers to the monitoring network management table 35 (S62), and based on the identifier information 70 of the target system, a network device such as a router or a switch (both ends 2) address information 90, logical network (eg, VLAN: Virtual Local Area Network) ID (identifier) information 91, bandwidth information 92, etc. Is set (S63).

  Further, as the monitoring function introduction process (S52), a storage area for accumulating newly collected management logs is secured in the storage device (S64).

  The order of the monitoring agent installation process (S60 to S61), the monitoring logical network establishment process (S62 to S63), and the monitoring log collection area securing process (S64) is executed in parallel as shown in the flowchart of FIG. However, unlike the flowchart of FIG. 6, a sequential execution method may be used. However, if the installation of the collected monitoring log and the communication line for sending the monitoring log to the integrated management server 8 are not completed, the new monitoring target is integrated even if the installation of the monitoring agent is completed. It cannot be monitored by the management server 8. Accordingly, one desirable form of the monitoring function introduction procedure is to first secure a monitoring log collection area (S64), then open a monitoring logical network (S62 to S63), and then install a monitoring agent (S60 to S60). (S61).

  In this embodiment, it is assumed that information of the switching system management table 300, the monitoring target management table 36, and the monitoring network management table 35 is registered at the time of system construction. However, regarding the ID information 91 of the logical network, the ID being used is registered and managed in the monitoring network management table 35, one ID that is not yet used is extracted and assigned in S63, and the newly assigned ID is assigned in S63. A form registered in the monitoring network management table 35 is desirable.

  In the above description, the method of giving the setting information when deploying the monitoring agent 10b is described. However, when the monitoring agent 10b is moved in the virtual environment as shown in FIG. An image file including the agent 10b may be created, and when the monitoring function is introduced (S52) when the configuration change notification is received (S50), the image file may be in a usable state. In this case, until the configuration change notification is received, the created image file is managed by the monitoring agent deployment function unit 39 of the integrated monitoring server 8, and after receiving the configuration change notification (S50), the standby system 7 May be introduced into the public cloud 5 that is prepared (S23). By not introducing the image file until the configuration change notification is received, the public cloud 5 will not be used until a new system to be monitored is activated. Can be suppressed.

  The above embodiment has been described by taking the DR system and the HA system as an example, but the same effect can be obtained also in the case of migrating to a different system environment without preparing a standby system. In the migration case, the configuration change monitoring function 12 monitors the migration opportunity, and the dynamic deployment function 13 introduces the monitoring function based on the notification from the configuration change monitoring function 12 (S52), so that the system at the migration destination A monitoring function can be dynamically introduced at the timing of starting operation.

  As described above, the switching change procedure of the monitoring target accompanying the system switching or migration has been described, but the procedure for deleting the monitoring function from the system that was operating before the system switching or migration occurred will be described in the third embodiment.

  In this example, even when servers are automatically added or deleted when the server load exceeds the threshold, as in the auto-scaling function provided by the cloud service, the server increases and decreases. An example of a configuration change tracking type monitoring system that performs monitoring will be described.

  FIG. 10 is an example of a configuration diagram of a configuration change tracking type monitoring system according to the second embodiment. The description of the components having the same functions as those shown in FIG. 1 already described with reference to FIG. 1 is omitted.

  When the server 101 is operating in a certain zone A (105), the autoscale function 108 monitors the load threshold of the server 101 based on the set threshold information. When the load on the server 101 exceeds the threshold, the autoscale function 108 adds a new server. At this time, the newly added server may be added to the same zone A (105) as the server 101 or may be added to a zone B (106) different from the server 101. The configuration change tracking type monitoring system performs introduction setting of a monitoring function to add a newly added server (102 or 103) as a monitoring target.

  The configuration change monitoring function 12 monitors a change in the autoscale function 108 or a notification from the autoscale function 108 in order to perform introduction setting of the monitor function following server addition. The configuration change monitoring function 12 that has received a configuration change opportunity such as server expansion from the autoscale function 108 sends a configuration change notification to the dynamic deployment function 13. Regarding the acquisition of the configuration change trigger, the configuration change monitoring function 12 may periodically poll the autoscale function 108, or the configuration change monitoring function 12 may receive notification from the autoscale function 108.

  Upon receiving the configuration change notification, the dynamic deployment function 13 introduces a monitoring agent for monitoring a newly added server. The basic operation flow is the same as the procedure of FIG. 5 described in the first embodiment. The difference from the first embodiment is a process of identifying a new monitoring target (in the second embodiment, a server newly added by auto scaling) (S52). In the first embodiment, the switching system management table 300 is searched and the address information 72 of the standby system 7 to be newly monitored is acquired. However, in the second embodiment, the switching system management table 300 does not exist. In the second embodiment, address information of a new monitoring target (a server newly added by auto-scaling) is included in information acquired from the auto-scaling function 108 by the configuration change monitoring function 12, and the configuration change monitoring function 12 The address information is transmitted to the dynamic deployment function 13.

  When this is shown in the configuration change notification message shown in FIG. 15, “addition” is designated in the command 150, and information on the address of a newly added server (address of a server to be newly monitored) is included in 151. It becomes a shape.

  In the second embodiment, the usage of the monitoring target management table 36 is also different from that of the first embodiment. As described above, in the second embodiment, the monitoring target address 80 is information acquired from the autoscale function 108 via the configuration change monitoring function 12, and is not registered at the time of system construction as in the first embodiment. The monitoring target management table 36 according to the second embodiment is configured as shown in FIG. The dynamic deployment function 13 searches the address range 111 including the address based on the new monitoring target address information, and information necessary for notification of the monitoring information set in advance at the time of system construction or the like 70, 81 to 83 are acquired. In the second embodiment, the identifier information 70 may be matched with the zone identifier.

  There are two cases regarding the introduction of the monitoring agent. One case is a case where the server 102 added to the zone A (105), which is the same network zone as the server 101, is a new monitoring target. In this case, if the monitoring agent 10b that has already been installed can permit monitoring of the server 102 at the same time, there is no need to introduce a new monitoring agent, and the address of the server 102 to be newly monitored is set in the monitoring agent 10b. All you need to do is add information. Conversely, if the monitoring agent 10b does not have the capacity to add the server 102 as a new monitoring target, it is necessary to introduce a new monitoring agent.

  The other case is a case where the server 103 added to the zone B (106), which is a network zone different from the server 101, is a new monitoring target. In this case, since the zones are different, the monitoring agent 10 c different from the monitoring agent 10 b is responsible for monitoring the server 103. Also in this case, if the monitoring agent 10c has already been installed in the zone B (106) and there is a room for adding the server 103 as a new monitoring target, the server 103 to be a new monitoring target is set in the monitoring agent 10c. Just add the address information. On the other hand, even if the monitoring agent has not been installed in zone B (106) or has been installed, if there is no room for the installed monitoring agent to add the server 103 as a monitoring target, a new monitoring agent is added. Introduce.

  The processing procedure related to the installation setting of the monitoring agent is the same in both the case where a new monitoring target is added to the same zone and the case where a new monitoring target is added to a different zone, and the flowchart shown in FIG. That is, it is confirmed whether the monitoring agent has been installed in the zone (S120). If the monitoring agent has been installed, it is checked whether the monitoring agent already installed can permit monitoring of a new monitoring target (S121). If it is acceptable, information on the new monitoring target is registered in the existing monitoring agent (S122). On the other hand, if a monitoring agent has not been installed in the zone, or if monitoring of a new monitoring target is not permitted even if it has been installed, a new monitoring agent is introduced (S123). The procedure shown in FIG. 12 replaces S60 and S61 in FIG.

  Whether the monitoring agent has been installed is managed by the monitoring target management table 36. Specifically, when a monitoring agent is introduced (S123), management is performed by registering the identifier of the monitoring agent in the corresponding zone 70 of the monitoring target management table 36 or the item area 112 of the corresponding address range 111.

  Further, the permissible status of installed monitoring agents is managed by the monitoring agent management table 130 shown in FIG. The monitoring agent management table 130 is also managed by the dynamic deployment function unit 13 in the same manner as the monitoring target management table 36. The flow of processing related to the monitoring agent management table 130 is as follows. When introducing the monitoring agent (S123), an area for recording the information of each agent 131 is created and managed together with the information of the monitoring target 132. When adding a monitoring target to an existing monitoring agent, information is added to the monitoring target column 132 of the corresponding monitoring agent. Whether or not a new monitoring target can be added to an existing monitoring agent is referred to the information in the additional accommodation availability column 133. For example, if the monitoring agent load required to monitor each monitoring target is constant, the allowable number of monitoring targets calculated in advance is registered as an initial value, and the count is decremented each time a monitoring target is added. When becomes zero, it is determined that it is impossible to add a new monitoring target.

  Regarding the monitoring logical network 14, the bandwidth of the monitoring logical network 14 is increased in accordance with an increase in the amount of monitoring traffic accompanying an increase in the number of servers to be monitored. The increase in the bandwidth of the monitoring logical network 14 is also performed by the dynamic deployment function 13 that has received the configuration change notification. However, when the existing bandwidth is sufficiently secured, it is not always necessary to increase the bandwidth, and instead of increasing the bandwidth, a new monitoring logical network may be opened. In an example of one embodiment, when the monitoring agent 10 is introduced, a bandwidth 92 including the amount of monitoring traffic equivalent to the number of monitoring target servers that the monitoring agent 10 can accept is secured. In this embodiment, it is not necessary to change the bandwidth of the monitoring logical network 14 as the number of monitoring servers increases, and the monitoring logical network 14 can be controlled when a monitoring agent 10 is newly installed.

  The dynamic deployment function 13 that has received the configuration change notification secures a monitoring log storage area in the monitoring log collection function unit 11 for accumulating the monitoring log of the newly added server, as in the first embodiment. To do.

  In the present embodiment, an example of a configuration change tracking type monitoring system that deletes unnecessary monitoring functions in accordance with a configuration change such as suspension or deletion of a monitoring target will be described. The system configuration and components are the same as those in the first or second embodiment. That is, the configuration change monitoring function 12 monitors whether the operating system 6 is stopped or the autoscale 108 is degenerated, and the dynamic deployment function 13 performs processing in response to a notification from the configuration change monitoring function 12. is there.

  The difference is that the content notified by the configuration change notification (S21) is not a new monitoring target address but a target address to be deleted from the monitoring target. The processing procedure of the dynamic deployment function 13 is the same as in FIG. 5 until the configuration change notification is received from the configuration change monitoring function 12 (S50) and the content of the received message is analyzed. A difference is that the analysis result of the received message is determined to be the deletion of the monitoring target, and the monitoring function deletion process is performed as a process corresponding to S52. Further, “delete” is designated in the command 150 of the configuration change notification message shown in FIG. 15, and address information to be deleted from the monitoring target is included in 151.

  The detailed procedure of the monitoring function deletion process is shown in FIG. The dynamic deployment function 13 that has received the monitoring target deletion notification (S140) as the configuration change notification (S21) checks the monitoring target management table 36 and the monitoring agent management table 130. If the number of monitoring targets 132 of the monitoring agent that is monitoring the monitoring target to be deleted is one (S141), the monitoring agent is deleted when it is deleted by this configuration change notification. (S142). If a monitoring logical network is introduced in pair with the monitoring agent, this monitoring logical network is also unnecessary. The monitoring target management table is searched with the address of the monitoring target to be deleted, an identifier is specified, the monitoring network management table 36 is searched using this identifier, and the ID (91) of the management logical network to be deleted or the target device is deleted. The address (90) is specified, and the management logical network is deleted using this information (S143).

  On the other hand, as a result of the confirmation processing in S141, even if the monitoring target that received the deletion notification is deleted, if the monitoring target monitored by the monitoring agent remains, the monitoring agent is not deleted and the notified monitoring target is used as the monitoring agent. (S144). Specifically, the notified monitoring target is removed from the monitoring target item 132 of the monitoring agent management table 130. The monitoring logical network is not deleted, but only the bandwidth for notifying one piece of monitoring data to be monitored becomes unnecessary, so the unnecessary bandwidth is reduced (S145). In this case as well, the monitoring target management table is searched to identify the identifier 70 related to the monitoring target to be deleted, and the monitoring network management table is searched based on this identifier information to change the bandwidth setting. The address (90) is specified and changed.

  In the monitoring function deletion processing procedure described above, unlike the procedure for introducing the monitoring function, the monitoring log collection area is not processed, but this is to keep the acquired monitoring data. Deletion of monitoring data and monitoring log collection area that are no longer required is processed at a different timing from the timing of deleting the monitoring target.

  In addition, this invention is not limited to an above-described Example, Various modifications are included. For example, the above-described embodiments describe the present invention in an easy-to-understand manner, and are not necessarily limited to those having all the configurations described. In addition, it is possible to add, delete, and replace other configurations for a part of the configuration of the embodiment.

3 Monitoring Center 4 Shared Dedicated Line 5 Public Cloud 8 Integrated Monitoring Server 10 Monitoring Agent 12 Configuration Change Monitoring Function 13 Dynamic Deployment Function 14 Monitoring Logical Network

Claims (12)

A monitoring server that is connected to one or more data centers via a network line and monitors an operating state of an application constituting a system constructed on one or more computers of the one or more data centers. There,
When the monitoring server detects an increase in the number of operation of the application or a change in the arrangement destination, agent software for monitoring the operation state of the application is installed in the computer in which the computer that operates the changed or increased application is installed. deploy to the center of the computer, to open a logical network using monitoring information Health changes or increased the application to receive from the agent software on the network line,
A logical network for collecting monitoring information from a software agent installed to monitor the application before the increase in the number of operations or the change of the placement destination is set on the network line,
When detecting an increase in the number of operation of the application or a change in the arrangement destination, it is determined whether the operation state of the application that has been changed or increased can be monitored by the installed software agent. The bandwidth of the set logical network is expanded . The monitoring server according to claim 1,
The detection of the change of the application destination is detection of switching from the operating system to the standby system. The monitoring server according to claim 1,
The detection of the change of the application destination is detection of migration of the system in operation. The monitoring server according to claim 1,
The detection of an increase in the number of operating applications is detection of scale-out of the operating system. The monitoring server according to claim 4 ,
A software agent is installed to monitor the application before the deployment destination is changed,
The monitoring server deletes the agent software for monitoring the deleted application when the application before the change is deleted in accordance with the change of the arrangement destination of the application. The monitoring server according to claim 1 ,
The monitoring server secures a storage area for storing the monitoring information collected from the agent software as the agent software is deployed. A monitoring server that is connected to one or more data centers via a network line and monitors an operating state of an application constituting a system constructed on one or more computers of the one or more data centers. A control method,
When the monitoring server detects an increase in the number of operation of the application or a change in the arrangement destination, agent software for monitoring the operation state of the application is installed in the computer in which the computer that operates the changed or increased application is installed. deploy to the center of the computer, to open a logical network using monitoring information Health changes or increased the application to receive from the agent software on the network line,
A logical network for collecting monitoring information from a software agent installed to monitor the application before the increase in the number of operations or the change of the placement destination is set on the network line,
When the monitoring server detects an increase in the number of operations of the application or a change in the arrangement destination, it can determine whether or not the operating state of the application that has been changed or increased can be monitored by the installed software agent. If it is determined, the bandwidth of the set logical network is expanded . The monitoring server control method according to claim 7 ,
The detection of the change of the application destination is detection of switching from the operating system to the standby system. The monitoring server control method according to claim 7 ,
The detection of the change of the application destination is detection of migration of the system in operation. The monitoring server control method according to claim 7 ,
The detection of an increase in the number of operating applications is detection of scale-out of the operating system. The monitoring server control method according to claim 10 , comprising:
A software agent is installed to monitor the application before the deployment destination is changed,
The monitoring server deletes the agent software for monitoring the deleted application when the application before the change is deleted in accordance with the change of the arrangement destination of the application. The monitoring server control method according to claim 7 ,
The monitoring server secures a storage area for storing the monitoring information collected from the agent software as the agent software is deployed.

Images