Method and device for determining reason of business exception

Abstract

The embodiment of the invention provides a method and a device for determining the cause of business abnormity, under the condition that a plurality of businesses are abnormal, the abnormal businesses are determined as abnormal businesses, an abnormal business set is obtained, each business is realized through a plurality of systems, and the abnormal businesses are caused by the system abnormity in the businesses; determining an abnormal system in the abnormal service set to obtain a plurality of abnormal systems; according to the method, the target abnormal system is determined in the plurality of abnormal systems, and the reasons of the abnormity of the plurality of businesses are determined through the target abnormal system, so that the problems of complicated operation and low efficiency of judging the reasons of the abnormity of the businesses through logs in related technologies are solved, and the effect of improving the abnormity judgment efficiency is further achieved.

Description

Technical Field

[0001] The embodiments of the present invention relate to the computer field, and in particular, to a method and device for determining the cause of a service abnormality. Background Art

[0002] A business is usually implemented by multiple systems. For example, a transaction is completed by system A, system B, system C, and system D. An abnormality in a system will cause a transaction to fail. In addition, system abnormalities will cause many transactions to be abnormal in actual scenarios. In the prior art, the cause of the abnormality is usually determined by analyzing the transaction log. However, the transaction log contains a large number of logs. In the prior art, it is necessary to manually find the abnormal log information in a large amount of log information, and then determine the cause of the business abnormality. The operation is complicated and inefficient.

[0003] There is currently no effective solution to the above problems. Summary of the invention

[0004] The embodiments of the present invention provide a method and device for determining the cause of a business abnormality, so as to at least solve the problem in the related art that determining the cause of a business abnormality through logs is complex and inefficient.

[0005] According to one embodiment of the present invention, a method for determining the cause of a business abnormality is provided, comprising: in the event that abnormalities occur in multiple businesses, determining the business in which the abnormalities occur as an abnormal business, and obtaining a set of abnormal businesses, wherein each of the businesses is implemented through multiple systems, and the abnormal business is caused by an abnormality in a system in the business; determining an abnormal system in the set of abnormal businesses, and obtaining multiple abnormal systems; determining a target abnormal system among the multiple abnormal systems, and determining the cause of the abnormalities occurring in the multiple businesses through the target abnormal system.

[0006] In an exemplary embodiment, determining a target abnormal system among the multiple abnormal systems includes: determining the target abnormal system among the multiple abnormal systems according to the relationship between the systems in the multiple businesses; or determining the system having the most abnormalities among the multiple abnormal systems as the target abnormal system.

[0007] In an exemplary embodiment, the target abnormal system is determined among the multiple abnormal systems based on the relationship between the systems in the multiple businesses, including: determining the number of abnormal systems appearing in the upstream systems of the respective abnormal systems, wherein the upstream system is a system that is located before the abnormal system in the respective businesses where the abnormal system is located and interacts with the abnormal system; determining the target abnormal system based on the number of abnormal systems appearing in the upstream systems of the multiple abnormal systems.

[0008] In an exemplary embodiment, the target abnormal system is determined based on the number of abnormal systems occurring in the upstream systems of the multiple abnormal systems, including: determining the system in the upstream systems of the multiple abnormal systems in which the largest number of abnormal systems occurs as the target abnormal system; or determining the system in the upstream systems of the multiple abnormal systems in which the number of abnormal systems occurring is greater than or equal to a preset value as the target abnormal system.

[0009] In an exemplary embodiment, determining the reasons why the abnormalities occur in the multiple businesses through the target abnormality system includes: acquiring a service code of the target abnormality system to obtain multiple service codes, wherein the service code is used to identify each software service of the target abnormality system; and determining the reasons why the abnormalities occur in the multiple businesses based on the multiple service codes.

[0010] In an exemplary embodiment, determining the cause of the abnormality occurring in the multiple services based on the multiple service codes includes: determining a deployment unit associated with each of the service codes, wherein each of the service codes is associated with at least one deployment unit; and determining the cause of the abnormality occurring based on the deployment unit associated with the service code.

[0011] In an exemplary embodiment, determining the cause of the exception according to the deployment units associated with the service code includes: acquiring data of each of the deployment units; and determining the cause of the exception according to the data of the deployment units.

[0012] In an exemplary embodiment, determining the cause of the exception based on the data of the deployment unit includes: when the data of the deployment unit indicates insufficient hardware resources, determining the cause of the exception as a hardware exception; when the data of the deployment unit indicates a service exception, determining the cause of the exception as a software service exception.

