A method and system for cloud monitoring and edge operation and maintenance

Abstract

The application discloses a kind of cloud monitoring and edge operation and maintenance method and system, the method includes: server receives the acquisition monitoring data request sent by monitoring system and sends the monitoring data instruction of grabbing to the client of edge node;Client is according to the monitoring data of the predetermined grabbing rule of edge node application and is uploaded to server;Server returns monitoring data to monitoring system, so that monitoring system judges whether monitoring data exists exception, if exists, then send alarm signal to outside;Server receives operation and maintenance instruction, and sends operation and maintenance instruction to client;Client carries out operation and maintenance to edge node, and returns operation and maintenance result to server;Server receives operation and maintenance result and uploads operation and maintenance result to operation and maintenance interface to feedback.The application is deployed server in cloud, and client is deployed in edge node, to establish tunnel between cloud and edge node, realizes the unified monitoring and fast operation and maintenance of cloud to edge node in edge computing scene.

Description

Technical Field

[0001] This invention relates to the field of operation and maintenance monitoring technology, and in particular to a method and system for cloud monitoring and edge operation and maintenance. Background Technology

[0002] Edge computing extends cloud computing capabilities to edge nodes closer to end devices, offering advantages such as reduced latency and bandwidth usage, and has gained increasingly widespread adoption. Containers' inherent lightweight and portability make them ideal for edge computing scenarios. Kubernetes (k8s, an open-source platform for managing containerized applications across multiple hosts in a cloud platform) has become the de facto standard for cloud-native orchestration. Edge computing platforms based on k8s leverage k8s' container orchestration and scheduling capabilities to manage user-hosted edge nodes, extending cloud applications to the edge, linking data between the edge and cloud, and meeting customers' needs for remote control, data processing, analysis, decision-making, and intelligent management of edge computing resources.

[0003] Application monitoring involves collecting data for multi-dimensional statistics and visualization, providing real-time feedback on monitoring status, anticipating potential faults and issuing timely alerts, providing various indicator data at the time of fault occurrence to assist in fault analysis and localization, and offering data support for performance optimization. There are many types of monitoring systems, with widely used ones including Prometheus and Zabbix, but their architectures and deployment methods vary. Application operation and maintenance, such as daily inspections and emergency fault handling, is crucial for ensuring stable business operation and rapid recovery after faults. In edge computing scenarios, edge nodes are often located in local area networks behind firewalls. Edge nodes can directly access the cloud for registration, but the cloud cannot directly access edge nodes. Furthermore, network instability such as latency and packet loss between the cloud and edge nodes can affect data transmission between them. Existing monitoring and operation and maintenance systems struggle to meet users' needs for reliable, unified monitoring and convenient, rapid operation and maintenance in edge computing scenarios through simple configuration. Summary of the Invention

[0004] This invention provides a method and system for cloud monitoring and edge operation and maintenance, aiming to solve the problem that in the prior art, unified monitoring and rapid operation and maintenance cannot be achieved through simple configuration in edge computing scenarios.

[0005] In a first aspect, embodiments of the present invention provide a method for cloud monitoring and edge operation and maintenance, including:

[0006] The server receives a request from the monitoring system to obtain monitoring data, and sends a command to the client of the edge node to retrieve monitoring data according to the request.

[0007] The client receives the command to capture monitoring data, captures the monitoring data of the edge node application according to the predetermined capture rules, and uploads it to the server.

[0008] After receiving the uploaded monitoring data, the server returns the monitoring data to the monitoring system, so that the monitoring system can determine whether there is any abnormality in the monitoring data. If there is, the monitoring system sends an alarm signal.

[0009] The server receives maintenance instructions issued by the user based on the alarm signal and sends the maintenance instructions to the client of the edge node;

[0010] The client performs maintenance on the edge nodes according to the maintenance instructions and returns the maintenance results to the server.

[0011] After receiving the operation and maintenance results, the server uploads the results to the operation and maintenance interface for feedback.

[0012] Secondly, embodiments of the present invention provide a cloud monitoring and edge operation and maintenance system, comprising:

[0013] Server and client;

[0014] The server is used to receive the monitoring data acquisition request sent by the monitoring system, and send the monitoring data capture instruction to the client of the edge node according to the monitoring data acquisition request.

[0015] The server is also used to receive the uploaded monitoring data and return the monitoring data to the monitoring system, so that the monitoring system can determine whether there is any abnormality in the monitoring data. If there is, the monitoring system will send an alarm signal.

[0016] The server is also used to receive maintenance instructions issued by the user based on the alarm signal, and send the maintenance instructions to the client of the edge node;

