Fault location method, device, computer readable medium and electronic device

Abstract

The present application belongs to the field of emerging information technology, and specifically relates to a fault location method, device, computer-readable medium and electronic device. The present application obtains a container cluster management architecture and multiple fault alarm information, and constructs a container cluster management tree based on the container cluster management architecture; the multiple alarm information is marked on the container cluster management tree to form multiple fault domains, the multiple fault domains are converged to form a convergence domain, and finally the location of the fault is determined according to the convergence domain. The present application makes full use of the characteristics of hierarchical management of container clusters. According to the idea that the failure of the parent node will cause the failure of the child node, the fault location can be automatically located without manual judgment. Moreover, the present application can cover abnormal events and faults outside the alarm rules, realize rapid location of faults, and ensure the normal use of the container cluster management system.

Description

Technical Field

[0001] The present application belongs to the field of emerging information technology, and specifically relates to a fault location method, a fault location device, a computer-readable medium, and an electronic device. Background Art

[0002] With the continuous upgrading of software development, container cluster management systems have also developed. Container cluster management systems can provide a series of complete functions such as deployment and operation, resource scheduling, service discovery and dynamic scaling for containerized applications, improving the convenience of large-scale container cluster management.

[0003] However, while the container cluster management system achieves rapid deployment of applications and efficient use of resources, it also introduces a more complex system architecture, making fault location and root cause analysis more difficult; the large-scale deployment of containers also brings greater challenges to fault location and root cause analysis. Currently, the fault location is usually determined by using policy association rules and manually setting rules. This method requires rich expert experience and cannot cover abnormal events and faults outside the alarm rules. Therefore, it is impossible to quickly locate faults, affecting the use of the container cluster management system.

[0004] It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of the present application, and therefore may include information that does not constitute the prior art known to ordinary technicians in the field. Summary of the invention

[0005] The purpose of the present application is to provide a fault location method, a fault location device, a computer-readable medium and an electronic device, which at least to a certain extent overcome the technical problems in the related art that fault location in the container cluster management system needs to rely on expert experience, the fault location is inaccurate, and the fault cannot be automatically located.

[0006] Other features and advantages of the present application will become apparent from the following detailed description, or may be learned in part by the practice of the present application.

[0007] According to one aspect of an embodiment of the present application, a fault location method is provided, including:

[0008] Obtain container cluster management architecture and multiple fault alarm information;

[0009] Based on the container cluster management architecture, construct a container cluster management tree;

[0010] Marking the multiple alarm information onto the container cluster management tree to form multiple fault domains, where the fault domains include locations on the container cluster management tree that contain the alarm information;

[0011] Converging the multiple fault domains to form a convergence domain;

[0012] The fault location is determined according to the convergence region.

[0013] In some embodiments of the present application, based on the above technical solution, the container cluster management architecture includes a control node, a service node, a sub-unit and a container. Based on the container cluster management architecture, a method for constructing a container cluster management tree includes:

[0014] Based on the hierarchical relationship among control nodes, service nodes, sub-units and containers, the control node is used as the initial node, and the container cluster management tree is constructed in sequence according to the hierarchical relationship.

[0015] In some embodiments of the present application, based on the above technical solution, the method of marking the multiple alarm information on the container cluster management tree includes:

[0016] Parsing the multiple fault warning information to obtain the warning subjects of the multiple fault warning information;

[0017] The multiple fault alarm information are respectively marked on tree nodes corresponding to the alarm subject in the container cluster management tree.

[0018] In some embodiments of the present application, based on the above technical solution, a method for converging the multiple fault domains to form a convergence domain includes:

[0019] Analyze the multiple fault warning information to obtain the warning contents of the multiple fault warning information;

[0020] If there is no other node other than the fault domain to be converged at the subordinate level of the parent node of the fault domain to be converged, then determining the similarity relationship of the alarm contents of each fault domain in the fault domain to be converged;

[0021] If the alarm contents of each fault domain in the to-be-converged fault domain are similar, converge the to-be-converged fault domain, and use the parent node as the convergence domain of the to-be-converged fault domain;

[0022] The fault domains to be converged include at least two fault domains having the same parent node among the multiple fault domains.

[0023] In some embodiments of the present application, based on the above technical solution, a method for determining the similarity relationship of the alarm contents of the to-be-converged fault domain includes:

[0024] Convert the alarm content of the to-be-converged fault domain into a character string;

[0025] Calculating the similarity of the alarm contents of each fault domain in the to-be-converged fault domain by using a string similarity algorithm;

[0026] If the similarity of the alarm contents of each fault domain in the to-be-converged fault domain is greater than a set threshold, the alarm contents of each fault domain in the to-be-converged fault domain are similar.

[0027] In some embodiments of the present application, based on the above technical solution, the method of converging the multiple fault domains to form a convergence domain further includes:

[0028] Analyze the multiple fault warning information to obtain the warning contents of the multiple fault warning information;

[0029] If there are other nodes other than the fault domain to be converged at the subordinate level of the parent node of the fault domain to be converged, the fault domain to be converged is used as the convergence domain;

[0030] The fault domains to be converged include at least two fault domains having the same parent node among the multiple fault domains.

[0031] In some embodiments of the present application, based on the above technical solution, the method of converging the multiple fault domains to form a convergence domain further includes:

[0032] Analyze the multiple fault warning information to obtain the warning contents of the multiple fault warning information;

[0033] If there is no other node other than the fault domain to be converged at the subordinate level of the parent node of the fault domain to be converged, then determining the similarity relationship of the alarm contents of each fault domain in the fault domain to be converged;

[0034] If the alarm contents of each fault domain in the to-be-converged fault domain are not similar, the to-be-converged fault domain is used as the convergence domain;

[0035] The fault domains to be converged include at least two fault domains having the same parent node among the multiple fault domains.

[0036] According to another aspect of an embodiment of the present application, a fault location device is provided, including:

[0037] The acquisition module is used to obtain the container cluster management architecture and multiple fault alarm information;

[0038] A construction module, used to construct a container cluster management tree based on the container cluster management architecture;

[0039] A marking module, used to mark the multiple alarm information on the container cluster management tree to form multiple fault domains, wherein the fault domain includes a location on the container cluster management tree containing the alarm information;

[0040] A convergence module, used for converging the multiple fault domains to form a convergence domain;

[0041] A positioning module is used to determine the location of the fault according to the convergence domain.

[0042] In some embodiments of the present application, based on the above technical solution, the container cluster management architecture includes a control node, a service node, a sub-unit and a container, and the building module includes:

[0043] The construction unit is used to build a container cluster management tree based on the hierarchical relationship among control nodes, service nodes, sub-units and containers, with the control node as the initial node, according to the hierarchical relationship.

[0044] In some embodiments of the present application, based on the above technical solution, the marking module includes:

[0045] A subject parsing unit, used to parse the multiple fault warning information and obtain the warning subjects of the multiple fault warning information;

[0046] The marking unit is used to mark the multiple fault alarm information respectively on the tree nodes corresponding to the alarm subject in the container cluster management tree.

[0047] In some embodiments of the present application, based on the above technical solution, the convergence module includes:

[0048] A content parsing unit, configured to parse the plurality of fault warning information and obtain the warning contents of the plurality of fault warning information;

[0049] If there is no other node other than the fault domain to be converged at the subordinate level of the parent node of the fault domain to be converged, then determining the similarity relationship of the alarm contents of each fault domain in the fault domain to be converged;

[0050] A convergence unit, configured to converge the fault domain to be converged when the alarm contents of each fault domain in the fault domain to be converged are similar, and use the parent node as a convergence domain of the fault domain to be converged;

[0051] The fault domains to be converged include at least two fault domains having the same parent node among the multiple fault domains.

[0052] In some embodiments of the present application, based on the above technical solution, the convergence unit includes:

[0053] A character conversion unit, used for converting the alarm content of the to-be-converged fault domain into a character string;

[0054] A similarity calculation unit, used for calculating the similarity of the alarm contents of each fault domain in the to-be-converged fault domain by using a string similarity algorithm;

[0055] The similarity determination unit is used to determine that the alarm contents of each fault domain in the to-be-converged fault domain are similar when the similarity of the alarm contents of each fault domain in the to-be-converged fault domain is greater than a set threshold.

[0056] In some embodiments of the present application, based on the above technical solution, the convergence module further includes:

[0057] A content parsing unit, configured to parse the plurality of fault warning information and obtain the warning contents of the plurality of fault warning information;

[0058] A convergence conversion unit, configured to use the to-be-converged fault domain as a convergence domain when there are other nodes other than the to-be-converged fault domain at the subordinate level of the parent node of the to-be-converged fault domain;

[0059] The fault domains to be converged include at least two fault domains having the same parent node among the multiple fault domains.

[0060] In some embodiments of the present application, based on the above technical solution, the convergence module further includes:

[0061] A content parsing unit, configured to parse the plurality of fault warning information and obtain the warning contents of the plurality of fault warning information;

[0062] A similarity judgment unit, configured to judge the similarity relationship of the alarm contents of each fault domain in the fault domain to be converged when there is no other node other than the fault domain to be converged at the subordinate level of the parent node of the fault domain to be converged;

[0063] A convergence replacement unit, configured to use the to-be-converged fault domain as a convergence domain when the alarm contents of the fault domains in the to-be-converged fault domain are not similar;

[0064] The fault domains to be converged include at least two fault domains having the same parent node among the multiple fault domains.

[0065] According to one aspect of an embodiment of the present application, a computer-readable medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the fault location method in the above technical solution is implemented.

[0066] According to one aspect of an embodiment of the present application, an electronic device is provided, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute the fault location method in the above technical solution by executing the executable instructions.

[0067] According to one aspect of the embodiments of the present application, a computer program product or a computer program is provided, the computer program product or the computer program includes computer instructions, the computer instructions are stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the fault location method in the above technical solution.

[0068] In the technical solution provided in the embodiment of the present application, the present application obtains the container cluster management architecture and multiple fault alarm information, and constructs a container cluster management tree based on the container cluster management architecture; the multiple alarm information is marked on the container cluster management tree to form multiple fault domains, the multiple fault domains are converged to form a convergence domain, and finally the fault location is determined according to the convergence domain. Using the method of the present application, the location of the fault in the container cluster management system can be determined after converging according to the location of multiple fault alarm information in the container cluster management system on the container cluster management tree, and the fault location can be automatically located without manual judgment. Moreover, the present application can cover abnormal events and faults outside the alarm rules, realize rapid fault location, and ensure the normal use of the container cluster management system.

[0069] Furthermore, the present application uses a string similarity algorithm to converge the multiple fault domains to form a convergence domain, and converges the faults of multiple child nodes through a string similarity algorithm to determine the fault location. The present application makes full use of the characteristics of hierarchical management of container clusters, and according to the idea that a parent node failure will cause a child node failure, the accuracy of the container cluster management system in determining the fault location can be improved.

[0070] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0071] The drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present application, and together with the specification are used to explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application, and for ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0072] Figure 1 The exemplary system architecture block diagram applying the technical solution of the present application is schematically shown.

[0073] Figure 2 The flowchart of the fault location method of the present application is schematically shown.

[0074] Figure 3 A schematic diagram of a container cluster management architecture of the present application is schematically shown.

[0075] Figure 4 The application is schematically shown Figure 3 Schematic diagram of the container cluster management tree constructed corresponding to the container cluster management architecture.

[0076] Figure 5 The flowchart of the method for forming a fault domain of the present application is schematically shown.

[0077] Figure 6 A schematic diagram of the structure of a fault domain of the present application is shown schematically.