[0013] According to another embodiment of the present invention, a device for determining the cause of a service abnormality is provided, comprising: a first determination module, in the case of multiple services having abnormalities, determining the service having the abnormality as an abnormal service, and obtaining an abnormal service set, wherein each service is implemented by multiple systems, and the abnormal service is caused by an abnormality in the system of the service; a second determination module, determining an abnormal system in the abnormal service set, and obtaining multiple abnormal systems; a third determination module, determining a target abnormal system in the multiple abnormal systems, and determining the cause of the abnormality in the multiple services through the target abnormal system. .

[0014] According to yet another embodiment of the present invention, a computer-readable storage medium is provided, wherein a computer program is stored in the computer-readable storage medium, wherein the computer program implements the steps of any of the above methods when executed by a processor.

[0015] According to yet another embodiment of the present invention, there is provided an electronic device, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0016] According to yet another embodiment of the present invention, a computer program product is provided, comprising a computer program, wherein when the computer program is executed by a processor, the steps of any of the above methods are implemented.

[0017] According to yet another embodiment of the present invention, a computer program product is provided, comprising computer instructions, wherein when the computer instructions are executed by a processor, the steps of any of the above methods are implemented.

[0018] Through the present invention, when multiple businesses are abnormal, the business with the abnormality is determined as an abnormal business, and an abnormal business set is obtained, wherein each business is implemented by multiple systems, and the abnormal business is caused by the abnormality of the system in the business; the abnormal system is determined in the abnormal business set to obtain multiple abnormal systems; the target abnormal system is determined in the multiple abnormal systems, and the reasons for the abnormality of multiple businesses are determined through the target abnormal system. Therefore, the problem of complex operation and low efficiency in determining the reasons for the abnormality of the business through logs in the related technology can be solved, and the effect of improving the efficiency of determining the abnormality can be achieved. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 It is a hardware structure block diagram of a mobile terminal of a method for determining the cause of a service abnormality according to an embodiment of the present invention;

[0020] Figure 2 is a flowchart of a method for determining the cause of a service abnormality according to an embodiment of the present invention;

[0021] Figure 3 is a flow chart according to an embodiment of the present invention;

[0022] Figure 4 4 is a structural block diagram of an apparatus for determining a cause of a service abnormality according to an embodiment of the present invention. DETAILED DESCRIPTION

[0023] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings and in combination with the embodiments.

[0024] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0025] The method for determining the cause of a service anomaly provided in the embodiments of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Taking running on a mobile terminal as an example, Figure 1 FIG. 1 is a hardware structure block diagram of a mobile terminal of a method for determining the cause of a service abnormality according to an embodiment of the present invention. Figure 1 As shown, the mobile terminal may include one or more ( Figure 1 Only one is shown in the figure) a processor 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA) and a memory 104 for storing data, wherein the mobile terminal may also include a transmission device 106 and an input / output device 108 for communication functions. It can be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the mobile terminal. Figure 1 More or fewer components as shown, or with Figure 1 Different configurations are shown.

[0026] The memory 104 can be used to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the method for determining the cause of business abnormality in the embodiment of the present invention. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, that is, the above method is implemented. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include a memory remotely arranged relative to the processor 102, and these remote memories may be connected to the mobile terminal via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof.

[0027] The transmission device 106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the mobile terminal. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, referred to as NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0028] In this embodiment, a method running on the above mobile terminal or network architecture is provided. Figure 2 is a flow chart of a method for determining the cause of a service abnormality according to an embodiment of the present invention. Figure 2 As shown, the process includes the following steps:

[0029] Step S202: in the case where multiple services are abnormal, the service where the abnormality occurs is determined as an abnormal service, and an abnormal service set is obtained, wherein each service is implemented by multiple systems, and the abnormal service is caused by an abnormality in the system of the service;

[0030] The above business, i.e., a transaction, is actually composed of a series of transactions. Each of the above businesses is implemented through multiple systems, for example: Business 1: A->B->C->D; Business 2: E->F->C->G->H; Business 1 is implemented by four systems, A, B, C, and D, and Business 2 is implemented by five systems, E, F, C, G, and H. The above business anomalies are unexpected situations or errors that occur in the system during the transaction, resulting in the inability to complete the transaction smoothly or problems, including network failures, database failures, hardware failures, software vulnerabilities, security vulnerabilities, third-party service failures, etc. Multiple of the above abnormal businesses constitute an abnormal business set.