[0017] The server is also used to receive the operation and maintenance results and then upload the operation and maintenance results to the operation and maintenance interface for feedback.

[0018] The client is used to receive the command to capture monitoring data, capture monitoring data of edge node applications according to predetermined capture rules, and upload it to the server.

[0019] The client is also used to perform maintenance on the edge nodes according to the maintenance instructions and return the maintenance results to the server.

[0020] This invention provides a method and system for cloud monitoring and edge operation and maintenance. The method includes: a server receiving a monitoring data acquisition request from a monitoring system, and sending a monitoring data capture instruction to a client on an edge node according to the request; the client receiving the monitoring data capture instruction, capturing monitoring data of the edge node application according to predetermined capture rules, and uploading it to the server; the server receiving the uploaded monitoring data, returning the monitoring data to the monitoring system, enabling the monitoring system to determine whether the monitoring data is abnormal, and if so, issuing an alarm signal; the server receiving an operation and maintenance instruction issued by a user based on the alarm signal, and sending the operation and maintenance instruction to the client on the edge node; the client performing operation and maintenance on the edge node according to the operation and maintenance instruction, and returning the operation and maintenance result to the server; the server receiving the operation and maintenance result, uploading the result to the operation and maintenance interface for feedback. This invention establishes a tunnel between the cloud and the edge node by deploying a server in the cloud and a client on the edge node, thereby realizing unified monitoring and rapid operation and maintenance of edge nodes from the cloud in an edge computing scenario. Attached Figure Description

[0021] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the following description of the embodiments will be briefly introduced. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0022] Figure 1 A flowchart illustrating the cloud monitoring and edge operation and maintenance method provided in this embodiment of the invention;

[0023] Figure 2 This is a schematic block diagram of a cloud monitoring and edge operation and maintenance system provided in an embodiment of the present invention. Detailed Implementation

[0024] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0025] It should be understood that, when used in this specification and the appended claims, the terms "comprising" and "including" indicate the presence of the described features, integrals, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or collections thereof.

[0026] It should also be understood that the terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to limit the invention. As used in this specification and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless the context clearly indicates otherwise.

[0027] It should also be further understood that the term "and / or" as used in this specification and the appended claims refers to any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0028] Please see Figure 1 , Figure 1 This is a flowchart illustrating a cloud monitoring and edge operation and maintenance method provided in an embodiment of the present invention, which includes steps S101 to S106.

[0029] S101. The server receives a request to obtain monitoring data sent by the monitoring system, and sends a command to the client of the edge node to capture monitoring data according to the request.

[0030] S102. The client receives the command to capture monitoring data, captures the monitoring data of the edge node application according to the predetermined capture rules, and uploads it to the server.

[0031] S103. After receiving the uploaded monitoring data, the server returns the monitoring data to the monitoring system, so that the monitoring system can determine whether there is any abnormality in the monitoring data. If there is, the monitoring system sends an alarm signal.

[0032] S104. The server receives the maintenance instructions issued by the user based on the alarm signal and sends the maintenance instructions to the client of the edge node.

[0033] S105. The client performs maintenance on the edge node according to the maintenance instructions and returns the maintenance results to the server.

[0034] S106. After receiving the operation and maintenance result, the server uploads the operation and maintenance result to the operation and maintenance interface for feedback.

[0035] In this embodiment, the server and client establish a pre-defined WebSocket connection. The server connects to the monitoring system via a pre-configured connection interface. The monitoring system sends a request to the server to obtain monitoring data. Upon receiving the request, the server generates a monitoring data capture instruction and sends it to the client. The client captures monitoring data from edge node applications according to predetermined capture rules and uploads it to the server. Simultaneously, it saves the monitoring data locally for backup. The server then returns the monitoring data to the monitoring system. At this point, the monitoring system judges the received monitoring data to determine if there are any anomalies. If no anomalies are found, the monitoring data is saved; otherwise, an alarm signal is issued. When the user receives the alarm signal, they send a corresponding maintenance instruction to the server. Upon receiving the maintenance instruction, the server sends it to the client. The client executes the maintenance instruction and returns the maintenance result to the server. The service station returns the maintenance result to the maintenance interface, thus presenting it to the user. If the monitoring data received by the monitoring system is normal, users can also enter maintenance commands in the maintenance interface and send them to the server, so that the client can perform maintenance; or, after receiving a signal that the disk space memory exceeds the specified value, send maintenance commands to the server to clean up the memory space of the specified directory.

