Automatic operation and maintenance method and device supporting cloud edge data synchronization

Abstract

The embodiment of the invention provides an automatic operation and maintenance method and device supporting cloud edge data synchronization, and relates to the technical field of automatic operation and maintenance. The method comprises the following steps of: constructing an Opentelemetry collector on an edge server on the basis of an Opentelemetry protocol; the Opentelemetry collector is used for acquiring operation and maintenance data; a first network abstraction layer is constructed on the edge server on the basis of an Opentelemetry collector; the first network abstraction layer is used for packaging an Opentenetry protocol; the first network abstraction layer is used for packaging the Opentenetry protocol; constructing a second network abstraction layer in communication adaptation with the first network abstraction layer on the cloud server; each of the first network abstraction layer and the second network abstraction layer comprises a universal abstraction interface for receiving and transmitting data; and the second network abstraction layer on the cloud server distributes the received operation and maintenance data to an application module on the cloud server. The implementation mode provided by the invention can better adapt to a data transmission scene of a complex network environment in the process industry.

Description

Technical Field

[0001] The present application relates to the field of automated operation and maintenance technology, and specifically to an automated operation and maintenance method supporting cloud-edge data synchronization, an automated operation and maintenance device supporting cloud-edge data synchronization, an electronic device, and a corresponding storage medium. Background Art

[0002] Today, process industries are gradually undergoing digital transformation. However, because their network topologies differ significantly from those of traditional internet companies, they cannot enjoy the advantages of traditional internet companies, such as deploying all applications in their own data centers and maintaining a stable network environment. Instead, they need to frequently transmit data across data centers and network environments.

[0003] If various automation tools commonly used in the Internet industry, such as Kubernetes and Ansible, are used, server operation permissions will be exposed to the external network, leading to major security risks.

[0004] The transition from traditional monolithic architectures to cloud-native architectures has dramatically increased the complexity of hybrid cloud management and the risk of single points of failure. For example, in hybrid public and private cloud scenarios, uneven resource allocation can easily lead to performance bottlenecks, potentially causing service outages during peak business hours. Furthermore, if microservice architectures lack well-designed load balancing and disaster recovery mechanisms, local failures can trigger cascading failures.

[0005] Existing tools primarily focus on technical-level monitoring, with limited support for business systems. Problems such as disorganized CMDB configuration item management and a lack of version control are common. Configuration errors can trigger cascading service disruptions, such as a network planning error paralyzing a logistics system. Cross-platform automated orchestration capabilities are insufficient, and troubleshooting still relies on manual intervention. Therefore, an automated operations and maintenance tool that can be used across network environments is needed. Summary of the Invention

[0006] The purpose of the embodiments of the present application is to provide an automated operation and maintenance method and device that supports cloud-edge data synchronization, and to provide a set of automated operation and maintenance tools that can be used across network environments to realize various server data collection, data encryption transmission, application remote publishing and other functions, so as to at least solve some of the problems in the background technology.

[0007] In order to achieve the above-mentioned objectives, the present application provides an automated operation and maintenance method supporting cloud-edge data synchronization, which includes: constructing an Opentelemetry collector based on the Opentelemetry protocol on the edge server; the Opentelemetry collector is used to obtain operation and maintenance data; constructing a first network abstraction layer based on the Opentelemetry collector on the edge server; the first network abstraction layer is used to encapsulate the Opentelemetry protocol; constructing a second network abstraction layer on the cloud server that is compatible with the communication with the first network abstraction layer; the first network abstraction layer and the second network abstraction layer both include a universal abstract interface for data transmission and reception; the second network abstraction layer on the cloud server distributes the received operation and maintenance data to the application module on the cloud server.

[0008] Optionally, an Opentelemetry collector is built on the edge server based on the Opentelemetry protocol, including: building components based on Opentelemetry and configuration files provided by Opentelemetry, and building the following sub-modules respectively: a sampling data exporter that supports the OTLP protocol; a batch processor that supports parallel processing of multiple sampling data; a data receiver for multiple monitoring indicators that supports the OTLP protocol; a data receiver that supports multiple database monitoring indicators; and a receiver that supports Nginx and Kafka data.

