A management and monitoring system for edge gateway applications

Abstract

The application belongs to the technical field of edge gateway, and particularly relates to a management and monitoring system for edge gateway application. The system comprises a basic application, wherein the basic application comprises application management deployed on a host and application coordination deployed on a container; the application coordination comprises application control and application resource collection; the application control is used for executing application control instructions; the application resource collection is used for acquiring resource information and log information of the application in the container and sending the information to a message bus; the application management comprises application monitoring and application configuration; the application monitoring is used for acquiring resource information and log information of each application on the host and acquiring resource information occupation and log information of the application in the container through the message bus; and the application configuration is used for configuring application policy information. The application solves the technical problem that a unified management and monitoring mode is lacked for application software in an edge gateway system in the prior art.

Description

Technical Field

[0001] This invention belongs to the field of edge gateway technology, specifically relating to a management and monitoring system for edge gateway applications. Background Technology

[0002] An edge gateway is a gateway device deployed at locations such as substations, distribution substations / transformer areas / towers, and grid connection points of emerging market players such as distributed new energy sources. It is responsible for collecting local power grid operation data, uploading it to the edge cluster, and implementing commands such as switching power grid operation modes and frequency / peak regulation. It has edge computing and cloud-edge collaborative application functions to support dispatching operations and market operations.

[0003] Edge gateways contain a variety of applications, which can be broadly categorized into three types based on function: basic applications, southbound applications, and northbound applications. Basic applications primarily handle management, monitoring, data storage, and logging. Southbound applications collect data from access devices, while northbound applications forward data to the scheduling master station. Edge gateways employ a container-based software architecture. Typically, basic applications are deployed on the host machine, while southbound and northbound applications are deployed in containers. If a container or application malfunctions or fails, it may be difficult to detect in a timely manner, leading to instability in the entire edge gateway system and potentially interrupting data transmission from the gateway to the scheduling master station. Traditional communication devices, upon detecting application process anomalies, often trigger a watchdog timer to restart the entire device. While this can sometimes recover from application anomalies, the recovery time is slow and it can also affect data collection or forwarding for other normally functioning applications.

[0004] Current technologies lack a unified management and monitoring method for application software in edge gateway systems. Summary of the Invention

[0005] The purpose of this invention is to provide a management and monitoring system for edge gateway applications, in order to solve the technical problem that existing technologies lack a unified management and monitoring method for application software in edge gateway systems.

[0006] To address the aforementioned technical problems, the first aspect of this invention provides a management and monitoring system for edge gateway applications, including a basic application, wherein the basic application includes application management deployed on a host machine and application co-control deployed in a container; The application co-control includes application control and application resource acquisition; the application control is used to execute application control instructions; the application resource acquisition is used to obtain resource information and log information of the application in the container and send them to the message bus. The application management includes application monitoring and application configuration; the application monitoring is used to obtain resource information and log information of each application on the host machine, and to obtain resource information and log information of the application in the container through the message bus; the application configuration is used to configure application policy information. The application management system matches application policy information capable of handling anomalies based on the abnormal resource information and / or abnormal log information obtained from application monitoring, and sends application control instructions based on the application policy information to control the applications with anomalies.

[0007] In one possible implementation, the application management also includes application installation and application deletion; The application installation is used to download and install the application onto the target container and save the application management record information; The application deletion is used to delete the application in the container and delete the application's management record information.

[0008] In one possible implementation, the application co-control starts along with the container; after the application co-control starts, it starts the applications that need to be started within the container according to the records in the application management.

[0009] In one possible implementation, the underlying application also includes container management deployed on the host machine; the container management includes container installation, container deletion, container configuration, container control, and container monitoring. The container installation is used to create containers and save the container management record information; The container deletion is used to delete the container, including its management records and all application information within the container. The container configuration is used to configure container policy information; The container control is used to execute container control instructions; The container monitoring is used to obtain resource information and log information for each container; The container management system matches container policy information capable of handling anomalies with abnormal resource information and / or abnormal log information obtained from container monitoring, and executes corresponding container control instructions based on the container policy information.

