Cloud native alarm system and method, electronic equipment and storage medium

Abstract

The invention provides a cloud native alarm system and method, electronic equipment and a storage medium, and relates to the technical field of cloud computing. The system comprises: an anomaly monitoring module monitors anomaly information including an abnormal K8S event and / or abnormal index data in a K8S cluster environment, and sends the anomaly information to a root cause analysis module; the root cause analysis module calls a resource cache module to obtain target resource information according to the abnormal information; determining a root cause based on a preset analysis strategy, the abnormal information and the target resource information; according to the abnormal information, the target resource information and the root cause, alarm content is generated, and the alarm content is sent to an alarm triggering module; and the alarm triggering module generates target alarm information according to the alarm content, and forwards the target alarm information, so that problem positioning, root cause analysis and real-time alarm are quickly and accurately performed on abnormal information, and the troubleshooting cost in the cloud native operation and maintenance process is effectively reduced.

Description

Technical Field

[0001] The present application relates to the field of cloud computing technology, and in particular to a cloud-native alarm system, method, electronic device and storage medium. Background Art

[0002] With the development of cloud-native technology, more and more applications are built and deployed in a cloud-native way. The call chain between applications is complicated, and each application relies on many external middlewares. Any failure may cause cascading failures. Therefore, timely alarms have become an indispensable part of the cloud-native environment when failures occur.

[0003] Currently, in a cloud-native environment, after applications are deployed in containers in a K8S cluster, traditional alarm systems cannot quickly and accurately locate problems and analyze root causes in some specific scenarios. Therefore, an effective solution for cloud-native alarms is urgently needed. Summary of the invention

[0004] The present application provides a cloud-native alarm system, method, electronic device and storage medium to solve the problem that traditional alarm systems cannot quickly and accurately locate problems and analyze root causes in some specific scenarios, and provides an effective solution for cloud-native alarms.

[0005] In a first aspect, the present application provides a cloud native alarm system, including: an anomaly monitoring module, a resource caching module, a root cause analysis module, and an alarm triggering module;

[0006] The abnormality monitoring module is used to monitor the abnormal information in the K8S cluster environment and send the abnormal information to the root cause analysis module. The abnormal information includes abnormal K8S events and / or abnormal indicator data;

[0007] The root cause analysis module is used to call the resource cache module to obtain the target resource information corresponding to the abnormal information according to the abnormal information; determine the root cause corresponding to the abnormal information based on the preset analysis strategy, abnormal information and target resource information; generate alarm content according to the abnormal information, target resource information and root cause, and send the alarm content to the alarm trigger module;

[0008] The alarm trigger module is used to generate target alarm information according to the alarm content and forward the target alarm information.

[0009] In a second aspect, the present application provides a cloud native alarm method, which is applied to the cloud native alarm system as described in the first aspect of the present application. The cloud native alarm method includes:

[0010] The anomaly monitoring module monitors the anomaly information in the K8S cluster environment and sends the anomaly information to the root cause analysis module. The anomaly information includes abnormal K8S events and abnormal indicator data.

[0011] The root cause analysis module calls the resource cache module to obtain the target resource information corresponding to the abnormal information based on the abnormal information; determines the root cause corresponding to the abnormal information based on the preset analysis strategy, abnormal information and target resource information; generates alarm content based on the abnormal information, target resource information and root cause, and sends the alarm content to the alarm trigger module;

[0012] The alarm trigger module generates target alarm information according to the alarm content and forwards the target alarm information.

[0013] In a third aspect, the present application provides an electronic device, comprising: a processor, and a memory communicatively connected to the processor;

[0014] Memory stores computer-executable instructions;

[0015] The processor executes the computer-executable instructions stored in the memory to implement the above second aspect and / or various possible implementations of the second aspect.

[0016] In a fourth aspect, the present application provides a computer-readable storage medium, in which computer program instructions are stored. When the computer program instructions are executed, the above second aspect and / or various possible implementations of the second aspect are implemented.

[0017] In a fifth aspect, the present application provides a computer program product, including a computer program, which implements the above second aspect and / or various possible implementation methods of the second aspect when the computer program is executed.

[0018] The cloud-native alarm system, method, electronic device and storage medium provided by the present application, the cloud-native alarm system includes an anomaly monitoring module, a resource caching module, a root cause analysis module and an alarm triggering module; the anomaly monitoring module monitors the anomaly information in the K8S cluster environment, and sends the anomaly information to the root cause analysis module, the anomaly information includes an abnormal K8S event and abnormal indicator data; the root cause analysis module calls the resource caching module to obtain the target resource information corresponding to the anomaly information based on the anomaly information, and determines the root cause corresponding to the anomaly information based on the preset analysis strategy, the anomaly information and the target resource information, generates an alarm content according to the anomaly information, the target resource information and the root cause, and sends the alarm content to the alarm triggering module; the alarm triggering module generates the target alarm information according to the alarm content, and forwards the target alarm information, so as to realize the problem location and root cause analysis of the abnormal K8S events and abnormal indicator data quickly and accurately in the cloud-native environment, and perform real-time alarm, which can greatly reduce the troubleshooting cost in the cloud-native operation and maintenance process, and effectively improve the problem solving efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0020] Figure 1 A schematic diagram of a cloud native alarm system provided in one embodiment of the present application;

[0021] Figure 2 A schematic diagram of a cloud native alarm system provided in another embodiment of the present application;

[0022] Figure 3 A schematic diagram of the cloud-native NAS mounting principle provided in one embodiment of the present application;

[0023] Figure 4 Schematic diagram of the process of the cloud native alarm method provided in the embodiment of the present application Figure 1 ;

[0024] Figure 5 Schematic diagram of the process of the cloud native alarm method provided in the embodiment of the present application Figure 2 ;

[0025] Figure 6 Schematic diagram of the process of the cloud native alarm method provided in the embodiment of the present application Figure 3 ;

[0026] Figure 7 Schematic diagram of the process of the cloud native alarm method provided in the embodiment of the present application Figure 4 ;

