Link monitoring methods, media, apparatuses, and computing devices

Abstract

Embodiments of the present disclosure provide a link monitoring method, medium, device and computing device. The method comprises: in response to a received configuration command, sending a probe packet to an address of a target virtual node to obtain a feedback packet replied by the target virtual node based on the probe packet, and in response to the feedback packet, determining state information of a to-be-monitored link corresponding to the target virtual node to determine a state of the to-be-monitored link according to the state information of the to-be-monitored link. The present disclosure solves the problem of low efficiency of troubleshooting of abnormalities in the related art, quickly and effectively locates the device, gateway and the like where the abnormality occurs, thereby accelerating the problem troubleshooting speed, saving the problem positioning time, and improving the overall utilization rate of cloud computing services.

Description

Technical Field

[0001] The embodiments of this disclosure relate to the field of Internet technology, and more specifically, the embodiments of this disclosure relate to a link monitoring method, medium, apparatus, and computing device. Background Technology

[0002] This section is intended to provide background or context for the embodiments of this disclosure as set forth in the claims. The description herein is not intended to be a prior art simply because it is included in this section.

[0003] With the development of cloud computing technology, providing cloud computing services through data centers and allocating, managing, and maintaining the computing and traffic resources and networks of these data centers has become a major application area. In addition to maintaining computing resources and traffic, data centers also need to monitor network links to ensure normal communication between physical nodes (i.e., computing nodes) and virtual nodes, thereby guaranteeing the normal operation of cloud-based applications.

[0004] In related technologies, virtual machines are typically deployed on each computing node that provides computing resources in order to monitor the status of that computing node. However, it is impossible to accurately monitor the communication status between different virtual nodes within a computing node, which results in long investigation times and low efficiency once traffic communication anomalies occur in the data center. Summary of the Invention

[0005] This disclosure provides a link monitoring method, medium, apparatus, and computing device to address the problem of low efficiency in troubleshooting link anomalies in related technologies.

[0006] In a first aspect of this disclosure, a link monitoring system is provided, comprising:

[0007] The monitoring manager, monitoring server, and monitoring agent are interconnected, as well as interactive data processing applications that communicate with the monitoring manager and monitoring agent;

[0008] The monitoring manager is used to send configuration commands to the monitoring server, so that the monitoring server forwards the configuration commands to the corresponding monitoring agent. The configuration commands include the address of the computing node where the link to be monitored is located and the address of the target virtual node corresponding to the link to be monitored. The target virtual node is deployed in the computing node.

[0009] The monitoring agent is used to receive configuration commands sent by the monitoring server, monitor the status of the target virtual node corresponding to the link to be monitored in the computing node it is located in, and send the monitoring data obtained to the interactive data processing application. The status of the link to be monitored is used to indicate the communication status between the communication node and the target virtual node. The communication node is used to indicate the virtual node that has a communication connection with the target virtual node.

[0010] The monitoring manager is also used to retrieve monitoring data from interactive data processing applications.

[0011] In a second aspect of this disclosure, a link monitoring method is provided, applied to a monitoring agent, comprising:

[0012] In response to the received configuration command, a probe message is sent to the address of the target virtual node to obtain the feedback message replied by the target virtual node based on the probe message. The configuration command includes the address of the computing node where the link to be monitored is located and the address of the target virtual node corresponding to the link to be monitored. The target virtual node is deployed in the computing node, and the monitoring agent is set in the computing node where the link to be monitored is located.

[0013] In response to the feedback message, the status information of the link to be monitored corresponding to the target virtual node is determined. The status of the link to be monitored is determined based on the status information of the link to be monitored. The status of the link to be monitored is used to indicate the communication status between the communication node and the target virtual node. The communication node is used to indicate the virtual node that has a communication connection with the target virtual node.

[0014] In a third aspect of this disclosure, a link monitoring method is provided, applied to a monitoring manager, comprising:

[0015] Obtain information about the virtual network to be monitored;

[0016] Based on virtual network information, virtual node information in the corresponding virtual network is obtained through a defined application interface;

[0017] Based on virtual node information and virtual network information, a configuration command for setting the application architecture is generated and sent to the monitoring server. The monitoring server then forwards the configuration command to the corresponding monitoring agent. The monitoring agent is used to monitor the status of the link to be monitored corresponding to the target virtual node in the virtual node information. The status of the link to be monitored indicates the communication status between the communication node and the target virtual node. The communication node indicates the virtual node that has a communication connection with the target virtual node. The configuration command includes the address of the computing node where the link to be monitored is located and the address of the target virtual node corresponding to the link to be monitored. The target virtual node is deployed in the computing node.

[0018] In a fourth aspect of this disclosure, a link monitoring method is provided, applied to a monitoring server, comprising:

[0019] In response to the received configuration command, the configuration command is forwarded to the monitoring agent on the corresponding compute node through the target protocol. The configuration command includes the address of the compute node where the link to be monitored is located and the address of the target virtual node corresponding to the link to be monitored. The target virtual node is deployed in the compute node. The monitoring agent is used to monitor the status of the link to be monitored corresponding to the target virtual node in the virtual node information. The status of the link to be monitored is used to indicate the communication status between the communication node and the target virtual node. The communication node is used to indicate the virtual node that has a communication connection with the target virtual node.

[0020] In a fifth aspect of this disclosure, a computer-readable storage medium is provided, comprising:

[0021] The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the link monitoring method as described in the first aspect of this disclosure; and / or, when executed by a processor, are used to implement the link monitoring method as described in the second aspect of this disclosure; and / or, when executed by a processor, are used to implement the link monitoring method as described in the third aspect of this disclosure.

[0022] In a sixth aspect of this disclosure, a link monitoring device is provided, applied to a monitoring agent, comprising:

[0023] The sending module is used to send probe messages to the address of the target virtual node in response to the received configuration command, so as to obtain the feedback message replied by the target virtual node based on the probe message. The configuration command includes the address of the computing node where the link to be monitored is located and the address of the target virtual node corresponding to the link to be monitored. The target virtual node is deployed in the computing node, and the monitoring agent is set in the computing node where the link to be monitored is located.

[0024] The processing module is used to respond to the feedback message and determine the status information of the link to be monitored corresponding to the target virtual node. The status of the link to be monitored is determined based on the status information of the link to be monitored. The status of the link to be monitored is used to indicate the communication status between the communication node and the target virtual node. The communication node is used to indicate the virtual node that has a communication connection with the target virtual node.

[0025] In a seventh aspect of this disclosure, a link monitoring device is provided, applied to a monitoring manager, comprising:

[0026] The first acquisition module is used to acquire information about the virtual network to be monitored;

[0027] The second acquisition module is used to acquire virtual node information in the virtual network corresponding to the virtual network information through a set application interface based on the virtual network information.

[0028] The sending module generates configuration commands for setting the application architecture based on virtual node information and virtual network information, and sends them to the monitoring server. The monitoring server then forwards the configuration commands to the corresponding monitoring agent. The monitoring agent monitors the status of the link to be monitored corresponding to the target virtual node in the virtual node information. The status of the link to be monitored indicates the communication status between the communication node and the target virtual node. The communication node indicates the virtual node that has a communication connection with the target virtual node. The configuration command includes the address of the computing node where the link to be monitored is located and the address of the target virtual node corresponding to the link to be monitored. The target virtual node is deployed in the computing node.

[0029] In an eighth aspect of this disclosure, a link monitoring device is provided, applied to a monitoring server, comprising:

[0030] The processing module is used to respond to the received configuration command and forward the configuration command to the monitoring agent on the corresponding computing node through the target protocol. The configuration command includes the address of the computing node where the link to be monitored is located and the address of the target virtual node corresponding to the link to be monitored. The target virtual node is deployed in the computing node. The monitoring agent is used to monitor the status of the link to be monitored corresponding to the target virtual node in the virtual node information. The status of the link to be monitored is used to indicate the communication status between the communication node and the target virtual node. The communication node is used to indicate the virtual node that has a communication connection with the target virtual node.

[0031] In a ninth aspect of the present disclosure, a computing device is provided, comprising: at least one processor;

[0032] and memory that is communicatively connected to at least one processor;

[0033] The memory stores instructions that can be executed by at least one processor to cause the computing device to perform the link monitoring method as described in the first aspect of this disclosure.

[0034] According to the link monitoring method, medium, apparatus, and computing device of this disclosure, a probe message is sent to the address of a target virtual node based on a received configuration command to obtain a feedback message from the target virtual node based on the probe message. Upon receiving the feedback message, the status information of the link to be monitored corresponding to the target virtual node is determined, and the status of the link to be monitored is determined based on the status information of the link to be monitored. Thus, by constructing and sending probe messages according to the configuration command, and then receiving the corresponding feedback messages, the virtual nodes in the virtual network specified by the real-time received configuration command are monitored. This enables comprehensive monitoring of the communication status of dynamically changing nodes in the user's corresponding virtual network and facilitates the assessment of resources allocated to the user in the cloud computing network, i.e., the network connectivity of the user's corresponding virtual network. This allows for quick and effective location of abnormal devices, gateways, and virtual nodes when anomalies occur in the user's corresponding virtual network, thereby accelerating troubleshooting, saving troubleshooting time, and improving the overall utilization rate of cloud computing services. Attached Figure Description

[0035] The above and other objects, features, and advantages of this disclosure will become readily apparent from the following detailed description of exemplary embodiments, taken in conjunction with the accompanying drawings. Several embodiments of this disclosure are illustrated in the drawings by way of example and not limitation, in which:

