Cloud-side collaborative alarm system

Abstract

The invention discloses a cloud side collaborative alarm system. The system comprises a cloud Prometheus, a cloud OpenVPN (Open Virtual Private Network) service and a cloud alarm management component. A cloud Promeheus is connected to a cloud OpenVPN service through a cloud OpenVPN client, and the service is connected with an edge Promeheus through an edge OpenVPN client, so that a safe tunnel network communication link is established between the cloud and the edge. And the cloud OpenVPN terminal registers to the OpenVPN service so as to join in the tunnel network, so that real-time detection of the cloud Prometheus on the edge Prometheus service state and the connectivity of the edge OpenVPN terminal is realized, and a detection result is sent to the alarm management component. And the alarm management component pushes an alarm to the user in time according to the received abnormal information, thereby realizing comprehensive monitoring and abnormal response to the edge monitoring service and the network condition thereof.

Description

Technical Field

[0001] This application relates to the field of computer network technology, specifically to a cloud-edge collaborative alarm system. Background Technology

[0002] Currently, the AI ​​customer flow analysis system deployed in various shopping malls needs to monitor the operating status of its operating system, Kubernetes cluster, and customer flow analysis service in real time. Once a service anomaly is detected, the abnormal business information on the edge side needs to be pushed to the operation and maintenance personnel for handling.

[0003] To achieve this monitoring goal, the conventional approach is to deploy the Prometheus monitoring system in a Kubernetes cluster: the Prometheus on the edge node collects monitoring metrics from multiple Exporters within the cluster, runs preset alarm rules, and then sends the generated edge-side business anomaly information to AlertManager, which ultimately notifies operations and maintenance personnel to repair the fault.

[0004] However, the monitoring system itself is also susceptible to failure. For example, when the public network experiences an outage or the edge Prometheus service malfunctions, the monitoring system cannot function properly, resulting in the inability to generate and send abnormal service information on the edge side. In this situation, operations and maintenance personnel may be unable to ascertain the specific cause of the failure, and may mistakenly believe that no service abnormality exists, thus affecting timely response and problem remediation. Summary of the Invention

[0005] To address the aforementioned issues, this application provides a cloud-edge collaborative alarm system that can simultaneously monitor anomalies in edge-side business systems and faults in the monitoring system itself (including edge Prometheus services and public network communication, etc.). It also provides a mechanism that allows operations and maintenance personnel to accurately identify the cause of a fault when the monitoring system itself fails, thereby avoiding misjudgments or omissions due to monitoring failures.

[0006] The embodiments of this application disclose the following technical solutions:

[0007] A cloud-edge collaborative alarm system includes: a cloud-based Prometheus, a cloud-based OpenVPN service, and a cloud-based alarm management component; the cloud-based Prometheus is connected to the cloud-based OpenVPN service via a cloud-based OpenVPN terminal; the cloud-based OpenVPN service is connected to the edge Prometheus via an edge OpenVPN terminal; and the cloud-based Prometheus establishes a communication connection with the edge Prometheus via a tunnel network.

[0008] The cloud-based Prometheus is used to send a connection request to the cloud-based OpenVPN service via the cloud-based OpenVPN terminal to join the tunnel network.

[0009] The cloud-based OpenVPN service is used to authenticate and register cloud-based OpenVPN terminals and edge OpenVPN terminals that send connection requests to the cloud-based OpenVPN service. After registration is completed, the registered cloud-based OpenVPN terminals and their connected cloud-based Prometheus, as well as the registered edge OpenVPN terminals and their connected edge Prometheus, are all included in the tunnel network.

[0010] The cloud-based Prometheus is also used to detect whether the edge Prometheus service is normal and the connectivity of the edge OpenVPN terminal through the tunnel network, and send the detection results to the cloud-based alarm management component; the detection results include abnormal status information of the edge Prometheus service and / or unconnected status information of the edge OpenVPN terminal.

[0011] The cloud-based alarm management component is used to send alarm information about edge Prometheus service anomalies and / or edge OpenVPN terminal connectivity failures to users.