[0009] Optionally, before the Opentelemetry collector obtains operation and maintenance data, the method further includes: deploying a control-end program on the cloud server and deploying a management client on the edge server; registering the edge server to be managed in the control-end program and entering identification information of the edge server; configuring parameters for the first network abstraction layer in the edge server and the second network abstraction layer in the cloud server; starting the management client of the edge server and initiating registration with the control-end program; the control-end program generates communication parameters based on the identification information carried by the management client during registration, and the communication parameters are used to control communication information between the cloud server and the edge server; the control-end program sends an operation and maintenance task to the edge server based on the communication parameters, and the operation and maintenance task is used to trigger the edge server to obtain operation and maintenance data.

[0010] Optionally, the control-end program sends an operation and maintenance task to the edge server based on the communication parameters, including: selecting the edge server to be operated and maintained in the control-end program; selecting the task to be sent, creating the task and generating a task ID; the control-end program sends the task ID and task parameters to the edge server to be operated and maintained; the control-end program is configured to periodically check the task execution status of the edge server until the task execution is completed.

[0011] Optionally, deploying the management client on the edge server includes local deployment and remote deployment; the remote deployment includes the following steps: pulling code from the Git repository, packaging the code in a compilation method that supports Docker or native build, building an application version, and remotely publishing the code package.

[0012] Optionally, after the control-end program sends the task ID and task parameters to the edge server to be operated and maintained, the method also includes: the edge server to be operated and maintained performs idempotent judgment based on the task ID, and the same task ID will only be received and executed once; and the control-end program finds that the task has not been completed after the timeout, and re-sends the task ID and task parameters to the edge server to be operated and maintained.

[0013] Optionally, the Opentelemetry collector obtains operation and maintenance data through the following steps: tracking monitoring indicators in the business code of the business system; during the execution of the business code, the tracking sends the operation and maintenance data to the monitoring indicator exporter through the Opentelemetry protocol; the monitoring indicator exporter exports the operation and maintenance data to the Opentelemetry collector through the Opentelemetry protocol.

[0014] Optionally, monitoring indicators are tracked in the business code of the business system, including: selecting a monitoring indicator tracking SDK that is adapted to the Opentelemetry protocol according to the language type of the business code, and deploying the monitoring indicator tracking SDK in the business system; wherein, the monitoring indicator tracking SDK is generated through the following steps: obtaining the Tracer of the current thread, encapsulating the method of creating a Span based on the current Tracer, encapsulating the method of creating a nested Span, encapsulating the context transfer method, encapsulating the indicator tracking method, and encapsulating the exporter.

[0015] Optionally, the general abstract interfaces for data sending and receiving included in both the first network abstraction layer and the second network abstraction layer include: indicator data sending interface, indicator data receiving interface, task data sending interface, task data receiving interface, task status query interface, file sending interface and file receiving interface.

[0016] Optionally, the control end program generates communication parameters according to the identification information carried by the management client during registration, including: the control end program generates a key used for data encryption according to the identification information carried by the management client during registration.

[0017] Optionally, the control end program generates communication parameters according to the identification information carried by the management client during registration, including: the control end program generates fragment information for file fragment transmission according to the identification information carried by the management client during registration.

[0018] Optionally, a local message queue is set between the Opentelemetry collector of the edge server and the first network abstraction layer, and a distributed message queue is set on the cloud server. The distributed message queue is used to cache the operation and maintenance data received by the second network abstraction layer.

[0019] This application also provides an automated operation and maintenance device that supports cloud-edge data synchronization, which includes: a collector construction module, which is used to build an Opentelemetry collector based on the Opentelemetry protocol on an edge server; the Opentelemetry collector is used to obtain operation and maintenance data; an edge abstraction module, which is used to build a first network abstraction layer based on the Opentelemetry collector on the edge server; the first network abstraction layer is used to encapsulate the Opentelemetry protocol; a cloud abstraction module, which is used to build a second network abstraction layer on the cloud server that is compatible with the communication with the first network abstraction layer; the first network abstraction layer and the second network abstraction layer both include a universal abstract interface for data transmission and reception; and a cloud distribution module, which is used to distribute the received operation and maintenance data to the application module on the cloud server based on the second network abstraction layer on the cloud server.

[0020] This application also provides an electronic device comprising: at least one processor; a memory connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the at least one processor implements the aforementioned automated operation and maintenance method supporting cloud-edge data synchronization by executing the instructions stored in the memory.

[0021] This application also provides a machine-readable storage medium, which stores instructions. When the instructions are executed by a processor, the processor is configured to execute the aforementioned automated operation and maintenance method that supports cloud-edge data synchronization.