[0027] Figure 8 A schematic diagram of the structure of an electronic device provided in one embodiment of the present application.

[0028] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0029] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0030] First, the terms involved in this application are explained:

[0031] Containers are an application container engine that allows developers to package applications and their dependent software into a portable container in a unified way. They can be lightweight virtualized and support seamless deployment across environments.

[0032] K8S, short for Kubernetes, is an open source software cluster used for large-scale deployment and management of containers. It has the capabilities of resource scheduling, application deployment and management, automatic repair, service discovery and load balancing, and elastic scaling, becoming the standard for container orchestration.

[0033] The container cloud platform is an enterprise-level cloud platform for managing multiple K8S clusters.

[0034] Network Attached Storage (NAS) is a dedicated data storage server that completely separates storage devices from servers and manages data in a centralized manner.

[0035] Prometheus is an open source system monitoring and alarm framework that can monitor the status of applications and systems by collecting and storing time series data. It also has powerful query languages ​​and visualization tools that can quickly diagnose and solve problems.

[0036] A distributed key-value storage system (ETCD) is a distributed key-value storage system developed based on the Raft protocol. It is used for service discovery, shared configuration, and consistency assurance. It is a component in Kubernetes.

[0037] The front-end interface (APIServer) of the Kubernetes cluster is the Application Programming Interface (API) of Kubernetes, which enables users to interact with the Kubernetes cluster through the API to manage the resources in the Kubernetes cluster.

[0038] Prometheus query language is a query language used to query and analyze time series data in Prometheus components. It allows users to select and aggregate time series data based on conditions such as identifiers, labels, and functions, and supports operations similar to Structured Query Language (SQL), such as selection, filtering, aggregation, and sorting.

[0039] K8S event is a resource object in the K8S system, which records the action performed by a component at a certain time and is used to track and display changes in the status of resources within the cluster.

[0040] The NotReady event is triggered when the node is unavailable due to resource shortage, network problems, or storage problems.

[0041] Pod creation failed (PodFailedCreate). When Pod creation fails, this event is generated to indicate the possible cause of the creation failure.

[0042] Namespace is a mechanism for dividing cluster resources into multiple independent areas. These areas are called namespaces. Resources in each namespace are visible only within the same namespace.

[0043] A workload is a resource object in Kubernetes and a collection of container instance replicas.

[0044] Namespace quota is a method used to limit and control resource usage in a specific namespace in a K8S cluster. Namespace quota can limit the number of objects such as Pods and workloads in a namespace, as well as the total amount of computing resources and storage resources used by these objects. Computing resources include central processing units (CPU) and memory.

[0045] A Pod is a collection of container instances and their dependent storage and configuration.

[0046] An inode is a data structure used to store file metadata in a file system of a UNIX-like operating system.

[0047] Under the trend of cloud-native infrastructure, with the extreme optimization of resource management, traditional cloud platforms are gradually transforming into container cloud platforms. However, in the cloud-native environment, after the application is deployed in the K8S cluster in a containerized manner, it brings challenges to daily operation and maintenance. For some specific scenarios, the traditional alarm system cannot quickly and accurately locate the problem and analyze the root cause. The relevant scenarios include: (1) After the node in the K8S cluster crashes, the application Pod affected cannot be located in real time, resulting in the inability to timely handle the problem and identify risks; (2) During the application release process, the namespace quota is insufficient and it is impossible to locate it in real time, resulting in unnecessary troubleshooting costs, which in turn affects the normal application pipeline release; (3) Since the mounting method of cloud-native NAS is different from the traditional cloud method, the capacity problem of cloud-native NAS cannot be detected and discovered in real time, which may cause the unavailability of application services and affect daily transactions. The traditional alarm system can no longer meet the existing needs. In order to achieve problem location and root cause analysis in the cloud-native environment, an effective solution for cloud-native alarm is urgently needed, that is, it is urgent to build cloud-native custom alarms based on K8S characteristics in a multi-cluster environment to assist the smooth operation of daily applications.

[0048] Based on the above problems, the present application provides a cloud native alarm system, method, electronic device and storage medium. Based on Prometheus components and K8S native events, a cloud native custom alarm system is constructed, which includes an anomaly monitoring module, a resource caching module, a root cause analysis module and an alarm triggering module. The system can realize real-time positioning of the application impact range after node downtime, real-time and accurate locking of application namespace quota problems, and real-time alarm of cloud native NAS capacity in the workload dimension, which can greatly reduce the troubleshooting cost in the cloud native operation and maintenance process.

[0049] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0050] Figure 1 A schematic diagram of a cloud native alarm system provided in one embodiment of the present application. Figure 1 As shown, the cloud native alarm system 100 of the embodiment of the present application includes an abnormality monitoring module 101, a resource cache module 102, a root cause analysis module 103 and an alarm triggering module 104. Among them:

[0051] The abnormality monitoring module 101 is used to monitor abnormal information in the K8S cluster environment and send the abnormal information to the root cause analysis module 103. The abnormal information includes abnormal K8S events and / or abnormal indicator data.

[0052] The root cause analysis module 103 is used to call the resource cache module 102 to obtain the target resource information corresponding to the exception information according to the exception information; determine the root cause corresponding to the exception information based on the preset analysis strategy, exception information and target resource information; generate alarm content according to the exception information, target resource information and root cause, and send the alarm content to the alarm trigger module 104.

[0053] The alarm triggering module 104 is used to generate target alarm information according to the alarm content and forward the target alarm information.

[0054] In an embodiment of the present application, the cloud native alarm system 100 is composed of an anomaly monitoring module 101, a resource caching module 102, a root cause analysis module 103 and an alarm triggering module 104, which is automatically deployed on multiple K8S clusters to realize real-time status monitoring and alarm generation of the K8S cluster.