[0036] In this embodiment, the server is deployed in the cloud, and the client is deployed on edge nodes. A proxy is used as the server, and an agent as the client. A WebSocket connection is established between the server and the client to create a communication tunnel between the cloud and the edge nodes. The cloud proxy supports integration with various monitoring systems (such as Prometheus), and the agent on the edge node can collect monitoring data from edge applications. The proxy responds to requests from the monitoring system to collect monitoring data and sends the requests to the agent through the tunnel. After the agent retrieves the monitoring data from its edge node application, it returns it to the proxy, which then returns the monitoring data to the monitoring system. This process aggregates the monitoring data from edge applications into the cloud monitoring system for unified management. This embodiment, by deploying a server in the cloud and a client on the edge nodes, allows the cloud to manage the monitoring data from the edge nodes uniformly. Furthermore, the server, by setting up interfaces, can accommodate different monitoring systems. Simple configuration enables standardized and seamless monitoring management of edge nodes. Using a WebSocket tunnel between the cloud and edge nodes, compared to conventional solutions using the HTTP protocol, results in a lightweight data format, lower performance overhead, and better conservation of server resources and bandwidth. This tunnel enables bidirectional communication between the cloud and edge nodes, even when network limitations exist in edge computing scenarios.

[0037] In a specific application scenario, first prepare 5 virtual machines configured with 16GB of memory and 8-core CPUs as the cloud environment. Deploy a highly available Kubernetes cluster (3 master nodes) on it, and deploy the Kubeedge cloud component, Prometheus, and Proxy on it. Prepare 3 virtual machines configured with 1GB of memory and 1-core CPU as edge nodes, register them with the cloud Kubernetes cluster, and deploy an Agent on each edge node. Then deploy the application on the edge nodes. The application exposes monitoring data through the interface " / metrics" and configures the Proxy information in Prometheus. Prometheus will periodically send requests to the Proxy to retrieve monitoring data according to the configuration. The Proxy then forwards the requests to the Agent, which retrieves the monitoring data and returns it to the Proxy, which then returns the result to Prometheus. An operations and maintenance interface is set up in the cloud to log in to the edge nodes connected to the cluster and view the real-time CPU, memory, and other information of the edge nodes.

[0038] In one embodiment, sending a command to the client of the edge node to retrieve monitoring data according to the request for obtaining monitoring data includes:

[0039] When sending a command to the client at the edge node to retrieve monitoring data fails, the command to retrieve monitoring data is sent to the client repeatedly within the time interval.

[0040] If the command to capture monitoring data fails to be sent within the interval, a failure signal is sent back to the monitoring system, and a new WebSocket connection is established with the client.

[0041] In this embodiment, if the server fails to send a command to the client to capture monitoring data, it resends the command to the same client within an interval. If the command fails to send within the interval, it is determined that the connection between the server and the client is broken, and a new WebSocket connection is established between the server and the client.

[0042] In one embodiment, step S102 includes:

[0043] Determine whether the monitoring data uploaded by the client is monitoring data of edge node applications captured according to predetermined capture rules;

[0044] If the monitoring data uploaded by the client is not the monitoring data of the edge node application captured by the predetermined capture rules, a new command to capture monitoring data will be generated and sent to the client so that the client can capture the data again.

[0045] In this embodiment, after the server receives monitoring data uploaded by the client, it determines whether the uploaded monitoring data is monitoring data captured according to the capture rules. If not, the server considers the received monitoring data to be unsuitable for the target monitoring data and should re-capture it, generating a new monitoring data capture instruction and sending it to the client for re-capture. By judging the uploaded monitoring data, the server avoids the occurrence of incorrect uploads by the client, thus ensuring the accuracy of the data.

[0046] In one embodiment, step S104 includes:

[0047] If sending maintenance instructions to the client at the edge node fails, the maintenance instructions will be sent to the client repeatedly within the time interval.

[0048] If the operation and maintenance instructions fail to be sent within the interval period, a failure signal is sent to the user, and a new WebSocket connection is established with the client.

[0049] In this embodiment, when the server fails to send maintenance instructions to the client, it first tries to send the maintenance instructions to the client again within an interval. If it fails to send the instructions within the interval, it is determined that the server and the client are disconnected. The server sends a failure signal to the user and re-establishes the WebSocket connection.

[0050] In one embodiment, step S105 includes:

[0051] Determine whether the operation and maintenance results contain any abnormal data;

[0052] If the operation and maintenance results contain abnormal data, the operation and maintenance instructions are regenerated and sent to the client, so that the client can perform the operation and maintenance again.