[0022] A computer program product is also provided in the present application, including a computer program, which, when executed by a processor, implements the aforementioned automated operation and maintenance method supporting cloud-edge data synchronization.

[0023] The above technical solution has the following beneficial effects: This patent solves the problem of lack of automated operation and maintenance technology components in the process industry in the past. It can greatly reduce the workload of manual operation and maintenance, and reduce various types of anomalies caused by manual operation and maintenance due to misoperation.

[0024] The introduction of the Opentelemetry protocol reduces the collection cost of various monitoring indicators. Collecting edge monitoring indicators to the cloud for centralized management can greatly improve the current problems of unstable edge deployment services and untimely problem detection.

[0025] The introduction of a network abstraction layer and local message queues also addresses issues with unstable cloud-edge networks and the proneness to various exceptions. When an exception occurs, tasks can be automatically restored and file transfers can be resumed through cloud services.

[0026] Other features and advantages of the embodiments of the present application will be described in detail in the subsequent detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] The accompanying drawings are used to provide a further understanding of the embodiments of the present application and constitute a part of the specification. Together with the following detailed description, they are used to explain the embodiments of the present application but do not constitute a limitation on the embodiments of the present application. In the accompanying drawings: Figure 1 Schematically illustrates the steps of an automated operation and maintenance method supporting cloud-edge data synchronization according to an embodiment of the present application; Figure 2 Schematically shows a component architecture diagram after implementation of the automated operation and maintenance method supporting cloud-edge data synchronization according to an embodiment of the present application; Figure 3 The following schematically shows a structural diagram of an automated operation and maintenance device supporting cloud-edge data synchronization according to an embodiment of the present application; Figure 4 The internal structure of an electronic device according to an embodiment of the present application is schematically shown. DETAILED DESCRIPTION

[0028] The following describes the specific implementation of the embodiment of the present application in detail with reference to the accompanying drawings. It should be understood that the specific implementation described herein is only used to illustrate and explain the embodiment of the present application and is not intended to limit the embodiment of the present application.

[0029] Figure 1 The following schematically shows the steps of the automated operation and maintenance method for supporting cloud-edge data synchronization according to the embodiment of the present application. Figure 1 As shown, the method includes: Building an Opentelemetry collector based on the Opentelemetry protocol on the edge server; the Opentelemetry collector is used to obtain operation and maintenance data; Building a first network abstraction layer based on the Opentelemetry collector on the edge server; the first network abstraction layer is used to encapsulate the Opentelemetry protocol; Constructing a second network abstraction layer on the cloud server that is compatible with the first network abstraction layer; both the first network abstraction layer and the second network abstraction layer include a universal abstract interface for data transmission and reception; The second network abstraction layer on the cloud server distributes the received operation and maintenance data to the application module on the cloud server.

[0030] Through the above implementation method, the various APIs provided by the Opentelemetry protocol are used to simplify the development cost of developing monitoring plug-ins for different languages. At the same time, a network abstraction layer is provided to adapt to the data transmission scenarios in the complex network environment of the process industry. The local message queue is used to reduce the performance requirements of the server and improve the reliability of data transmission.

[0031] Figure 2 The following schematically shows the component architecture diagram after the implementation of the automated operation and maintenance method supporting cloud-edge data synchronization in the embodiment of the present application. Figure 2 As shown in the figure, the network abstraction layers are differentiated by their location. The network abstraction layer on the cloud server is the second network abstraction layer, and the network abstraction layer on the edge server is the first network abstraction layer. The Opentelemetry Collector shown in the figure is the aforementioned Opentelemetry collector. The indicator alarms, log analysis, link tracking, device management, and application management in the figure are the application modules on the cloud server.

[0032] In some embodiments of the present application, the steps for constructing the Opentelemetry collector are provided, including: in combination with the Opentelemetry protocol, a module for collecting raw data needs to be constructed. Build a builder for the collector component. This step can use the construction components officially provided by Opentelemetry. Based on the construction components and the configuration files provided by the official Opentelemetry documentation, the basic configuration is as follows: Build an Opentelemetry collector based on the Opentelemetry protocol on the edge server, including: based on the Opentelemetry construction components and the configuration files provided by Opentelemetry, respectively construct the following sub-modules: a sampling data exporter that supports the OTLP protocol; a batch processor that supports parallel processing of multiple sampling data; a data receiver for multiple monitoring indicators that supports the OTLP protocol; a data receiver that supports multiple database monitoring indicators; and a receiver that supports Nginx and Kafka data.