[0055] Specifically, the abnormal monitoring module 101 monitors the abnormal information in the K8S cluster environment in real time, and sends the abnormal information to the root cause analysis module 103, where the abnormal information includes abnormal K8S events and / or abnormal indicator data. Optionally, both abnormal K8S events and abnormal indicator data are configurable. Exemplarily, according to different cloud native failure scenarios, abnormal K8S events and abnormal indicator data corresponding to cloud native failure scenarios can be pre-configured on demand. Among them, cloud native failure scenarios include, for example, node downtime scenarios, insufficient namespace quota scenarios, and cloud native NAS capacity abnormality scenarios. For node downtime scenarios, for example, the abnormal K8S event can be pre-configured as a node not ready event; for namespace quota insufficient scenarios, for example, the abnormal K8S event can be pre-configured as a Pod creation failure event; for cloud native NAS capacity abnormality scenarios, for example, the abnormal indicator data can be pre-configured as abnormal NAS file system usage, abnormal NAS file system inode usage, and the NAS file system status is read-only. For configured abnormal K8S events, the abnormal monitoring module 101 can automatically turn on the monitoring mode to capture new or updated abnormal K8S events. For abnormal K8S events that occur repeatedly within a preset time, it can also converge and merge events of the same type. Abnormal indicator data can also be called abnormal Prometheus indicator data, and the abnormal indicator data can be determined based on the Prometheus component. Specifically, for the configured abnormal indicator data, the indicator query group corresponding to each abnormal indicator data can be configured based on the configured abnormal indicator data. Each indicator query group is configured with different indicator query statements, query frequencies and alarm thresholds to realize the query of the Prometheus component server-side indicator data in the same K8S cluster, and capture abnormal indicator data (such as host-level NAS capacity abnormal data) in real time.

[0056] The resource cache module 102 can obtain K8S object information in real time without intrusion, that is, obtain resource details in the K8S cluster environment. Users can customize the K8S resource types that need to be cached; support various conditional queries, including but not limited to obtaining all Pod information on a specified node, obtaining specified Pod information according to the Pod identifier (ID) (such as Pod name, namespace, workload, etc.); the front-end interface APIServer of the K8S cluster can be called to refresh the resource cache in real time to ensure the consistency of the cached resources and the ETCD database, and avoid frequent access to ETCD to a great extent.

[0057] The root cause analysis module 103 is the decision maker of cloud native alarm triggering. Users can customize analysis strategies according to their needs, obtain abnormal K8S events and abnormal indicator data monitored by the entire system, and use the resource cache module 102 to obtain resource information in the current K8S cluster environment to assist in the root cause analysis of specific problem scenarios, and finally call the alarm trigger module 104 to achieve alarm aggregation and notification. The root cause analysis module 103 can also automatically match the disposal strategy for specific problem scenarios based on the environmental information provided by the resource cache module 102, and provide the disposal suggestions to the alarm trigger module 104 to assist the business party in closed-loop processing of alarms. In an embodiment of the present application, after receiving the abnormal information sent by the abnormal monitoring module 101, the root cause analysis module 103 can call the resource cache module 102 according to the abnormal information to obtain the target resource information corresponding to the abnormal information, such as the detailed information of the Pod that triggered the abnormal information. The root cause analysis module 103 determines the root cause corresponding to the abnormal information based on the abnormal information and the target resource information using a preset analysis strategy, thereby generating alarm content based on the abnormal information, the target resource information and the root cause, and sending the alarm content to the alarm triggering module 104.

[0058] After receiving the alarm content sent by the root cause analysis module 103, the alarm trigger module 104 can generate target alarm information in real time according to the alarm content and in a preset format, and forward the target alarm information, such as by email or SMS notification. The alarm trigger module 104 can also configure the blacklist and whitelist strategy corresponding to the alarm, set the alarm forwarding frequency, and set the alarm current limiting strategy, etc., to achieve diversification and personalization of the alarm function.

[0059] The cloud-native alarm system provided in the embodiment of the present application includes an abnormality monitoring module, a resource caching module, a root cause analysis module and an alarm triggering module; the abnormality monitoring module monitors the abnormal information in the K8S cluster environment, and sends the abnormal information to the root cause analysis module, the abnormal information including abnormal K8S events and abnormal indicator data; the root cause analysis module calls the resource caching module to obtain the target resource information corresponding to the abnormal information based on the abnormal information, and determines the root cause corresponding to the abnormal information based on the preset analysis strategy, abnormal information and target resource information, generates alarm content according to the abnormal information, and sends the alarm content to the alarm triggering module; the alarm triggering module generates target alarm information according to the alarm content, and forwards the target alarm information, so as to realize fast and accurate problem location and root cause analysis of abnormal K8S events and abnormal indicator data in the cloud-native environment, and perform real-time alarm, which can greatly reduce the troubleshooting cost in the cloud-native operation and maintenance process and effectively improve the problem solving efficiency.

[0060] Figure 2 Schematic diagram of a cloud native alarm system provided by another embodiment of the present application. Based on the above embodiment, the present application embodiment further describes the cloud native alarm system 100. Figure 2 As shown, in the cloud native alarm system 100 of the embodiment of the present application, the abnormal monitoring module includes an event monitoring submodule 1011 and a Pro docking submodule 1012; the event monitoring submodule 1011 is used to monitor abnormal K8S events in the K8S cluster environment, and the abnormal K8S events that need to be monitored can be configured; the Pro docking submodule 1012 is used to monitor the abnormal indicator data in the K8S cluster environment based on the Prometheus component, and can provide the query capability of the Pro indicator data. Specifically, the event monitoring submodule 1011 can support users to customize the abnormal K8S event types that need to be monitored, and automatically turn on the monitoring mode to capture the newly added or updated abnormal K8S events in the K8S cluster environment. For abnormal K8S events that occur repeatedly within a preset time, the convergence and merging of the same type of events can also be performed. The Pro docking submodule 1012 can realize the query of the Prometheus component server-side indicator data in the same cluster. Users can set different groups and set different Pro query statements, query frequencies and alarm thresholds based on the groups. In addition, at the health check level, the Prometheus docking submodule 1012 will regularly monitor the accessibility of the Prometheus component server. If an abnormality occurs, the alarm trigger module 104 will be called immediately for notification. Figure 2The alarm trigger module 104 in may include an alarm generation submodule 1041, an alarm forwarding submodule 1042 and an alarm configuration submodule 1043; wherein the alarm generation submodule 1041 is used to generate target alarm information in real time according to a preset format based on the alarm content sent by the root cause analysis module 103; the alarm forwarding submodule 1042 is used to forward the target alarm information, and the forwarding method includes, for example, email or SMS notification. The alarm configuration submodule 1043 can configure the black and white list strategy corresponding to the alarm, set the alarm forwarding frequency, and set the alarm current limiting strategy, etc. It can also customize the alarm root cause analysis strategy, and combine abnormal K8S events, abnormal indicator data and K8S resource data to further expand the types of cloud native custom alarms, so as to realize the diversification and personalization of the alarm function; the relevant description of the resource cache module 102 can refer to the above embodiment. Figure 2 It also shows the interaction relationship between each module in the cloud native alarm system 100 and the Prometheus component in the K8S cluster and the front-end interface (APIServer) of the K8S cluster.