[0078] Figure 7 A schematic diagram of the structure of another fault domain of the present application is shown schematically.

[0079] Figure 8 The flowchart of the method for forming the convergence region of the present application is schematically shown.

[0080] Fig. 9 The method of calculating the similarity relationship of the alarm contents of the to-be-converged fault domain in the present application is schematically shown.

[0081] Fig.10 The structural diagram of a convergence region of the present application is schematically shown.

[0082] Fig.11 The structural block diagram of the fault location device of the present application is schematically shown.

[0083] Fig.12 The structure block diagram of a computer system suitable for implementing an electronic device of an embodiment of the present application is schematically shown. DETAILED DESCRIPTION

[0084] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this application will be more comprehensive and complete and fully convey the concept of example embodiments to those skilled in the art.

[0085] In addition, described feature, structure or characteristic can be combined in one or more embodiments in any suitable manner. In the following description, many specific details are provided to provide a full understanding of the embodiments of the present application. However, those skilled in the art will appreciate that the technical scheme of the present application can be put into practice without one or more of the specific details, or other methods, components, devices, steps, etc. can be adopted. In other cases, known methods, devices, realizations or operations are not shown or described in detail to avoid blurring the various aspects of the application.

[0086] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities may be implemented in software form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0087] The flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all the contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps can be decomposed, and some operations / steps can be combined or partially combined, so the actual execution order may change according to actual conditions.

[0088] The fault location method of the present application can be used for fault location in a container cluster management system, and can also be used in other systems where there are upper and lower hierarchical relationships and the upper and lower hierarchical relationships have mutual influence. The following is an example of a container cluster management system for illustration.

[0089] With the continuous upgrading of software development, application container engine technology has been greatly developed. Application container engine (hereinafter referred to as Docker) allows developers to package their applications and dependent packages into a portable container, and then publish them to a machine with an operating system, and can also achieve virtualization. With the help of Docker, the development platform and applications can be separated, and the development platform can be managed like an application. Docker can quickly develop applications, quickly test applications, and quickly deploy applications, and shorten the cycle interval between developing code and executing code.

[0090] With the widespread popularity of Docker technology, container cluster management systems have also developed. Based on Docker technology, container cluster management systems provide a series of complete functions such as deployment and operation, resource scheduling, service discovery, and dynamic scaling for containerized applications, improving the convenience of large-scale container cluster management.

[0091] The composition structure of the container cluster management system includes hardware and software. Among them, the hardware mainly includes clusters and nodes. The cluster is a whole, which contains many nodes inside. The cluster can intelligently distribute work to each node. If any node is added or deleted, the cluster will switch in work as needed. The node is the smallest computing hardware unit in the container cluster management system. It is a representation of a single machine in the cluster. In most production systems, the node is likely to be a physical machine in a data center, or a virtual machine hosted on a cloud provider like Google Cloud Platform.

[0092] Nodes mainly include control nodes and service nodes. The control node (MasterNode) is responsible for managing the cluster, providing access to the cluster's resource data, and is the only entry for adding, deleting, modifying, and checking all resources in the container cluster management system. The service node (serviceNode) is the unit of cluster operation in the container cluster management system, which is used to carry the operation of the assigned sub-unit (Pod) and is the host for the sub-unit (Pod) to run. It is also associated with the control node.

[0093] From a software perspective, the container cluster management system includes subunits (hereinafter referred to as Pods) and containers. One or more containers are encapsulated in a Pod. Any container in the same Pod will share the same namespace and local network. Containers can easily communicate with other containers in the same Pod, just as if they were on the same machine while maintaining a certain degree of isolation. Containers allow the creation of self-sufficient system execution environments. Any program and all its dependencies can be packaged into a single file and then shared on the network. Anyone can download the container and deploy it on their infrastructure, and very little setup is required. Creating a container can be done programmatically.

[0094] The present application can use the Kubectl command line tool to manage the container cluster management system. The Kubectl command line tool can be used to send different control commands to the control node (MasterNode) to achieve control and management of the container cluster management system.

[0095] However, while the container cluster management system enables rapid deployment of applications and efficient use of resources, it also introduces a more complex system architecture, making fault location and root cause analysis more difficult. To locate faults, we can use policy association rules. For the original alarm sequence, we can design alarm information merging rules based on expert experience and converge the fault domain based on the merging rules. The above solution uses artificially set rules, which requires rich expert experience and cannot cover abnormal events and faults outside the alarm rules. Therefore, it is impossible to quickly locate faults.

[0096] In order to solve the above technical problems, the present application discloses a fault location method, a fault location device, a computer-readable medium and an electronic device. The content of the present application will be further explained in various aspects below.

[0097] Figure 1 The exemplary system architecture block diagram applying the technical solution of the present application is schematically shown.

[0098] like Figure 1As shown, the system architecture 100 may include a terminal device 110, a network 120, and a server 130. The terminal device 110 may include various electronic devices such as a smart phone, a tablet computer, a laptop computer, and a desktop computer. The server 130 may be an independent physical server, or a server cluster or a distributed system composed of multiple physical servers, or a cloud server providing cloud computing services. The network 120 may be a communication medium of various connection types that can provide a communication link between the terminal device 110 and the server 130, such as a wired communication link or a wireless communication link.

[0099] According to the implementation requirements, the system architecture in the embodiment of the present application can have any number of terminal devices, networks and servers. For example, the server 130 can be a server group composed of multiple server devices. In addition, the technical solution provided in the embodiment of the present application can be applied to the terminal device 110, can also be applied to the server 130, or can be implemented by the terminal device 110 and the server 130 together, and the present application does not make any special restrictions on this.

[0100] The terminal device 110 or server 130 of the present application can obtain the container cluster management architecture and multiple fault alarm information through the network 120; then build a container cluster management tree based on the container cluster management architecture; then mark multiple alarm information on the container cluster management tree to form multiple fault domains, and then converge multiple fault domains to form a convergence domain; finally determine the location of the fault based on the convergence domain. The fault location can be quickly and automatically located without manual judgment, and can cover abnormal events and faults outside the alarm rules, ensuring the normal use of the container cluster management system.