[0033] In some embodiments of the present application, before the Opentelemetry collector obtains the operation and maintenance data, the method further includes: deploying the control-end program on the cloud server and deploying the management client on the edge server; registering the edge server to be managed in the control-end program, and entering the identification information of the edge server, such as the IP and MAC address of the edge server. Parameter configuration is performed on the first network abstraction layer in the edge server and the second network abstraction layer in the cloud server, for example, according to the specific cloud-edge server network environment, selecting protocols such as HTTP / ProtoBuffer for the network abstraction layer, as well as the data push or pull method between the cloud server and the edge server. Start the management client of the edge server and initiate registration with the control-end program; the control-end program generates communication parameters based on the identification information carried by the management client when registering, and the communication parameters are used to control the communication information between the cloud server and the edge server; the control-end program sends operation and maintenance tasks to the edge server based on the communication parameters, and the operation and maintenance tasks are used to trigger the edge server to obtain operation and maintenance data.

[0034] In some optional embodiments, the aforementioned communication parameters include the key used for data encryption. In this embodiment, after the network abstraction layer selects a specific transmission protocol based on the network environment of the edge server, there will still be problems with plaintext data transmission, resulting in security risks. Therefore, a new data encryption transmission component needs to be added to the network abstraction layer. Taking HTTP protocol transmission as an example, the transmitted message data needs to be encrypted using the national secret SM4 algorithm. The key used for encryption using the SM4 encryption algorithm is generated by negotiation between the edge server and the cloud server when the edge server goes online.

[0035] In some embodiments of the present application, the aforementioned communication parameters include fragment information when the file is transmitted in fragments. In the aforementioned remote publishing scenario and operation and maintenance data upload scenario, it is necessary to support breakpoint resumption of file transmission. When creating a remote publishing task for a code package, the corresponding file fragments should be sent. After each successful transmission, the number of bytes sent should be recorded. If the transmission fails, the transmission will start from the number of bytes recorded after the last successful transmission. The receiver will write the file immediately after receiving the bytes and return a message indicating the writing success.

[0036] In some embodiments of the present application, the control-end program sends an operation and maintenance task to the edge server based on the communication parameters, including: selecting the edge server to be operated and maintained in the control-end program; selecting the task to be sent, creating the task and generating a task ID; the control-end program sends the task ID and task parameters to the edge server to be operated and maintained; the control-end program is configured to periodically check the task execution status of the edge server until the task execution is completed.

[0037] In some embodiments of the present application, deploying the management client on the edge server includes local deployment and remote deployment; the remote deployment includes the following steps: pulling code from a Git repository, packaging the code with support for compilation methods such as Docker or native builds, building an application version, and remotely publishing the code package. This embodiment supports remote deployment of the management client, and remote deployment requires the use of remote deployment-related components. These components need to include the following functions: pulling code from a Git repository, packaging the code with support for compilation methods such as Docker or native builds, building an application version, and remotely publishing the code package.

[0038] In some embodiments of the present application, after the control-end program sends the task ID and task parameters to the edge server to be operated and maintained, the method further includes: the edge server to be operated and maintained performs an idempotent judgment based on the task ID, and the same task ID will only be received and executed once; and the control-end program finds that the task has not been completed after the timeout, and re-sends the task ID and task parameters to the edge server to be operated and maintained. In this embodiment, atomic operations that support cloud-edge synchronization are provided. When the cloud control end sends a control instruction, a task recovery mechanism needs to be provided to ensure that the execution of the task can still be restored when the network jitters or the service is abnormal. When the task starts to be executed, a task ID needs to be created. When the edge end receives the task, an idempotent judgment is performed based on the task ID. The same task ID will only be received and executed once; at the same time, if a failure occurs on the edge end, resulting in task interruption or loss, the cloud control program will find that the task has not been completed after the timeout, and will resend the task. The edge end will re-receive the task and execute it.