[0061] The cloud native alarm system provided by the embodiment of the present application includes an event monitoring submodule, a Pro docking submodule, a resource caching module, a root cause analysis module and an alarm triggering module; the event monitoring submodule monitors abnormal K8S events in the K8S cluster environment, and the Pro docking submodule monitors abnormal indicator data in the K8S cluster environment; the root cause analysis module calls the resource caching module to obtain the target resource information corresponding to the abnormal information based on the abnormal information, the abnormal information including abnormal K8S events and / or abnormal indicator data, and determines the root cause corresponding to the abnormal information based on the preset analysis strategy, abnormal information and target resource information, generates alarm content according to the abnormal information, the target resource information and the root cause, and sends the alarm content to the alarm triggering module; the alarm triggering module generates target alarm information according to the alarm content, and forwards the target alarm information, so as to realize fast and accurate problem location and root cause analysis of abnormal K8S events and abnormal indicator data in the cloud native environment, and perform real-time alarm, which can greatly reduce the troubleshooting cost in the cloud native operation and maintenance process and effectively improve the problem solving efficiency.

[0062] On the basis of the above embodiments, taking into account the node downtime scenario in the cloud native environment, optionally, the abnormal K8S event is a node not ready event. When the root cause analysis module 103 is used to call the resource cache module 102 to obtain the target resource information corresponding to the abnormal information according to the abnormal information, it can be specifically used for: determining the target node that triggers the node not ready event according to the node not ready event; according to the target node, calling the resource cache module 102 to obtain the target resource information corresponding to the node not ready event, and the target resource information is the business Pod information on the target node.

[0063] Exemplarily, the K8S event type to be monitored can be pre-configured as a node not ready event. When a node not ready event occurs, it means that the node's regular health check has failed and the node's function is limited. At this time, the business Pod will not be expelled immediately, but the business Pod will be terminated after a preset fixed time, and then the business Pod will be rebuilt. The root cause analysis module 103 can determine the target node that triggers the node not ready event based on the node not ready event, and obtain all business Pod information on the target node from the resource cache module 102 based on the target node. Thus, the root cause analysis module 103 can obtain all application project information of the downtime node and complete deduplication based on the business Pod information on the target node, clarify the business impact scope of this downtime, and finally implement alarm reporting through the alarm trigger module 104. For the specific processing flow, please refer to the subsequent embodiments.

[0064] On the basis of the above embodiments, taking into account the scenario of insufficient namespace quota in a cloud-native environment, optionally, the abnormal K8S event is a Pod creation failure event. When the root cause analysis module 103 is used to call the resource cache module 102 to obtain the target resource information corresponding to the abnormal information based on the abnormal information, it can be specifically used to: determine the first target Pod that triggers the Pod creation failure event based on the Pod creation failure event; based on the first target Pod, call the resource cache module 102 to obtain the target resource information corresponding to the Pod creation failure event, and the target resource information is the detailed information of the first target Pod.

[0065] Exemplarily, the K8S event type to be monitored can be pre-configured as a Pod creation failure event. The root cause analysis module 103 can determine the first target Pod that triggers the Pod creation failure event based on the Pod creation failure event, and obtain detailed information of the first target Pod from the resource cache module 102 based on the first target Pod. The detailed information of the first target Pod includes, for example, the workload and namespace to which the first target Pod belongs. Thus, the root cause analysis module 103 can determine that the reason for the failure of this Pod creation is insufficient namespace quota, and clarify the specific resource type and current value of the insufficient namespace quota. The specific resource types include, for example, CPU, memory, and number of Pods; at the same time, aggregate Pods with the same problem within a recent period of time into the workload dimension to avoid repeated alarms; finally, the alarm is reported through the alarm trigger module 104. For the specific processing flow, please refer to the subsequent embodiments.

[0066] On the basis of the above embodiments, taking into account the cloud-native NAS capacity abnormality scenario, optionally, the abnormal indicator data includes abnormal NAS file system usage, abnormal NAS file system inode usage and the NAS file system status is read-only, and the root cause analysis module 103 is used to call the resource cache module 102 to obtain the target resource information corresponding to the abnormal information according to the abnormal information. It can be specifically used to: determine the target node file path that triggers the abnormal indicator data according to the abnormal indicator data; call the resource cache module 102 according to the target node file path to obtain the second target Pod and the target resource information corresponding to the abnormal indicator data, where the target resource information is the detailed information of the second target Pod.