[0036] Figure 1 An application scenario diagram illustrating an embodiment of the present disclosure is shown schematically;

[0037] Figure 2 A schematic diagram of the structure of a link monitoring system according to another embodiment of the present disclosure is shown;

[0038] Figure 3 A flowchart illustrating a link monitoring method according to another embodiment of this disclosure is shown schematically;

[0039] Figure 4a A flowchart illustrating a link monitoring method according to another embodiment of this disclosure is shown schematically;

[0040] Figure 4b schematically shown Figure 4a The flowchart of the method for constructing and sending probe messages provided in the embodiment shown is as follows;

[0041] Figure 5 A flowchart illustrating a link monitoring method according to another embodiment of this disclosure is shown schematically;

[0042] Figure 6 A flowchart illustrating a link monitoring method according to another embodiment of this disclosure is shown schematically;

[0043] Figure 7A flowchart illustrating a link monitoring method according to another embodiment of this disclosure is shown schematically;

[0044] Figure 8 A schematic diagram of the structure of a storage medium according to another embodiment of the present disclosure is shown;

[0045] Figure 9 A schematic diagram of the structure of a link monitoring device according to another embodiment of the present disclosure is shown;

[0046] Figure 10 A schematic diagram of the structure of a link monitoring device according to another embodiment of the present disclosure is shown;

[0047] Figure 11 A schematic diagram of the structure of a link monitoring device according to another embodiment of the present disclosure is shown;

[0048] Figure 12 A schematic diagram of the structure of a computing device according to another embodiment of the present disclosure is shown.

[0049] In the accompanying drawings, the same or corresponding reference numerals indicate the same or corresponding parts. Detailed Implementation

[0050] The principles and spirit of this disclosure will now be described with reference to several exemplary embodiments. It should be understood that these embodiments are given merely to enable those skilled in the art to better understand and implement this disclosure, and are not intended to limit the scope of this disclosure in any way. Rather, these embodiments are provided to make this disclosure more thorough and complete, and to fully convey the scope of this disclosure to those skilled in the art.

[0051] Those skilled in the art will recognize that embodiments of this disclosure can be implemented as a system, apparatus, device, method, or computer program product. Therefore, this disclosure can be specifically implemented in the following forms: entirely hardware, entirely software (including firmware, resident software, microcode, etc.), or a combination of hardware and software.

[0052] According to embodiments of this disclosure, a link monitoring method, medium, apparatus, and computing device are proposed.

[0053] In this document, it should be understood that the terminology used is for convenience of understanding only and does not imply any limitation on its meaning. Furthermore, any number of elements in the accompanying drawings is for illustrative purposes only and not for limitation, and any naming is for distinction only and has no limiting meaning.

[0054] The following is a description of the terminology used in this disclosure:

[0055] Compute node: In a cloud computing environment, a physical machine is used to provide computing resources and run computing services. Each physical machine corresponds to one compute node; different compute nodes can communicate and connect with each other through gateway devices, etc.

[0056] Virtual networks, also known as virtual cloud networks or private cloud networks, are user-facing network services deployed on computing nodes. Each user who purchases cloud computing services is assigned a virtual network. A virtual network can occupy a portion of the computing resources of a single computing node or simultaneously occupy the computing resources of multiple computing nodes. Computing resources within a virtual network can communicate with each other, even if they are located on different computing nodes, as long as they belong to the same virtual network. Different virtual networks, however, typically cannot communicate with each other.

[0057] Virtual nodes: Virtual computing nodes are defined in a virtual network. Multiple virtual computing nodes can be used to execute different tasks or to jointly execute more complex tasks. A virtual network usually contains multiple virtual nodes, and different virtual nodes in the same virtual network can generally communicate with each other to jointly execute tasks.

[0058] Link: In this disclosure, it mainly refers to the path status of communication with network components (including hardware such as computing nodes and software such as virtual nodes). The link corresponding to a certain component refers to the communication status between other components and the corresponding component. Accordingly, there are two categories: physical link (i.e., the communication status when communication hardware communicates with each other) and virtual link (i.e., the communication status when software communicates with each other).

[0059] In this document, it should be understood that the terminology used is for convenience of understanding only and does not imply any limitation on its meaning. Furthermore, any number of elements in the accompanying drawings is for illustrative purposes only and not for limitation, and any naming is for distinction only and has no limiting meaning.

[0060] In addition, the data involved in this disclosure may be data authorized by the user or fully authorized by all parties. The collection, dissemination and use of the data shall comply with the requirements of relevant national laws and regulations. The implementation methods / executives of this disclosure may be combined with each other. Invention Overview

[0062] The inventors have discovered that, with the development of cloud computing technology, providing cloud computing services through data centers and allocating and managing computing resources and traffic based on the traffic and computing demands of cloud computing has become a major application direction. Data centers deploy a large number of computing nodes to provide computing resources and can allocate certain computing resources according to user needs, as well as establish corresponding virtual networks or private cloud networks for users. Based on this, the data center monitors the communication traffic between users and computing resources to achieve on-demand allocation of network traffic, optimize network service efficiency, and enhance the value of network resources. This traffic monitoring involves monitoring the status of links between various computing nodes, virtual nodes within computing nodes, and devices. If link anomalies occur, they typically affect user traffic, thereby impacting user data security and user experience. Therefore, when link anomalies occur, timely investigation and handling are necessary to minimize the impact of link anomalies.

[0063] In related technologies, a virtual node dedicated to network monitoring is typically deployed on each computing node that provides computing resources to monitor the process status of the physical machine corresponding to that computing node. However, this approach cannot accurately monitor the communication status of links between virtual nodes in the virtual network within the computing node (because virtual nodes in different virtual networks usually cannot communicate directly). This results in long troubleshooting times and low efficiency when abnormal traffic or link communication occurs. At the same time, such virtual nodes consume the computing resources of the computing node, leading to a significant waste of computing resources when there are many computing nodes.

[0064] The link monitoring method and system disclosed herein configure a monitoring agent on each computing node, and the monitoring agent sends probe messages to the virtual nodes corresponding to the links to be monitored and receives corresponding feedback messages according to the configuration commands received containing information about the links to be monitored. Based on this, the status of the links to be monitored can be determined. Thus, the status of each virtual node can be accurately determined, which significantly improves the time efficiency for troubleshooting abnormal link communication.

[0065] After introducing the basic principles of this disclosure, various non-limiting embodiments of this disclosure will be described in detail below.

[0066] Application Scenarios Overview

[0067] First refer to Figure 1The diagram illustrates an application scenario of the link monitoring method provided in this disclosure. During link monitoring, the monitoring manager 110 sends the corresponding information of the link to be monitored to the monitoring server 120 via a configuration command. The monitoring server 120 then forwards this information to the corresponding monitoring agent 130. The monitoring agent 130, based on the received configuration command, monitors the corresponding links of virtual nodes 151 in different virtual networks 150 within the computing node 140, thereby realizing the link monitoring process.

[0068] It should be noted that, Figure 1 In the scenario shown, only one or two of the monitoring manager, monitoring server, monitoring agent, compute node, virtual network, and virtual node are used as examples for illustration, but this disclosure is not limited to this. That is to say, the number of monitoring managers, monitoring servers, monitoring agents, compute nodes, virtual networks, and virtual nodes can be arbitrary.

[0069] The following is combined Figure 1 Application scenarios, refer to Figures 3 to 7 This document describes a link monitoring method according to exemplary embodiments of the present disclosure. It should be noted that the above application scenarios are shown only to facilitate understanding of the spirit and principles of the present disclosure, and the embodiments of the present disclosure are not limited in any way. Rather, the embodiments of the present disclosure can be applied to any applicable scenario.

[0070] Figure 2 This is a schematic diagram of the structure of a link monitoring system provided in one embodiment of this disclosure. Figure 2 As shown, the link monitoring system 200 provided in this embodiment includes:

[0071] The monitoring manager 210, monitoring server 220 and monitoring agent 230 are interconnected, as well as the interactive data processing application that is interconnected with the monitoring manager 210 and monitoring agent 230;

[0072] The monitoring manager 210 is used to send configuration commands to the monitoring server 220, so that the monitoring server 220 forwards the configuration commands to the corresponding monitoring agent 230. The configuration commands include the address of the computing node 232 where the monitoring link 231 is located and the address of the target virtual node 233 corresponding to the monitoring link 231. The target virtual node 233 is deployed in the computing node 232.

[0073] The monitoring agent 230 is used to receive configuration commands sent by the monitoring server 220, monitor the status of the link 231 to be monitored corresponding to the target virtual node 233 in the computing node 232, and send the monitoring data obtained to the interactive data processing application. The status of the link 231 to be monitored is used to indicate the communication status between the communication node and the target virtual node 233. The communication node is used to indicate the virtual node that has a communication connection with the target virtual node 233.

[0074] Monitoring Manager 210 is also used to obtain monitoring data from interactive data processing applications.

[0075] Specifically, the monitoring manager 210 is usually associated with the data center it is located in (it can be a single device or system, or a unified system deployed among multiple devices) to monitor the traffic of the entire data center.

[0076] There can be one or more monitoring servers 220. The monitoring server 220 corresponds to and is connected to the monitoring manager 210. The monitoring server 220 mainly receives information (i.e. configuration commands) sent by the monitoring manager 210, processes it, and forwards it to the corresponding monitoring agent 230. Therefore, one monitoring server 220 usually corresponds to multiple monitoring agents 230 at the same time (there may be a one-to-one correspondence between a specific important monitoring agent 230 and the monitoring server 220).