[0012] In one possible implementation, the cloud-based Prometheus is also used for:

[0013] Obtain the Internet Protocol IP address and port number of each edge Prometheus and the IP address of each edge OpenVPN terminal;

[0014] Add the IP addresses and port numbers of each edge Prometheus instance to the service detection table, and add the IP addresses of each edge OpenVPN endpoint to the network connectivity detection table.

[0015] In one possible implementation, the cloud-based Prometheus is specifically used for:

[0016] Based on the service detection table, detect the service running status of the edge Prometheus corresponding to each address;

[0017] Based on the network connectivity detection table, the connectivity of the edge OpenVPN terminals corresponding to each address is detected periodically;

[0018] The detection results are generated based on the abnormal service status results of edge Prometheus and / or the disconnection status results of edge OpenVPN terminals, and the detection results are sent to the cloud alarm management component.

[0019] In one possible implementation, the cloud-based Prometheus is specifically used for:

[0020] For any edge Prometheus, if the service status of the edge Prometheus is abnormal after m consecutive probes, the service status of the edge Prometheus is recorded as abnormal; m is a positive integer.

[0021] For any edge OpenVPN terminal, if the terminal fails to connect after n consecutive probes, record that the edge OpenVPN terminal has a connectivity failure; n is a positive integer.

[0022] The detection results are generated based on the abnormal service status records of edge Prometheus and / or the connectivity failure records of edge OpenVPN terminals, and the detection results are sent to the cloud alarm management component.

[0023] In one possible implementation, the cloud-based alarm management component is further used for:

[0024] When the edge Prometheus is in normal service status and the edge OpenVPN terminal is in normal connectivity status, receive edge-side service abnormality information sent by the edge Prometheus.

[0025] Send the edge-side service anomaly information to the user.

[0026] In one possible implementation, when the edge Prometheus sends edge-side service anomaly information to the cloud alarm management component, it performs encrypted transmission through the edge OpenVPN terminal; the edge-side service anomaly information includes the edge node identifier, the time of anomaly occurrence, and specific values ​​of service metrics.

[0027] In one possible implementation, the cloud-based alarm management component is further used for:

[0028] When sending the alarm information, duplicate alarms of the same type on the same edge node are deduplicated, and different notification channels are set according to the alarm level.

[0029] In one possible implementation, the cloud-based alarm management component sends alarm information or edge-side service anomaly information to the user via email, SMS, mobile application push, or telephone notification.

[0030] In one possible implementation, the cloud-based OpenVPN service is also used for:

[0031] When the connection between the edge OpenVPN terminal and the cloud OpenVPN service is interrupted and then restored, the cloud OpenVPN service re-verifies the identity of the edge OpenVPN terminal and re-joins it into the tunnel network after successful verification.

[0032] In one possible implementation, the cloud-based alarm management component further includes a user access control module:

[0033] The user permission management module is used to control the access and operation permissions of different users to alarm information.

[0034] Compared with the prior art, this application has the following beneficial effects:

[0035] This application provides a cloud-edge collaborative alarm system designed to improve the reliability of edge monitoring services and the visualization of network connectivity. The system mainly consists of three parts: a cloud-based Prometheus, a cloud-based OpenVPN service, and a cloud-based alarm management component. Specifically, the cloud-based Prometheus establishes a secure connection with the cloud-based OpenVPN service through its own configured cloud-based OpenVPN client. The cloud-based OpenVPN service, in turn, connects to edge Prometheus instances deployed at various shopping malls or edge nodes through edge OpenVPN clients, thus constructing a secure and stable tunnel network to achieve bidirectional communication between the cloud and the edge. The cloud-based OpenVPN terminal actively sends a connection request to the cloud-based OpenVPN service, completes registration after authentication, and successfully joins the tunnel network, simultaneously including the connected cloud-based Prometheus instance in the tunnel network. Similarly, the edge OpenVPN terminal also authenticates with the cloud-based OpenVPN service and joins the network along with the edge Prometheus, placing the cloud and edge Prometheus in a unified virtual private network environment. Based on this, the cloud-based Prometheus can use the tunnel network to detect the real-time operating status of the edge Prometheus and the connectivity of the edge OpenVPN terminal. The cloud-based Prometheus system periodically checks whether the edge Prometheus service is running normally and whether the network connectivity of the edge OpenVPN endpoints is unobstructed. Any abnormal states detected (such as edge Prometheus service malfunctions or OpenVPN endpoint disconnections) are promptly reported to the cloud-based alarm management component. Based on the received status information, the cloud-based alarm management component quickly generates and pushes corresponding alarm notifications to operations and maintenance personnel, achieving comprehensive monitoring of the edge monitoring system and its network environment.