[0039] In some embodiments of the present application, the Opentelemetry collector acquires operation and maintenance data through the following steps: tracking monitoring indicators in the business code of the business system; during the execution of the business code, the tracking sends the operation and maintenance data to the monitoring indicator exporter via the Opentelemetry protocol; and the monitoring indicator exporter exports the operation and maintenance data to the Opentelemetry collector via the Opentelemetry protocol. This embodiment provides a specific operation and maintenance data collection process, including: tracking monitoring indicators in the business system code; during the execution of the business code, the tracking sends data to the monitoring indicator exporter via the Opentelemetry protocol; the exporter exports the monitoring indicator data to the monitoring indicator collector via the Opentelemetry protocol. If a local message queue exists, the monitoring indicator collector sends the data to the local message queue for caching. The first network abstraction layer selects the data transmission protocol used for cloud-edge data synchronization based on the specific configuration and sends the operation and maintenance data to the second network abstraction layer in the cloud via push or pull. If a message queue exists in the cloud, the data is stored in the cloud message queue. The cloud service retrieves the monitoring indicator operation and maintenance data from the message queue and performs relevant alarm logic judgments through streaming computing.

[0040] In some embodiments of the present application, a monitoring indicator tracking SDK adapted to the Opentelemetry protocol is developed for each language. The Opentelemetry protocol itself provides two communication methods based on HTTP and GRPC, and the tracking function needs to be developed according to the following steps. The steps include: according to the language type of the business code, selecting a monitoring indicator tracking SDK adapted to the Opentelemetry protocol, and deploying the monitoring indicator tracking SDK in the business system; wherein, the monitoring indicator tracking SDK is generated by the following steps: obtaining the Tracer of the current thread, encapsulating the method of creating Span based on the current Tracer, encapsulating the method of creating nested Span, encapsulating the context transfer method, encapsulating the indicator tracking method, and encapsulating the exporter. After this step is completed, the collection of operation and maintenance data of various monitoring indicators on the edge can be completed. The collected indicator data is stored in the local message queue, and services are provided to the cloud through the first network abstraction layer, supporting cloud services to obtain data by calling the interface or actively push data to the cloud service.

[0041] In some embodiments of the present application, in order to adapt to the complex network scenarios of the process industry, it is necessary to develop a network abstraction layer in accordance with the following steps to provide a universal abstract interface for various network protocols. The universal abstract interfaces for data transmission and reception included in both the first network abstraction layer and the second network abstraction layer include: an indicator data sending interface, an indicator data receiving interface, a task data sending interface, a task data receiving interface, a task status query interface, a file sending interface, and a file receiving interface. Among them, the indicator data sending interface and the indicator data receiving interface are respectively used to send and receive operation and maintenance indicator data, the task data sending interface and the task data receiving interface are respectively used to send and receive task data, the file sending interface and the file receiving interface are respectively used to send and receive file data, and the task status query interface is used to query the execution status of the current task.

[0042] In some embodiments of the present application, a local message queue is set between the Opentelemetry collector of the edge server and the first network abstraction layer, and a distributed message queue is set on the cloud server, and the distributed message queue is used to cache the operation and maintenance data received by the second network abstraction layer. The monitoring indicator collector sends the data to the local message queue for caching. The first network abstraction layer of the edge server selects the data transmission protocol used for cloud-edge data synchronization according to the specific configuration, sends the data to the second network abstraction layer in the cloud by push or pull, and stores the data in the distributed message queue in the cloud. The cloud server takes out the monitoring indicators from the distributed message queue and performs relevant alarm logic judgment through streaming computing. This embodiment can realize breakpoint resumption when the data transmission network between cloud-edge servers is unstable by accessing the local message queue. This embodiment realizes data forwarding between the second network abstraction layer and the data forwarding service through a distributed message queue.

[0043] Based on the same inventive concept, this application also provides an automated operation and maintenance device that supports cloud-edge data synchronization. Figure 3 The schematic diagram shows the structure of the automated operation and maintenance device that supports cloud-edge data synchronization according to the embodiment of the present application. Figure 3As shown, the device includes: a collector construction module, which is used to build an Opentelemetry collector based on the Opentelemetry protocol on an edge server; the Opentelemetry collector is used to obtain operation and maintenance data; an edge abstraction module, which is used to build a first network abstraction layer based on the Opentelemetry collector on the edge server; the first network abstraction layer is used to encapsulate the Opentelemetry protocol; a cloud abstraction module, which is used to build a second network abstraction layer on the cloud server that is compatible with the communication with the first network abstraction layer; the first network abstraction layer and the second network abstraction layer both include a universal abstract interface for data transmission and reception; and a cloud distribution module, which is used to distribute the received operation and maintenance data to the application module on the cloud server based on the second network abstraction layer on the cloud server.