[0010] In one possible implementation, the basic application further includes device management deployed on the host machine; the device management includes device upgrades, device configuration, device control, and device monitoring. The device upgrade is used to upgrade the applications on the host machine; The device configuration is used to configure device policy information; The device control is used to execute device control commands; The device monitoring is used to obtain resource information and log information for gateway devices, container management, and application management; The device management system matches device policy information capable of handling anomalies with abnormal resource information and / or abnormal log information obtained from device monitoring, and executes corresponding device control commands based on the device policy information.

[0011] In one possible implementation, the underlying application also includes file transfer deployed on the host machine to enable local and remote file transfer functionality.

[0012] In one possible implementation, the basic application also includes log management deployed on the host machine for receiving and storing logs from various devices, containers, and applications; the log management includes log querying and log retrieval. The log query is used to generate a specified log query response message based on the received log query command, and send it to the sender of the log query command through the message bus; The log recall is used to generate corresponding log files based on the received log recall command.

[0013] In one possible implementation, the basic application also includes a startup management system deployed on the host machine; the startup management system starts automatically when the edge gateway starts, and after the startup management system starts, it starts the other basic applications.

[0014] In one possible implementation, the basic application also includes a data center deployed on the host machine; the data center is used to receive data collection information from various applications and save it to a real-time library and a database.

[0015] In one possible implementation, the resource information includes CPU, memory, disk, and processes, and their corresponding limits and / or thresholds.

[0016] The beneficial effects of this invention are as follows: The monitoring system of this invention can effectively realize the management and maintenance functions of edge gateway applications, unify the management method of edge gateway applications, and improve the management efficiency of edge gateways; it can monitor application anomalies of the gateway in real time, not only quickly detect application anomalies in the host machine or container, but also automatically recover from anomalies, and promptly and proactively send alarm information. It is not only highly reliable and has a fast recovery speed, but also supports customized anomaly recovery strategies, as well as main station-side operation and maintenance management and manual intervention, ensuring the normal operation of application software and guaranteeing the stability of the entire edge gateway system. This invention solves the technical problem of the lack of a unified management and monitoring method for application software in edge gateway systems in existing technologies. Attached Figure Description

[0017] Figure 1This is a schematic diagram of the gateway management and monitoring system structure in the implementation of the edge gateway application management and monitoring system of the present invention; Figure 2 This is a flowchart illustrating the gateway system application startup process in an implementation of the edge gateway application management and monitoring system of the present invention. Figure 3 This is a schematic diagram of gateway management and monitoring message interaction in an implementation of the management and monitoring system for edge gateway applications of the present invention; Figure 4 This is a flowchart illustrating the gateway device monitoring process in an implementation of the edge gateway application management and monitoring system of the present invention. Figure 5 This is a flowchart illustrating the gateway container monitoring process in an implementation of the edge gateway application management and monitoring system of the present invention. Figure 6 This is a flowchart illustrating the gateway application monitoring process in an implementation of the edge gateway application management and monitoring system of the present invention. Detailed Implementation

[0018] The monitoring system of this invention effectively manages and maintains edge gateway applications, unifies the management methods for edge gateway applications, and improves the management efficiency of edge gateways. It can monitor application anomalies in the gateway in real time, quickly detect anomalies in the host machine or containers, automatically recover from anomalies, and promptly and proactively send alarm information. It is highly reliable and has a fast recovery speed. It supports customized anomaly recovery strategies, as well as main station-side operation and maintenance management and manual intervention, ensuring the normal operation of application software and guaranteeing the stability of the entire edge gateway system. This invention solves the technical problem of the lack of a unified management and monitoring method for application software in edge gateway systems in existing technologies.

[0019] To make the objectives, technical solutions, and advantages of the present invention clearer, the technical solutions of the present invention will be further described in detail below with reference to the accompanying drawings.