[0031] Step S204, determining an abnormal system in the abnormal business set to obtain a plurality of abnormal systems;

[0032] The above-mentioned abnormal system is a system that issues an alarm during the process of providing services for the above-mentioned abnormal transactions, such as business 1: A->B->C->D; business 2: E->F->C->G->H; the above-mentioned business 1 is implemented by four systems A, B, C, and D, and the above-mentioned business 2 is implemented by five systems E, F, C, G, and H. If, during the implementation of businesses 1 and 2, abnormalities occur in businesses 1 and 2, the system where the abnormality occurs is determined in systems A, B, C, E, F, G, and H, and multiple abnormal systems are obtained.

[0033] Step S206, determining a target abnormal system from among the multiple abnormal systems, and determining the reasons why the abnormalities occur in the multiple services through the target abnormal system.

[0034] As an optional implementation manner, the target abnormal system is determined among the multiple abnormal systems according to the relationship between the systems in the multiple services.

[0035] Specifically, the number of abnormal systems appearing in the upstream systems of each of the abnormal systems is determined, wherein the upstream system is a system located before the abnormal system in each business where the abnormal system is located and interacts with the abnormal system; the target abnormal system is determined according to the number of abnormal systems appearing in the upstream systems of the multiple abnormal systems.

[0036] For example, business 1: A->B->C->D. The above business 1 is implemented by four systems A, B, C, and D. If an exception occurs during the implementation of business 1, it is found that systems A, B, and C have exceptions. For system C, systems A and B are the upstream systems of system C. For system B, system A is the upstream system of system B.

[0037] Specifically, among the upstream systems of the multiple abnormal systems, the system in which the largest number of abnormal systems occurs is determined as the target abnormal system; or, among the upstream systems of the multiple abnormal systems, the system in which the number of abnormal systems occurs is greater than or equal to a preset value is determined as the target abnormal system.

[0038] For example, the number of upstream abnormal systems of the abnormal system C is 2, the number of upstream abnormal systems of the abnormal system B is 1, and the number of upstream abnormal systems of the abnormal system A is 0, that is, the number of systems with abnormalities in the upstream system of the abnormal system C is the largest, and the abnormal system C is determined as the target abnormal system. Alternatively, the number of abnormal systems in the upstream system of the abnormal system is preset to be 2 (pre-set according to actual conditions, here the example provides fewer systems for transactions, so the preset value is smaller, and the actual preset value can be determined according to the number of systems that actually provide transactions), then the number of upstream abnormal systems of the abnormal system C is 2, which is greater than or equal to the preset value 2, and the abnormal system C is determined as the target abnormal system.

[0039] As an optional implementation, a system having the largest number of abnormalities among the multiple abnormal systems is determined as the target abnormal system.

[0040] For example, business 1: A->B->C->D; business 2: E->F->C->G->H; the above business 1 is implemented by four systems A, B, C, and D, and the above business 2 is implemented by five systems E, F, C, G, and H. If during the implementation of business 1 and 2, business 1 and 2 have abnormalities, and systems A, B, C, E, and F are abnormal systems, then the number of abnormalities in systems A, B, E, and F is 1, and the number of abnormalities in system C is 2, then the abnormal system C is determined as the target abnormal system.

[0041] As an optional implementation, determining the reasons why the abnormalities occur in the multiple businesses through the target abnormality system includes: acquiring a service code of the target abnormality system to obtain multiple service codes, wherein the service code is used to identify each software service of the target abnormality system; and determining the reasons why the abnormalities occur in the multiple businesses based on the multiple service codes.

[0042] The above service code is a unique code used to identify and recognize a specific transaction. The above code is usually composed of numbers or letters, which can help the system automatically identify and process transactions to ensure the accuracy and completeness of transactions. To obtain the service code of the above target abnormal system, first check the system log file: the system usually records the log information of each transaction, including service code, transaction time, transaction content, etc. By viewing the log file, you can find the corresponding service code and view the detailed information of the transaction to determine the cause of the abnormality. Then analyze the abnormal information: After finding the corresponding service code in the log file, you need to carefully analyze the abnormal information that appears during the transaction, including error prompts, abnormal stack information, etc. By analyzing the abnormal information, determine the cause of the abnormality of the above business.

[0043] As an optional implementation, determining the cause of the abnormality occurring in the multiple services based on the multiple service codes includes: determining the deployment unit associated with each of the service codes, wherein each of the service codes is associated with at least one deployment unit; and determining the cause of the abnormality occurring based on the deployment unit associated with the service code.