[0044] In some optional embodiments, an Opentelemetry collector is built based on the Opentelemetry protocol on the edge server, including: based on the Opentelemetry building components and the configuration file provided by Opentelemetry, respectively building the following sub-modules: a sampling data exporter that supports the OTLP protocol; a batch processor that supports parallel processing of multiple sampling data; a data receiver for multiple monitoring indicators that supports the OTLP protocol; a data receiver that supports multiple database monitoring indicators; and a receiver that supports Nginx and Kafka data.

[0045] In some optional embodiments, before the Opentelemetry collector obtains operation and maintenance data, the method further includes: deploying a control-end program on the cloud server and deploying a management client on the edge server; registering the edge server to be managed in the control-end program and entering identification information of the edge server; configuring parameters for the first network abstraction layer in the edge server and the second network abstraction layer in the cloud server; starting the management client of the edge server and initiating registration with the control-end program; the control-end program generates communication parameters based on the identification information carried by the management client during registration, and the communication parameters are used to control communication information between the cloud server and the edge server; the control-end program sends operation and maintenance tasks to the edge server based on the communication parameters, and the operation and maintenance tasks are used to trigger the edge server to obtain operation and maintenance data.

[0046] In some optional implementations, the control-end program sends an operation and maintenance task to the edge server based on the communication parameters, including: selecting the edge server to be operated and maintained in the control-end program; selecting the task to be sent, creating the task and generating a task ID; the control-end program sends the task ID and task parameters to the edge server to be operated and maintained; the control-end program is configured to periodically check the task execution status of the edge server until the task execution is completed.

[0047] In some optional embodiments, deploying the management client on the edge server includes local deployment and remote deployment; the remote deployment includes the following steps: pulling code from the Git repository, packaging the code in a compilation method that supports Docker or native build, building an application version, and remotely publishing the code package.

[0048] In some optional implementations, after the control-end program sends the task ID and task parameters to the edge server to be operated and maintained, the method also includes: the edge server to be operated and maintained performs idempotent judgment based on the task ID, and the same task ID will only be received and executed once; and the control-end program finds that the task has not been completed after the timeout, and re-sends the task ID and task parameters to the edge server to be operated and maintained.

[0049] In some optional implementations, the Opentelemetry collector obtains operation and maintenance data through the following steps: tracking monitoring indicators in the business code of the business system; during the execution of the business code, the tracking sends the operation and maintenance data to the monitoring indicator exporter through the Opentelemetry protocol; the monitoring indicator exporter exports the operation and maintenance data to the Opentelemetry collector through the Opentelemetry protocol.

[0050] In some optional implementations, monitoring indicator tracking is performed in the business code of the business system, including: selecting a monitoring indicator tracking SDK that is adapted to the Opentelemetry protocol according to the language type of the business code, and deploying the monitoring indicator tracking SDK in the business system; wherein, the monitoring indicator tracking SDK is generated by the following steps: obtaining the Tracer of the current thread, encapsulating a method for creating a Span based on the current Tracer, encapsulating a method for creating a nested Span, encapsulating a context transfer method, encapsulating an indicator tracking method, and encapsulating an exporter.

[0051] In some optional embodiments, the general abstract interfaces for data transmission and reception included in both the first network abstraction layer and the second network abstraction layer include: an indicator data sending interface, an indicator data receiving interface, a task data sending interface, a task data receiving interface, a task status query interface, a file sending interface, and a file receiving interface.

[0052] In some optional implementations, the control end program generates communication parameters according to the identification information carried by the management client during registration, including: the control end program generates a key used for data encryption according to the identification information carried by the management client during registration.

[0053] In some optional implementations, the control end program generates communication parameters according to the identification information carried by the management client during registration, including: the control end program generates fragment information for file fragment transmission according to the identification information carried by the management client during registration.

[0054] In some optional implementations, a local message queue is set between the Opentelemetry collector of the edge server and the first network abstraction layer, and a distributed message queue is set on the cloud server. The distributed message queue is used to cache the operation and maintenance data received by the second network abstraction layer.