[0077] The monitoring agent 230 is set in the computing node 232 to monitor the link status in the computing node 232. Therefore, the monitoring agent 230 and the computing node 232 usually correspond one-to-one (it is also possible that the monitoring agent 230 does not correspond to the computing node 232 but to other device nodes, such as the gateway node).

[0078] Compute node 232 is configured with virtual networks 234 for user use. Depending on the computing resources required by the virtual networks 234, a single compute node 232 may contain multiple virtual networks 234, or only one virtual network 234, or some virtual networks 234 may occupy several compute nodes 232 simultaneously.

[0079] Each virtual network 234 typically contains one or more virtual nodes, which are the target virtual nodes 233 corresponding to the monitored link 231 (because the monitoring agent 230 usually monitors all links corresponding to virtual nodes in the compute node 232, therefore, the target virtual node 233 corresponding to the monitored link 231 is all virtual nodes in the virtual network 234). Communication nodes are typically virtual nodes belonging to the same virtual network 234 as the target virtual node 233. These can be virtual nodes within the same virtual network 234 of the same compute node 232, or virtual nodes within the same virtual network 234 of different compute nodes 232 (in which case the virtual network 234 exists simultaneously through the compute node 232 and can communicate with each other internally).

[0080] Each monitored link 231 corresponds to a target virtual node 233. In other words, each monitored link 231 is a link corresponding to a target virtual node 233.

[0081] Therefore, by monitoring all the links 231 to be monitored in the computing node 232, the communication status of all virtual nodes in the corresponding computing node 232 can be monitored, thereby ensuring the overall traffic and communication status of the computing node 232.

[0082] Furthermore, the monitoring agent 230, upon obtaining link status-related monitoring data from each monitored link 231, directly sends it to a separately configured interactive data processing application 240. The interactive data processing application 240 is typically deployed on a separate device and can communicate with the monitoring manager 210 and all monitoring agents 230. Thus, the monitoring manager 210 can extract monitoring data from the interactive data processing application 240 to adjust the configuration commands sent to the monitoring server 220 based on specific information in the monitoring data (thereby continuously updating the monitored links 231 in the corresponding link monitoring system 200), or generate notification and alarm information to send to administrators. This facilitates administrators in quickly and directly identifying the location of abnormal links, reducing the time and effort required for troubleshooting.

[0083] Furthermore, the interactive data processing application 240 can use a message management system / application to receive monitoring data and allow the monitoring manager 210 to extract it. The specific message management system can be an existing system such as Kafka or RocketMQ, and there are no restrictions here.

[0084] In one embodiment of this disclosure, the link monitoring system 200 is further configured with a cloud network environment component based on a software-defined network architecture, and the monitoring manager 210 is communicatively connected to the cloud network environment component.

[0085] Specifically, based on the software-defined networking architecture, i.e. the existing SDN architecture, the link monitoring system 200 is configured through cloud network environment components based on the SDN architecture. It can take advantage of the feature of separating network control functions from forwarding functions, move the monitoring of various node devices in the data center to external computing devices, and make the status of each node device highly transparent to the link monitoring system 200. This facilitates the data center's link monitoring of various distributed node devices and improves management efficiency.

[0086] In one embodiment of this disclosure, the link monitoring system 200 is further configured with a distributed coordination service 250 for configuring the status of devices in the cloud network, and the monitoring manager 210 is communicatively connected to the distributed coordination service 250.

[0087] Specifically, the distributed coordination service 250 ensures data consistency among devices in the link monitoring system 200, preventing issues such as dirty reads. It also facilitates the monitoring manager 210 in reading configuration information from each computing node in the data center through the distributed coordination service 250, enabling the generation of configuration commands.

[0088] In one embodiment of this disclosure, the change information obtained in the distributed coordination service 250 is periodically stored in the corresponding recording device, storage system or storage service of the data center so that the monitoring manager can obtain the corresponding configuration information from the data center through the corresponding application interface.

[0089] The specific distributed coordination service can be implemented using existing services such as ZooKeeper and Nacos.

[0090] In one embodiment of this disclosure, the monitoring agent 230 is configured based on a virtual switch service, which provides the monitoring agent 230 with the communication commands and virtual communication ports required to obtain monitoring data.

[0091] Specifically, the virtual switch service simulates the function of a virtual switch to provide the monitoring agent 230 with virtual ports for sending and receiving probe and feedback messages, without the need to actually configure a virtual node in the computing node. This significantly reduces the consumption of computing resources and is not subject to communication restrictions between different virtual networks in the computing node 232, thereby enabling link monitoring of all virtual nodes in the computing node 232.

[0092] Specific virtual switch services can be implemented using existing services such as OpenvSwitch and Hyper-V.

[0093] In one embodiment of this disclosure, the monitoring manager 210 is further configured to generate alarm information based on abnormal data in the monitoring data and generate corresponding log records.

[0094] Specifically, when an anomaly is detected in the monitored link 231, the monitoring manager 210 will generate corresponding alarm information and log information based on the computing node 232 and the target virtual node 233 where the monitored link 231 is located, so that the administrator can carry out timely maintenance and make it easier to perform log analysis later for better updates and maintenance.

[0095] In one embodiment of this disclosure, the monitoring server 220 further includes a calling interface for invoking the virtual network's corresponding computing node, gateway node, and monitoring agent 230; the monitoring server 220 is also used to manage the status of the virtual network's corresponding computing node and gateway node.

[0096] Specifically, the monitoring server 220 communicates with the monitoring agents 230 in each device node by calling the interfaces of various device nodes; at the same time, it determines which monitoring agent 230 needs to send configuration commands by managing the status of the device nodes.

[0097] The link monitoring system according to the present disclosure combines a monitoring manager, a monitoring server, a monitoring agent, and an interactive data processing application to monitor the links corresponding to target virtual nodes in the corresponding virtual network of the corresponding user. This enables the monitoring of the connectivity of the user-side network, effectively ensuring the timely detection of traffic anomalies in the cloud computing network, improving the efficiency of problem investigation, quickly locating the location of abnormal links, and improving the overall availability of cloud computing services.

[0098] Figure 3 This is a flowchart illustrating a link monitoring method provided in one embodiment of this disclosure. Figure 3 As shown, the link monitoring method provided in this embodiment includes the following steps:

[0099] Step S301: In response to the received configuration command, send a probe message to the address of the target virtual node to obtain a feedback message from the target virtual node based on the probe message.

[0100] The configuration command includes the address of the computing node where the link to be monitored is located and the address of the target virtual node corresponding to the link to be monitored. The target virtual node is deployed in the computing node, and the monitoring agent is set in the computing node where the link to be monitored is located.

[0101] Specifically, the configuration command is generated by the monitoring manager and sent to the monitoring server, which then forwards the instruction information to the monitoring agent. The configuration command is used to pass information about the link to be monitored (i.e., the address of the computing node where the link to be monitored is located and the address of the target virtual node corresponding to the link to be monitored) to the monitoring agent, so that the monitoring agent can determine the target virtual node to be monitored and the address required to send probe packets according to the configuration command.

[0102] The configuration command typically contains information about all target virtual nodes that need to be monitored in the compute node where the monitoring agent is located, as well as the corresponding links to be monitored. When the virtual network within the compute node changes or the virtual nodes within the virtual network change, the monitoring manager usually regenerates the corresponding configuration command and passes it to the monitoring agent to ensure that the monitoring agent can monitor and cover all target virtual nodes that need to be monitored in the compute node in real time.

[0103] The target virtual node's address is its network address and the port address used to receive probe packets. The target virtual node is typically any of the virtual nodes in the compute node set (or a virtual node selected during the process of iterating through all virtual nodes).

[0104] The monitoring agent can temporarily generate virtual packet sending and receiving ports within the compute node through the virtual switch service and send probe packets. Compared with related technologies, it does not require fixed occupation of computing resources within the compute node, thus improving the efficiency of computing resource utilization. Moreover, sending probe packets through the temporarily generated virtual packet sending and receiving ports has the same effect as sending probe packets through the communication node within the compute node to the target virtual node (because the virtual packet sending and receiving ports and the ports of the communication nodes within the compute node are of the same type of virtual ports). Therefore, the communication status between the communication node and the target virtual node can be determined by the packet communication status between the virtual packet sending and receiving ports and the corresponding ports of the target virtual node, thereby determining the communication status of the link to be monitored.

[0105] The purpose of probe messages is to obtain the feedback messages returned by the target virtual node based on the probe messages. By transmitting probe messages and feedback messages back and forth, the connectivity of the monitored link corresponding to the target virtual node can be confirmed (because the probe messages and feedback messages can be transmitted back and forth normally, it means that the monitoring agent and the target virtual node can communicate normally. At this time, it can be considered that the communication status to the target virtual node is normal. Therefore, it can be confirmed that the link corresponding to the target virtual node is in a normal state).

[0106] The probe message is a pre-defined message that requests the receiving node to send a feedback message. It is simple in content and consumes little bandwidth.

[0107] Step S302: In response to the feedback message, determine the status information of the link to be monitored corresponding to the target virtual node, so as to determine the status of the link to be monitored based on the status information of the link to be monitored.

[0108] Among them, the status of the link to be monitored is used to indicate the communication status between the communication node and the target virtual node; the communication node is used to indicate the virtual node that has a communication connection with the target virtual node.

[0109] Specifically, the monitoring agent determines the virtual network information corresponding to the target virtual node and the virtual node information in the virtual network through configuration commands. Then, it can communicate with the port of the target virtual node through the temporarily generated virtual message sending and receiving ports, achieving the effect of communicating with the target virtual node as if it were a communication node in the same virtual network. This allows the agent to determine the status of the link to be monitored corresponding to the target virtual node.