[0101] The above section introduces the contents of an exemplary system architecture applying the technical solution of the present application, and the following will continue to introduce the fault location method of the present application.

[0102] like Figure 2 As shown, Figure 2 The flowchart of the fault location method of the present application is schematically shown.

[0103] The present application provides a fault location method, including steps S210 to S250.

[0104] In step S210: a container cluster management architecture and multiple fault alarm information are obtained.

[0105] Among them, the container cluster management architecture and multiple fault alarm information can be obtained through information uploaded by users, and can also be automatically obtained through the container cluster management system.

[0106] The container cluster management architecture refers to the composition architecture of the container cluster management system. For a container cluster management system, it can be composed of a control node (MasterNode), multiple service nodes (serviceNode), multiple Pods, and multiple containers (Container). Among them, the control node (MasterNode), multiple service nodes (serviceNode), multiple Pods, and multiple containers (Container) are hierarchical relationships from top to bottom.

[0107] like Figure 3 As shown, Figure 3 A schematic diagram of a container cluster management architecture of the present application is schematically shown.

[0108] For example, the container cluster management architecture 300 of the container cluster management system A is as follows: Figure 3 As shown, the container cluster management architecture 300 includes a control node 310 and two service nodes, namely, a first service node 321 and a second service node 322. The first service node 321 includes two Pods, namely, a first Pod 331 and a second Pod 332. The second service node 322 includes a Pod, namely, a third Pod 333. In each Pod, there are two containers, namely, container A and container B. Therefore, by obtaining the container cluster management architecture, the composition of the container cluster management system can be determined, which is conducive to analyzing the fault location.

[0109] The fault alarm information of this application refers to the alarm information when a container cluster management system fails. For a container cluster management system, each part of its component architecture may fail, so an alarm will be prompted. For example, abnormal Pod behavior, service node downtime, and inability to create a new Pod on a service node. For fault alarm information, it includes a fault alarm subject and a fault alarm content. The fault alarm subject indicates which part has a fault. For example, for abnormal Pod behavior, the fault alarm subject is the Pod. The fault alarm content is abnormal behavior. At the same time, the fault alarm information can also include alarm attribute information, such as the specific alarm time, alarm status, alarm ID and other information.

[0110] In step S220: based on the container cluster management architecture, a container cluster management tree is constructed.

[0111] In one embodiment of the present application, a container cluster management architecture includes a control node, a service node, a sub-unit, and a container. A method for constructing a container cluster management tree based on the container cluster management architecture includes:

[0112] Based on the hierarchical relationship among control nodes, service nodes, sub-units and containers, the control node is used as the initial node, and the container cluster management tree is constructed in sequence according to the hierarchical relationship.

[0113] Continue with Figure 3 Taking the container cluster management architecture 300 of the corresponding container cluster management system A as an example, a container cluster management tree is constructed based on the container cluster management architecture 300 .

[0114] like Figure 4 As shown, Figure 4 The application is schematically shown Figure 3 Schematic diagram of the container cluster management tree constructed corresponding to the container cluster management architecture.

[0115] exist Figure 4 In Figure 3 The corresponding container cluster management architecture 300 uses the control node as the initial node and constructs the container cluster management tree in sequence according to the upper and lower hierarchical relationships. After the construction is completed, the container cluster management tree will form multiple levels, namely the control node layer 410, the service node layer 420, the Pod layer 430 and the container layer 440, wherein the object pointed by the arrow in the figure is the parent node of the pointed object. For example, the control node in the control node layer 410 of the present application is the parent node of the two service nodes in the service node layer 420. Through the constructed container cluster management tree, the relationship between the various hierarchical architectures in the container cluster management architecture can be clearly confirmed.

[0116] Among them, when constructing the container cluster management tree, the present application does not need to be constructed according to the upper and lower hierarchical relationships of the control nodes, service nodes, sub-units and containers. The present application can selectively select some of the component architectures for construction. In one embodiment of the present application, the present application can be constructed according to the alarm subject information of multiple alarm information. For example, when it is found that the alarm subject information included in the multiple alarm information of the container cluster management system is a Pod and a corresponding container, a two-layer tree structure can be constructed at this time, that is, the Pod is used as the parent node and the container is used as the child node of each Pod. This method can effectively improve the construction speed of the container cluster management tree, omit the component architecture where the alarm information does not exist, and increase the construction rate.

[0117] In step S230: multiple alarm information are marked on the container cluster management tree to form multiple fault domains, and the fault domain includes the location containing the alarm information on the container cluster management tree.

[0118] In one embodiment of the present application, Figure 5 As shown, Figure 5 The flowchart of the method for forming a fault domain of the present application is schematically shown.

[0119] The method of marking multiple alarm information on a container cluster management tree to form multiple fault domains includes steps S510 to S520.

[0120] Step S510: parse multiple fault alarm information to obtain alarm bodies of multiple fault alarm information.

[0121] The fault alarm information contains the subject of the fault occurrence. Therefore, by parsing multiple fault alarm information, the alarm subjects of multiple fault alarm information can be obtained. Figure 3 Taking the corresponding container cluster management architecture as an example, under this architecture, three alarm messages appear, namely, container A and container B of the first Pod 331 under the first service node 321, and container A of the second Pod 332 under the second service node 322. Therefore, the location of the architecture component corresponding to the alarm subject can be determined.

[0122] Step S520: Mark the multiple fault alarm information respectively on the tree nodes corresponding to the alarm subjects in the container cluster management tree.

[0123] After the alarm subject is determined, multiple fault alarm information are marked on tree nodes corresponding to the alarm subject in the container cluster management tree.