[0067] For example, Figure 3 A schematic diagram of the cloud native NAS mounting principle provided in an embodiment of the present application is shown in FIG. Figure 3 As shown in the figure, in a cloud-native environment, to mount a NAS on a business Pod, you first need to complete the NAS mounting on the host (i.e., node) where the Pod is located, and then map it to the actual Pod through the file directory. Figure 3 Taking the example that stateless workload 1 (Deployment1) corresponds to Pod1 and Pod2, and stateless workload 2 (Deployment2) corresponds to Pod3 and Pod4, " / xx-1" represents the node file path of the file system of node 1 corresponding to Pod1; " / xx-2" represents the node file path of the file system of node 2 corresponding to Pod2; " / yy-1" represents the node file path of the file system of node 1 corresponding to Pod3; " / yy-2" represents the node file path of the file system of node 2 corresponding to Pod4; NAS device 1 and NAS device 2 respectively correspond to the service Internet Protocol (IP).

[0068] In this embodiment, the abnormal indicator data includes abnormal NAS file system usage, abnormal NAS file system inode usage, and the NAS file system status is read-only. The indicator query group corresponding to each abnormal indicator data can be pre-configured, and each indicator query group is configured with different indicator query statements, query frequencies, and alarm thresholds to achieve the query of the Prometheus component server-side indicator data in the same K8S cluster. Exemplarily, the abnormal indicator data also includes a node file path, and the node file path includes the ID information of the Pod. The root cause analysis module 103 can determine the target node file path that triggers the abnormal indicator data based on the abnormal indicator data, and obtain the second target Pod and the second target Pod's detailed information from the resource cache module 102 based on the target node file path. The detailed information of the second target Pod includes, for example, the workload and namespace to which the second target Pod belongs.

[0069] Optionally, the detailed information of the second target Pod includes the workload to which the second target Pod belongs. When the root cause analysis module 103 is used to generate alarm content based on the abnormal information, target resource information and the root cause, it can be specifically used to: aggregate the abnormal information according to the workload to obtain abnormal information in the workload dimension; generate alarm content in the workload dimension based on the abnormal information in the workload dimension, the detailed information of the second target Pod and the root cause.

[0070] Exemplarily, the root cause analysis module 103 can use the screening function of the resource cache module 102 to complete the mapping of the target node file path to the actual second target Pod, and finally aggregate the NAS capacity anomaly problem of the second target Pod under the same workload to the workload level according to the workload to which the second target Pod belongs, and realize the conversion of the host-level NAS file system capacity anomaly information to the workload-level NAS file system capacity anomaly information, and finally realize the alarm reporting through the alarm trigger module 104. The specific processing flow can refer to the subsequent embodiments.

[0071] Based on the above embodiments, Figure 4 Schematic diagram of the process of the cloud native alarm method provided in the embodiment of the present application Figure 1 , applied to the cloud native alarm system in any of the above embodiments. Figure 4 As shown, the method of the embodiment of the present application includes:

[0072] S401. The abnormal monitoring module monitors the abnormal information in the K8S cluster environment and sends the abnormal information to the root cause analysis module. The abnormal information includes abnormal K8S events and abnormal indicator data.

[0073] For example, abnormal K8S events and abnormal indicator data can be pre-configured according to different cloud-native fault scenarios, so that the abnormal monitoring module can monitor the abnormal information in the K8S cluster environment in real time and send the abnormal information to the root cause analysis module.

[0074] S402. The root cause analysis module calls the resource cache module to obtain the target resource information corresponding to the exception information based on the exception information; determines the root cause corresponding to the exception information based on the preset analysis strategy, exception information and target resource information; generates alarm content based on the exception information, target resource information and root cause, and sends the alarm content to the alarm trigger module.

[0075] In this step, after receiving the abnormal information sent by the abnormal monitoring module, the root cause analysis module can locate the problem and analyze the root cause according to the abnormal information, thereby generating alarm content and sending the alarm content to the alarm triggering module.

[0076] S403: The alarm triggering module generates target alarm information according to the alarm content, and forwards the target alarm information.

[0077] In this step, after receiving the alarm content sent by the root cause analysis module, the alarm trigger module can generate target alarm information in real time according to the alarm content and in a preset format, and forward the target alarm information, such as by email or SMS notification, to promptly process the target alarm information.

[0078] The cloud-native alarm method provided in the embodiment of the present application monitors the abnormal information in the K8S cluster environment through the abnormal monitoring module, and sends the abnormal information to the root cause analysis module, the abnormal information including abnormal K8S events and abnormal indicator data; the root cause analysis module calls the resource cache module to obtain the target resource information corresponding to the abnormal information according to the abnormal information; based on the preset analysis strategy, the abnormal information and the target resource information, the root cause corresponding to the abnormal information is determined; according to the abnormal information, the target resource information and the root cause, the alarm content is generated, and the alarm content is sent to the alarm trigger module; the alarm trigger module generates the target alarm information according to the alarm content, and forwards the target alarm information, so as to realize the problem location and root cause analysis of the abnormal K8S events and abnormal indicator data in the cloud-native environment quickly and accurately, and perform real-time alarm, which can greatly reduce the troubleshooting cost in the cloud-native operation and maintenance process, and effectively improve the problem solving efficiency.

[0079] Based on the above embodiments, for the node downtime scenario in the cloud native environment, Figure 5 Schematic diagram of the process of the cloud native alarm method provided in the embodiment of the present application Figure 2 , applied to a cloud-native alarm system as in any of the above embodiments.

[0080] like Figure 5 As shown, the method of the embodiment of the present application may include:

[0081] S501, the event monitoring submodule monitors abnormal K8S events in the K8S cluster environment, and sends abnormal K8S events to the root cause analysis module. The abnormal K8S events are node unready events.

[0082] Exemplarily, the K8S event type to be monitored can be pre-configured as a node not ready event. When a node not ready event occurs, it means that the node's regular health check has failed and the node's function is limited. At this time, the business Pod will not be expelled immediately, but the business Pod will be terminated after a preset fixed time and then rebuilt. In this step, the event monitoring submodule monitors abnormal K8S events in the K8S cluster environment in real time and sends abnormal K8S events to the root cause analysis module.

[0083] S502: The root cause analysis module determines the target node that triggers the node not ready event according to the node not ready event.

[0084] In this step, after receiving the node not ready event, the root cause analysis module may determine the target node that triggers the node not ready event according to the node not ready event.