[0020] Implementation methods for management and monitoring systems of edge gateway applications: A management and monitoring system for edge gateway applications, such as Figure 1 As shown, the system includes essential, non-removable applications such as Startup Management, Device Management, Container Management, Application Management, Log Management, Application Co-control, Management Channel, Data Center, and File Transfer. Startup Management, Device Management, Container Management, Application Management, Log Management, Management Channel, Data Center, and File Transfer are deployed on the gateway host machine. Application Co-control is deployed on the gateway container. The various applications can interact via a message bus. The message bus can take any form, such as an application or a dynamic library. Figure 3 As shown.

[0021] Startup management, device management, container management, application management, log management, management channel, data center, and file transfer are deployed on the gateway host. Application co-control is deployed on the gateway container. Various applications can interact via a message bus. The message bus can take any form, including applications and dynamic libraries.

[0022] Startup management enables the management of startup of applications on the host machine.

[0023] Startup management is added to the edge gateway system's auto-start service entry file and starts automatically when the gateway device starts.

[0024] After the management application starts, it launches applications such as file transfer, device management, container management, application management, data center, management channel, and log management. Figure 2 As shown.

[0025] Equipment management includes functions such as equipment upgrades, equipment configuration, equipment control, and equipment monitoring.

[0026] Device upgrades can upgrade host applications other than startup management and file transfer.

[0027] Device configuration allows for the configuration of device policy information. Device policy information includes device policy retrieval information, device policy action information, and device policy relationship information. Device policy retrieval information includes resource information, critical logs, etc. Device action information includes device restart actions, device alarm actions, etc. Device policy relationship information is the association information between device retrieval information and action information. The gateway has preset default device configuration information, which can be updated through device configuration operations.

[0028] Device control includes operations such as device restart. In addition to device control operations generated by the device management system itself, it can also receive and execute device control commands sent by other applications.

[0029] Device monitoring detects real-time resource usage and critical log information of gateway devices, while also receiving resource and log information from container management and application management. Device management generates device policy collection information based on resource and log information from device management, container management, and application management. It then matches this information with device policy retrieval information, determines device policy action information based on device policy relationship information, and finally executes specific device actions, such as... Figure 4 As shown.

[0030] Container management includes functions such as container installation, container deletion, container configuration, container control, and container monitoring.

[0031] Container installation can create a container with specified container configuration information and save the container's management records.

[0032] The container deletion function can delete a specified container and its management records. The container deletion operation will also simultaneously delete all application information within the container.

[0033] Container configuration allows you to configure container policy information. Container policy information includes container policy retrieval information, container policy action information, and container policy relationship information. Container policy retrieval information includes resource information, critical logs, etc. Container action information includes container restart actions, container start actions, container stop actions, container alarm actions, etc. Container policy relationship information is the association information between container retrieval information and action information. The gateway has default container configuration information, which can be updated through container configuration operations; each container can be configured and updated individually.

[0034] Container control includes container control operations such as container restart, container startup, and container shutdown. In addition to container control operations generated by the container management system itself, it can also receive and execute container control operation commands sent by other applications.

[0035] Container monitoring continuously monitors the resource usage and critical log information of each container on the gateway device, while also receiving resource and log information from application management. Container management generates container policy collection information based on resource and log information from container management and application management. It then matches this information with container policy retrieval information, determines container policy action information based on container policy relationship information, and finally executes specific container actions, such as... Figure 5 As shown.

[0036] After container management is started, the required containers are started based on the container management log information.

[0037] Application management includes functions such as application installation and deletion in containers, as well as application monitoring and configuration in both the host machine and containers.

[0038] Application installation can download application installation packages, install applications with specified application configuration information onto the target container, and save the application management record information.

[0039] Application deletion can remove a specified application from the container and delete the application's management records.

[0040] Application configuration allows for the configuration of application policy information. Application policy information includes application policy retrieval information, application policy action information, and application policy relationship information. Application policy retrieval information includes resource information, critical logs, etc. Application action information includes application restart actions, application start actions, application stop actions, application alarm actions, etc. Application policy relationship information refers to the association between application retrieval information and action information. The gateway has preset default application configuration information, which can be updated through application configuration operations; each application can be configured and updated individually.