[0036] This application establishes a secure, encrypted OpenVPN-based channel between the cloud server and the mall's internal servers. This allows the cloud-based Prometheus to proactively probe the connectivity (including public network status) of the edge OpenVPN network and the operational status of the edge Prometheus service. When the public network is interrupted or the edge Prometheus malfunctions, the cloud-based Prometheus can directly issue alerts, thus improving data transmission security. Furthermore, the cloud-edge communication enabled by the tunnel network ensures that the cloud can independently obtain status information from the edge monitoring system. This allows users to receive not only edge-side service anomaly information but also, in the event of a failure in the monitoring system itself, clearly identify whether the problem stems from an edge Prometheus service malfunction or a network connectivity issue. This avoids misjudgments or omissions due to monitoring failures, ensuring timely and accurate operational responses. Attached Figure Description

[0037] To more clearly illustrate the technical solutions in this embodiment or the prior art, the drawings used in the description of the embodiment or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0038] Figure 1 A schematic diagram of the structure of a cloud-edge collaborative alarm system provided in an embodiment of this application;

[0039] Figure 2 This is a schematic diagram of another cloud-edge collaborative alarm system provided in an embodiment of this application. Detailed Implementation

[0040] To facilitate understanding of the technical solutions provided in the embodiments of this application, the background technology involved in the embodiments of this application will be described below.

[0041] Currently, the AI-powered customer flow analysis systems deployed in shopping malls require real-time monitoring of their operating systems, Kubernetes clusters, and customer flow analysis services. In the event of anomalies, information about these anomalies should be pushed to operations and maintenance personnel. This is typically achieved by deploying a Prometheus monitoring system within the Kubernetes cluster. This system collects metrics from multiple exporters, executes alert rules, and sends anomaly information to the AlertManager, which then notifies operations and maintenance personnel. However, the monitoring system itself is susceptible to failure. For example, public network outages or Prometheus service malfunctions may prevent the generation and transmission of anomaly information, leaving operations and maintenance personnel unaware of the true nature of the fault and hindering timely handling and repair.

[0042] To address this issue, this application provides a cloud-edge collaborative alarm system. This system includes a cloud-based Prometheus, a cloud-based OpenVPN service, and a cloud-based alarm management component. Each component connects to OpenVPN terminals at the edge via a tunnel network. Both the cloud-based and edge OpenVPN terminals can request to join the tunnel network. The cloud-based OpenVPN service authenticates and registers the cloud and edge OpenVPN terminals that request connection, incorporating them into the tunnel network. Simultaneously, the Prometheus instances connected to each OpenVPN terminal are also included in the tunnel network. The cloud-based Prometheus, using the tunnel network, can detect the service status of the edge Prometheus and the connectivity of the edge OpenVPN terminals. It then sends the detection results, including relevant anomaly information, to the cloud-based alarm management component. Finally, the cloud-based alarm management component conveys alarm information regarding edge Prometheus service anomalies and / or edge OpenVPN terminal connectivity failures to the user. This application establishes a secure encrypted channel between the cloud and the mall server via OpenVPN, enabling the cloud-based Prometheus to proactively monitor the connectivity of the edge OpenVPN network (including public network status) and the operation of the edge Prometheus service. It can directly issue alerts when the public network is interrupted or the edge Prometheus malfunctions, thus improving data transmission security and allowing the cloud to independently obtain the status of the edge monitoring system. This allows users to receive abnormal information about edge services and, when monitoring system failures occur, clearly identify whether the problem is a service or network issue, avoiding misjudgments and ensuring timely and accurate operation and maintenance.

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