[0085] S503: The root cause analysis module calls the resource cache module according to the target node to obtain the target resource information corresponding to the node unready event, where the target resource information is the business Pod information on the target node.

[0086] In this step, the root cause analysis module can obtain all business Pod information on the target node from the resource cache module according to the target node.

[0087] S504. The root cause analysis module determines the root cause corresponding to the abnormal K8S event based on the preset analysis strategy, abnormal K8S event and target resource information; generates alarm content according to the abnormal K8S event, target resource information and root cause, and sends the alarm content to the alarm trigger module.

[0088] Exemplarily, preset analysis strategies and handling strategies for specific problem scenarios can be customized according to needs. The root cause analysis module can determine the root cause corresponding to the abnormal K8S event based on the preset analysis strategy, abnormal K8S event and target resource information, obtain all application project information of the downtime node and complete deduplication, clarify the business impact scope of this downtime, thereby generating alarm content and sending the alarm content to the alarm trigger module. It can also automatically match the handling strategy for specific problem scenarios based on the environmental information provided by the resource cache module, and provide the handling suggestions to the alarm trigger module to assist the business party in closed-loop processing of alarms.

[0089] S505: The alarm triggering module generates target alarm information according to the alarm content, and forwards the target alarm information.

[0090] In this step, after receiving the alarm content, the alarm trigger module can generate target alarm information in real time according to the alarm content and in a preset format, and forward the target alarm information, for example, by email or SMS notification.

[0091] The cloud-native alarm method provided in the embodiment of the present application monitors abnormal K8S events in the K8S cluster environment through an event monitoring submodule, and sends abnormal K8S events to the root cause analysis module, where the abnormal K8S events are node not ready events; the root cause analysis module determines the target node that triggers the node not ready event based on the node not ready event, and calls the resource cache module to obtain target resource information based on the target node, where the target resource information is the business Pod information on the target node, and determines the root cause corresponding to the abnormal K8S event based on the preset analysis strategy, abnormal K8S event and target resource information, generates alarm content based on the abnormal K8S event, target resource information and root cause, and sends the alarm content to the alarm trigger module; the alarm trigger module generates target alarm information based on the alarm content, and forwards the target alarm information, thereby realizing real-time monitoring of node abnormal events based on K8S events, timely obtaining the application impact scope involved in the node and issuing alarms, and assisting in the location of basic resource problems in the process of business abnormality troubleshooting, which can greatly reduce the troubleshooting cost in the cloud-native operation and maintenance process and effectively improve the problem solving efficiency.

[0092] Based on the above embodiments, for the scenario where namespace quota is insufficient in a cloud native environment, Figure 6 Schematic diagram of the process of the cloud native alarm method provided in the embodiment of the present application Figure 3 , applied to the cloud native alarm system in any of the above embodiments. Figure 6 As shown, the method of the embodiment of the present application may include:

[0093] S601, the event monitoring submodule monitors abnormal K8S events in the K8S cluster environment, and sends abnormal K8S events to the root cause analysis module. The abnormal K8S events are Pod creation failure events.

[0094] Exemplarily, the monitored K8S event type can be pre-configured as a Pod creation failure event, so that the event monitoring submodule can monitor abnormal K8S events in the K8S cluster environment in real time and send abnormal K8S events to the root cause analysis module.

[0095] S602. The root cause analysis module determines the first target Pod that triggers the Pod creation failure event according to the Pod creation failure event.

[0096] In this step, after receiving the Pod creation failure event, the root cause analysis module can determine the first target Pod that triggers the Pod creation failure event based on the Pod creation failure event.

[0097] S603. The root cause analysis module calls the resource cache module according to the first target Pod to obtain target resource information corresponding to the Pod creation failure event, where the target resource information is detailed information of the first target Pod.

[0098] In this step, the root cause analysis module can obtain detailed information of the first target Pod from the resource cache module according to the first target Pod. The detailed information of the first target Pod includes, for example, the workload and namespace to which the first target Pod belongs.

[0099] S604. The root cause analysis module determines the root cause corresponding to the abnormal K8S event based on the preset analysis strategy, abnormal K8S event and target resource information; generates alarm content according to the abnormal K8S event, target resource information and root cause, and sends the alarm content to the alarm trigger module.

[0100] Exemplarily, the preset analysis strategy can be customized according to the needs. In this step, the root cause analysis module can determine that the root cause corresponding to the abnormal K8S event is insufficient namespace quota based on the preset analysis strategy, abnormal K8S event and target resource information, and clarify the specific resource type and current value of the insufficient namespace quota. Specific resource types include CPU, memory and number of Pods, etc. At the same time, the root cause analysis module aggregates Pods with the same problem within a recent period of time into the workload dimension to avoid duplicate alarms, thereby generating alarm content and sending the alarm content to the alarm trigger module.

[0101] S605: The alarm triggering module generates target alarm information according to the alarm content, and forwards the target alarm information.

[0102] In this step, after receiving the alarm content, the alarm trigger module can generate target alarm information in real time according to the alarm content and in a preset format, and forward the target alarm information, for example, by email or SMS notification.

[0103] The cloud-native alarm method provided in the embodiment of the present application monitors abnormal K8S events in the K8S cluster environment through an event monitoring submodule, and sends abnormal K8S events to the root cause analysis module, where the abnormal K8S events are Pod creation failure events; the root cause analysis module determines the first target Pod that triggers the Pod creation failure event based on the Pod creation failure event, and calls the resource cache module to obtain target resource information based on the first target Pod, where the target resource information is detailed information of the first target Pod, and determines the root cause corresponding to the abnormal K8S event based on the preset analysis strategy, the abnormal K8S event and the target resource information, and generates alarm content based on the abnormal K8S event, the target resource information and the root cause, and sends the alarm content to the alarm trigger module; the alarm trigger module generates target alarm information based on the alarm content, and forwards the target alarm information, thereby monitoring the scenario of insufficient namespace quota in real time based on the K8S self-monitoring capability, completing the one-stop triggering of namespace quota alarms, realizing the location of quota problems in the application deployment process, and issuing alarms, which can greatly reduce the troubleshooting cost in the cloud-native operation and maintenance process and effectively improve the problem solving efficiency.

