Network fault positioning method and device, electronic equipment and storage medium
By acquiring and analyzing the detection data of key nodes on the target request link from the client to the server, the accuracy of network failure location is solved, and the fault nodes are quickly identified and network stability is improved.
Patent Information
- Application Number
- CN202510134469.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-02-07
- Publication Date
- 2025-06-13
AI Technical Summary
During the process of the client requesting application services, if the network node fails, the failed node cannot be located in the requested link in a timely and accurate manner, affecting network stability.
By obtaining the target detection data of multiple key nodes on the corresponding target request link of the client to the server, the access success rate of the first key node and the target detection success rate of the second key node at the target moment are determined, and when the access success rate is lower than the threshold, a faulty node is determined from the multiple key nodes based on the target detection success rate.
It realizes that when the client access success rate decreases, network failure nodes are accurately and timely judged, improves the comprehensiveness and accuracy of network failure judgments, and reduces the losses caused by network failures.
Smart Images

Figure CN120151185A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of network technologies, and in particular, to a method, apparatus, electronic device, and storage medium for network fault location. Background Art
[0002] With the development of Internet technologies, more and more application services rely on the network to complete information interaction. During the process of a client requesting an application service, information exchange among multiple nodes or devices is involved in the entire request link. If one or more of these nodes fail, the client's request for the application service will fail. Therefore, how to locate the faulty node in a timely and accurate manner is an urgent problem to be solved to ensure the stability of the entire request link. Summary of the Invention
[0003] This application provides a method, apparatus, electronic device, and storage medium for network fault location. The technical solutions are as follows:
[0004] According to one aspect of this application, a method for network fault location is provided. The method includes:
[0005] Obtaining target detection data of multiple key nodes on a target request link from a client to a server, where the multiple key nodes include a client node, intermediate nodes, and a server node, and the intermediate nodes include at least one of an external network node, an internal network node, an access layer node, and a network device node;
[0006] Based on the target detection data, determining the access success rate of a first key node and the target detection success rate of a second key node at a target moment, where the first key node is the client node, and the second key node is other key nodes except the client node;
[0007] In the case where the access success rate is lower than an access threshold, determining a faulty node from the multiple key nodes based on the target detection success rate.
[0008] According to another aspect of this application, a network fault location apparatus is provided. The apparatus includes:
[0009] An obtaining module, configured to obtain target detection data of multiple key nodes on a target request link from a client to a server, where the multiple key nodes include a client node, intermediate nodes, and a server node, and the intermediate nodes include at least one of an external network node, an internal network node, an access layer node, and a network device node;
[0010] A first determination module, configured to determine the access success rate of a first key node and the target detection success rate of a second key node at a target moment based on the target detection data, where the first key node is the client node, and the second key node is other key nodes except the client node;
[0011] A second determination module, configured to determine a faulty node from the multiple key nodes based on the target detection success rate when the access success rate is lower than an access threshold.
[0012] According to one aspect of the present application, there is provided an electronic device, including: a processor and a memory storing a program, where the program includes instructions that, when executed by the processor, cause the processor to execute the network fault location method as described above.
[0013] According to another aspect of the present application, there is provided a non-transitory computer-readable storage medium storing computer instructions for causing a computer to execute the network fault location method as described above.
[0014] According to another aspect of the present application, there is provided a computer program product, which includes computer instructions 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 above-mentioned network fault location method.
[0015] The beneficial effects brought by the technical solution provided by the embodiments of the present application at least include:
[0016] The embodiments of the present application provide a network fault location method: by obtaining target detection data of each key node on the target request link from the client to the server, and based on the target detection data, determining the access success rate of the first key node and the target detection success rate of the second key node at the target moment; further, when the access success rate of the client node is lower than the access threshold, determining a faulty node from the multiple key nodes based on the target detection success rate of the second key node. Since the detection success rates of each key node on the target request link are obtained and statistically analyzed in advance, it is possible to accurately and timely determine the faulty node of the network when the access success rate of the client decreases, improve the comprehensiveness and accuracy of network fault judgment, and thus reduce the losses caused by network faults. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] In the following description of exemplary embodiments with reference to the accompanying drawings, more details, features, and advantages of the present application are disclosed. In the drawings:
[0018] Figure 1Shows a schematic structural diagram of a network fault location system provided by an exemplary embodiment of the present application;
[0019] Figure 2 Shows a flowchart of a network fault location method according to an exemplary embodiment of the present application;
[0020] Figure 3 Shows a schematic structural diagram of a fault detection module provided by an exemplary embodiment of the present application;
[0021] Figure 4 Shows a flowchart of another network fault location method according to an exemplary embodiment of the present application;
[0022] Figure 5 Shows a flowchart of another network fault location method according to an exemplary embodiment of the present application;
[0023] Figure 6 Shows a flowchart of another network fault location method according to an exemplary embodiment of the present application;
[0024] Figure 7 Shows a flowchart of another network fault location method according to an exemplary embodiment of the present application;
[0025] Figure 8 Is a schematic diagram of a target display interface provided by an exemplary embodiment of the present application;
[0026] Figure 9 Is a complete flowchart of fault node location provided by an exemplary embodiment of the present application;
[0027] Figure 10 Is a schematic structural diagram of a network fault location device provided by an embodiment of the present application;
[0028] Figure 11 Shows a structural block diagram of an exemplary electronic device that can be used to implement the embodiments of the present disclosure. Detailed Description of the Invention
[0029] Embodiments of the present application will be described in more detail below with reference to the accompanying drawings. Although some embodiments of the present application are shown in the drawings, it should be understood that the present application can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Instead, these embodiments are provided to more thoroughly and completely understand the present application. It should be understood that the drawings and embodiments of the present application are only for exemplary purposes and are not used to limit the protection scope of the present application.
[0030] It should be understood that the various steps described in the method embodiments of the present application may be executed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present application is not limited in this regard.
[0031] As used herein, the term "including" and its variants are open-ended, that is, "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". The relevant definitions of other terms will be given in the following description. It should be noted that the concepts such as "first" and "second" mentioned in the present application are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units. It should be noted that the modifications of "one" and "multiple" mentioned in the present application are illustrative rather than restrictive. Those skilled in the art should understand that unless clearly indicated otherwise in the context, it should be understood as "one or more". The names of the messages or information exchanged between multiple devices in the embodiments of the present application are only for illustrative purposes and are not used to limit the scope of these messages or information.
[0032] The solution of the present invention will be described below with reference to the drawings. The technical solutions provided by the embodiments of the present invention will be described in detail through specific embodiments and their application scenarios.
[0033] Aiming at the problem that the fault source cannot be accurately located in a timely manner in the related network fault detection method, the present application monitors the entire request link of the user client's request for services in all directions and aggregates the detection data to locate the fault efficiently and accurately. Figure 1 The structural schematic diagram of the network fault location system provided by the exemplary embodiment of the present application is shown. As Figure 1 shown, the network fault location system 100 includes three major parts: a fault detection module 110, a fault location module 120, and a visualization module 130. The fault detection module 110 is used to detect multiple key nodes involved in the process of the user client accessing the service, and report the detected detection data to the fault location module 120; the fault location module 120 performs aggregation calculation on the detected detection data reported, and finally locates the node where the fault occurs; the visualization module 130 reads the data calculated by the fault location module 120 and performs visualization display.
[0034] It should be noted that since the fault detection module 110 needs to detect each key node, the fault detection module 110 is generally deployed at each key node or at a device close to the key node. The fault location module 120 and the visualization module 130 can be integrated into the same device, for example, a network fault location device or a network monitoring device.
[0035] Please refer to Figure 2 , which shows a flowchart of a network fault location method according to an exemplary embodiment of the present application. This method is described by taking its application to a network fault location device as an example. As Figure 2 shown, the method includes:
[0036] Step 201, obtain target detection data of multiple key nodes on the target request link from the client to the server. The multiple key nodes include a client node, an intermediate node, and a server node. The intermediate node includes at least one of an external network node, an internal network node, an access layer node, and a network device node.
[0037] In the entire request link where the user client accesses the server, the key nodes involved usually include the user's terminal device (which can also be called the client), the operator's public network, the enterprise internal network, the access layer, the enterprise internal network devices (such as switches, routers, etc.), and the service that finally processes the request, etc. When any one of these key nodes is abnormal, it will cause the user client to be unable to access the service. In order to timely detect and locate the abnormalities of each key node, it is necessary to detect each key node. And because the locations of each key node are different, it is necessary to deploy relevant detection points at each key node or at a device near the key node. Therefore, as Figure 3 shown, the fault detection module 110 further includes multiple sub-modules: a user terminal detection sub-module 301, an external network detection sub-module 302, an internal network detection sub-module 303, an access layer detection sub-module 304, a network detection sub-module 305, and a service detection sub-module 306.
[0038] Among them, the user terminal detection sub-module is deployed on the client side and is used to detect whether each service request of the client is successful; the external network detection sub-module is used to be deployed in the devices of operators in each region and is used to detect whether the service request directly through the operator network is successful (that is, the request does not pass through the client); the internal network detection sub-module is used to be deployed in the internal devices covered by the enterprise internal network and is used to detect whether the service request directly through the enterprise internal network is successful (that is, the request does not pass through the client and the operator external network); the access layer detection sub-module is deployed in the devices covered by the enterprise internal network and close to the server where the access layer is located and is used to detect whether the access layer can successfully receive the request; the network detection sub-module is deployed in the devices covered by the enterprise internal network and close to each network device and is used to detect whether these network devices (the network devices can be load balancing devices, routers, switches, etc.) can successfully receive the request; the service detection sub-module is deployed in the devices covered by the enterprise internal network and close to each service providing device and is used to detect whether the service that provides functions for users has an abnormality itself.
[0039] Since there are differences in the target request links passed by the client to request different services, which may be caused by different enterprise internal service architectures or rules. For example, there is no access layer deployed in some enterprises, and there is no need to forward through the access layer during the process of the client requesting services. Then, in the fault location scenario, the sub-modules included in the fault detection module may be different. For example, in the case where there is no need to forward through the access layer, there is no need to deploy the access layer detection sub-module. Therefore, during the fault location process, it is first necessary to determine multiple key nodes included in the target request link from the client to the server, and then obtain the detection data at each key node for subsequent fault node location when the request fails. Among them, the multiple key nodes include the client node, the intermediate node, and the server node, and the intermediate node includes at least one of the external network node, the internal network node, the access layer node, and the network device node. The client node corresponds to the user terminal detection sub-module, the external network node corresponds to the deployment of the external network detection sub-module, the internal network node corresponds to the deployment of the internal network detection sub-module, the access layer node corresponds to the deployment of the access layer detection sub-module, the network device node corresponds to the deployment of the network detection sub-module, and the server node corresponds to the deployment of the service detection sub-module.
[0040] In a possible implementation manner, the fault detection sub-modules corresponding to multiple key nodes on the target request link from the client to the server will detect whether the corresponding target request is successful in real time, and report the target detection data to the network fault location device. The corresponding network fault location device will obtain the target detection data of each key node, and the fault location module in the network fault location device will analyze the target detection data so as to accurately locate the fault node in the target request link based on the target detection data in a timely manner when the user client access fails.
[0041] Exemplarily, taking the target request link including a client node, an external network node, an internal network node, an access layer node, a network device node, and a server node as an example, the user terminal detection sub-module corresponding to the client node will report in real time whether each service request of the user client is successful. When the client accesses the service and fails or times out, the user terminal detection sub-module will record the terminal device model of the user client this time, the region and network operator where the user client is located, the APP (application) version number used by the user client, the requested domain name, the request time, and the failure reason, and report the above target detection data to the network fault location device; the external network detection sub-module corresponding to the external network node will simulate in real time whether the request to the server through the operator network is successful (i.e., the request does not pass through the client), and report the request result as the target detection data to the network fault location device; the internal detection sub-module corresponding to the internal network node will simulate in real time whether the request to the service through the enterprise internal network is successful (i.e., the request does not pass through the client and the operator external network), and report the request result as the target detection data to the network fault location device; the access layer detection sub-module corresponding to the access layer node will simulate in real time sending a request to the access layer to detect whether the access layer can successfully receive the request, and report the request result as the target detection data to the network fault location device; the network detection sub-module corresponding to the network device node will simulate in real time sending a request to the corresponding network device to detect whether the network device can successfully receive the request, and report the request result as the target detection data to the network fault location device; the service detection sub-module corresponding to the server node will trigger the service to execute its own function in real time to determine whether the service itself has an abnormality, and report the request result as the target detection data to the network fault location device.
[0042] Optionally, on the target request link from the client to the server, all intermediate nodes may be included, that is, the multiple key nodes on the target request link include: the client node, the external network node, the internal network node, the access layer node, the network device node, and the server node; or some intermediate nodes may be included. For example, in some company internal service architectures, there is no access layer, and the multiple key nodes on the corresponding target request link are: the client node, the external network node, the internal network node, the network device node, and the server node.
[0043] Step 202, based on the target detection data, determine the access success rate of the first key node and the target detection success rate of the second key node at the target moment. The first key node is the client node, and the second key node is other key nodes except the client node.
[0044] After the network fault location device receives the target detection data reported by the fault detection sub-modules corresponding to each key node, it will calculate the request success rate at each moment based on the target detection data. Since the target detection data reported by the client node is the request result corresponding to the real access request, while the target detection data reported by other key nodes are all the request results corresponding to the simulated requests, the request success rate determined based on the target detection data can include the access success rate of the first key node (i.e., the client node) and the target detection success rate of the second key node. The second key node is other key nodes except the client node.
[0045] Regarding the determination method of the access success rate: the fault location module will calculate the target detection data reported by multiple user terminal detection sub-modules at the target moment to determine the number of successful accesses (or failed accesses) and the total number of accesses of multiple client nodes accessing the same server, and then determine the access success rate based on the ratio of the number of successful accesses to the total number of accesses; or, first determine the number of successful accesses according to the difference between the number of failed accesses and the total number of accesses, and then determine the access success rate according to the ratio of the number of successful accesses to the total number of accesses.
[0046] Similar to the determination method of the access success rate, when determining the target detection success rate, the fault location module will also calculate the target detection data reported by multiple external network detection sub-modules at the target moment to determine the number of successful detections (or failed detections) and the total number of detections for each second key node, and then determine the detection success rate based on the ratio of the number of successful detections to the total number of detections; or, first determine the number of successful detections according to the difference between the number of failed detections and the total number of detections, and then determine the detection success rate according to the ratio of the number of successful detections to the total number of detections.
[0047] Taking the second key node including external network nodes, internal network nodes, access layer nodes, network device nodes, and server nodes as an example, the target detection success rate includes the first detection success rate corresponding to the external network nodes, the second detection success rate corresponding to the internal network nodes, the third detection success rate corresponding to the access layer nodes, the fourth detection success rate corresponding to the network device nodes, and the fifth detection success rate corresponding to the server nodes.
[0048] Step 203, in the case where the access success rate is lower than the access threshold, based on the target detection success rate, determine the faulty node from multiple key nodes.
[0049] To determine whether there is a network access failure, an access threshold is set. When the access success rate at the target moment obtained by statistics is lower than the access threshold, it indicates that there is a faulty node in the target request link for the client to access the server. Since the target detection success rates of other second key nodes are obtained in advance, the faulty node can be further determined from multiple key nodes based on the target detection success rates of other second key nodes.
[0050] In an ideal state, when there is no network failure, the access success rate of the client accessing the server should be 100%, so the access threshold can be set to 100%. Optionally, to avoid accidental errors, when there is no network failure, the access success rate of the client accessing the server may not reach 100%, then the access threshold can be set according to historical access situations. For example, the access threshold can be 98%.
[0051] In summary, the embodiment of the present application provides a network fault location method: by obtaining the target detection data of each key node on the target request link from the client to the server, and based on the target detection data, determining the access success rate of the first key node and the target detection success rate of the second key node at the target moment; furthermore, when the access success rate of the client node is lower than the access threshold, based on the target detection success rate of the second key node, the faulty node is determined from multiple key nodes. Since the detection success rates of each key node on the target request link are obtained and statistically analyzed in advance, it is possible to accurately and timely determine the faulty node of the network when the access success rate of the client decreases, improve the comprehensiveness and accuracy of network fault judgment, and thus reduce the losses caused by network faults.
[0052] In the process of locating the faulty node based on the target detection success rate, considering the order of the client accessing the server as: client node ~ external network node ~ internal network node ~ access layer node ~ network device node ~ server node. Then in the process of locating the faulty node, the judgment is also carried out in this access order in turn.
[0053] Please refer to Figure 4 , which shows a flowchart of another network fault location method according to an exemplary embodiment of the present application. This method is described by taking its application to a network fault location device as an example. As Figure 4 shown, this method includes:
[0054] Step 401, obtain the target detection data of multiple key nodes on the target request link from the client to the server, where the multiple key nodes include a client node, intermediate nodes, and a server node, and the intermediate nodes include at least one of an external network node, an internal network node, an access layer node, and a network device node.
[0055] Step 402: Based on the target detection data, determine the access success rate of the first key node and the target detection success rate of the second key node at the target moment. The first key node is the client node, and the second key node is other key nodes except the client node.
[0056] For the implementation manners of Step 401 and Step 402, reference can be made to Step 201 and Step 202, which will not be elaborated in this embodiment.
[0057] Step 403: In the case where the access success rate is lower than the access threshold, obtain the first detection success rate of the external network node from the target detection success rate.
[0058] In the case where the access success rate of the client node is lower than the access threshold, since the client node needs to pass through the client node, the external network node, the internal network node, the access layer node, the network device node, and the server node when accessing the server, the failure of any of the corresponding key nodes may cause the access success rate to decrease. In order to accurately locate the faulty node, first obtain the first detection success rate corresponding to the external network node from the target detection success rate. Since the first detection success rate indicates the detection success rate of accessing the client without passing through the client and passing through the external network (operator network), the client node can be determined whether there is a fault based on the first detection success rate.
[0059] Optionally, in the case where the access success rate is greater than or equal to the access threshold, it indicates that the client can successfully access the server, corresponding to that there is no faulty node on the target request link from the client to the server, and the entire target request link is normal.
[0060] Step 404: If the first detection success rate is greater than or equal to the first detection threshold, determine the client node as the faulty node.
[0061] Among them, a first detection threshold is set to be used to determine whether the detection success rate of the external network node has decreased. Correspondingly, if it is determined that the first detection success rate is greater than or equal to the first detection threshold, it means that the server can be successfully accessed through the external network (operator network), that is, there is no network fault on the request link from the external network node to the server. In this case, the client cannot access the server, and only the client node may be faulty. Correspondingly, the client node can be determined as the faulty node.
[0062] Exemplarily, the first detection threshold can also be 100%.
[0063] In the case where the client node is determined to be a faulty node, since the access results of multiple clients at the target moment are counted when calculating the access success rate, there may be differences among multiple clients. For example, there are differences in the terminal models. Therefore, in order to more accurately locate a type of client with a fault, the fault location module also calculates the access success rate of each type of terminal, the access success rate of clients in each region, and the access success rate of each operator at the target moment based on the target detection data reported by each user terminal fault detection sub-module, so as to locate a certain type of client node with anomalies or faults from the more detailed access success rate data.
[0064] Exemplarily, if the fault location module statistically obtains that the access success rate of type A terminals is 95%, the access success rate of type B terminals is 100%, and the access success rate of type C terminals is 100%, then on the basis of determining that the faulty node is a client node, it can be further determined that there is an anomaly in type A terminals.
[0065] Step 405, if the first detection success rate is lower than the first detection threshold, based on the target detection success rate, determine the faulty node from the second key nodes.
[0066] On the contrary, if the first detection success rate is also lower than the first detection threshold, it indicates that the faulty node is not caused by the client node, but by the failure of the second key node on the request link from the external network node to the server node. Therefore, it is also necessary to further determine the faulty node from the second key nodes based on the target detection success rates of other second key nodes.
[0067] It should be noted that in the case where it is determined that the first detection success rate is also lower than the first detection threshold, it may be a client node failure or a failure of the second key node on the request link from the external network node to the server node. However, the network fault location method provided in the embodiments of the present application is designed on the premise that there is only a single node failure in the target access link. Therefore, it is defaulted that the client node is not a faulty node, but is caused by the failure of the second key node on the request link from the external network node to the server node, and it is necessary to further locate the faulty node from the second key nodes according to the target detection success rates of other subsequent second key nodes.
[0068] In this embodiment, in the case where it is determined that the access success rate of the client decreases, the first detection success rate of the external network node can be further obtained, and it is determined whether the first detection success rate decreases. If the first detection success rate does not decrease, it can be determined that there is no anomaly in the request link between the external network node and the server node, and the client node is further located as a faulty node; since the first detection success rate corresponding to the external network node excludes the influence of the client, the accuracy of locating the client as a faulty node can be guaranteed.
[0069] On the request link between the external network node and the server node, the following second key nodes are included: the external network node, the internal network node, the access layer node, the network device node, and the server node. It is necessary to further determine whether the target detection success rate of each second key node has decreased to locate the faulty node.
[0070] Based on Figure 4 as shown in Figure 5 Step 405 can be replaced by Steps 501 to 503.
[0071] Step 501, if the first detection success rate is lower than the first detection threshold, obtain the second detection success rate of the internal network node from the target detection success rate.
[0072] To exclude the influence of the network between the external network and the internal network, when the first detection success rate is lower than the first threshold, further obtain the second detection success rate of the internal network node from the target detection success rate. The second detection success rate of the internal network node is detected by excluding the influence of the client and the external network, so as to locate the faulty node by judging whether the second detection success rate is lower than the second detection threshold.
[0073] Step 502, if the second detection success rate is greater than or equal to the second detection threshold, determine the external network node as the faulty node.
[0074] If the second detection success rate is greater than or equal to the second detection threshold, it indicates that the request link between the internal network node and the server node is normal. The corresponding abnormal one should be the external network node, so the external network node is determined as the faulty node. Exemplarily, the second detection threshold can also be 100%.
[0075] Furthermore, after determining that the external network node is the faulty node, it is also possible to count the detection success rates of each operator network and the detection success rates of the external network in each region according to the target detection data reported by the external network detection module, so as to locate the specific operator network with anomalies or the operator network in a certain region. Specifically, if the detection success rate of a certain operator network is lower than the preset threshold, it can be determined that there is an anomaly in that operator network; or, if the detection success rate of the external network in a certain region is lower than the preset threshold, it can be determined that there is an anomaly in the external network of that region.
[0076] Step 503, if the second detection success rate is lower than the second detection threshold, determine the faulty node from the second key nodes based on the target detection success rate.
[0077] If the second detection success rate is also lower than the second detection threshold, it indicates that the problem may not be with the client node or the external network node, but rather with the request link between the internal network node and the server node. In this case, it is necessary to further locate the faulty node in the request link from the internal network node to the server node based on the target detection success rates of the access layer node, network device node, and server node.
[0078] In this embodiment, when it is determined that the access success rate of the client has decreased and the first detection success rate of the external network node has also decreased, the second detection success rate of the internal network node can be further obtained, and it is determined whether the second detection success rate has decreased. If the second detection success rate has not decreased, it can be determined that the external network node is the faulty node; since the first detection success rate corresponding to the internal network node excludes the influence of the client and the external network node, the accuracy of locating the external network node as the faulty node can be ensured.
[0079] The request link between the internal network node and the server node includes the following second key nodes: the access layer node, the network device node, and the server node. Then, it is necessary to further determine whether the target detection success rates of each second key node have decreased to locate the faulty node.
[0080] On Figure 5 this basis, as Figure 6 shown, step 503 can also be replaced by step 601 and step 602.
[0081] Step 601, if the second detection success rate is lower than the second detection threshold, obtain the third detection success rate of the access layer node, the fourth detection success rate of the network device node, and the fifth detection success rate of the server node from the target detection success rates.
[0082] When the second detection success rate corresponding to the internal network node is also lower than the second detection threshold, it indicates that there may be an abnormality in the access layer within the enterprise internal network, or an abnormality in the network device or the server. Therefore, to further locate the abnormal location, the third detection success rate of the access layer node, the fourth detection success rate of the network device node, and the fifth detection success rate of the server node are respectively obtained from the target detection success rates, and the faulty node is located by determining whether the third detection success rate, the fourth detection success rate, and the fifth detection success rate have decreased.
[0083] Step 602, based on the third detection success rate, the fourth detection success rate, and the fifth detection success rate, determine the faulty node from the access layer node, the network device node, and the server node.
[0084] Since the third detection success rate is counted by detecting whether the access layer can receive requests, the fourth detection success rate is counted by detecting whether the network device node can receive requests, and the fifth detection success rate is counted by detecting whether the server node can execute the corresponding function. That is to say, by respectively judging whether the third detection success rate, the fourth detection success rate, and the fifth detection success rate decrease, it is possible to directly determine whether there are abnormalities in the access layer node, the network device node, and the server node; in a possible implementation manner, based on the third detection success rate, the fourth detection success rate, and the fifth detection success rate, a faulty node can be determined from the access layer node, the network device node, and the server node.
[0085] Optionally, step 602 may further include step 602A and step 602B.
[0086] Step 602A, determining the target success rate among the third detection success rate, the fourth detection success rate, and the fifth detection success rate that is lower than the target detection threshold.
[0087] Step 602B, determining the target node corresponding to the target success rate that is lower than the target detection threshold as the faulty node.
[0088] Specifically, detection thresholds are respectively set for the third detection success rate, the fourth detection success rate, and the fifth detection success rate. If the third detection success rate is lower than its corresponding detection threshold, it indicates that the access layer node is a faulty node; if the fourth detection success rate is lower than its corresponding detection threshold, it indicates that the network device node is a faulty node; if the fifth detection success rate is lower than its corresponding detection threshold, it indicates that the server node is a faulty node. That is to say, when determining the faulty node, the third detection success rate is respectively compared with its corresponding third detection threshold, the fourth detection success rate is compared with its corresponding fourth detection threshold, and the fifth detection success rate is compared with its corresponding fifth detection threshold to determine the target success rate among the third detection success rate, the fourth detection success rate, and the fifth detection success rate that is lower than the target detection threshold, and then determine the target node corresponding to the target success rate that is lower than the target detection threshold as the faulty node.
[0089] Optionally, if there are multiple detection success rates among the third detection success rate, the fourth detection success rate, and the fourth detection success rate that are all lower than their corresponding detection thresholds, it indicates that there are also multiple faulty nodes correspondingly. Exemplarily, if the third detection success rate is lower than the third detection threshold and the fourth detection success rate is lower than the third detection threshold, the access layer node and the network device node can be determined as faulty nodes.
[0090] Optionally, if it is determined that the server node is a faulty node, since the service includes multiple service instances, it is possible to further determine from the detection data reported by the service detection sub-module corresponding to the server node which specific service instance has a fault, or whether the entire service has an exception.
[0091] Optionally, if the third detection success rate is not lower than the third detection threshold, the fourth detection success rate is not lower than the fourth detection threshold, and the fifth detection success rate is not lower than the fifth detection threshold, it indicates that the access layer node, the network device node, and the server node are not faulty nodes; then the reason for the client's failure to request the server may be an unknown exception, and it is necessary to send an unknown exception reminder to the user to remind the user that manual participation in judgment is required.
[0092] In this embodiment, when it is determined that the access success rate of the client decreases, the first detection success rate of the external network node also decreases, and the second detection success rate of the internal network node, it is possible to further obtain the third detection success rate of the access layer node, the fourth detection success rate of the network device node, and the fifth detection success rate of the server node, and determine whether the third detection success rate and the fourth detection success rate decrease, and whether the fifth detection success rate decreases, and determine the key node corresponding to the decreased detection success rate as the faulty node. Since the third detection success rate, the fourth detection success rate, and the fifth detection success rate all characterize whether their respective key nodes are abnormal, it is possible to ensure the accuracy of locating the access layer node, the network device node, or the server node as the faulty node.
[0093] In order to enable users to more intuitively and efficiently perceive the faulty node, the network fault location device further includes a visualization module for displaying information such as the access success rate and the detection success rate calculated by the fault location module.
[0094] Please refer to Figure 7 , which shows a flowchart of another network fault location method according to an exemplary embodiment of the present application. This method is described by taking its application to a network fault location device as an example. As Figure 7 shown, the method includes:
[0095] Step 701, determine multiple key nodes included in the target request link corresponding to the client to the server, the multiple key nodes include a client node, an intermediate node, and a server node, and the intermediate node includes at least one of an external network node, an internal network node, an access layer node, and a network device node.
[0096] Step 702, obtain the access success rate of the first key node and the target detection success rate of the second key node, the first key node is the client node, and the second key node is other key nodes except the client node.
[0097] The implementation manners of steps 701 and 702 can refer to the above embodiments, and will not be elaborated herein.
[0098] Step 703, determine abnormal first display information and normal second display information from the access success rate and the target detection success rate.
[0099] In order to enable users to more intuitively perceive the faulty nodes with anomalies, when displaying the access success rate and the target detection success rate, the normal first display information and the abnormal second display information can be distinguished by different styles. Correspondingly, first determine the abnormal first display information from the access success rate and the target detection success rate (that is, the access success rate lower than the access threshold in the access success rate, and the target detection success rate lower than the detection threshold in the target detection success rate), and determine the normal second display information (that is, the access success rate greater than or equal to the access threshold in the access success rate, and the target detection success rate greater than or equal to the detection threshold in the target detection success rate).
[0100] Step 704, display the first display information in a first style and display the second display information in a second style on the target display interface, where the first style is different from the second style.
[0101] Regarding the first display information and the second display information, the abnormal first display information obviously needs to be concerned by users at the first time. Therefore, in order to distinguish the first display information and the second display information, the first display information can be displayed in a first style and the second display information can be displayed in a second style on the target display interface, and the first style and the second style are different.
[0102] Exemplarily, the difference between the first style and the second style can be that the information display colors of the first display information and the second display information are different. For example, the information display color of the first display information can be red, while the information display color of the second display information is black.
[0103] Please refer to Figure 8 , which is a schematic diagram of the target display interface provided by an exemplary embodiment of the present application. As Figure 8 shown, the visualization module is mainly used to display the access success rate and the detection success rates corresponding to each key node. Vertically, it mainly includes the detection success rates of each fault detection sub-module in the fault detection module (user access success rate, external network detection success rate, internal network detection success rate, access layer detection success rate, network device detection success rate, and service detection success rate). Horizontally, it is mainly divided into two parts: overview and details. Among them, the overview shows the overall detection success rate of the fault detection sub-module, and the details list the detailed success rates of the fault detection sub-module. For example, the detection success rates of network A, network B, and network C in the external network detection sub-module, etc.
[0104] In this embodiment, when displaying the access success rate and the target detection success rate, different styles can be used to distinguish abnormal display information from normal display information, so that users can intuitively identify which key node has an abnormality and improve the efficiency of locating the fault source.
[0105] Figure 9 It is a complete flowchart of fault node location provided by an exemplary embodiment of the present application. As Figure 9 shown, the fault location module will check whether the access success rate of the user has decreased. If not, it means that there is no abnormality in the entire request link. If the access success rate has decreased, but the external network detection success rate has not decreased, it indicates that there is an abnormality in the client or the request of a single user; if the access success rate has decreased, it is necessary to further determine whether the internal network detection success rate has decreased. If not, it means that only the external network has an abnormality, and the fault node can be further determined according to the operator network detection success rate and the detection success rate of each region returned by the external network detection module. If the internal network detection success rate has also decreased, further check whether the access layer or the network detection success rate has decreased. If so, it means that there is a fault in the access layer or the network device, and the fault can be determined according to the data reported by the access layer detection sub-module or the network detection sub-module. If there is no abnormality in the access layer or the network device, determine whether the service detection success rate has decreased. If so, it can be determined whether a single instance or the entire service is abnormal according to the relevant data. If not, it means that an unknown abnormality has occurred and manual intervention is required for judgment.
[0106] Please refer to Figure 10 which is a schematic structural diagram of a network fault location device provided by an embodiment of the present application. Exemplarily, as Figure 10 shown, the device 1000 includes:
[0107] An acquisition module 1001, configured to acquire target detection data of multiple key nodes on a target request link from a client to a server, where the multiple key nodes include a client node, an intermediate node, and a server node, and the intermediate node includes at least one of an external network node, an internal network node, an access layer node, and a network device node;
[0108] A first determination module 1002, configured to determine an access success rate of a first key node and a target detection success rate of a second key node at a target moment based on the target detection data, where the first key node is the client node, and the second key node is other key nodes except the client node;
[0109] A second determination module 1003, configured to determine a fault node from the multiple key nodes based on the target detection success rate when the access success rate is lower than an access threshold.
[0110] Optionally, the second determination module 1003 is further configured to:
[0111] When the access success rate is lower than the access threshold, obtain the first detection success rate of the external network node from the target detection success rate;
[0112] If the first detection success rate is greater than or equal to the first detection threshold, determine the client node as the faulty node;
[0113] If the first detection success rate is lower than the first detection threshold, determine the faulty node from the second key nodes based on the target detection success rate.
[0114] Optionally, the second determination module 1003 is further configured to:
[0115] If the first detection success rate is lower than the first detection threshold, obtain the second detection success rate of the internal network node from the target detection success rate;
[0116] If the second detection success rate is greater than or equal to the second detection threshold, determine the external network node as the faulty node;
[0117] If the second detection success rate is lower than the second detection threshold, determine the faulty node from the second key nodes based on the target detection success rate.
[0118] Optionally, the second determination module 1003 is further configured to:
[0119] If the second detection success rate is lower than the second detection threshold, obtain the third detection success rate of the access layer node, the fourth detection success rate of the network device node, and the fifth detection success rate of the server node from the target detection success rate;
[0120] Determine the faulty node from the access layer node, the network device node, and the server node based on the third detection success rate, the fourth detection success rate, and the fifth detection success rate.
[0121] Optionally, the second determination module 1003 is further configured to:
[0122] Determine the target detection success rate that is lower than the target detection threshold among the third detection success rate, the fourth detection success rate, and the fifth detection success rate;
[0123] Determine the target node corresponding to the target detection success rate that is lower than the target detection threshold as the faulty node.
[0124] Optionally, the apparatus further includes:
[0125] A third determination module, configured to determine that there is no such faulty node when the access success rate is greater than or equal to the access threshold.
[0126] Optionally, the apparatus further includes:
[0127] A fourth determination module, configured to determine abnormal first display information and normal second display information from the access success rate and the target detection success rate;
[0128] A display module, configured to display the first display information in a first style and display the second display information in a second style in a target display interface, where the first style is different from the second style.
[0129] An exemplary embodiment of the present application further provides an electronic device, including: at least one processor; and a memory communicatively connected to the at least one processor. The memory stores a computer program that can be executed by the at least one processor, and when the computer program is executed by the at least one processor, it is used to cause the electronic device to execute the method according to the embodiment of the present application.
[0130] An exemplary embodiment of the present application further provides a non-transitory computer-readable storage medium storing a computer program, where the computer program is used to cause a computer to execute the method according to the embodiment of the present application when executed by a processor of the computer.
[0131] An exemplary embodiment of the present application further provides a computer program product, including a computer program, where the computer program is used to cause a computer to execute the method according to the embodiment of the present application when executed by a processor of the computer.
[0132] Reference Figure 11 , the following will describe a block diagram of an electronic device 1100 that can be a server or a client of the present application. It is an example of a hardware device that can be applied to various aspects of the present application. The electronic device is intended to represent various forms of digital electronic computer devices, such as, a laptop computer, a desktop computer, a workbench, a personal digital assistant, a server, a blade server, a mainframe computer, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as, a personal digital processor, a cellular phone, a smart phone, a wearable device, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present application described and / or claimed herein.
[0133] As Figure 11As shown, the electronic device 1100 includes a computing unit 1101, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 1102 or a computer program loaded from a storage unit 1108 into a random access memory (RAM) 1103. In the RAM 1103, various programs and data required for the operation of the device 1100 can also be stored. The computing unit 1101, the ROM 1102, and the RAM 1103 are connected to each other via a bus 1104. An input / output (I / O) interface 1105 is also connected to the bus 1104.
[0134] Multiple components in the electronic device 1100 are connected to the I / O interface 1105, including: an input unit 1106, an output unit 1107, a storage unit 1108, and a communication unit 1109. The input unit 1106 can be any type of device capable of inputting information into the electronic device 1100. The input unit 1106 can receive input digital or character information and generate key signal inputs related to the user settings and / or function controls of the electronic device. The output unit 1107 can be any type of device capable of presenting information and can include, but is not limited to, a display, a speaker, a video / audio output terminal, a vibrator, and / or a printer. The storage unit 1108 can include, but is not limited to, a magnetic disk, an optical disk. The communication unit 1109 allows the electronic device 1100 to exchange information / data with other devices via a computer network such as the Internet and / or various telecommunication networks and can include, but is not limited to, a modem, a network card, an infrared communication device, a wireless communication transceiver, and / or a chipset, such as a Bluetooth device, a WiFi device, a WiMax device, a cellular communication device, and / or the like.
[0135] The computing unit 1101 can be various general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 1101 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The computing unit 1101 executes the various methods and processes described above. For example, in some embodiments, Figure 2 , Figure 4 , Figure 5 , Figure 6 , Figure 7The method shown can be implemented as a computer software program tangibly embodied in a machine-readable medium, such as storage unit 1108. In some embodiments, part or all of the computer program may be loaded and / or installed onto the electronic device 1100 via ROM 1102 and / or communication unit 1109. In some embodiments, the computing unit 1101 may be configured to execute Figure 2 , Figure 4 , Figure 5 , Figure 6 , Figure 7 the method shown.
[0136] The program code for implementing the method of this application can be written in any combination of one or more programming languages. These program codes can be provided to the processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing devices, such that when executed by the processor or controller, the functions / operations specified in the flowchart and / or block diagram are implemented. The program code can be executed entirely on the machine, partially on the machine, executed partially on the machine as an independent software package and partially on a remote machine, or executed entirely on a remote machine or server.
[0137] In the context of this application, a machine-readable medium can be a tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0138] As used in this application, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, device, and / or apparatus (e.g., a disk, an optical disc, a memory, a programmable logic device (PLD)) for providing machine instructions and / or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal for providing machine instructions and / or data to a programmable processor.
[0139] To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which the user can provide input to the computer. Other kinds of devices can also be used to provide for interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, speech input, or tactile input).
[0140] The systems and techniques described here can be implemented in a computing system including a back-end component (e.g., as a data server), or a computing system including a middleware component (e.g., an application server), or a computing system including a front-end component (e.g., a user computer having a graphical user interface or a web browser through which the user can interact with an implementation of the systems and techniques described here), or a computing system including any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), and the Internet.
[0141] A computer system can include clients and servers. Clients and servers are generally remote from each other and typically interact through a communication network. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship to each other.
Claims
1. A network fault location method, characterized in that: The method comprises: Obtain target detection data of multiple key nodes on a target request link from a client to a server, wherein the multiple key nodes include a client node, an intermediate node, and a server node, and the intermediate node includes at least one of an external network node, an internal network node, an access layer node, and a network device node; Based on the target detection data, determine the access success rate of the first key node and the target detection success rate of the second key node at the target time, the first key node is the client node, and the second key node is other key nodes except the client node; In a case where the access success rate is lower than an access threshold, a faulty node is determined from the multiple key nodes based on the target detection success rate.
2. The method according to claim 1, characterized in that The step of determining a faulty node from the plurality of key nodes based on the target detection success rate when the access success rate is lower than an access threshold includes: When the access success rate is lower than the access threshold, obtaining the first detection success rate of the external network node from the target detection success rate; If the first detection success rate is greater than or equal to a first detection threshold, determining the client node as the faulty node; If the first detection success rate is lower than the first detection threshold, the faulty node is determined from the second key nodes based on the target detection success rate.
3. The method according to claim 2, characterized in that If the first detection success rate is lower than the first detection threshold, determining the faulty node from the second key nodes based on the target detection success rate includes: If the first detection success rate is lower than the first detection threshold, obtaining a second detection success rate of the intranet node from the target detection success rate; If the second detection success rate is greater than or equal to a second detection threshold, determining the external network node as the faulty node; If the second detection success rate is lower than the second detection threshold, the faulty node is determined from the second key nodes based on the target detection success rate.
4. The method according to claim 3, characterized in that If the second detection success rate is lower than the second detection threshold, determining the faulty node from the second key nodes based on the target detection success rate includes: If the second detection success rate is lower than the second detection threshold, obtaining the third detection success rate of the access layer node, the fourth detection success rate of the network device node, and the fifth detection success rate of the service end node from the target detection success rate; Based on the third detection success rate, the fourth detection success rate and the fifth detection success rate, the faulty node is determined from among the access layer nodes, the network device nodes and the service end nodes.
5. The method according to claim 4, characterized in that The determining the faulty node from the access layer node, the network device node, and the service end node based on the third detection success rate, the fourth detection success rate, and the fifth detection success rate includes: Determine a target detection success rate that is lower than a target detection threshold among the third detection success rate, the fourth detection success rate, and the fifth detection success rate; The target node corresponding to the target detection success rate lower than the target detection threshold is determined as the fault node.
6. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: When the access success rate is greater than or equal to the access threshold, it is determined that the faulty node does not exist.
7. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: Determine abnormal first display information and normal second display information from the access success rate and the target detection success rate; The first display information is displayed in a first style in the target display interface, and the second display information is displayed in a second style, wherein the first style is different from the second style.
8. A network fault location device, characterized in that: The device comprises: An acquisition module, used to acquire target detection data of multiple key nodes on a target request link from a client to a server, wherein the multiple key nodes include a client node, an intermediate node, and a server node, and the intermediate node includes at least one of an external network node, an internal network node, an access layer node, and a network device node; A first determination module, configured to determine, based on the target detection data, an access success rate of a first key node and a target detection success rate of a second key node at a target time, wherein the first key node is the client node, and the second key node is a key node other than the client node; The second determination module is used to determine the faulty node from the multiple key nodes based on the target detection success rate when the access success rate is lower than the access threshold.
9. An electronic device, comprising: processor; as well as Memory for storing programs, The program includes instructions, which, when executed by the processor, cause the processor to perform the method according to any one of claims 1 to 7.
10. A non-transitory computer-readable storage medium storing computer instructions, wherein: The computer instructions are used to cause the computer to execute the method according to any one of claims 1-7.