[0044] See Figure 1 , Figure 1 This is a structural diagram of a cloud-edge collaborative alarm system provided in an embodiment of this application. Figure 1 Arrows with the same line type represent the same type of functional logic.

[0045] Combination Figure 1The system architecture shown illustrates the operational logic of this cloud-edge collaborative alarm system, which can be explained in detail as follows: The system is deployed based on cloud nodes and edge nodes. Core components include cloud-based Prometheus, an OpenVPN Server serving as the cloud OpenVPN service, and OpenVPN Clients and Prometheus distributed across each node. Regarding network connection construction, a specific node in the cloud (e.g., ...) Figure 1 In the cloud node B), the cloud-based Prometheus connects with another cloud node (such as...) through its integrated cloud-based OpenVPN client (i.e., OpenVPN Client). Figure 1 Communication is established with the OpenVPN Server within the cloud node A, while communication is also established with each edge node (such as...). Figure 1 The edge Prometheus instances in edge nodes a and b) connect to the OpenVPN Server via their respective edge OpenVPN clients. This multi-layered client interconnection model gradually builds a stable tunnel network between the cloud-based Prometheus and each edge Prometheus instance, laying a solid foundation for cross-node data interaction. Meanwhile, the cloud-based alarm management component (though not explicitly shown in the diagram, it logically collaborates with the cloud-based Prometheus) can leverage the edge OpenVPN client links to ensure independent and reliable alarm transmission.

[0046] In actual operation, Prometheus in the cloud, acting as the core monitoring node, initiates a connection request to the OpenVPN Server through its own cloud-based OpenVPN terminal to join the tunnel network. This is a prerequisite for starting cloud-edge collaborative monitoring. The OpenVPN Server is responsible for identity verification and network access control. It authenticates and registers all access requesting nodes (including the nodes where the cloud-based OpenVPN terminal is located and the nodes where the edge OpenVPN terminal is located) according to preset authentication mechanisms (such as certificate and key verification), and includes legitimate nodes in the tunnel network, thus building a security barrier for monitoring data transmission.

[0047] Once the network was ready, Prometheus in the cloud, relying on the tunnel network, conducted two key probes (corresponding to...). Figure 2 (Logic of the "probe" arrow in the middle): On the one hand, such as Figure 1 As shown by the dotted-line arrow, the cloud-based Prometheus performs service status probing (i.e., checks whether the service is normal) on the edge Prometheus nodes a and b, verifying whether their monitoring metrics collection and alarm rule execution are normal; on the other hand, as... Figure 1As shown by the dashed arrows, Prometheus in the cloud performs network connectivity monitoring (i.e., connectivity detection) on the edge OpenVPN terminals at edge nodes a and b. When an anomaly is detected (such as no response from edge Prometheus or an interruption of the OpenVPN Client link), it generates detection results containing service anomalies and connectivity failures, and pushes them to the alarm management component in real time.

[0048] Ultimately, the cloud-based alarm management component integrates anomaly information to accurately identify issues such as "edge Prometheus service anomalies" or "OpenVPN terminal connectivity failures," and sends corresponding alarm notifications to users. Through this architecture and process, the system achieves comprehensive awareness of the edge-side monitoring status, effectively avoiding the problems of hidden edge faults and misjudgments in traditional models, and helping operations and maintenance personnel quickly locate and respond to monitoring faults in cloud-edge collaborative scenarios.

[0049] In one possible implementation, in addition to establishing a communication connection with the edge Prometheus via an OpenVPN tunnel, the cloud-based Prometheus also has the function of dynamically managing and maintaining information about the monitored objects.