[0041] Application monitoring monitors the resource usage and critical log information of each application on the gateway host in real time, and simultaneously receives real-time resource usage information and critical log information of each application on the container from application co-control. Application management generates application policy collection information based on resource and log information from container management, application management, and application co-control. It matches application policy retrieval information with this collection information, determines application policy action information based on application policy relationship information, and finally executes the specific application action. Application management integrates resource and log messages from various applications on the host and containers, and forwards them to device management and container management, such as... Figure 6 As shown.

[0042] Application co-control includes functions such as application control within containers and application resource acquisition.

[0043] Application control includes application control operations such as restarting, starting, and stopping applications within the container. In addition to application control operations generated by the application co-control itself, it also receives and executes application control commands sent by other applications.

[0044] Application resource acquisition can detect the resource usage of each application in the container in real time and send it to the message bus.

[0045] The application co-control is packaged into the container image and set as the entry point for the image to run, so that it starts automatically when the container starts.

[0046] After the application co-control starts, it starts the applications that the container needs to start according to the application management records.

[0047] Log management includes the functions of receiving and storing log messages from devices, containers, and applications. It also includes log querying and log retrieval functions. Log management receives log query commands and log retrieval commands from other applications. Log querying can generate a specified log query response message based on the query information and send it to the other side via the message bus. Log retrieval can generate a specified log file based on the retrieval information and transfer the log file to the other side via file transfer.

[0048] The management channel can interact with the dispatch master station or local operation and maintenance tools, including executing downlink management commands and sending alarm information.

[0049] The management channel receives downlink management commands and forwards them to the corresponding application modules for execution. Downlink device management commands include device upgrades, device configurations, and device control, and must be forwarded to device management for execution. Downlink container management commands include container installation, container deletion, container configuration, and container control, and must be forwarded to container management for execution. Downlink application management commands include application installation, application deletion, application configuration, and application control, and must be forwarded to application management for execution. Downlink log management commands include log queries and log file retrieval, and must be forwarded to log management for execution.

[0050] The management channel receives alarm information from devices, containers, and applications and sends it to the dispatch master station or local operation and maintenance tools in real time.

[0051] File transfer includes local or remote file transfer functionality, primarily involving the download of application and application configuration files, and the upload of application configuration and log files. File transfer can exist in the form of applications or dynamic libraries.

[0052] The data center is responsible for receiving data collection information from various applications and saving it to the real-time library and database.

[0053] Resource information includes information on resources such as CPU, memory, disk, and processes, as well as limits and thresholds for each resource.

[0054] Log information consists of real-time log messages generated during the runtime of various applications. These log messages are categorized and classified. Applications on both the host machine and containers generate logs and send them to the message bus; simultaneously, each application can analyze these log messages to obtain key log information. Policy information includes policy retrieval information, policy action information, and policy relationship information. Policy retrieval information includes resource information, critical logs, etc. Action information includes restart actions, start actions, stop actions, alarm actions, etc. Policy relationship information is the specific relationship information between policies. Policy collection information is a collection set generated from resource information, critical logs, and other information received by the application.

[0055] The technical solution of this implementation method is further illustrated below with two examples.

[0056] Example 1: 1. Deploy basic applications such as startup management, device management, container management, application management, log management, management channel, data center, and file transfer on the edge gateway, add startup management to the gateway system's auto-start service entry file, and restart the gateway.

[0057] 2. Create a container image, add the application co-controller to the image, and set it as the entry point for the image to run; the gateway loads the container image.

[0058] 3. The simulation master station establishes a connection with the management channel in the gateway and issues a container installation command, with the container name being c_south.

[0059] 4. The management channel forwards the container installation command to the container management system. The container management system receives and executes the container installation command, creates and runs the c_south container, and the applications within the container automatically start and run. Simultaneously, a container management record is generated and written to the corresponding database.

[0060] 5. The simulation master station sends an application installation command to the management channel to install the southbound application m104 into the c_south container.

[0061] 6. The management channel downloads the application file via file transfer and forwards the application installation command to the application manager. The application manager receives and executes the application installation command, installing the m104 application into the container c_south. Simultaneously, an application management record is generated and written to the corresponding database.