[0110] The feedback message is a message automatically generated by the target virtual node when it receives a probe message. The target virtual node sends a feedback message based on the address of the probe message (i.e., the port address of the monitoring agent that sent the probe message). The purpose of the feedback message is to indicate that the probe message has been received; therefore, like the probe message, it is a simple, pre-defined message to avoid consuming unnecessary bandwidth.

[0111] The monitoring agent can obtain the status information of the target virtual node corresponding to the link to be monitored by comparing the received feedback messages and probe messages (such as the sending and receiving time, whether there is information loss, packet loss rate, etc.).

[0112] The status information includes whether the communication of the link corresponding to the target virtual node is normal, the latency, and packet loss. Among these, whether the communication is normal or not is the status of the link to be monitored that needs to be determined. Based on the status information obtained from the communication between the monitoring agent and the target virtual node, the communication status between other communication nodes and the target virtual node can be determined (because if the monitoring agent cannot communicate with the target virtual node, it can be directly assumed that other communication nodes are also generally unable to guarantee normal communication with the target virtual node, i.e., the status of the link to be monitored corresponding to the target virtual node is that it cannot communicate normally).

[0113] According to the link monitoring method of this disclosure, a configuration command sent by a monitoring server is obtained, and the address of the target virtual node is determined based on the virtual network information and virtual node information corresponding to the configuration command. Then, based on the address of the target virtual node, a probe packet is constructed and sent. In response to the received feedback packet, the probe packet is forwarded to a designated link latency monitoring port through a virtual switch service, and the feedback packet is obtained through the link latency monitoring port. Based on the feedback packet and the probe packet, the status information of the link to be monitored is determined, and the status of the link to be monitored is determined according to the status information of the link to be monitored. This enables the monitoring agent to construct and send probe packets according to the configuration command, and then receive the corresponding feedback packet to monitor the virtual nodes in the virtual network specified by the real-time received configuration command. This allows for comprehensive monitoring of the communication status of dynamically changing nodes in the user's corresponding virtual network and facilitates the determination of the resources allocated to the user in the cloud computing network, i.e., the network connectivity of the user's corresponding virtual network. This allows for quick and effective location of abnormal devices, gateways, and virtual nodes when anomalies occur in the user's corresponding virtual network, thereby accelerating troubleshooting, saving troubleshooting time, and improving the overall utilization rate of cloud computing services.

[0114] Figure 4a This is a flowchart illustrating a link monitoring method provided in one embodiment of this disclosure. Figure 4a As shown, the link monitoring method provided in this embodiment includes the following steps:

[0115] Step S401: Obtain the configuration command sent by the monitoring server.

[0116] The configuration command is generated by the monitoring manager based on the set application architecture. The monitoring manager is used to generate configuration commands based on the acquired virtual network information and virtual node information to be monitored.

[0117] Specifically, configuration commands are typically issued by the monitoring manager when it determines that a virtual network or compute node in the cloud computing network has changed, in order to ensure that the monitoring agent's monitoring can cover all virtual nodes of the corresponding compute node and avoid any omissions of virtual nodes.

[0118] The application architecture is configured to constrain the style of configuration command generation, ensuring the simplicity and reliability of configuration commands when transmitted between different interfaces of the monitoring manager, monitoring server, and monitoring agent. Specifically, the application architecture can be a RESTful style (Representational State Transfer) or a similar architecture used for transmitting information through different interfaces.

[0119] In one embodiment of this disclosure, the virtual network information includes: virtual private cloud information corresponding to the virtual network, computing node where the monitoring agent of the virtual network is located, and port and address of the device corresponding to the computing node; the virtual node information includes virtual nodes in the virtual network and addresses of the virtual nodes, and the virtual node information is obtained through the application interface of the monitoring manager; the port information of the device corresponding to the computing node is obtained through the distributed coordination service.

[0120] Specifically, virtual network information is used by the monitoring agent to determine which virtual networks exist in the corresponding computing node, so that the monitoring agent can monitor the internal links of the virtual network based on the private cloud information corresponding to each virtual network, without being restricted by the inability of virtual networks to communicate with each other. Virtual node information is used by the monitoring agent to determine the information of the target virtual node, so that the monitoring agent can determine all the links to be monitored in each virtual network and perform monitoring.

[0121] The virtual node information is obtained by the monitoring manager through its application interface, which contains information about the virtual nodes corresponding to each virtual network. (Because the virtual node information contained in each virtual network is generated and stored synchronously when the virtual network is created, the monitoring manager can obtain it from the data center records or through the distributed coordination service via the corresponding interface.) Similarly, information such as the port addresses of the compute nodes can also be obtained by the monitoring manager through the distributed coordination service.

[0122] Step S402: Determine the address of the target virtual node based on the virtual network information and virtual node information corresponding to the configuration command.

[0123] Specifically, based on the virtual network information and virtual node information in the configuration command, the monitoring agent can determine each target virtual node and its corresponding monitoring link. The process involves the monitoring agent sequentially determining the target virtual node and its address from the virtual node and its address in the virtual network information corresponding to the configuration command, thus determining the corresponding address of the monitoring link.

[0124] Step S403: Construct and send a probe message based on the address of the target virtual node.

[0125] Specifically, the status of each link corresponding to a target virtual node can be determined by sending probe messages to it.

[0126] like Figure 4b The diagram shows a flowchart of a method for constructing and sending probe messages, which specifically includes the following steps:

[0127] Step S4031: Construct a probe packet with a set coloring mark using the packet construction command provided by the virtual switch service.

[0128] Among them, the color markers are used to identify probe messages.

[0129] Specifically, the monitoring agent is configured with a virtual switch service, which can provide packet construction commands to automatically generate packets of a specified type.

[0130] To facilitate the rapid and accurate identification of probe packets used for link monitoring by target virtual nodes, enabling quick processing and response, a coloring mark can be added to the probe packets. This allows the target virtual node to quickly identify the probe packets based on the coloring mark (since the coloring mark is usually at the beginning or front of the packet, the target virtual node can confirm that the packet is a probe packet upon reading the coloring mark, without needing to read the subsequent content of the packet). This leads to a faster response, reduces the CPU resources occupied by the computing node, and improves identification efficiency.

[0131] Step S4032: Send probe packets to the address of the target virtual node through the virtual communication port provided by the virtual switch service.

[0132] Specifically, the virtual switch service can provide temporary virtual communication ports to send probe messages and receive feedback messages from the target virtual node based on the probe messages.

[0133] Step S404: In response to the received feedback message, forward the probe message to the designated link delay monitoring port through the virtual switch service.

[0134] The link latency monitoring port is located on the computing node where the monitoring agent is located.

[0135] Specifically, when the target virtual node receives a probe message, it will directly return a feedback message based on the address of the virtual communication port corresponding to the probe message, indicating that the corresponding probe message has been received.

[0136] In order to determine the status of the link to be monitored, the monitoring agent needs to forward the received feedback messages directly to the link latency monitoring port configured through the virtual switch service. The link latency monitoring port can then determine the status of the corresponding link to be monitored by comparing the feedback messages and probe messages.

[0137] Step S405: Obtain feedback messages through the link delay monitoring port.

[0138] Specifically, the link delay monitoring port has a built-in program to capture and parse feedback messages, and then compare the feedback messages with the probe messages.

[0139] Step S406: Based on the feedback message and probe message, determine the status information of the link to be monitored, so as to determine the status of the link to be monitored according to the status information of the link to be monitored.

[0140] Specifically, by comparing the sending and receiving times of feedback messages and probe messages, the delay of the target virtual node corresponding to the link to be monitored can be determined. Based on the delay, the status information of the link to be monitored (such as whether it is normal, the delay time, etc.) can be determined, and thus the status of the link to be monitored can be determined.

[0141] In one embodiment of this disclosure, a set number of probe messages can be sent to the target virtual node at regular intervals, and the presence and rate of packet loss can be determined based on the received feedback messages. The packet loss rate is also included as part of the status information.

[0142] Step S407: If the monitoring agent does not receive a feedback message within the set time period, an abnormal notification message is generated.

[0143] Specifically, if the monitored link is not in a normal state (such as abnormal operation of the target virtual node, deletion, or address change), the monitoring agent (virtual communication port) will not receive feedback messages (or the interval between receiving the feedback message and sending the probe message is too long). In this case, it can be considered that the monitored link corresponding to the target virtual node is abnormal, and corresponding abnormal notification information will be generated (the abnormal notification information can be considered as a type of status information, so it is not necessary to generate a separate status information).

[0144] In one embodiment of this disclosure, in addition to generating anomaly notification information, the monitoring agent also generates a separate status information so that the monitoring manager can record the status of the corresponding monitored link based on the status information when generating log records.

[0145] Step S408: Send the abnormal notification information to the interactive data processing application so that the monitoring manager can obtain the abnormal notification information from the interactive data processing application and generate abnormal alarms and corresponding log records.

[0146] Specifically, since the monitoring manager typically does not directly monitor the agent's communication connections, the monitoring agent can send anomaly notification information to the interactive data processing application. This allows the monitoring manager to obtain the anomaly notification information from the interactive data processing application, determine the target virtual node, corresponding virtual network, and computing node corresponding to the monitored link that experienced the anomaly, and generate an anomaly alarm accordingly. This facilitates administrators in quickly locating the anomaly and performing maintenance. Simultaneously, by generating log records, more accurate analysis can be performed based on the log records during subsequent maintenance and updates of the computing nodes, thereby reducing the occurrence of link anomalies.