[0124] like Figure 6 As shown, Figure 6 The schematic diagram of the structure of a fault domain of the present application is shown schematically. When three alarm messages appear, namely, container A and container B of the first Pod331 under the first service node 321, and container A of the second Pod332 under the second service node 322, multiple fault alarm messages are marked on the tree nodes corresponding to the alarm subject in the container cluster management tree, for example, the corresponding nodes can be marked black to form Figure 6 The multiple fault domains shown are respectively located on the first fault domain 610 on the container A of the first Pod 331, the second fault domain 620 on the container B of the first Pod 331, and the third fault domain 630 on the container A of the second Pod 332. The fault domain includes the location containing the alarm information on the container cluster management tree, which corresponds to the tree node corresponding to the alarm subject in the container cluster management tree.

[0125] When marking the tree node corresponding to the alarm subject in the container cluster management tree, the present application may also mark the fault alarm content and alarm attribute information of multiple fault alarm information to facilitate rapid fault location.

[0126] Through steps S510 to S520 of the present application, the location of the fault domain in the container cluster management tree can be determined. Continue to step S240.

[0127] In step S240: multiple fault domains are converged to form a convergence domain.

[0128] There are many methods for converging multiple fault domains in this application. For example, this application can design alarm information merging rules for multiple alarm information based on the strategy association rules, and converge the fault domains based on the alarm information merging rules. Figure 3 , experts or operators found in actual operation that when the container A and container B of the third Pod333 simultaneously fail due to an error in the IP address of the Pod, the failure does not occur on container A and container B, but on the parent node third Pod333 corresponding to container A and container B. Therefore, this application can merge a series of fault determination rules based on the experience of experts and operators to form an alarm information merging rule. And the alarm information merging rule is stored in the server 130 or the terminal device 110. When the server 130 or the terminal device 110 identifies multiple alarm information in the alarm information merging rule, the multiple fault domains can be converged to form a convergence domain. The convergence domain refers to the parent node of multiple fault domains. For example, when the server 130 or the terminal device 110 determines that multiple alarm information is that the container A and container B of the third Pod333 simultaneously fail due to an error in the IP address of the Pod, the fault domains located on the container A and container B of the third Pod333 can be converged to the fault domain located on the third Pod333 to form a convergence domain.

[0129] Therefore, through the above method, the present application can realize automatic fault location and improve the efficiency of fault location. However, the above method needs to rely on the alarm information merging rule. When the alarm information that appears is new information, that is, the alarm information is not in the alarm information merging rule, the above method cannot locate the fault location well. For example, Figure 7 As shown, Figure 7 The structure diagram of another fault domain of the present application is schematically shown. Figure 7 The corresponding fault domain includes a third service node 710 and three Pods, namely PodA720, PodB730 and PodC740. Among them, the alarm information contents of the three Pods are that PodA cannot pull the image, PodB cannot pull the image and PodC cannot pull the image. However, the alarm information for pulling the image is not included in the alarm information merging rules. Therefore, this application cannot effectively converge these three fault domains. In order to further solve the above problems, this application proposes another method of converging multiple fault domains to form a convergence domain.

[0130] In one embodiment of the present application, Figure 8 As shown, Figure 8The flow chart of the method for forming a convergence domain of the present application is schematically shown. The method for converging multiple fault domains to form a convergence domain includes steps S810 to S830.

[0131] Step S810: parse multiple fault warning information to obtain warning contents of multiple fault warning information.

[0132] By parsing multiple fault warning information, the fault warning content and warning attribute information of the multiple fault warning information can be obtained, wherein the fault warning content and warning attribute information can be used as the data basis for similarity comparison of multiple fault warning information.

[0133] Step S820: If there are no other nodes other than the fault domain to be converged under the parent node of the fault domain to be converged, then determine the similarity relationship between the alarm contents of each fault domain in the fault domain to be converged.

[0134] The failure domain to be converged in the present application includes at least two failure domains with the same parent node among multiple failure domains. Figure 6 and Figure 7 , Figure 6 The first fault domain 610 and the second fault domain 620 constitute the fault domain to be converged, and Figure 7 The fault domain composed of PodA720, PodB730 and PodC740 also constitutes the fault domain to be converged. Figure 6 There is only one third fault domain 630, which is insufficient in number. Therefore, it is not a fault domain to be converged.

[0135] After the fault domain to be converged is determined, it is further determined whether there are other nodes other than the fault domain to be converged under the parent node of the fault domain to be converged.

[0136] According to the characteristics of hierarchical management of container cluster systems, the idea that a parent node failure will cause a child node failure. In one embodiment of the present application, if the parent node of the fault domain to be converged has other nodes other than the fault domain to be converged, the fault domain to be converged will be used as the convergence domain. Due to the characteristics of hierarchical management of container cluster systems, if the parent node has other nodes other than the fault domain to be converged, it means that the fault is not from the parent node. Therefore, at this time, the fault domain of the fault domain to be converged cannot be converged, and the fault domain to be converged will be directly used as the convergence domain. The corresponding fault location is on the fault domain to be converged.

[0137] If the parent node of the fault domain to be converged does not have other nodes other than the fault domain to be converged, the fault of the fault domain to be converged may come from its parent node. However, if the fault domain to be converged is directly converged, the parent node may not be faulty, but each fault domain in the fault domain to be converged may fail. Therefore, in order to avoid fault location errors, the present application can continue to determine the similarity relationship of the alarm content of each fault domain in the fault domain to be converged, and then proceed to step S830.

[0138] Step S830: If the alarm contents of each fault domain in the fault domain to be converged are similar, converge the fault domain to be converged, and use the parent node as the convergence domain of the fault domain to be converged; wherein the fault domain to be converged includes at least two fault domains with the same parent node among the multiple fault domains.