[0050] Specifically, the cloud-based Prometheus first obtains the Internet Protocol (IP) addresses and port numbers of each edge Prometheus instance, as well as the IP addresses of the corresponding edge OpenVPN endpoints. This IP address and port information is fundamental for the cloud-based Prometheus to accurately locate and access edge monitoring services and their network interfaces. Subsequently, the cloud-based Prometheus adds the collected IP addresses and port numbers of each edge Prometheus instance to a "Service Probe Table," which stores information on all Prometheus service nodes that need to be monitored and periodically tested. Simultaneously, the IP addresses of each edge OpenVPN endpoint are added to a "Network Connectivity Probe Table" for performing network status checks on the OpenVPN endpoints. By maintaining these two clearly structured and detailed probe tables, the cloud-based Prometheus can systematically manage the health status of edge services and network interfaces, achieving automated and continuous service availability and network connectivity monitoring. Once an anomaly is detected in an edge Prometheus service or an unreachable OpenVPN link, the cloud-based Prometheus can quickly locate the specific IP address and port number corresponding to the node, and promptly report the anomaly information to the cloud-based alarm management component. This ensures comprehensive monitoring coverage and accurate and effective alarm response. This detection mechanism, based on IP address and port number classification management, greatly improves the system's adaptability to the complex and ever-changing conditions of the edge environment and enhances monitoring efficiency, providing solid data support for subsequent fault diagnosis and operational decisions.

[0051] In one possible implementation, cloud-based Prometheus undertakes the core monitoring responsibilities, specifically using two types of probe tables to comprehensively understand the operational status and network connectivity of the edge environment. First, based on a pre-maintained service probe table, cloud-based Prometheus periodically initiates service health checks on the IP addresses and port numbers of each edge Prometheus instance recorded therein. These checks include, but are not limited to, accessing Prometheus's metric interfaces, verifying the normality of its data collection, and confirming key indicators such as service response time and status codes, thereby accurately assessing the real-time operational status of each edge Prometheus service. Second, based on the network connectivity probe table, cloud-based Prometheus periodically performs connectivity tests on the IP addresses of edge OpenVPN terminals, typically using network detection technologies such as Internet Control Message Protocol Ping (ICMP Ping) or Transmission Control Protocol (TCP) port handshakes to confirm whether the OpenVPN tunnel maintains stable communication, ensuring uninterrupted data transmission links between the cloud and the edge.

[0052] After completing the above two aspects of detection, the cloud-based Prometheus will comprehensively analyze the results: if an edge Prometheus service malfunctions (e.g., fails to respond to requests or returns error messages), or if the corresponding edge OpenVPN terminal detects a connection interruption or unreachability, the system will summarize these abnormal states as detection results. These detection results not only include the specific anomaly type and the identification information of the affected nodes, but also reflect the severity of the problem and its potential impact. Subsequently, the cloud-based Prometheus promptly sends this key detection information to the cloud-based alarm management component. Based on the received information, the cloud-based alarm management component further determines the alarm level and push strategy, ensuring that operations and maintenance personnel can receive accurate and detailed alarm notifications as soon as possible, achieving efficient operation and maintenance management and rapid fault response for edge monitoring services and the network environment.

[0053] Through this multi-dimensional, timed detection mechanism, Prometheus in the cloud can not only perceive the operational health of the distributed edge system in real time, but also effectively distinguish between service-level problems and network-level faults, providing a solid and reliable monitoring guarantee for the entire cloud-edge collaboration system and greatly improving the system's stability and operational efficiency.