[0053] In this embodiment, after the server receives the maintenance result sent by the client, it determines whether the maintenance result contains abnormal data. If abnormal data is found, the server resends the maintenance instructions to the client and performs maintenance again. Abnormal data in this embodiment includes, but is not limited to, incomplete maintenance data and maintenance data that does not conform to the maintenance instructions.

[0054] In one embodiment, step S105 includes:

[0055] When the client fails to perform maintenance on the edge node according to the maintenance instructions, it sends a maintenance failure signal to the server.

[0056] The server regenerates maintenance instructions based on the maintenance failure signal and sends them to the client, enabling the client to perform maintenance operations again.

[0057] In this embodiment, when the client fails to perform maintenance, it sends a maintenance failure signal to the server. The server then generates new maintenance instructions and sends them to the client, enabling the client to perform maintenance again.

[0058] Please see Figure 2 , Figure 2 This is a schematic block diagram of a cloud monitoring and edge operation and maintenance system provided in an embodiment of the present invention. The system includes:

[0059] Server 201 and Client 202;

[0060] The server 201 is used to receive a request to obtain monitoring data sent by the monitoring system, and to send a command to the client of the edge node to capture monitoring data according to the request.

[0061] The server 201 is also used to receive the uploaded monitoring data and return the monitoring data to the monitoring system, so that the monitoring system can determine whether there is an anomaly in the monitoring data. If there is, the monitoring system will send an alarm signal.

[0062] The server 201 is also used to receive maintenance instructions issued by the user based on the alarm signal, and send the maintenance instructions to the client of the edge node;

[0063] The server 201 is also used to upload the operation and maintenance results to the operation and maintenance interface for feedback after receiving the operation and maintenance results;

[0064] The client 202 is used to receive the command to capture monitoring data, capture monitoring data of edge node applications according to predetermined capture rules, and upload it to the server.

[0065] The client 202 is also used to perform maintenance on the edge nodes according to the maintenance instructions and return the maintenance results to the server.

[0066] In one embodiment, the server 201 of the cloud monitoring and edge operation and maintenance system is further configured to repeatedly send the command to the client to capture monitoring data within an interval when the command to capture monitoring data fails to be sent to the client of the edge node.

[0067] The server 201 is also configured to send a failure signal to the monitoring system and re-establish a websocket connection with the client if it fails to send commands to capture monitoring data within the time interval.

[0068] In one embodiment, the server 201 of the cloud monitoring and edge operation and maintenance system is further used to determine whether the monitoring data uploaded by the client is monitoring data of the edge node application captured according to a predetermined capture rule;

[0069] The server 201 is also configured to, if the monitoring data uploaded by the client is not the monitoring data of the edge node application captured by the predetermined capture rules, regenerate the capture monitoring data instruction and send it to the client so that the client can capture again.

[0070] In one embodiment, the server 201 of the cloud monitoring and edge operation and maintenance system is further configured to repeatedly send operation and maintenance instructions to the client within an interval when sending operation and maintenance instructions to the client of the edge node fails.

[0071] The server 201 is also used to send a failure signal to the user if the operation and maintenance instructions fail to be sent within the time interval, and to re-establish the websocket connection with the client.

[0072] In one embodiment, the server 201 of the cloud monitoring and edge operation and maintenance system is further used to determine whether there is abnormal data in the operation and maintenance results;

[0073] The server 201 is also used to regenerate maintenance instructions and send them to the client if there is abnormal data in the maintenance results, so that the client can perform maintenance operations again.

[0074] In one embodiment, the client 202 of the cloud monitoring and edge operation and maintenance system is further configured to send an operation and maintenance failure signal to the server when the client fails to perform operation and maintenance on the edge node according to the operation and maintenance instructions;

[0075] The server 201 is also used to regenerate maintenance instructions based on the maintenance failure signal and send them to the client so that the client can perform maintenance operations again.

[0076] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the systems disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the descriptions are relatively simple; relevant parts can be referred to in the method section. It should be noted that those skilled in the art can make various improvements and modifications to this invention without departing from its principles, and these improvements and modifications also fall within the protection scope of the claims of this invention.

[0077] It should also be noted that, in this specification, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

Claims