[0147] Steps S407 to S408 are optional steps parallel to steps S404 to S406. Those skilled in the art can select the corresponding steps to execute according to the scenario in the actual application.

[0148] According to the link monitoring method of this disclosure, configuration commands sent by the monitoring server are obtained, and the address of the target virtual node is determined based on the virtual network information and virtual node information corresponding to the configuration commands. Then, based on the address of the target virtual node, a probe packet is constructed and sent. Finally, the status of the link to be monitored is determined based on whether a corresponding feedback packet is received. Therefore, the link status of all virtual nodes in a computing node can be effectively monitored without being limited by the difficulty of communication between different virtual networks, improving the accuracy and comprehensiveness of monitoring. Furthermore, the monitoring process does not require the establishment of separate virtual nodes; only temporary ports need to be generated through the virtual switch service, significantly reducing the occupation and consumption of computing resources and improving monitoring efficiency and practicality.

[0149] Figure 5 This is a flowchart illustrating a link monitoring method provided in one embodiment of this disclosure. Figure 5 As shown, the link monitoring method provided in this embodiment includes the following steps:

[0150] Step S501: Obtain the configuration command regenerated by the monitoring server based on the received configuration information.

[0151] The configuration information is generated by the monitoring manager based on the status change information of the computing nodes.

[0152] Specifically, the configuration information consists of the relevant information about each compute node, virtual network, and virtual node in the data center required for link monitoring. When there are changes to compute nodes or virtual networks within the cloud computing center, if the monitoring of each link is still based on the original configuration commands, abnormal problems may occur (such as links not being monitored after adding compute nodes, the inability to monitor corresponding virtual networks after virtual network addresses change, and the absence of monitorable links at the original addresses of deleted virtual nodes). Therefore, when such changes occur, it is necessary to regenerate the configuration commands based on the corresponding status change information.

[0153] In one embodiment of this disclosure, the state change information of the computing node includes the following:

[0154] Scenario 1: A new child node without a corresponding hash child node is added to the root node in the virtual network, so that the first type of root node event change information generated by the computing node is generated.

[0155] Specifically, a virtual network contains several virtual nodes, which typically have certain relationships, such as belonging to the same root node, or belonging to corresponding root nodes and child nodes. The highest-level node among the virtual nodes is the root node (the root node is usually determined when the virtual network is established, and it is usually allocated the most computing resources). Below the root node are one or more child nodes (the number of child nodes can vary depending on the actual tasks being performed), and sometimes there are even lower-level subordinate nodes below the child nodes.

[0156] Each root node and its child nodes (and subordinate nodes) have a corresponding port name. These port names are usually long strings or arrays in a specified base, such as "532d-1d2e-4f4c-b203-c30aa". To facilitate monitoring the status of each node, the actual monitoring of these nodes usually involves performing a hash algorithm on their port names and extracting a portion of the result as the hash port name for monitoring. Nodes with the same hash port name and at the same level can be recorded as hash nodes. For example, the result of hashing the aforementioned port name can be "36c……a2". In this case, the first two, first three, or last two digits can be extracted as its hash port name, i.e., 36, 36c, or a2.

[0157] When there are many nodes at the same level, there will be many nodes with the same hash port name. That is, there are multiple nodes corresponding to the same hash node. If these nodes are child nodes belonging to the same root node, then the hash nodes corresponding to these child nodes can be recorded as hash child nodes.

[0158] The link monitoring system, through its configured distributed coordination service, can monitor the state changes of these root nodes and hash child nodes to handle situations such as the addition and deletion of nodes and ports. Since changes in the child nodes corresponding to hash child nodes also lead to changes in the hash child nodes themselves, monitoring the root node and its hash child nodes significantly reduces computational load while ensuring monitoring effectiveness compared to directly monitoring the root node and its child nodes.

[0159] When a new child node without a corresponding hash child node is added under the root node, the root node typically generates notification information to record the node event change (and generates the corresponding hash child node), which is the first type of root node event change information (this type of information usually includes the port name of the corresponding child node and the port name of the newly added hash child node). At this time, after the distributed coordination service collects this type of information, it enables the monitoring manager to determine that there is a state change in the compute node and the specific details of the change.

[0160] Scenario 2: A new child node with an existing corresponding hash child node is added to the root node in the virtual network to update the child node change information generated by the compute node.

[0161] Specifically, if a newly added child node in the root node can directly correspond to an existing hash child node, the hash child node will generate a corresponding notification message (usually including the corresponding child node port name) to inform that a new child node exists in the hash child node under a certain root node.

[0162] Scenario 3: A child node is deleted from the root node in the virtual network, and the corresponding hash child node no longer contains child nodes, so that the hash child node generated by the compute node changes.

[0163] Specifically, when a child node is deleted within the root node, causing its corresponding hash child node to no longer correspond to any child node within the root node, the hash child node is usually deleted, and corresponding hash child node change information is generated (usually recording the deleted child node and the port name of the hash child node).

[0164] Case 4: A child node is deleted from the root node in the virtual network, and the corresponding hash child node contains at least one child node, so that the compute node generates the second type of root node change information.

[0165] Specifically, if a child node within the root node is deleted, and its corresponding hash child node still corresponds to at least one child node within the root node, then the child node can be retained, and a corresponding notification message (containing the port name of the deleted child node) can be generated through the hash child node.

[0166] Step S502: Send a probe message to the address of the target virtual node to obtain the feedback message replied by the target virtual node based on the probe message.

[0167] Specifically, the configuration commands generated based on the changed configuration information ensure that the monitoring agent accurately covers all monitored links in the computing node, thereby guaranteeing the comprehensiveness and reliability of monitoring.

[0168] Step S503: In response to the feedback message, determine the status information of the link to be monitored corresponding to the target virtual node, so as to determine the status of the link to be monitored based on the status information of the link to be monitored.

[0169] The status of the monitored link is used to indicate the status of communication with the target virtual node.

[0170] Specifically, this step is related to Figure 3 The corresponding steps shown are the same, so they will not be repeated here.

[0171] According to the link monitoring method of this disclosure, a configuration command regenerated by the monitoring server based on received configuration information is obtained, and a probe message is sent to the corresponding link to be monitored based on the configuration command. The status of the link to be monitored is determined based on the received feedback message. This allows the monitoring server to ensure coverage of all virtual nodes and their corresponding links in the computing nodes, without being affected by changes in virtual nodes, thereby guaranteeing the comprehensiveness and reliability of monitoring all nodes in the data center.

[0172] Figure 6 This is a flowchart illustrating a link monitoring method provided in one embodiment of this disclosure. The link monitoring method shown in this embodiment is applied to a monitoring manager. Figure 6 As shown, the link monitoring method provided in this embodiment includes the following steps:

[0173] Step S601: Obtain the virtual network information to be monitored.

[0174] Specifically, the monitoring manager obtains the configuration information of the computing nodes recorded in the data center, and obtains the virtual network information of each computing node and the corresponding virtual network in the data center through the distributed coordination service (this virtual network information is the virtual network information to be monitored). Based on this information, it determines the links to be monitored, generates and sends the corresponding configuration commands to achieve real-time monitoring of each link in the data center.

[0175] In one embodiment of this disclosure, the virtual network information includes virtual private cloud information corresponding to the virtual network, computing node where the monitoring agent corresponding to the virtual network is located, and port and address of the device corresponding to the computing node.

[0176] Specifically, the virtual network information obtained by the monitoring manager is the latest information on each virtual network in the data center obtained by the distributed coordination service.

[0177] When any virtual network in the data center changes (such as changes in virtual nodes, deletion or creation of virtual networks), the distributed coordination service can obtain relevant information about the changes in the corresponding virtual network and update the virtual network information based on this information. This ensures that the monitoring manager obtains the latest virtual network information, thereby guaranteeing effective monitoring of each node and link in the data center and ultimately ensuring the overall management effectiveness of the data center.

[0178] In one embodiment of this disclosure, after obtaining the information of the virtual network to be monitored, the port information of the device corresponding to the computing node of the virtual network can also be obtained through the distributed coordination service.

[0179] Specifically, after obtaining the information of the virtual network to be monitored, the monitoring manager will continue to listen to the ports of each computing node through the distributed coordination service to determine whether there are any changes in the virtual network (or virtual nodes within the virtual network), so as to update the information of the virtual network to be monitored in a timely manner.

[0180] Step S602: Based on the virtual network information, obtain the virtual node information in the virtual network corresponding to the virtual network information through the set application interface.

[0181] Specifically, since the information of the virtual network to be monitored usually only includes the information of the virtual network that exists and the computing node where it is located, but does not include the specific information of the nodes inside the virtual network (such as only recording that a new child node has been added to the hash child node 00 in the virtual network 00f1 in computing node A01, without giving the specific address of the child node and the information of other virtual nodes in the virtual network 00f1), the monitoring manager needs to further obtain the specific virtual node information (i.e., the information of all virtual nodes contained in the virtual network 00f1).

[0182] In one embodiment of this disclosure, the virtual node information includes virtual nodes in a virtual network and the addresses of the virtual nodes.

[0183] Specifically, the monitoring manager can obtain the configuration information of virtual nodes recorded in the data center through the application interface that communicates with the data center.

[0184] Step S603: Based on the virtual node information and virtual network information, generate a configuration command to set the application architecture and send it to the monitoring server so that the monitoring server forwards the configuration command to the corresponding monitoring agent.