[0044] Specifically, determining the cause of the exception according to the deployment units associated with the service code includes: acquiring data of each of the deployment units; and determining the cause of the exception according to the data of the deployment units.

[0045] The data of the above deployment units include transaction volume, regular transaction volume, successful transaction volume of the system, abnormal transaction volume, CPU utilization, memory utilization, etc. In this embodiment, in order to realize the system display to the deployment unit, it supports viewing the service code contained in the system, the deployment unit, and which service codes of the upstream system are related to the expanded system, which AP deployment units are related to the service code, and which downstream systems these AP deployment units are specifically related to. When the transaction path nodes converge, the deployment units are merged, and the generated format becomes one service code corresponding to multiple deployment units, and the transaction index calculation is performed on the deployment unit dimension at the same time. In this way, it is possible to realize which service codes there are after the system is expanded, which deployment units these service codes are associated with, and the transaction indicators corresponding to each of these deployment units: transaction volume, long transaction volume, and successful transaction volume of the system. The cause of the above anomaly can be determined according to the deployment unit associated with the above service code through the following steps: 1. Check the configuration of the deployment unit: First, check whether the configuration of the deployment unit is correct, including software version, environment variables, dependencies, etc., to ensure that there is no configuration error causing the anomaly. 2. Log analysis: View the log file of the deployment unit, find abnormal information or error prompts, and analyze the abnormal situation in the log, which can help determine the cause of the anomaly. 3. Monitoring system: If a monitoring system is deployed on the deployment unit, you can view the monitoring data, analyze the system's performance indicators, and determine whether there are performance problems that cause the anomaly. 4. Network connection: Check whether the network connection of the deployment unit is normal, including network configuration, firewall settings, etc., to ensure that there are no problems with the network connection. 5. Code review: If possible, you can conduct a code review to check whether the code of the deployment unit has bugs or logical errors. It may be that the code problem causes the anomaly. 6. Test environment reproduction: Try to reproduce the anomaly in the test environment to find the root cause of the problem.

[0046] Optionally, when the data of the deployment unit indicates insufficient hardware resources, the cause of the exception is determined to be a hardware exception; when the data of the deployment unit indicates a service exception, the cause of the exception is determined to be a software service exception.

[0047] The above-mentioned hardware resources include CPU, memory, server, network equipment, security equipment, etc. If the data of the above-mentioned deployment unit indicates that the above-mentioned hardware resources are insufficient, such as low CPU utilization, low memory utilization, etc., then it is determined that the cause of the above-mentioned business abnormality is a hardware abnormality; if the data of the above-mentioned deployment unit indicates a service abnormality, such as a service code vulnerability, then it is determined that the cause of the above-mentioned business abnormality is a software service abnormality.

[0048] Optionally, the executor of the above steps may be a background processor, or other devices with similar processing capabilities, or a machine that integrates at least an image acquisition device and a data processing device, wherein the image acquisition device may include a graphics acquisition module such as a camera, and the data processing device may include a computer, a mobile phone or other terminal, but is not limited thereto.

[0049] Through the above steps, the problems of complicated operation and low efficiency in judging the cause of business anomalies through logs in related technologies are solved, and the effect of improving the efficiency of judging anomalies is improved.

[0050] Figure 3 is a flow chart according to an embodiment of the present invention, such as Figure 3 As shown,

[0051] Transaction details are stored in Kafka, and Spark Streaming is used to consume transaction details from Kafka in real time. The reduceByKey operator is used to generate a transaction path according to certain serial rules, and a unique identifier is generated for the transaction path, that is, the transaction path unique identifier. The reduceByKeyAndWindow operator is used to aggregate according to the transaction path unique identifier, count the transaction path data for 1 minute, and calculate the indicators of each node (node ​​refers to the service code) of the transaction path: transaction volume, long transaction volume, and system failure transaction volume.

[0052] In order to realize the display of the system to the deployment unit, support viewing the service codes and deployment units contained in the system, as well as which service codes of the upstream system are related to the expanded system, which AP deployment units are related to the service codes, and which downstream systems these AP deployment units are specifically related to, it is necessary to optimize and improve on the original basis, merge the deployment units while the transaction path nodes converge, and the generated format will become one service code corresponding to multiple deployment units, and calculate the transaction indicators for the deployment unit dimension at the same time. In this way, it is possible to realize which service codes there are after the system is expanded, which deployment units these service codes are associated with, and the transaction indicators corresponding to each of these deployment units: transaction volume, long transaction volume, and system successful transaction volume. The transaction path data is stored in the Elasticsearch database according to the data of each node on the path, and the deployment unit information of the current node is added to the storage format.