[0054] In one possible implementation, cloud-based Prometheus accurately determines the service and network status of edge nodes through a rigorous and fault-tolerant continuous probing mechanism. Specifically, for any edge Prometheus instance, cloud-based Prometheus performs periodic probes to check if its service is functioning correctly. If the edge Prometheus fails to respond normally in m consecutive probes (e.g., 5) (i.e., all m probes show service anomalies), the system determines that the edge Prometheus service does indeed have an anomaly and records this anomaly. Here, the parameter m is a positive integer, and its setting can be adjusted according to actual business needs, preventing false alarms due to occasional probe failures while ensuring timely fault detection. Similarly, for any edge OpenVPN terminal, cloud-based Prometheus employs a similar strategy for connectivity testing. If the OpenVPN terminal shows no connectivity in n consecutive probes (e.g., 5), meaning that neither ICMP Ping nor TCP handshake tests succeed, the terminal is determined to have a network connectivity failure, and this is recorded. The parameter n is also a positive integer, used to control the sensitivity and stability of the detection.

[0055] Based on the continuous probing status records, the cloud-based Prometheus system integrates the records of edge Prometheus service anomalies and edge OpenVPN terminal connectivity failures to generate a comprehensive probing report. This report accurately reflects the health status of edge monitoring nodes and their network links, effectively filtering out occasional, transient anomalies and improving the accuracy and reliability of alarms. Subsequently, these probing results are promptly sent to the cloud-based alarm management component for further analysis and processing, ensuring that operations personnel receive accurate, clear, and uninterrupted alarm information to quickly locate and resolve potential problems. By introducing a continuous multi-anomaly confirmation mechanism, the entire cloud-edge collaborative alarm system avoids misjudgments caused by single anomaly probes, improving system stability and operational efficiency, and providing robust technical support for monitoring and management in large-scale distributed environments.

[0056] In one possible implementation, the cloud-based alarm management component not only handles service anomaly and network failure alarms reported by the cloud-based Prometheus, but also intelligently distinguishes different states of the edge system, thereby achieving more accurate and effective alarm management. Specifically, when the cloud-based Prometheus detects that an edge Prometheus service is operating normally, and the corresponding edge OpenVPN terminal network connectivity remains stable, the cloud-based alarm management component will continue to receive business-level anomaly information reported by that edge Prometheus. For example, the edge Prometheus may detect abnormal passenger flow statistics, abnormal device data collection, or other issues directly related to the business. This information indicates that although the monitoring system and communication links are operating normally, actual business operations have experienced anomalies. In this case, the cloud-based alarm management component will aggregate and process this edge-side business anomaly information and promptly push it to operations and maintenance personnel or relevant users.

[0057] This design effectively avoids misjudgments caused by monitoring service malfunctions or network issues, ensuring that real business anomaly information is only transmitted to users when both the monitoring system and the network links are healthy, thereby improving the accuracy and reliability of alarm information.

[0058] In one possible implementation, when edge Prometheus sends edge-side service anomaly information to the cloud alarm management component, it uses an edge OpenVPN terminal to encrypt the data during transmission, ensuring the security and integrity of the information in the cloud-edge network. Specifically, the service anomaly data collected by edge Prometheus is first sent through a secure tunnel established by the local OpenVPN client. This effectively prevents the data from being stolen, tampered with, or lost during transmission, thereby protecting sensitive business metrics and node information from being leaked.

[0059] The transmitted edge-side service anomaly information includes edge node identifiers, anomaly occurrence times, and specific service metric values. The unique identifier of the edge node identifies the source of the anomaly; the specific timestamp of the anomaly helps to accurately pinpoint the time window in which the problem occurred; and the detailed service metric values ​​reflect the specific manifestations and severity of the anomaly, providing strong data support for subsequent fault analysis and incident response.

[0060] Through this encrypted transmission mechanism, the system not only enhances the security of data transmission, but also ensures the accurate and timely delivery of abnormal information. This enables the cloud alarm management component to obtain comprehensive and reliable business anomaly information as soon as possible, thereby accurately triggering alarm policies and improving the reliability and security of the overall cloud-edge collaborative monitoring system.