[0185] The monitoring agent is used to monitor the status of the link to be monitored corresponding to the target virtual node in the virtual node information. The status of the link to be monitored is used to indicate the communication status between the communication node and the target virtual node. The communication node is used to indicate the virtual node that has a communication connection with the target virtual node. The configuration command includes the address of the computing node where the link to be monitored is located and the address of the target virtual node corresponding to the link to be monitored. The target virtual node is deployed in the computing node.

[0186] Specifically, based on the required virtual node and virtual network information, the monitoring manager can generate corresponding configuration commands and send them to the monitoring agent via the monitoring server to monitor the monitored links. For details on how the monitoring agent monitors the status of the monitored links, please refer to... Figure 3 The relevant details in the illustrated embodiments will not be repeated here.

[0187] In one embodiment of this disclosure, the virtual node information and virtual network information included in the configuration command can be related information of all virtual networks and virtual nodes in the data center to ensure the comprehensiveness of monitoring; or it can be related information of some virtual networks and virtual nodes that need to be updated to improve the efficiency of data transmission while ensuring the monitoring effect.

[0188] According to the link monitoring method of this disclosure, the virtual network information and virtual node information to be monitored are obtained, and configuration commands are generated and sent accordingly. This enables the determination of the links to be monitored based on the latest, real-time updated virtual network information, thereby ensuring comprehensive coverage and effective monitoring of the changed virtual network even after changes occur, thus guaranteeing the effectiveness and reliability of data center network management.

[0189] Figure 7 This is a flowchart illustrating a link monitoring method provided in one embodiment of this disclosure. The link monitoring method shown in this embodiment is applied to a monitoring server. Figure 7 As shown, the link monitoring method provided in this embodiment includes the following steps:

[0190] Step S701: In response to the received configuration command, forward the configuration command to the monitoring agent on the corresponding computing node through the target protocol.

[0191] The configuration command includes the address of the computing node where the link to be monitored is located and the address of the target virtual node corresponding to the link to be monitored. The target virtual node is deployed in the computing node. The monitoring agent is used to monitor the status of the link to be monitored corresponding to the target virtual node in the virtual node information. The status of the link to be monitored is used to indicate the communication status between the communication node and the target virtual node. The communication node is used to indicate the virtual node that has a communication connection with the target virtual node.

[0192] Specifically, monitoring agents are typically configured on different devices than the monitoring server, and the monitoring server usually needs to support multiple monitoring agents (sending configuration commands to these agents simultaneously or at different times). Therefore, when the monitoring server forwards configuration commands to the monitoring agents, it needs to use a pre-defined target protocol to achieve the effect of transmitting configuration commands between different devices. For monitoring the status of the monitoring link, the monitoring agent can refer to... Figure 3 The relevant details in the illustrated embodiments will not be repeated here.

[0193] In one embodiment of this disclosure, the target protocol can be an RPC protocol (Remote Procedure Call) or a similar remote service call protocol, so as to achieve the effect of transmitting configuration commands without needing to adjust the underlying technology of different devices. Thus, when the monitoring server and the monitoring agent are adjusted and configured separately, the validity of the transmission of configuration commands can still be guaranteed, and the other device does not need to be updated after the device on one side is updated.

[0194] According to the link monitoring method of this disclosure, the received configuration command is forwarded to the monitoring agent on the corresponding computing node via a target protocol. This achieves the effect of transmitting configuration commands between the monitoring manager and the monitoring agent, enabling a single monitoring manager to uniformly manage the monitoring agents on each computing node, thereby ensuring the effectiveness and reliability of overall data center management.

[0195] Exemplary media

[0196] After introducing the methods of exemplary embodiments of this disclosure, the following references are made. Figure 8 The storage medium of the exemplary embodiments of this disclosure will be described.

[0197] refer to Figure 8 As shown, a program product 80 for implementing the above-described method according to an embodiment of the present disclosure is described. This product may employ a portable compact disc read-only memory (CD-ROM) and include program code, and may run on a terminal device, such as a personal computer. However, the program product of the present disclosure is not limited thereto.

[0198] The program product may employ any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0199] A readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying readable program code. This propagated data signal may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium.

[0200] Program code for performing the operations disclosed herein can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java and C++, and conventional procedural programming languages ​​such as C or similar languages. The program code can execute entirely on the user's computing device, partially on the user's computing device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing devices can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN).

[0201] Exemplary device

[0202] Having introduced the medium of exemplary embodiments of this disclosure, the following references are made to... Figures 9 to 11 The link monitoring device according to the exemplary embodiments of this disclosure will be described. Its implementation principle and technical effects are similar to those of the corresponding methods described above, and will not be repeated here. For example, Figure 9 The link monitoring device shown is applied to the monitoring agent to achieve the above. Figures 3 to 5 The link monitoring method shown in the method embodiment.

[0203] The link monitoring device 900 provided in this disclosure includes:

[0204] The sending module 910 is used to send a probe message to the address of the target virtual node in response to the received configuration command, so as to obtain the feedback message replied by the target virtual node based on the probe message. The configuration command includes the address of the computing node where the link to be monitored is located and the address of the target virtual node corresponding to the link to be monitored. The target virtual node is deployed in the computing node, and the monitoring agent is set in the computing node where the link to be monitored is located.

[0205] The processing module 920 is used to respond to the feedback message and determine the status information of the link to be monitored corresponding to the target virtual node, so as to determine the status of the link to be monitored based on the status information of the link to be monitored. The status of the link to be monitored is used to indicate the communication status between the communication node and the target virtual node. The communication node is used to indicate the virtual node that has a communication connection with the target virtual node.

[0206] In one exemplary embodiment of this disclosure, the sending module 910 is specifically used to: obtain a configuration command sent by the monitoring server, wherein the configuration command is generated by the monitoring manager based on a set application architecture, and the monitoring manager is used to generate the configuration command based on the obtained virtual network information and virtual node information to be monitored; determine the address of the target virtual node based on the virtual network information and virtual node information corresponding to the configuration command; and construct and send a probe message based on the address of the target virtual node.

[0207] In one exemplary embodiment of this disclosure, the sending module 910 specifically includes: virtual network information including: virtual private cloud information corresponding to the virtual network, computing node where the monitoring agent of the virtual network is located, and port and address of the device corresponding to the computing node; virtual node information including virtual nodes in the virtual network and addresses of the virtual nodes, which are obtained through the application interface of the monitoring manager; and port information of the device corresponding to the computing node obtained through a distributed coordination service.

[0208] In an exemplary embodiment of this disclosure, the sending module 910 is specifically used to: determine the target virtual node and the address of the target virtual node from the virtual node and the address of the virtual node in the virtual network information corresponding to the configuration command.

[0209] In one exemplary embodiment of this disclosure, the sending module 910 is specifically configured to: construct a probe message with a set coloring mark by means of a message construction command provided by the virtual switch service, wherein the coloring mark is used to identify the probe message; and send the probe message to the address of the target virtual node by means of a virtual communication port provided by the virtual switch service.

[0210] In an exemplary embodiment of this disclosure, the processing module 920 is specifically configured to: in response to a received feedback message, forward a probe message to a set link delay monitoring port via a virtual switch service, wherein the link delay monitoring port is set in the computing node where the monitoring agent is located; obtain the feedback message through the link delay monitoring port; and determine the status information of the link to be monitored based on the feedback message and the probe message, so as to determine the status of the link to be monitored according to the status information of the link to be monitored.

[0211] In one exemplary embodiment of this disclosure, the sending module 910 is specifically configured to: obtain a configuration command regenerated by the monitoring server based on the received configuration information, wherein the configuration information is generated by the monitoring manager based on the state change information of the computing node; and send a probe message to the address of the target virtual node to obtain a feedback message from the target virtual node based on the probe message.

[0212] In one exemplary embodiment of this disclosure, the sending module 910 specifically includes: the state change information of the computing node's state node includes: adding a child node without a corresponding hash child node within the root node of the virtual network, thereby generating first-type root node event change information; or adding a child node with an existing corresponding hash child node within the root node of the virtual network, thereby generating child node change information; or deleting a child node within the root node of the virtual network, and the corresponding hash child node no longer contains child nodes, thereby generating hash child node change information; or deleting a child node within the root node of the virtual network, and the corresponding hash child node contains at least one child node, thereby generating second-type root node change information.

[0213] In one exemplary embodiment of this disclosure, the sending module 910 is further configured to: after sending a probe message to the address of the target virtual node in response to a received configuration command, and obtaining a feedback message from the target virtual node based on the probe message, generate an abnormal notification message if the monitoring agent does not receive the feedback message within a set time period; and send the abnormal notification message to the interactive data processing application so that the monitoring manager can obtain the abnormal notification message from the interactive data processing application and generate an abnormal alarm and corresponding log record.

[0214] Next, as Figure 10 The link monitoring device shown is applied to the monitoring manager to achieve the above. Figure 6 The link monitoring method shown in the method embodiment.

[0215] The link monitoring device 1000 disclosed herein includes:

[0216] The first acquisition module 1010 is used to acquire information about the virtual network to be monitored;

[0217] The second acquisition module 1020 is used to acquire virtual node information in the virtual network corresponding to the virtual network information through a set application interface based on the virtual network information.

[0218] The sending module 1030 is used to generate configuration commands for setting the application architecture based on virtual node information and virtual network information, and send them to the monitoring server so that the monitoring server forwards the configuration commands to the corresponding monitoring agent. The monitoring agent is used to monitor the status of the link to be monitored corresponding to the target virtual node in the virtual node information. The status of the link to be monitored is used to indicate the communication status between the communication node and the target virtual node. The communication node is used to indicate the virtual node that has a communication connection with the target virtual node. The configuration command includes the address of the computing node where the link to be monitored is located and the address of the target virtual node corresponding to the link to be monitored. The target virtual node is deployed in the computing node.