[0055] The specific definitions of the various functional modules in the above-mentioned automated operation and maintenance device that supports cloud-edge data synchronization can be found in the above-mentioned definitions of the automated operation and maintenance method that supports cloud-edge data synchronization, which will not be repeated here. Each module in the above-mentioned system can be implemented in whole or in part by software, hardware and their combination. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules. It also uses various APIs provided by the Opentelemetry protocol, which simplifies the development cost when developing monitoring plug-ins for different languages; at the same time, it provides a network abstraction layer to adapt to the beneficial effects of data transmission scenarios in complex network environments under process industries.

[0056] In some embodiments of the present application, an electronic device is further provided, comprising: at least one processor; a memory connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the at least one processor executes the aforementioned automated operation and maintenance method supporting cloud-edge data synchronization. Its internal structure diagram can be as follows Figure 4 shown. Figure 4The internal structure diagram of an electronic device according to an embodiment of the present application is schematically shown. The electronic device includes a processor A01, a network interface A02, a memory (not shown in the figure) and a database (not shown in the figure) connected via a system bus. Among them, the processor A01 of the electronic device is used to provide computing and control capabilities. The memory of the electronic device includes an internal memory A03 and a non-volatile storage medium A04. The non-volatile storage medium A04 stores an operating system B01, a computer program B02 and a database (not shown in the figure). The internal memory A03 provides an environment for the operation of the operating system B01 and the computer program B02 in the non-volatile storage medium A04. The network interface A02 of the electronic device is used to communicate with an external terminal through a network connection. When the computer program B02 is executed by the processor A01, an automated operation and maintenance method that supports cloud-edge data synchronization is implemented.

[0057] Those skilled in the art will understand that Figure 4 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the electronic device to which the solution of the present application is applied. The specific electronic device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0058] In one embodiment provided in the present application, a machine-readable storage medium is provided, on which instructions are stored. When the instructions are executed by a processor, the processor is configured to execute the aforementioned automated operation and maintenance method supporting cloud-edge data synchronization.

[0059] In one embodiment provided in the present application, a computer program product is provided, including a computer program, which, when executed by a processor, implements the aforementioned automated operation and maintenance method supporting cloud-edge data synchronization.

[0060] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Furthermore, the present application may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0061] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0062] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0063] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 The steps for the function specified in one or more boxes.