[0104] Based on the above embodiments, for the cloud native NAS capacity abnormality scenario, Figure 7 Schematic diagram of the process of the cloud native alarm method provided in the embodiment of the present application Figure 4 , applied to the cloud native alarm system in any of the above embodiments. Figure 7 As shown, the method of the embodiment of the present application may include:

[0105] S701, the Pro docking submodule monitors the abnormal indicator data in the K8S cluster environment and sends the abnormal indicator data to the root cause analysis module. The abnormal indicator data includes abnormal NAS file system usage, abnormal NAS file system inode usage, and the NAS file system status is read-only.

[0106] For example, the indicator query group corresponding to each abnormal indicator data can be pre-configured, and each indicator query group is configured with different indicator query statements, query frequencies and alarm thresholds to achieve the query of the Prometheus component server indicator data in the same K8S cluster. In this step, the Prometheus docking submodule can monitor and capture the abnormal indicator data in the K8S cluster environment in real time, and send the abnormal indicator data to the root cause analysis module.

[0107] S702: The root cause analysis module determines the target node file path that triggers the abnormal indicator data according to the abnormal indicator data.

[0108] In this step, after receiving the abnormal indicator data, the root cause analysis module can determine the target node file path that triggers the abnormal indicator data according to the abnormal indicator data.

[0109] S703. The root cause analysis module calls the resource cache module to obtain the target resource information corresponding to the second target Pod and the abnormal indicator data according to the target node file path. The target resource information is the detailed information of the second target Pod.

[0110] For example, reference Figure 3 The root cause analysis module can call the resource cache module to obtain the second target Pod and the detailed information of the second target Pod according to the target node file path. The detailed information of the second target Pod includes, for example, the workload and namespace to which the second target Pod belongs.

[0111] S704. The root cause analysis module determines the root cause corresponding to the abnormal indicator data based on the preset analysis strategy, abnormal indicator data and target resource information; aggregates the abnormal information according to the workload to which the second target Pod belongs to obtain abnormal information in the workload dimension; generates alarm content in the workload dimension according to the abnormal information in the workload dimension, detailed information of the second target Pod and the root cause, and sends the alarm content in the workload dimension to the alarm trigger module.

[0112] Exemplarily, the preset analysis strategy can be customized according to the needs. In this step, the root cause analysis module can determine the root cause corresponding to the abnormal indicator data based on the preset analysis strategy, abnormal indicator data and target resource information, and can use the screening function of the resource cache module to complete the mapping of the target node file path to the actual second target Pod, and finally aggregate the NAS capacity abnormality problem of the second target Pod under the same workload to the workload level according to the workload to which the second target Pod belongs, realize the conversion of the host-level NAS file system capacity abnormality information to the workload-level NAS file system capacity abnormality information, generate the workload dimension alarm content, and send the workload dimension alarm content to the alarm trigger module.

[0113] S705. The alarm triggering module generates target alarm information according to the alarm content, and forwards the target alarm information.

[0114] In this step, after receiving the alarm content, the alarm trigger module can generate target alarm information in real time according to the alarm content and in a preset format, and forward the target alarm information, for example, by email or SMS notification.

[0115] The cloud native alarm method provided in the embodiment of the present application monitors the abnormal indicator data in the K8S cluster environment through the Pro docking submodule, and sends the abnormal indicator data to the root cause analysis module, wherein the abnormal indicator data includes abnormal NAS file system usage rate, abnormal NAS file system inode usage rate, and the NAS file system status is read-only; the root cause analysis module determines the target node file path that triggers the abnormal indicator data according to the abnormal indicator data, and calls the resource cache module to obtain the second target Pod and target resource information according to the target node file path, wherein the target resource information is the detailed information of the second target Pod; the root cause analysis module determines the corresponding abnormal indicator data based on the preset analysis strategy, abnormal indicator data, and target resource information. Root cause; According to the workload to which the second target Pod belongs, the exception information is aggregated to obtain the exception information of the workload dimension; According to the exception information of the workload dimension, the detailed information of the second target Pod and the root cause, the alarm content of the workload dimension is generated, and the alarm content of the workload dimension is sent to the alarm trigger module; The alarm trigger module generates target alarm information according to the alarm content and forwards the target alarm information, thereby realizing the aggregation of NAS-type alarms based on the Prometheus component and the workload as the main body, locating the NAS capacity abnormality of the container during the application operation in real time, and issuing an alarm, which can greatly reduce the troubleshooting cost in the cloud native operation and maintenance process and effectively improve the efficiency of problem solving.

[0116] In summary, the embodiment of the present application builds a cloud-native custom alarm generation system based on Prometheus components and K8S native events, which can realize real-time positioning of the application impact range after node downtime, real-time and accurate locking of application namespace quota problems, and real-time alarm of cloud-native NAS capacity in the workload dimension, which can greatly reduce the troubleshooting cost in the cloud-native operation and maintenance process.

[0117] Figure 8 This is a schematic diagram of the structure of an electronic device provided by an embodiment of the present application. Figure 8 As shown, the electronic device 800 may include: at least one processor 801 and a memory 802 .

[0118] The memory 802 is used to store programs. Specifically, the programs may include program codes, and the program codes include computer-executable instructions.

[0119] The memory 802 may include a high-speed random access memory (RAM), and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.

[0120] The processor 801 is used to execute the computer-executable instructions stored in the memory 802 to implement the cloud-native alarm method described in the aforementioned method embodiment. Among them, the processor 801 may be a central processing unit, or an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application. Specifically, when implementing the cloud-native alarm method described in the aforementioned method embodiment, the electronic device can be, for example, an electronic device with processing functions such as a server.