[0219] In one exemplary embodiment of this disclosure, the second acquisition module 1020 specifically includes: virtual network information including virtual private cloud information corresponding to the virtual network, computing node where the monitoring agent corresponding to the virtual network is located, and port and address of the device corresponding to the computing node; virtual node information including virtual nodes in the virtual network and addresses of the virtual nodes.

[0220] In one exemplary embodiment of this disclosure, the first acquisition module 1010 is further configured to: after acquiring the virtual network information to be monitored, acquire the port information of the device corresponding to the computing node of the virtual network through a distributed coordination service.

[0221] Next, as Figure 11 The link monitoring device shown is applied to the monitoring server to achieve the above. Figure 7 The link monitoring method shown in the method embodiment.

[0222] The link monitoring device 1100 provided in this disclosure includes:

[0223] The processing module 1110 is used to respond to the received configuration command and forward the configuration command to the monitoring agent on the corresponding computing node through the target protocol. The configuration command includes the address of the computing node where the link to be monitored is located and the address of the target virtual node corresponding to the link to be monitored. The target virtual node is deployed in the computing node. The monitoring agent is used to monitor the status of the link to be monitored corresponding to the target virtual node in the virtual node information. The status of the link to be monitored is used to indicate the communication status between the communication node and the target virtual node. The communication node is used to indicate the virtual node that has a communication connection with the target virtual node.

[0224] Exemplary computing device

[0225] Having described the methods, media, and apparatus of exemplary embodiments of this disclosure, the following references... Figure 12 A computing device according to an exemplary embodiment of the present disclosure will be described.

[0226] Figure 12 The computing device 1200 shown is merely an example and should not be construed as limiting the functionality and scope of use of the embodiments disclosed herein.

[0227] like Figure 12 As shown, the computing device 1200 is presented in the form of a general-purpose computing device. The components of the computing device 1200 may include, but are not limited to: at least one processing unit 1201, at least one storage unit 1202, and a bus 1203 connecting different system components (including the processing unit 1201 and the storage unit 1202).

[0228] Bus 1203 includes a data bus, a control bus, and an address bus.

[0229] Storage unit 1202 may include readable media in the form of volatile memory, such as random access memory (RAM) 12021 and / or cache memory 12022, and may further include readable media in the form of non-volatile memory, such as read-only memory (ROM) 12023.

[0230] Storage unit 1202 may also include a program / utility 12025 having a set (at least one) of program modules 12024, such program modules 12024 including but not limited to: operating system, one or more application programs, other program modules and program data, each or some combination of these examples may include an implementation of a network environment.

[0231] The computing device 1200 can also communicate with one or more external devices 1204 (e.g., keyboard, pointing device, etc.). This communication can be performed via the input / output (I / O) interface 1205. Furthermore, the computing device 1200 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via the network adapter 12012. Figure 12 As shown, network adapter 12012 communicates with other modules of computing device 1200 via bus 1203. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with computing device 1200, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0232] It should be noted that although several units / modules or sub-units / modules of the supply chain strategy determination device and the object scoring model training device are mentioned in the detailed description above, this division is merely exemplary and not mandatory. In fact, according to embodiments of this disclosure, the features and functions of two or more units / modules described above can be embodied in one unit / module. Conversely, the features and functions of one unit / module described above can be further divided and embodied by multiple units / modules.

[0233] Furthermore, although the operations of the methods disclosed herein are described in a specific order in the accompanying drawings, this does not require or imply that these operations must be performed in that specific order, or that all of the operations shown must be performed to achieve the desired result. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into one step, and / or one step may be broken down into multiple steps.

[0234] While the spirit and principles of this disclosure have been described with reference to several specific embodiments, it should be understood that this disclosure is not limited to the disclosed specific embodiments, and the division of aspects does not imply that features in these aspects cannot be combined for benefit; such division is merely for convenience of expression. This disclosure is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

Claims

1. A link monitoring system, characterized in that, The system includes: A monitoring manager, a monitoring server, and a monitoring agent that are interconnected, as well as an interactive data processing application that is interconnected with the monitoring manager and the monitoring agent; The monitoring manager is used to send configuration commands to the monitoring server, so that the monitoring server forwards the configuration commands to the corresponding monitoring agent. The configuration commands include the address of the computing node where the link to be monitored is located and the address of the target virtual node corresponding to the link to be monitored. The target virtual node is deployed in the computing node. The monitoring agent is set in the computing node and is configured by the virtual switch service. It is used to receive configuration commands sent by the monitoring server, monitor the status of the target virtual node corresponding to the link to be monitored in the computing node, and send the monitoring data obtained to the interactive data processing application. The status of the link to be monitored is used to indicate the communication status between the communication node and the target virtual node. The communication node is used to indicate the virtual node that has a communication connection with the target virtual node. The monitoring agent is specifically used to: obtain configuration commands sent by the monitoring server, wherein the configuration commands are generated by the monitoring manager based on the set application architecture, and the monitoring manager is used to generate the configuration commands based on the obtained virtual network information and virtual node information to be monitored; Based on the virtual network information and virtual node information corresponding to the configuration command, the address of the target virtual node is determined; Using the packet construction command provided by the virtual switch service, a probe packet with a set coloring mark is constructed, the coloring mark being used to identify the probe packet; The probe message is sent to the address of the target virtual node through the virtual communication port provided by the virtual switch service; The monitoring manager is also used to obtain the monitoring data from the interactive data processing application.

2. The system according to claim 1, characterized in that, The link monitoring system is also configured with a cloud network environment component based on a software-defined network architecture, and the monitoring manager communicates with the cloud network environment component.

3. The system according to claim 2, characterized in that, The link monitoring system is also configured with a distributed coordination service for configuring the status of devices in the cloud network, and the monitoring manager communicates with the distributed coordination service.

4. The system according to claim 1, characterized in that, The monitoring agent is configured based on a virtual switch service, which provides the communication commands and virtual communication ports required for the monitoring agent to obtain monitoring data.

5. The system according to any one of claims 1 to 4, characterized in that, The monitoring manager is also used to generate alarm information based on abnormal data in the monitoring data and generate corresponding log records.

6. The system according to any one of claims 1 to 4, characterized in that, The monitoring server also includes a calling interface for calling the virtual network's corresponding computing node, gateway node, and the monitoring agent; The monitoring server is also used to manage the status of the corresponding computing nodes and gateway nodes in the virtual network.

7. A link monitoring method, characterized in that, Applied to a monitoring agent, the method includes: In response to the received configuration command, a probe message is sent to the address of the target virtual node to obtain a feedback message from the target virtual node based on the probe message. The configuration command includes the address of the computing node where the link to be monitored is located and the address of the target virtual node corresponding to the link to be monitored. The target virtual node is deployed in the computing node, and the monitoring agent is set in the computing node where the link to be monitored is located. In response to the feedback message, the status information of the link to be monitored corresponding to the target virtual node is determined, so as to determine the status of the link to be monitored based on the status information of the link to be monitored. The status of the link to be monitored is used to indicate the communication status between the communication node and the target virtual node. The communication node is used to indicate the virtual node that has a communication connection with the target virtual node. In response to the received configuration command, a probe message is sent to the address of the target virtual node to obtain a feedback message from the target virtual node based on the probe message, including: The monitoring manager obtains a configuration command sent by the monitoring server. The configuration command is generated by the monitoring manager based on the set application architecture. The monitoring manager is used to generate the configuration command based on the obtained virtual network information and virtual node information to be monitored. Based on the virtual network information and virtual node information corresponding to the configuration command, the address of the target virtual node is determined; Using the packet construction command provided by the virtual switch service, a probe packet with a set coloring mark is constructed, the coloring mark being used to identify the probe packet; The probe message is sent to the address of the target virtual node through the virtual communication port provided by the virtual switch service.

8. The method according to claim 7, characterized in that, The virtual network information includes: The virtual network corresponds to the virtual private cloud information, the virtual network corresponds to the computing node where the monitoring agent is located, and the computing node corresponds to the port and address of the device. The virtual node information includes virtual nodes in the virtual network and the addresses of the virtual nodes. The virtual node information is obtained through the application interface of the monitoring manager. The port information of the device corresponding to the computing node is obtained through a distributed coordination service.

9. The method according to claim 8, characterized in that, Determining the address of the target virtual node based on the virtual network information and virtual node information corresponding to the configuration command includes: The target virtual node and its address are determined from the virtual nodes and their addresses in the virtual network information corresponding to the configuration command.

10. The method according to claim 7, characterized in that, The step of responding to the feedback message and determining the status information of the link to be monitored corresponding to the target virtual node, so as to determine the status of the link to be monitored based on the status information of the link to be monitored, includes: In response to the received feedback message, the probe message is forwarded to the designated link delay monitoring port through the virtual switch service. The link delay monitoring port is set in the computing node where the monitoring agent is located. The feedback message is obtained through the link delay monitoring port; Based on the feedback message and the probe message, the status information of the link to be monitored is determined, so as to determine the status of the link to be monitored according to the status information of the link to be monitored.

11. The method according to any one of claims 7 to 10, characterized in that, In response to the received configuration command, a probe message is sent to the address of the target virtual node to obtain a feedback message from the target virtual node based on the probe message, including: Obtain the configuration command regenerated by the monitoring server based on the received configuration information, which is generated by the monitoring manager based on the status change information of the computing nodes; Send a probe message to the address of the target virtual node to obtain a feedback message from the target virtual node based on the probe message.