[0139] When the alarm contents of each fault domain in the fault domain to be converged are similar, it means that the probability of a problem with its parent node is very high, because it is rare for similar alarm contents to appear at the same time for different fault domains. Therefore, if this happens, it is highly likely that their common parent node has a fault. Therefore, when the present application makes a convergence judgment, each fault domain with similar alarm contents in the fault domain to be converged is converged, and the parent node of the fault domain to be converged is used as the convergence domain of the fault domain to be converged, and the fault location can be determined accordingly.

[0140] In one embodiment of the present application, when the alarm contents of each fault domain in the fault domain to be converged are similar as in step S830, the present application can also record each fault domain in the fault domain to be converged and the corresponding parent node, and use the parent node as the convergence domain of the fault domain to be converged, thereby forming a new convergence rule, and the rule can be updated to the alarm information merging rule. If the same alarm information appears again next time, convergence can be performed directly to determine the fault location without repeating the contents of steps S810-step S830, thereby effectively improving the fault location efficiency.

[0141] Among them, other fault domains outside the to-be-converged fault domain can automatically be used as convergence domains, because these fault domains exist independently and have no common parent node, indicating that the fault occurs in them. Figure 6 The third fault domain 630 in.

[0142] Among them, the method for similarity judgment in this application can utilize the following method.

[0143] In one embodiment of the present application, Fig. 9 As shown, Fig. 9 The method for calculating the similarity relationship of the alarm contents of the to-be-converged fault domain of the present application is schematically shown, including steps S910 to S930.

[0144] Step S910: Convert the alarm content of the to-be-converged fault domain into a character string.

[0145] The conversion here can include the content of the alarm attribute information in the conversion, and can concatenate the various strings. For example, if the alarm content is that the image cannot be pulled, the alarm time is 0 o'clock, and the alarm ID is 001, then these information can be concatenated to form the string "Unable to pull the image 0 o'clock 001". This application can also obtain the above information separately to form multiple strings, that is, to form the strings corresponding to "Unable to pull the image", "0 o'clock" and "001".

[0146] Step S920: Calculate the similarity of the alarm contents of each fault domain in the to-be-converged fault domain using a string similarity algorithm.

[0147] This application can use the edit distance algorithm as a string similarity algorithm. The edit distance (Minimum Edit Distance, MED), also known as the Levenshtein distance, refers to the minimum number of editing operations required to convert one string into another. Allowed editing operations include: replacing one character with another character (substitution, s), inserting a character (insert, i) or deleting a character (delete, d). In the Levenshtein algorithm, the default distance required to add and delete a character is 1, and the distance required to modify a character is 2. The final D(n, m) is the minimum edit distance between the strings X[0...n] and Y[0...m].

[0148] Of course, this application can also use other string similarity algorithms, such as converting characters into vectors and then calculating the similarity of the vectors.

[0149] The present application can calculate the similarity of the string after the alarm content is spliced, or can calculate the similarity of each string separately, and then calculate the average value. Of course, the present application can also set different weights for different strings to calculate the average value of the similarity.

[0150] After obtaining the alarm content similarity of each fault domain in the to-be-converged fault domain through the above method, step S930 may be continued.

[0151] Step S930: If the similarity of the alarm contents of each fault domain in the to-be-converged fault domain is greater than a set threshold, the alarm contents of each fault domain in the to-be-converged fault domain are similar.

[0152] A threshold may be set based on actual conditions. In one embodiment of the present application, different thresholds corresponding to different fault domains to be converged may be different. For example, if the parent node of the fault domain to be converged is a service node, its threshold value must be higher than the fault domain to be converged whose parent node is a Pod.

[0153] When the alarm content similarity of each fault domain in the fault domain to be converged is greater than the set threshold, it means that the alarm content of each fault domain in the fault domain to be converged is similar. At this time, the parent node of the converged fault domain can be used as the convergence domain of the fault domain to be converged.

[0154] In one embodiment of the present application, if the alarm contents of each fault domain in the fault domain to be converged are not similar, the fault domain to be converged is used as the convergence domain. This means that the fault of each fault domain in the fault domain to be converged occurs in itself, rather than on its parent node. Therefore, each fault domain in the fault domain to be converged can be directly used as the convergence domain.

[0155] After the convergence region is determined by the above method, the process proceeds to step S250.

[0156] In step S250: the fault location is determined according to the convergence region.

[0157] Once the position of the convergence domain is determined, the position corresponding to the convergence domain is the fault location.

[0158] For example, Fig.10 As shown, Fig.10 The following schematically shows a structural diagram of a convergence region of the present application. Figure 6 Based on the corresponding fault domain, when the alarm contents of the first fault domain 610 and the second fault domain 620 are similar, the parent node of the first fault domain 610 and the second fault domain 620 is used as the convergence domain to form the first convergence domain 1010. Since the third fault domain 630 exists alone, the corresponding third fault domain 630 forms the second convergence domain 1020. At this time, the position corresponding to the first convergence domain 1010 and the second convergence domain 1020 is the position where the fault occurs, that is, the fault occurs on the container A of the first Pod 331 and the second Pod 332.

[0159] In the technical solution provided in the embodiment of the present application, the present application obtains the container cluster management architecture and multiple fault alarm information, and constructs a container cluster management tree based on the container cluster management architecture; multiple alarm information is marked on the container cluster management tree to form multiple fault domains, and multiple fault domains are converged to form a convergence domain, and finally the location of the fault is determined according to the convergence domain. Using the method of the present application, the location of the fault in the container cluster management system can be determined after converging according to the location of multiple fault alarm information in the container cluster management system on the container cluster management tree, and the fault location can be automatically located without manual judgment. Moreover, the present application can cover abnormal events and faults outside the alarm rules, realize rapid location of faults, and ensure the normal use of the container cluster management system.

[0160] Furthermore, the present application uses a string similarity algorithm to converge multiple fault domains to form a convergence domain, and converges the faults of multiple child nodes through a string similarity algorithm to determine the fault location. The present application makes full use of the characteristics of hierarchical management of container clusters. According to the idea that the failure of the parent node will cause the failure of the child node, the accuracy of the container cluster management system in determining the fault location can be improved.