[0061] In one possible implementation, the cloud-based alarm management component not only receives and sends various alarm information generated by edge nodes, but also possesses intelligent alarm optimization and processing capabilities. Specifically, when the cloud-based alarm management component is about to send an alarm to a user, it first performs deduplication on similar alarms generated by the same edge node. This avoids duplicate alarms causing maintenance personnel to receive a large amount of redundant information, thereby reducing their workload and improving the efficiency and accuracy of alarm response. The deduplication mechanism typically judges based on multiple dimensions such as alarm content, occurrence time window, and alarm type, ensuring that within a certain period, only one or a limited number of alarm notifications are triggered for the same issue, preventing alarm storms.

[0062] In one possible implementation, such as Figure 2 As shown, the cloud-based alarm management component possesses multi-channel and multi-format notification capabilities to ensure that alarm information and edge-side business anomaly information are delivered to users in a timely and accurate manner. Specifically, the cloud-based alarm management component can send detailed alarm reports via email, allowing users to view complete anomaly content and related data; simultaneously, SMS notifications, as a fast and universally supported communication method, can immediately alert operations and maintenance personnel to system anomalies; furthermore, mobile application push notifications utilize the instant messaging function of smartphones to achieve efficient and convenient real-time reminders, enhancing users' response speed and operational flexibility to alarms; for extremely urgent or important alarms, the cloud-based alarm management component also supports direct telephone notifications to relevant personnel to ensure that critical issues are not overlooked.

[0063] Through the aforementioned diverse notification methods, the system not only improves the coverage and reach of alarm information, but also meets the preferences and needs of different users, ultimately achieving efficient operation and maintenance support and rapid fault handling capabilities for the cloud-edge collaborative alarm system.

[0064] In one possible implementation, the cloud-based OpenVPN service possesses dynamic management capabilities for the connection status of edge OpenVPN endpoints. When the connection between an edge OpenVPN endpoint and the cloud-based OpenVPN service is interrupted due to network fluctuations or other failures, the cloud-based OpenVPN service immediately initiates a re-authentication process once the connection is restored. This ensures that the node reconnecting to the tunnel network has a legitimate and trusted identity. Through a strict authentication mechanism, unauthorized device access is effectively prevented, ensuring the security of the entire virtual private network. After successful authentication, the cloud-based OpenVPN service will re-add the edge OpenVPN endpoint to the secure tunnel network according to established rules, enabling it to continue participating in the transmission and interaction of cloud-edge collaborative monitoring data. This not only ensures service continuity and timely restoration of the monitoring link but also provides a solid guarantee for the monitoring system to quickly respond to network changes and maintain stable business operations. Through this mechanism, the cloud-based OpenVPN service achieves full-lifecycle management of the connection status of edge nodes, improving the overall robustness and reliability of the cloud-edge collaborative alarm system.

[0065] In one possible implementation, the cloud-based alarm management component also includes a user access control module. This module aims to provide granular access control for different users within the system. Specifically, the user access control module is responsible for defining and managing the access and operation permissions of various user groups, ensuring that users can only view, receive, or process alarm information within their authorized scope. For example, operations engineers may have comprehensive alarm viewing and processing permissions, while ordinary business personnel may be limited to receiving alarms related to specific business anomalies. Furthermore, administrators at different levels may have different configuration permissions, such as modifying alarm rules and adjusting notification policies. Through this module, the system can effectively prevent unauthorized users from accessing sensitive monitoring data and alarm content, ensuring data security and privacy, while improving the standardization and flexibility of management. Overall, this module provides robust security and access control capabilities for the cloud-based alarm management component, promoting the secure, stable, and efficient operation of the cloud-edge collaborative alarm system.

[0066] The foregoing has provided a detailed description of a cloud-edge collaborative alarm system provided in this application. The various embodiments in the specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to in the method section. It should be noted that those skilled in the art can make several improvements and modifications to this application without departing from the principles of this application, and these improvements and modifications also fall within the protection scope of the claims of this application.

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