[0121] Optionally, the electronic device 800 may further include a communication interface 803. In a specific implementation, if the communication interface 803, the memory 802 and the processor 801 are implemented independently, the communication interface 803, the memory 802 and the processor 801 may be interconnected through a bus and communicate with each other. The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc., but it does not mean that there is only one bus or one type of bus.

[0122] Optionally, in a specific implementation, if the communication interface 803, the memory 802 and the processor 801 are integrated on a chip, the communication interface 803, the memory 802 and the processor 801 can communicate through an internal interface.

[0123] The electronic device is used to execute the cloud-native alarm method in any of the aforementioned method embodiments, and its implementation principle and technical effects are similar, which will not be repeated here.

[0124] The present application also provides a computer-readable storage medium, in which computer program instructions are stored. When a processor executes the computer program instructions, the above-mentioned cloud-native alarm method is implemented.

[0125] The present application also provides a computer program product, including a computer program, which implements the above cloud-native alarm method when executed by a processor.

[0126] The computer-readable storage medium mentioned above can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The readable storage medium can be any available medium that can be accessed by a general or special-purpose computer.

[0127] An exemplary readable storage medium is coupled to a processor so that the processor can read information from the readable storage medium and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can be located in a dedicated integrated circuit. Of course, the processor and the readable storage medium can also exist as discrete components in the cloud native alarm system.

[0128] The division of units is only a logical function division, and there may be other divisions in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interface, device or unit, which can be electrical, mechanical or other forms.

[0129] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0130] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0131] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory, a random access memory (RAM), a disk or an optical disk.

[0132] Those skilled in the art can understand that all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, disk or optical disk and other media that can store program codes.

[0133] Finally, it should be noted that those skilled in the art will readily conceive of other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any variations, uses or adaptations of the present application, which follow the general principles of the present application and include common knowledge or customary technical means in the art that are not disclosed in the present application, are not limited to the precise structures described above and shown in the drawings, and may be modified and changed in various ways without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A cloud native alarm system, characterized in that: include: Abnormal monitoring module, resource caching module, root cause analysis module and alarm triggering module; The abnormality monitoring module is used to monitor abnormal information in the K8S cluster environment and send the abnormal information to the root cause analysis module, where the abnormal information includes abnormal K8S events and / or abnormal indicator data; The root cause analysis module is used to call the resource cache module to obtain target resource information corresponding to the exception information according to the exception information; Determine the root cause of the abnormal information based on the preset analysis strategy, the abnormal information and the target resource information; Generate alarm content according to the abnormal information, the target resource information and the root cause, and send the alarm content to the alarm trigger module; The alarm triggering module is used to generate target alarm information according to the alarm content and forward the target alarm information.

2. The cloud native alarm system according to claim 1, characterized in that: The abnormal monitoring module includes an event monitoring submodule and a Prometheus docking submodule; the event monitoring submodule is used to monitor the abnormal K8S events; the Prometheus docking submodule is used to monitor the abnormal indicator data based on the Prometheus component.

3. The cloud native alarm system according to claim 2, characterized in that: The abnormal K8S event is a node unready event. When the root cause analysis module is used to call the resource cache module to obtain the target resource information corresponding to the abnormal information according to the abnormal information, it is specifically used to: According to the node not ready event, determining a target node that triggers the node not ready event; According to the target node, the resource cache module is called to obtain target resource information corresponding to the node unready event, where the target resource information is the business Pod information on the target node.

4. The cloud native alarm system according to claim 2, characterized in that: The abnormal K8S event is a Pod creation failure event. When the root cause analysis module is used to call the resource cache module to obtain the target resource information corresponding to the abnormal information according to the abnormal information, it is specifically used to: According to the Pod creation failure event, determine a first target Pod that triggers the Pod creation failure event; According to the first target Pod, the resource cache module is called to obtain target resource information corresponding to the Pod creation failure event, where the target resource information is detailed information of the first target Pod.

5. The cloud native alarm system according to claim 2, characterized in that: The abnormal indicator data includes an abnormal network attached storage NAS file system usage rate, an abnormal NAS file system index node inode usage rate, and the NAS file system is in a read-only state. The root cause analysis module is used to call the resource cache module to obtain the target resource information corresponding to the abnormal information according to the abnormal information, specifically for: According to the abnormal indicator data, determine the target node file path that triggers the abnormal indicator data; According to the target node file path, the resource cache module is called to obtain the target resource information corresponding to the second target Pod and the abnormal indicator data, where the target resource information is the detailed information of the second target Pod.

6. The cloud native alarm system according to claim 5, characterized in that: The detailed information of the second target Pod includes the workload to which the second target Pod belongs, and the root cause analysis module, when used to generate alarm content according to the abnormal information, the target resource information and the root cause, is specifically used to: According to the workload, the abnormal information is aggregated to obtain abnormal information in the workload dimension; Generate alarm content of the workload dimension according to the abnormal information of the workload dimension, detailed information of the second target Pod, and the root cause.

7. The cloud native alarm system according to any one of claims 1 to 6, characterized in that: Both the abnormal K8S event and the abnormal indicator data can be configured.

8. A cloud native alarm method, characterized in that: The cloud native alarm method is applied to the cloud native alarm system according to any one of claims 1 to 7, and the cloud native alarm method includes: The abnormality monitoring module monitors the abnormal information in the K8S cluster environment and sends the abnormal information to the root cause analysis module. The abnormal information includes abnormal K8S events and abnormal indicator data; The root cause analysis module calls the resource cache module to obtain the target resource information corresponding to the abnormal information according to the abnormal information; determines the root cause corresponding to the abnormal information based on the preset analysis strategy, the abnormal information and the target resource information; generates alarm content according to the abnormal information, the target resource information and the root cause, and sends the alarm content to the alarm trigger module; The alarm triggering module generates target alarm information according to the alarm content and forwards the target alarm information.

9. An electronic device, characterized in that: include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the cloud-native alarm method as claimed in claim 8.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer program instructions, and when the computer program instructions are executed, the cloud-native alarm method according to claim 8 is implemented.

Images