12. The method according to claim 11, characterized in that, The state change information of the computing node includes: In the virtual network, a new child node without a corresponding hash child node is added to the root node to change the first type of root node event information generated by the compute node; Alternatively, a child node with an existing corresponding hash child node can be added to the root node in the virtual network to make the child node change information generated by the computing node available. Alternatively, a child node is deleted from the root node in the virtual network and the corresponding hash child node no longer contains child nodes, so that the hash child node generated by the compute node changes its information. Alternatively, a child node is deleted from the root node in the virtual network, and the corresponding hash child node contains at least one child node, so that the compute node generates a second type of root node change information.

13. The method according to any one of claims 7 to 10, characterized in that, After responding to the received configuration command by sending a probe message to the address of the target virtual node and obtaining a feedback message from the target virtual node based on the probe message, the process further includes: If the monitoring agent does not receive the feedback message within a set time period, it generates an abnormal notification message; The abnormal notification information is sent to the interactive data processing application so that the monitoring manager can obtain the abnormal notification information from the interactive data processing application and generate abnormal alarms and corresponding log records.

14. A link monitoring method, characterized in that, Applied to a monitoring manager, the method includes: Obtain information about the virtual network to be monitored; Based on the virtual network information, virtual node information in the virtual network corresponding to the virtual network information is obtained through the set application interface; Based on the virtual node information and virtual network information, a configuration command for setting the application architecture is generated and sent to the monitoring server, so that the monitoring server forwards the configuration command to the corresponding monitoring agent. The monitoring agent is used to monitor the status of the link to be monitored corresponding to the target virtual node in the virtual node information. The status of the link to be monitored is used to indicate the communication status between the communication node and the target virtual node. The communication node is used to indicate the virtual node that has a communication connection with the target virtual node. The configuration command includes the address of the computing node where the link to be monitored is located and the address of the target virtual node corresponding to the link to be monitored. The target virtual node is deployed in the computing node. After obtaining the virtual network information to be monitored, the process also includes: The port information of the devices corresponding to the computing nodes of the virtual network is obtained through the distributed coordination service.

15. The method according to claim 14, characterized in that, The virtual network information includes the virtual private cloud information corresponding to the virtual network, the computing node where the monitoring agent of the virtual network is located, and the port and address of the device corresponding to the computing node. The virtual node information includes the virtual nodes in the virtual network and their addresses.

16. A link monitoring method, characterized in that, Applied to a monitoring server, the method includes: In response to a received configuration command, the configuration command is forwarded to a monitoring agent on the corresponding compute node via a target protocol. The configuration command includes the address of the compute node where the link to be monitored is located and the address of the target virtual node corresponding to the link to be monitored. The target virtual node is deployed in the compute node. The monitoring agent is used to monitor the status of the link to be monitored corresponding to the target virtual node in the virtual node information. The status of the link to be monitored is used to indicate the communication status between the communication node and the target virtual node. The communication node is used to indicate the virtual node that has a communication connection with the target virtual node.

17. A computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are configured to implement the link monitoring method as described in any one of claims 7 to 13; and / or, when executed by a processor, are configured to implement the link monitoring method as described in any one of claims 14 to 15; and / or, when executed by a processor, are configured to implement the link monitoring method as described in claim 16.

18. A link monitoring device, characterized in that, Applied to a monitoring agent, the device includes: The sending module is used to send a probe message to the address of the target virtual node in response to the received configuration command, so as to obtain a feedback message from the target virtual node based on the probe message. The configuration command includes the address of the computing node where the link to be monitored is located and the address of the target virtual node corresponding to the link to be monitored. The target virtual node is deployed in the computing node, and the monitoring agent is set in the computing node where the link to be monitored is located. The processing module is used to respond to the feedback message and determine the status information of the link to be monitored corresponding to the target virtual node, so as to determine the status of the link to be monitored based on the status information of the link to be monitored. The status of the link to be monitored is used to indicate the communication status between the communication node and the target virtual node. The communication node is used to indicate the virtual node that has a communication connection with the target virtual node. The sending module is specifically used for: The monitoring manager obtains a configuration command sent by the monitoring server. The configuration command is generated by the monitoring manager based on the set application architecture. The monitoring manager is used to generate the configuration command based on the obtained virtual network information and virtual node information to be monitored. Based on the virtual network information and virtual node information corresponding to the configuration command, the address of the target virtual node is determined; Based on the address of the target virtual node, construct and send the probe message; The sending module is specifically used for: Using the packet construction command provided by the virtual switch service, a probe packet with a set coloring mark is constructed, the coloring mark being used to identify the probe packet; The probe message is sent to the address of the target virtual node through the virtual communication port provided by the virtual switch service.

19. The link monitoring device according to claim 18, characterized in that, The sending module specifically includes: The virtual network information includes: The virtual network corresponds to the virtual private cloud information, the virtual network corresponds to the computing node where the monitoring agent is located, and the computing node corresponds to the port and address of the device. The virtual node information includes virtual nodes in the virtual network and the addresses of the virtual nodes. The virtual node information is obtained through the application interface of the monitoring manager. The port information of the device corresponding to the computing node is obtained through a distributed coordination service.

20. The link monitoring device according to claim 19, characterized in that, The sending module is specifically used for: The target virtual node and its address are determined from the virtual nodes and their addresses in the virtual network information corresponding to the configuration command.

21. The link monitoring device according to claim 18, characterized in that, The processing module is specifically used for: In response to the received feedback message, the probe message is forwarded to the designated link delay monitoring port through the virtual switch service. The link delay monitoring port is set in the computing node where the monitoring agent is located. The feedback message is obtained through the link delay monitoring port; Based on the feedback message and the probe message, the status information of the link to be monitored is determined, so as to determine the status of the link to be monitored according to the status information of the link to be monitored.

22. The link monitoring device according to any one of claims 18 to 21, characterized in that, The sending module is specifically used for: Obtain the configuration command regenerated by the monitoring server based on the received configuration information, which is generated by the monitoring manager based on the status change information of the computing nodes; Send a probe message to the address of the target virtual node to obtain a feedback message from the target virtual node based on the probe message.

23. The link monitoring device according to claim 22, characterized in that, The state change information of the computing node includes: In the virtual network, a new child node without a corresponding hash child node is added to the root node to change the first type of root node event information generated by the compute node; Alternatively, a child node with an existing corresponding hash child node can be added to the root node in the virtual network to make the child node change information generated by the computing node available. Alternatively, a child node is deleted from the root node in the virtual network and the corresponding hash child node no longer contains child nodes, so that the hash child node generated by the compute node changes its information. Alternatively, a child node is deleted from the root node in the virtual network, and the corresponding hash child node contains at least one child node, so that the compute node generates a second type of root node change information.

24. The link monitoring device according to any one of claims 18 to 21, characterized in that, The sending module is also used for: After the monitoring agent sends a probe message to the address of the target virtual node in response to the received configuration command, and obtains a feedback message from the target virtual node based on the probe message, if the monitoring agent does not receive the feedback message within a set time period, it generates an abnormal notification message. The abnormal notification information is sent to the interactive data processing application so that the monitoring manager can obtain the abnormal notification information from the interactive data processing application and generate abnormal alarms and corresponding log records.

25. A link monitoring device, characterized in that, Applied to a monitoring manager, the device includes: The first acquisition module is used to acquire information about the virtual network to be monitored; The second acquisition module is used to acquire virtual node information in the virtual network corresponding to the virtual network information through a set application interface based on the virtual network information. The sending module is used to generate a configuration command for setting the application architecture based on the virtual node information and virtual network information, and send it to the monitoring server so that the monitoring server forwards the configuration command to the corresponding monitoring agent. The monitoring agent is used to monitor the status of the link to be monitored corresponding to the target virtual node in the virtual node information. The status of the link to be monitored is used to indicate the communication status between the communication node and the target virtual node. The communication node is used to indicate the virtual node that has a communication connection with the target virtual node. The configuration command includes the address of the computing node where the link to be monitored is located and the address of the target virtual node corresponding to the link to be monitored. The target virtual node is deployed in the computing node. The first acquisition module is also used for: After obtaining the information of the virtual network to be monitored, the port information of the corresponding device of the computing node of the virtual network is obtained through the distributed coordination service.

26. The link monitoring device according to claim 25, characterized in that, The virtual network information includes the virtual private cloud information corresponding to the virtual network, the computing node where the monitoring agent of the virtual network is located, and the port and address of the device corresponding to the computing node. The virtual node information includes the virtual nodes in the virtual network and their addresses.

27. A link monitoring device, characterized in that, The device, used in a monitoring server, includes: The processing module is used to respond to the received configuration command and forward the configuration command to the monitoring agent on the corresponding computing node through the target protocol. The configuration command includes the address of the computing node where the link to be monitored is located and the address of the target virtual node corresponding to the link to be monitored. The target virtual node is deployed in the computing node. The monitoring agent is used to monitor the status of the link to be monitored corresponding to the target virtual node in the virtual node information. The status of the link to be monitored is used to indicate the communication status between the communication node and the target virtual node. The communication node is used to indicate the virtual node that has a communication connection with the target virtual node.

28. A computing device, comprising: At least one processor; and memory that is communicatively connected to at least one processor; The memory stores instructions executable by at least one processor, which are executed by at least one processor to cause the computing device to perform the link monitoring method as described in any one of claims 7 to 13; and / or to cause the computing device to perform the link monitoring method as described in any one of claims 14 to 15; and / or to cause the computing device to perform the link monitoring method as described in claim 16.

Images