[0053] The format is:

[0054] "tranApgrps":[#Deployment unit information of the current node

[0055] {

[0056] "stamt":0,#Long transaction volume

[0057] "amt":1,#Transaction volume

[0058] "successForSysCount":0,#System successful transaction volume

[0059] "key":"xxxxxx"#Deployment unit

[0060] } ]

[0062] In addition, you also need to add the deployment unit information of the upstream system corresponding to the node for linking the downstream system. When linking the downstream system, you can filter according to the deployment unit of the parent node recorded in the downstream system node.

[0063] The format is:

[0064] "parTranApgrps":[#Deployment unit information of the current node associated with the parent node

[0065] {

[0066] "stamt":0,#Long transaction volume

[0067] "amt":1,#Transaction volume

[0068] "successForSysCount":0,#System successful transaction volume

[0069] "key":"xxxxx"#Deployment unit

[0070] } ]

[0072] When the front-end displays the query, it transmits the physical subsystem that needs to be expanded. The back-end queries the service codes of the current system based on the physical subsystem, searches for the corresponding deployment unit data based on the queried service code, and connects the relationships after obtaining the deployment unit data.

[0073] Through the above steps, the embodiment of the present invention realizes that the system can be expanded to the deployment unit dimension; it realizes the refined calculation of transaction indicators, which is refined to the deployment unit dimension of each node in the transaction path, and more accurately reflects the distribution of transaction conditions at that time, providing strong support for daily production emergency response.

[0074] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for enabling a terminal device (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present invention.

[0075] In this embodiment, a device for determining the cause of a business anomaly is also provided, and the device is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions that have been made are not repeated. As used below, the term "module" can implement a combination of software and / or hardware of a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0076] Figure 4 is a structural block diagram of an apparatus for determining the cause of a service abnormality according to an embodiment of the present invention, such as Figure 4 As shown, the device includes a first determination module 402, which, when an abnormality occurs in multiple businesses, determines the business where the abnormality occurs as an abnormal business, and obtains an abnormal business set, wherein each of the businesses is implemented through multiple systems, and the abnormal business is caused by an abnormality in the system of the business; a second determination module 404, which determines an abnormal system in the abnormal business set, and obtains multiple abnormal systems; a third determination module 406, which determines a target abnormal system among the multiple abnormal systems, and determines the cause of the abnormality occurring in the multiple businesses through the target abnormal system.

[0077] In an exemplary embodiment, the above-mentioned device is also used to determine the target abnormal system among the multiple abnormal systems based on the relationship between each system in the multiple businesses; or, determine the system with the most abnormalities among the multiple abnormal systems as the target abnormal system.

[0078] In an exemplary embodiment, the above-mentioned device is also used to determine the number of abnormal systems appearing in the upstream systems of each of the abnormal systems, wherein the upstream system is a system located before the abnormal system in each business where the abnormal system is located and interacts with the abnormal system; the target abnormal system is determined according to the number of abnormal systems appearing in the upstream systems of the multiple abnormal systems.

[0079] In an exemplary embodiment, the above-mentioned device is also used to determine the system in the upstream systems of the multiple abnormal systems in which the number of abnormal systems occurs is the target abnormal system; or, to determine the system in the upstream systems of the multiple abnormal systems in which the number of abnormal systems occurs is greater than or equal to a preset value as the target abnormal system.

[0080] In an exemplary embodiment, the above-mentioned device is also used to obtain the service code of the target abnormal system to obtain multiple service codes, wherein the service code is used to identify each software service of the target abnormal system; and determine the reasons for the abnormalities of the multiple services based on the multiple service codes.

[0081] In an exemplary embodiment, the apparatus is further used to determine a deployment unit associated with each of the service codes, wherein each of the service codes is associated with at least one deployment unit; and determine the cause of the exception according to the deployment unit associated with the service code.

[0082] In an exemplary embodiment, the above-mentioned device is also used to obtain data of each of the deployment units; and determine the cause of the abnormality according to the data of the deployment units.

[0083] In an exemplary embodiment, the above-mentioned device is also used to determine the cause of the exception as a hardware exception when the data of the deployment unit indicates insufficient hardware resources; when the data of the deployment unit indicates a service exception, determine the cause of the exception as a software service exception.

[0084] It should be noted that the above modules can be implemented by software or hardware. For the latter, it can be implemented in the following ways, but not limited to: the above modules are all located in the same processor; or the above modules are located in different processors in any combination.