1. A method for cloud-based monitoring and edge operation and maintenance, characterized in that, include: The server receives a request from the monitoring system to obtain monitoring data, and sends a command to the client of the edge node to retrieve monitoring data according to the request. The client receives the command to capture monitoring data, captures the monitoring data of the edge node application according to the predetermined capture rules, and uploads it to the server. After receiving the uploaded monitoring data, the server returns the monitoring data to the monitoring system, so that the monitoring system can determine whether there is any abnormality in the monitoring data. If there is, the monitoring system sends an alarm signal. The server receives maintenance instructions issued by the user based on the alarm signal and sends the maintenance instructions to the client of the edge node; The client performs maintenance on the edge nodes according to the maintenance instructions and returns the maintenance results to the server. After receiving the maintenance result, the server uploads the maintenance result to the maintenance interface for feedback. The step of sending a monitoring data capture instruction to the client of the edge node according to the monitoring data acquisition request includes: when sending the monitoring data capture instruction to the client of the edge node fails, repeatedly sending the monitoring data capture instruction to the client within an interval time period; if sending the monitoring data capture instruction fails within the interval time period, then sending a failure signal to the monitoring system and re-establishing the WebSocket connection with the client. The client receives the monitoring data capture instruction and captures monitoring data of edge node applications according to predetermined capture rules, and uploads it to the server. This includes: determining whether the monitoring data uploaded by the client is monitoring data of edge node applications captured according to predetermined capture rules; if the monitoring data uploaded by the client is not monitoring data of edge node applications captured according to predetermined capture rules, then regenerating the monitoring data capture instruction and sending it to the client, so that the client can re-capture the data. The server connects to different monitoring systems by setting up interface interfaces.

2. The method for cloud monitoring and edge operation and maintenance according to claim 1, characterized in that, The server receives maintenance instructions issued by the user based on the alarm signal and sends the maintenance instructions to the client of the edge node, including: If sending maintenance instructions to the client at the edge node fails, the maintenance instructions will be sent to the client repeatedly within the time interval. If the operation and maintenance instructions fail to be sent within the interval period, a failure signal is sent to the user, and a new WebSocket connection is established with the client.

3. The method for cloud monitoring and edge operation and maintenance according to claim 1, characterized in that, The client performs maintenance on the edge nodes according to the maintenance instructions and returns the maintenance results to the server, including: Determine whether the operation and maintenance results contain any abnormal data; If the operation and maintenance results contain abnormal data, the operation and maintenance instructions are regenerated and sent to the client, so that the client can perform the operation and maintenance again.

4. The method for cloud monitoring and edge operation and maintenance according to claim 1, characterized in that, The client performs maintenance on the edge nodes according to the maintenance instructions and returns the maintenance results to the server, including: When the client fails to perform maintenance on the edge node according to the maintenance instructions, it sends a maintenance failure signal to the server. The server regenerates maintenance instructions based on the maintenance failure signal and sends them to the client, enabling the client to perform maintenance operations again.

5. A system for cloud-based monitoring and edge operation and maintenance, characterized in that, include: Server and client; The server connects to different monitoring systems by configuring interface settings. The server is used to receive the monitoring data acquisition request sent by the monitoring system, and send the monitoring data capture instruction to the client of the edge node according to the monitoring data acquisition request. The server is also used to receive the uploaded monitoring data and return the monitoring data to the monitoring system, so that the monitoring system can determine whether there is any abnormality in the monitoring data. If there is, the monitoring system will send an alarm signal. The server is also used to receive maintenance instructions issued by the user based on the alarm signal, and send the maintenance instructions to the client of the edge node; The server is also used to receive the operation and maintenance results and then upload the operation and maintenance results to the operation and maintenance interface for feedback. The client is used to receive the command to capture monitoring data, capture monitoring data of edge node applications according to predetermined capture rules, and upload it to the server. The client is also used to perform maintenance on the edge nodes according to the maintenance instructions and return the maintenance results to the server. The server is also configured to repeatedly send the command to the client to capture monitoring data within an interval when the command to capture monitoring data fails to be sent to the client at the edge node; the server is also configured to send a failure signal to the monitoring system and re-establish the websocket connection with the client if the command to capture monitoring data fails to be sent within the interval. The server is also used to determine whether the monitoring data uploaded by the client is monitoring data of an edge node application captured according to a predetermined capture rule; the server is also used to regenerate a monitoring data capture instruction and send it to the client if the monitoring data uploaded by the client is not monitoring data of an edge node application captured according to the predetermined capture rule, so that the client can re-capture the data.

6. The cloud monitoring and edge operation and maintenance system according to claim 5, characterized in that, The server is also used to repeatedly send maintenance instructions to the client within an interval when it fails to send maintenance instructions to the client at the edge node. The server is also used to send a failure signal to the user if the maintenance instructions fail to be sent within the interval period, and to re-establish the websocket connection with the client.

Images