[0062] 7. The simulation master station sends the application startup command for m104 in container c_south to the management channel. The management channel forwards the command to the application co-controller in container c_south. The application co-controller executes the application startup operation for m104. Since m104 has not sent configuration information, the default application configuration information is used.

[0063] 8. After the m104 application has been running for a period of time, it sends a log message containing the critical information of "data collection thread deadlock" to the message bus. At the same time, the application co-controller collects the abnormal resource information of the m104 application's thread and sends it to the message bus.

[0064] 9. The application management receives the abnormal log message of the m104 application and the abnormal resource information of the application co-control, generates application policy collection information, matches the application policy retrieval information, and then determines the application policy action information as application restart and alarm based on the application policy relationship information. It sends the m104 application restart command of container c_south to the application co-control, and at the same time sends the m104 application abnormal restart alarm to the message bus.

[0065] 10. When the application co-controller of container c_south receives the application restart command, it restarts the m104 application within its container and generates an application restart log, which is then sent to the message bus.

[0066] 11. When the management channel receives an application alarm message, it proactively sends an alarm message about the abnormal restart of the m104 application in container c_south to the simulation master station.

[0067] 12. Log management receives log messages from the message bus in real time and stores them in the database.

[0068] Example 2: 1. The simulation master station issues a container installation command, and the container name is c_north.

[0069] 2. The management channel forwards the container installation command to the container management system. The container management system receives and executes the container installation command, creates and runs the c_north container, and the application in the container automatically starts and runs. At the same time, a container management record is generated and written to the corresponding database.

[0070] 3. The simulation master station sends an application installation command to the management channel to install the northbound application iec104 into the c_north container.

[0071] 4. The management channel downloads the application file via file transfer and forwards the application installation command to the application manager. The application manager receives and executes the application installation command, installing the iec104 application into the container c_north. Simultaneously, an application management record is generated and written to the corresponding database.

[0072] 5. The simulation master station sends an application configuration command for the iec104 application in container c_north to the management channel. The configuration content includes the application policy retrieval information as CPU resource utilization and a threshold of 80%, the application policy action information as application alarms, and the corresponding application policy relationship information.

[0073] 6. The management channel forwards application configuration commands to the message bus. The application management receives and executes the application configuration commands, and saves the iec104 configuration information to the database.

[0074] 7. The simulation master station sends the iec104 application start command for container c_north to the management channel. The management channel forwards the command to the application co-controller. The application co-controller executes the iec104 application start operation. Since iec104 has already issued configuration information, it uses the issued application configuration information.

[0075] 8. The application co-controller in container c_north monitors the resource usage of applications within the c_north container in real time and sends this information to the message bus. After the iec104 application has been running for a period of time, the application co-controller detects that the CPU usage of the iec104 application is 85% and sends this information to the message bus. Simultaneously, an application alarm log is generated and sent to the message bus.

[0076] 9. When the application management receives abnormal resource information from the application co-control, it generates application policy collection information and matches it with the application policy retrieval information. Then, based on the application policy relationship information, it determines the application policy action information as an application alarm and finally sends the IEC104 application alarm to the message bus. The alarm message content is "IEC104 application CPU usage exceeds limit".

[0077] 10. When the management channel receives an application alarm message, it proactively sends the application alarm message to the simulation master station.

[0078] 11. The log receives log messages from the message bus and stores them in the database.

[0079] 12. The simulation master station sends an application deletion command for the application using iec104 in container c_north to the management channel, and the management channel forwards the application deletion command to the application management.

[0080] 13. The application management receives and executes the application deletion command, deleting the iec104 application from the container c_north, and simultaneously deleting the application management record information for that application.

[0081] 14. The simulation master station sends a container deletion command for container c_north to the management channel, and the management channel forwards the container deletion command to the container management.

[0082] 15. The container management system receives and executes the container deletion command, deleting the container c_north and its container management records, as well as all application information within the container.