[0064] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0065] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0066] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can be implemented using any method or technology to store information. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change RAM (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media such as modulated data signals and carrier waves.

[0067] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.

[0068] The above are merely embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various modifications and variations. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application should all be included within the scope of the claims of the present application.

Claims

1. An automated operation and maintenance method supporting cloud-edge data synchronization, characterized in that: The method includes: Building an Opentelemetry collector based on the Opentelemetry protocol on the edge server; the Opentelemetry collector is used to obtain operation and maintenance data; Building a first network abstraction layer based on the Opentelemetry collector on the edge server; the first network abstraction layer is used to encapsulate the Opentelemetry protocol; Constructing a second network abstraction layer on the cloud server that is compatible with the first network abstraction layer; both the first network abstraction layer and the second network abstraction layer include a universal abstract interface for data transmission and reception; The second network abstraction layer on the cloud server distributes the received operation and maintenance data to the application module on the cloud server.

2. The method according to claim 1, characterized in that Build an Opentelemetry collector based on the Opentelemetry protocol on the edge server, including: Based on the Opentelemetry building components and the configuration files provided by Opentelemetry, the following sub-modules are constructed respectively: Sampling data exporter supporting OTLP protocol; Batch processor that supports parallel processing of multiple sampling data; Supports multiple monitoring indicator data receivers of OTLP protocol; Data sinks that support multiple database monitoring metrics; and Supports Nginx and Kafka data sinks.

3. The method according to claim 1, characterized in that Before the Opentelemetry collector obtains the operation and maintenance data, the method further includes: Deploy the control terminal program on the cloud server and deploy the management client on the edge server; Registering the edge server to be managed in the control terminal program and entering the identification information of the edge server; Configuring parameters for a first network abstraction layer in the edge server and a second network abstraction layer in the cloud server; Start the management client of the edge server and register with the control end program; The control end program generates communication parameters based on the identification information carried by the management client during registration. The communication parameters are used to control the communication information between the cloud server and the edge server; The control end program sends an operation and maintenance task to the edge server based on the communication parameters, and the operation and maintenance task is used to trigger the edge server to obtain operation and maintenance data.

4. The method according to claim 3, characterized in that The control end program sends operation and maintenance tasks to the edge server based on the communication parameters, including: Select the edge server to be operated and maintained in the control terminal program; Select the task to be issued, create the task and generate a task ID; The control end program sends the task ID and task parameters to the edge server to be operated and maintained; The control end program is configured to periodically check the task execution status of the edge server until the task execution is completed.

5. The method according to claim 3, characterized in that Deploying the management client on the edge server includes local deployment and remote deployment; The remote deployment includes the following steps: pulling code from the Git repository, packaging the code in a compilation method that supports Docker or native builds, building an application version, and remotely publishing the code package.

6. The method according to claim 3, characterized in that After the control end program sends the task ID and task parameters to the edge server to be operated and maintained, the method further includes: The edge server to be operated and maintained performs idempotency judgment based on the task ID. The same task ID will only be received and executed once; and The control-side program finds that the task has not been completed after the timeout, and resends the task ID and task parameters to the edge server to be operated and maintained.

7. The method according to claim 1, characterized in that The Opentelemetry collector obtains operation and maintenance data through the following steps: Track monitoring indicators in the business code of the business system; During the execution of business code, tracking points send operation and maintenance data to the monitoring indicator exporter through the OpenTelemetry protocol; The monitoring indicator exporter exports the operation and maintenance data to the Opentelemetry collector through the Opentelemetry protocol.

8. The method according to claim 7, characterized in that Tracking monitoring indicators in the business code of the business system includes: selecting a monitoring indicator tracking SDK that is adapted to the Opentelemetry protocol according to the language type of the business code, and deploying the monitoring indicator tracking SDK in the business system; wherein the monitoring indicator tracking SDK is generated by the following steps: obtaining the Tracer of the current thread, encapsulating a method for creating a Span based on the current Tracer, encapsulating a method for creating a nested Span, encapsulating a context transfer method, encapsulating an indicator tracking method, and encapsulating an exporter.

9. The method according to claim 1, characterized in that The general abstract interface for data transmission and reception included in both the first network abstraction layer and the second network abstraction layer includes: Indicator data sending interface, indicator data receiving interface, task data sending interface, task data receiving interface, task status query interface, file sending interface and file receiving interface.

10. The method according to claim 1, characterized in that The control end program generates communication parameters according to the identification information carried by the management client when registering, including: the control end program generates a key used for data encryption according to the identification information carried by the management client when registering.

11. The method according to claim 1, wherein The control end program generates communication parameters according to the identification information carried by the management client when registering, including: the control end program generates fragment information for file fragment transmission according to the identification information carried by the management client when registering.

12. The method according to claim 1, characterized in that A local message queue is set between the Opentelemetry collector of the edge server and the first network abstraction layer, and a distributed message queue is set on the cloud server. The distributed message queue is used to cache the operation and maintenance data received by the second network abstraction layer.

13. An automated operation and maintenance device supporting cloud-edge data synchronization, characterized in that: The device includes: A collector construction module is used to build an Opentelemetry collector based on the Opentelemetry protocol on the edge server; the Opentelemetry collector is used to obtain operation and maintenance data; An edge abstraction module is configured to build a first network abstraction layer based on the Opentelemetry collector on the edge server; the first network abstraction layer is configured to encapsulate the Opentelemetry protocol; a cloud abstraction module, configured to construct, on the cloud server, a second network abstraction layer adapted for communication with the first network abstraction layer; the first network abstraction layer and the second network abstraction layer both including a universal abstract interface for data transmission and reception; and The cloud distribution module is used to distribute the received operation and maintenance data to the application module on the cloud server based on the second network abstraction layer on the cloud server.

14. An electronic device, characterized in that: include: at least one processor; a memory connected to the at least one processor; In which, the memory stores instructions that can be executed by the at least one processor, and the at least one processor implements the automated operation and maintenance method supporting cloud-edge data synchronization as described in any one of claims 1 to 12 by executing the instructions stored in the memory.

15. A computer-readable storage medium having a computer program / instruction stored thereon, characterized in that: When the computer program / instruction is executed by a processor, it implements the automated operation and maintenance method supporting cloud-edge data synchronization as described in any one of claims 1 to 12.

16. A computer program product comprising a computer program / instructions, characterized in that When the computer program / instruction is executed by a processor, it implements the automated operation and maintenance method supporting cloud-edge data synchronization as described in any one of claims 1 to 12.

Images