[0161] The method corresponding to this patent makes full use of the characteristics of hierarchical management of container clusters. Based on the idea that the failure of the parent node will cause the failure of the child node, the cluster management tree is constructed. Based on the node position of the tree and the similarity of the alarm information, the step-by-step convergence of the fault domain is achieved, and the location of the fault is finally determined. The method of this application can quickly locate the fault, improve the efficiency of fault location, and can locate the fault of the alarm information outside the alarm information merging rules. It is more applicable and is conducive to the use of container cluster management.

[0162] It should be noted that although the steps of the method in the present application are described in a specific order in the drawings, this does not require or imply that the steps must be performed in this specific order, or that all the steps shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps, etc.

[0163] The above part introduces the content of the data fault locating method of the present application, and the following part will continue to introduce the content of the fault locating device of the present application.

[0164] According to another aspect of the embodiment of the present application, Fig.11 As shown, Fig.11 The present application provides a fault location device 1100, comprising:

[0165] An acquisition module 1110 is used to acquire a container cluster management architecture and multiple fault alarm information;

[0166] A construction module 1120 is used to construct a container cluster management tree based on the container cluster management architecture;

[0167] A marking module 1130 is used to mark multiple alarm information on the container cluster management tree to form multiple fault domains, where the fault domain includes a location on the container cluster management tree containing the alarm information;

[0168] A convergence module 1140, configured to converge multiple fault domains to form a convergence domain;

[0169] The positioning module 1150 is used to determine the fault location according to the convergence domain.

[0170] In one embodiment of the present application, the container cluster management architecture includes a control node, a service node, a sub-unit and a container, and the construction module 1120 includes:

[0171] The construction unit is used to build a container cluster management tree based on the hierarchical relationship among control nodes, service nodes, sub-units and containers, with the control node as the initial node, according to the hierarchical relationship.

[0172] In one embodiment of the present application, the marking module 1130 includes:

[0173] A subject parsing unit, used for parsing multiple fault alarm information and obtaining alarm subjects of multiple fault alarm information;

[0174] The marking unit is used to mark multiple fault alarm information respectively on the tree nodes corresponding to the alarm subjects in the container cluster management tree.

[0175] In some embodiments of the present application, based on the above technical solution, the convergence module 1140 includes:

[0176] A content analysis unit, used for analyzing multiple fault alarm information and obtaining alarm contents of multiple fault alarm information;

[0177] If there is no other node other than the fault domain to be converged under the parent node of the fault domain to be converged, then the similarity relationship of the alarm contents of each fault domain in the fault domain to be converged is determined;

[0178] A convergence unit, configured to converge the fault domain to be converged when the alarm contents of each fault domain in the fault domain to be converged are similar, and use the parent node as the convergence domain of the fault domain to be converged;

[0179] The fault domains to be converged include at least two fault domains having the same parent node among the multiple fault domains.

[0180] In some embodiments of the present application, based on the above technical solution, the convergence unit includes:

[0181] A character conversion unit, used for converting the alarm content of the fault domain to be converged into a character string;

[0182] A similarity calculation unit, used to calculate the similarity of the alarm contents of each fault domain in the fault domain to be converged by using a string similarity algorithm;

[0183] The similarity determination unit is used to determine that the alarm contents of each fault domain in the to-be-converged fault domain are similar when the similarity of the alarm contents of each fault domain in the to-be-converged fault domain is greater than a set threshold.

[0184] In some embodiments of the present application, based on the above technical solution, the convergence module 1140 further includes:

[0185] A content analysis unit, used for analyzing multiple fault alarm information and obtaining alarm contents of multiple fault alarm information;

[0186] A convergence conversion unit, configured to use the to-be-converged fault domain as a convergence domain when there are other nodes other than the to-be-converged fault domain at the subordinate level of the parent node of the to-be-converged fault domain;

[0187] The fault domains to be converged include at least two fault domains having the same parent node among the multiple fault domains.

[0188] In some embodiments of the present application, based on the above technical solution, the convergence module 1140 further includes:

[0189] A content analysis unit, used for analyzing multiple fault alarm information and obtaining alarm contents of multiple fault alarm information;

[0190] A similarity judgment unit, configured to judge the similarity relationship of the alarm contents of each fault domain in the fault domain to be converged when there is no other node other than the fault domain to be converged at the subordinate level of the parent node of the fault domain to be converged;

[0191] A convergence replacement unit, configured to use the to-be-converged fault domain as a convergence domain when alarm contents of various fault domains in the to-be-converged fault domain are not similar;

[0192] The fault domains to be converged include at least two fault domains having the same parent node among the multiple fault domains.

[0193] The specific details of the fault location device provided in each embodiment of the present application have been described in detail in the corresponding method embodiment, and will not be repeated here.

[0194] The above part introduces the content of the data similarity calculation device of this application, and the following will continue to introduce other aspects of this application.

[0195] According to one aspect of an embodiment of the present application, a computer-readable medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the fault location method in the above technical solution is implemented.

[0196] According to one aspect of an embodiment of the present application, an electronic device is provided, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute the fault location method in the above technical solution by executing the executable instructions.

[0197] According to one aspect of the embodiments of the present application, a computer program product or a computer program is provided, the computer program product or the computer program includes computer instructions, the computer instructions are stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the fault location method in the above technical solution.

[0198] Fig.12 The structure block diagram of a computer system for implementing an electronic device according to an embodiment of the present application is schematically shown.