[0068] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A cloud-edge collaborative alarm system, characterized in that, The system includes: a cloud-based Prometheus, a cloud-based OpenVPN service, and a cloud-based alarm management component; the cloud-based Prometheus is connected to the cloud-based OpenVPN service via a cloud-based OpenVPN terminal; the cloud-based OpenVPN service is connected to the edge Prometheus via an edge OpenVPN terminal; and the cloud-based Prometheus establishes a communication connection with the edge Prometheus via a tunnel network. The cloud-based Prometheus is used to send a connection request to the cloud-based OpenVPN service via the cloud-based OpenVPN terminal to join the tunnel network. The cloud-based OpenVPN service is used to authenticate and register cloud-based OpenVPN terminals and edge OpenVPN terminals that send connection requests to the cloud-based OpenVPN service. After registration is completed, the registered cloud-based OpenVPN terminals and their connected cloud-based Prometheus, as well as the registered edge OpenVPN terminals and their connected edge Prometheus, are all included in the tunnel network. The cloud-based Prometheus is also used to detect whether the edge Prometheus service is normal and the connectivity of the edge OpenVPN terminal through the tunnel network, and send the detection results to the cloud-based alarm management component; the detection results include abnormal status information of the edge Prometheus service and / or unconnected status information of the edge OpenVPN terminal. The cloud-based alarm management component is used to send alarm information about edge Prometheus service anomalies and / or edge OpenVPN terminal connectivity failures to users.

2. The system according to claim 1, characterized in that, The cloud-based Prometheus is also used for: Obtain the Internet Protocol IP address and port number of each edge Prometheus and the IP address of each edge OpenVPN terminal; Add the IP addresses and port numbers of each edge Prometheus instance to the service detection table, and add the IP addresses of each edge OpenVPN endpoint to the network connectivity detection table.

3. The system according to claim 2, characterized in that, The cloud-based Prometheus is specifically used for: Based on the service detection table, detect the service running status of the edge Prometheus corresponding to each address; Based on the network connectivity detection table, the connectivity of the edge OpenVPN terminals corresponding to each address is detected periodically; The detection results are generated based on the abnormal service status results of edge Prometheus and / or the disconnection status results of edge OpenVPN terminals, and the detection results are sent to the cloud alarm management component.

4. The system according to claim 3, characterized in that, The cloud-based Prometheus is specifically used for: For any edge Prometheus, if the service status of the edge Prometheus is abnormal after m consecutive probes, the service status of the edge Prometheus is recorded as abnormal; m is a positive integer. For any edge OpenVPN terminal, if the terminal fails to connect after n consecutive probes, record that the edge OpenVPN terminal has a connectivity failure; n is a positive integer. The detection results are generated based on the abnormal service status records of edge Prometheus and / or the connectivity failure records of edge OpenVPN terminals, and the detection results are sent to the cloud alarm management component.

5. The system according to claim 1, characterized in that, The cloud-based alarm management component is also used for: When the edge Prometheus is in normal service status and the edge OpenVPN terminal is in normal connectivity status, receive edge-side service abnormality information sent by the edge Prometheus. Send the edge-side service anomaly information to the user.

6. The system according to claim 5, characterized in that, When the edge Prometheus sends edge-side service anomaly information to the cloud alarm management component, it performs encrypted transmission through the edge OpenVPN terminal; the edge-side service anomaly information includes the edge node identifier, the time of anomaly occurrence, and the specific values ​​of service indicators.

7. The system according to claim 1, characterized in that, The cloud-based alarm management component is also used for: When sending the alarm information, duplicate alarms of the same type on the same edge node are deduplicated, and different notification channels are set according to the alarm level.

8. The system according to claim 1, characterized in that, The cloud-based alarm management component sends alarm information or edge-side service anomaly information to users via email, SMS, mobile application push, or telephone notification.

9. The system according to claim 1, characterized in that, The cloud-based OpenVPN service is also used for: When the connection between the edge OpenVPN terminal and the cloud OpenVPN service is interrupted and then restored, the cloud OpenVPN service re-verifies the identity of the edge OpenVPN terminal and re-joins it into the tunnel network after successful verification.

10. The system according to claim 1, characterized in that, The cloud-based alarm management component also includes a user access control module: The user permission management module is used to control the access and operation permissions of different users to alarm information.

Images