[0083] This invention has the following characteristics: Based on the aforementioned issues with existing technologies, this paper proposes a management and monitoring system and method for edge gateway applications. This system effectively manages and maintains edge gateway devices, containers, and applications, unifies the management of edge gateway applications, and improves the management efficiency of edge gateways. It can monitor device, container, and application anomalies in the gateway in real time, quickly detect application anomalies in the host machine or containers, automatically recover from anomalies, and promptly and proactively send alarm information. It is highly reliable and has a fast recovery speed. It supports custom anomaly recovery strategies, as well as main station-side operation and maintenance management and manual intervention, ensuring the normal operation of application software and guaranteeing the stability of the entire edge gateway system.

[0084] Finally, it should be noted that the above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art can still make modifications to the technical solutions described in the foregoing embodiments without creative effort, or make equivalent substitutions for some of the technical features. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A management and monitoring system for edge gateway applications, characterized in that, This includes basic applications, which include application management deployed on the host machine and application co-control deployed in containers; The application co-control includes application control and application resource acquisition; the application control is used to execute application control instructions; the application resource acquisition is used to obtain resource information and log information of the application in the container and send them to the message bus. The application management includes application monitoring and application configuration; the application monitoring is used to obtain resource information and log information of each application on the host machine, and to obtain resource information and log information of the application in the container through the message bus; the application configuration is used to configure application policy information. The application management system matches application policy information capable of handling anomalies based on the abnormal resource information and / or abnormal log information obtained from application monitoring, and sends application control instructions based on the application policy information to control the applications with anomalies.

2. The management and monitoring system for edge gateway applications according to claim 1, characterized in that, The application management also includes application installation and application deletion; The application installation is used to download and install the application onto the target container and save the application management record information; The application deletion is used to delete the application in the container and delete the application's management record information.

3. The management and monitoring system for edge gateway applications according to claim 1, characterized in that, The application co-control starts when the container starts; after the application co-control starts, it starts the applications that need to be started in the container according to the records in the application management.

4. The management and monitoring system for edge gateway applications according to claim 1, characterized in that, The basic application also includes container management deployed on the host machine; the container management includes container installation, container deletion, container configuration, container control, and container monitoring; The container installation is used to create containers and save the container management record information; The container deletion is used to delete the container, including its management records and all application information within the container. The container configuration is used to configure container policy information; The container control is used to execute container control instructions; The container monitoring is used to obtain resource information and log information for each container; The container management system matches container policy information capable of handling anomalies with abnormal resource information and / or abnormal log information obtained from container monitoring, and executes corresponding container control instructions based on the container policy information.

5. The management and monitoring system for edge gateway applications according to claim 2, characterized in that, The basic application also includes device management deployed on the host machine; the device management includes device upgrades, device configuration, device control, and device monitoring; The device upgrade is used to upgrade the applications on the host machine; The device configuration is used to configure device policy information; The device control is used to execute device control commands; The device monitoring is used to obtain resource information and log information for gateway devices, container management, and application management; The device management system matches device policy information capable of handling anomalies with abnormal resource information and / or abnormal log information obtained from device monitoring, and executes corresponding device control commands based on the device policy information.

6. The management and monitoring system for edge gateway applications according to claim 5, characterized in that, The basic applications also include file transfer deployed on the host machine to enable local and remote file transfer functionality.

7. The management and monitoring system for edge gateway applications according to claim 6, characterized in that, The basic application also includes log management deployed on the host machine for receiving and storing logs from various devices, containers, and applications; the log management includes log querying and log retrieval. The log query is used to generate a specified log query response message based on the received log query command, and send it to the sender of the log query command through the message bus; The log recall is used to generate corresponding log files based on the received log recall command.

8. The management and monitoring system for edge gateway applications according to claim 1, characterized in that, The basic applications also include startup management deployed on the host machine; startup management starts automatically when the edge gateway starts, and after startup management starts, it starts the other basic applications.

9. The management and monitoring system for edge gateway applications according to claim 1, characterized in that, The basic application also includes a data center deployed on the host machine; the data center is used to receive data collection information from various applications and save it to a real-time library and a database.

10. The management and monitoring system for edge gateway applications according to any one of claims 1 to 9, characterized in that, The resource information includes CPU, memory, disk, and processes, as well as their corresponding limits and / or thresholds.

Images