[0199] It should be noted that Fig.12 The computer system 1200 of the electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0200] like Fig.12 As shown, the computer system 1200 includes a central processing unit 1201 (CPU), which can perform various appropriate actions and processes according to the program stored in the read-only memory 1202 (ROM) or the program loaded from the storage part 1208 to the random access memory 1203 (RAM). Various programs and data required for system operation are also stored in the random access memory 1203. The central processing unit 1201, the read-only memory 1202 and the random access memory 1203 are connected to each other through a bus 1204. The input / output interface 1205 (Input / Output interface, i.e., I / O interface) is also connected to the bus 1204.

[0201] The following components are connected to the input / output interface 1205: an input section 1206 including a keyboard, a mouse, etc.; an output section 1207 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 1208 including a hard disk, etc.; and a communication section 1209 including a network interface card such as a LAN card, a modem, etc. The communication section 1209 performs communication processing via a network such as the Internet. A drive 1210 is also connected to the input / output interface 1205 as needed. A removable medium 1211, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1210 as needed so that a computer program read therefrom is installed into the storage section 1208 as needed.

[0202] In particular, according to an embodiment of the present application, the process described in each method flow chart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer readable medium, and the computer program contains a program code for executing the method shown in the flow chart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 1209, and / or installed from the removable medium 1211. When the computer program is executed by the central processor 1201, various functions defined in the system of the present application are executed.

[0203] It should be noted that the computer-readable medium shown in the embodiment of the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, a system, device or device of electricity, magnetism, light, electromagnetic, infrared, or semiconductor, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by an instruction execution system, device or device or used in combination with it. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, wherein a computer-readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer readable signal media may also be any computer readable medium other than computer readable storage media, which may send, propagate, or transmit programs for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on the computer readable medium may be transmitted using any suitable medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0204] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the above-mentioned module, program segment or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0205] It should be noted that, although several modules or units of the equipment for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present application, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into being embodied by multiple modules or units.

[0206] Through the description of the above implementation methods, it is easy for those skilled in the art to understand that the example implementation methods described here can be implemented by software or by combining software with necessary hardware. Therefore, the technical solution according to the implementation methods of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a touch terminal, or a network device, etc.) to execute the method according to the implementation methods of the present application.

[0207] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary technical means in the art that are not disclosed in the present application.

[0208] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A fault location method, characterized in that: include: Obtain container cluster management architecture and multiple fault alarm information; Based on the container cluster management architecture, construct a container cluster management tree; Parse the multiple fault alarm information, obtain the alarm subjects and alarm contents of the multiple fault alarm information, and mark the multiple fault alarm information on the tree nodes corresponding to the alarm subjects in the container cluster management tree, respectively, to form multiple fault domains, wherein the fault domains include the locations containing the fault alarm information on the container cluster management tree; If there is no other node other than the fault domain to be converged at the subordinate level of the parent node of the fault domain to be converged, then determine the similarity relationship of the alarm contents of each fault domain in the fault domain to be converged; wherein the fault domain to be converged includes at least two fault domains with the same parent node among the multiple fault domains; If the alarm contents of each fault domain in the to-be-converged fault domain are similar, converge the to-be-converged fault domain, and use the parent node as the convergence domain of the to-be-converged fault domain; The fault location is determined according to the convergence domain, wherein the location corresponding to the convergence domain is the fault location.

2. The fault location method according to claim 1, characterized in that: The container cluster management architecture includes a control node, a service node, a sub-unit and a container. Based on the container cluster management architecture, a container cluster management tree is constructed, including: Based on the hierarchical relationship among control nodes, service nodes, sub-units and containers, the control node is used as the initial node, and the container cluster management tree is constructed in sequence according to the hierarchical relationship.

3. The fault location method according to claim 1, characterized in that: Determining the similarity relationship of the alarm contents of the to-be-converged fault domain includes: Convert the alarm content of the to-be-converged fault domain into a character string; Calculating the similarity of the alarm contents of each fault domain in the to-be-converged fault domain by using a string similarity algorithm; If the similarity of the alarm contents of each fault domain in the to-be-converged fault domain is greater than a set threshold, the alarm contents of each fault domain in the to-be-converged fault domain are similar.

4. The fault location method according to claim 1, characterized in that: The method further comprises: If there are other nodes other than the fault domain to be converged at the subordinate level of the parent node of the fault domain to be converged, the fault domain to be converged is used as the convergence domain.

5. The fault location method according to claim 1, characterized in that: The method further comprises: If there is no other node other than the fault domain to be converged at the subordinate level of the parent node of the fault domain to be converged, then determining the similarity relationship of the alarm contents of each fault domain in the fault domain to be converged; If the alarm contents of each fault domain in the to-be-converged fault domain are not similar, the to-be-converged fault domain is used as the convergence domain.

6. A fault location device, characterized in that: include: The acquisition module is used to obtain the container cluster management architecture and multiple fault alarm information; A construction module, used to construct a container cluster management tree based on the container cluster management architecture; a marking module, configured to parse the plurality of fault alarm information, obtain alarm subjects and alarm contents of the plurality of fault alarm information, and mark the plurality of fault alarm information respectively on tree nodes corresponding to the alarm subjects in the container cluster management tree to form a plurality of fault domains, wherein the fault domains include positions on the container cluster management tree containing the fault alarm information; A convergence module, configured to determine the similarity relationship of the alarm contents of each fault domain in the fault domain to be converged if there is no other node other than the fault domain to be converged at the subordinate level of the parent node of the fault domain to be converged; wherein the fault domain to be converged includes at least two fault domains with the same parent node among the multiple fault domains; The convergence module is further configured to converge the fault domain to be converged and use the parent node as the convergence domain of the fault domain to be converged if the alarm contents of each fault domain in the fault domain to be converged are similar; A positioning module is used to determine the fault location according to the convergence domain, wherein the location corresponding to the convergence domain is the fault location.

7. A computer-readable medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the fault location method according to any one of claims 1 to 5.

8. An electronic device, characterized in that: include: processor; as well as A memory, configured to store executable instructions of the processor; The processor is configured to execute the fault location method according to any one of claims 1 to 5 by executing the executable instructions.

Images