[0085] An embodiment of the present invention further provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the steps of any of the above methods are implemented.

[0086] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.

[0087] An embodiment of the present invention further provides an electronic device, including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0088] In an exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.

[0089] For specific examples in this embodiment, reference may be made to the examples described in the above embodiments and exemplary implementation modes, and this embodiment will not be described in detail herein.

[0090] An embodiment of the present invention further provides a computer program product, including a computer program, which implements the steps of the method described in each embodiment of the present application when executed by a processor.

[0091] Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order than here, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present invention is not limited to any specific combination of hardware and software.

[0092] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A method for determining the cause of a service abnormality, characterized in that: include: In the case where multiple services are abnormal, the service where the abnormality occurs is determined as an abnormal service, and an abnormal service set is obtained, wherein each service is implemented by multiple systems, and the abnormal service is caused by an abnormality in the system of the service; Determining an abnormal system in the abnormal business set to obtain a plurality of abnormal systems; A target abnormal system is determined among the multiple abnormal systems, and reasons why the abnormalities occur in the multiple businesses are determined through the target abnormal system.

2. The method according to claim 1, characterized in that Determining a target abnormal system among the multiple abnormal systems comprises: Determine the target abnormal system from among the multiple abnormal systems according to the relationship between the systems in the multiple services; or A system among the multiple abnormal systems that has the most abnormalities is determined as the target abnormal system.

3. The method according to claim 2, characterized in that Determining the target abnormal system among the multiple abnormal systems according to the relationship between the systems in the multiple services includes: Determine the number of abnormal systems in the upstream systems of each of the abnormal systems, wherein the upstream system is a system located before the abnormal system in each of the businesses where the abnormal system is located and interacts with the abnormal system; The target abnormal system is determined according to the number of abnormal systems in the upstream systems of the plurality of abnormal systems.

4. The method according to claim 3, characterized in that Determining the target abnormal system according to the number of abnormal systems in the upstream systems of the multiple abnormal systems includes: Among the upstream systems of the plurality of abnormal systems, a system having the largest number of abnormal systems is determined as the target abnormal system; or Among the multiple abnormal system upstream systems, a system in which the number of abnormal systems is greater than or equal to a preset value is determined as the target abnormal system.

5. The method according to claim 1, characterized in that Determining, by the target abnormality system, reasons why the abnormalities occur in the multiple services includes: Acquire a service code of the target abnormal system to obtain a plurality of service codes, wherein the service code is used to identify each software service of the target abnormal system; The reasons why the abnormalities occur in the multiple services are determined according to the multiple service codes.

6. The method according to claim 5, characterized in that Determining the reasons why the multiple services have the abnormalities according to the multiple service codes includes: Determining the deployment units associated with each of the service codes, wherein each of the service codes is associated with at least one deployment unit; The cause of the exception is determined according to the deployment unit associated with the service code.

7. The method according to claim 6, characterized in that Determining a cause of the exception according to a deployment unit associated with the service code includes: Acquiring data of each of the deployment units; The cause of the abnormality is determined according to the data of the deployment unit.

8. The method according to claim 7, characterized in that Determining the cause of the abnormality according to the data of the deployment unit includes: In the case where the data of the deployment unit indicates insufficient hardware resources, determining the cause of the exception as a hardware exception; In the case where the data of the deployment unit indicates a service abnormality, the cause of the abnormality is determined to be a software service abnormality.

9. A device for determining the cause of a service anomaly, characterized in that: include: A first determination module, in the case where multiple services are abnormal, determines the service where the abnormality occurs as an abnormal service, and obtains an abnormal service set, wherein each service is implemented by multiple systems, and the abnormal service is caused by an abnormality in the system of the service; A second determination module determines an abnormal system in the abnormal business set to obtain a plurality of abnormal systems; The third determination module determines a target abnormal system among the multiple abnormal systems, and determines the reasons why the abnormalities occur in the multiple services through the target abnormal system.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program implements the steps of the method described in any one of claims 1 to 8 when executed by a processor.

11. An electronic device comprising a memory and a processor, characterized in that: A computer program is stored in the memory, and the processor is configured to run the computer program to perform the method according to any one of claims 1 to 8.

12. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method described in any one of claims 1 to 8 are implemented.

13. A computer program product comprising computer instructions, characterized in that: When the computer instructions are executed by a processor, the steps of the method described in any one of claims 1 to 8 are implemented.

Images