Fault positioning method, device, equipment, medium and product

Abstract

The invention discloses a fault positioning method and device, equipment, a medium and a product. The method comprises the following steps: acquiring a first service identifier and a first process track; the first service identifier is used for indicating a first service process; the first process track indicates that the first business process runs in a fault; acquiring a first service log based on the first service identifier; the first business log comprises an association log between an upstream module and a downstream module of the first business process, an execution mark log of request start and a completion mark log; and detecting the first process track based on the first business log, and determining a fault position of the first business process.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a fault location method, device, equipment, medium and product. Background Art

[0002] In the related art, in a multi-system and multi-engineering module environment, the log volume is usually large and cannot be correlated, making it impossible to quickly locate faults. Summary of the invention

[0003] The present application mainly provides a fault location method, device, equipment, medium and product.

[0004] The technical solution of this application is implemented as follows:

[0005] A fault location method, the method comprising:

[0006] Obtaining a first service identifier and a first process track; the first service identifier is used to indicate a first service process; the first process track indicates a running failure of the first service process;

[0007] Acquire a first business log based on the first business identifier; the first business log includes an association log between upstream and downstream modules of the first business process, an execution mark log of the request start, and a completion mark log;

[0008] The first process trajectory is detected based on the first business log to determine a fault location of the first business process.

[0009] In the above solution, the obtaining of the first service log based on the first service identifier includes:

[0010] Obtaining a first service request; the first service request is used to generate the first service identifier;

[0011] Generate a business process log based on the first business identifier; the business process log includes system information and module information called by the first business process;

[0012] The first service log is generated based on the system information and the module information.

[0013] In the above solution, the generating the first service log based on the system information and the module information includes:

[0014] The first system and the first module are called to traverse the system information and the module information to obtain the first business log; the first system indicates the first business system called by the first business process; the first module indicates the first business module called by the first business process.

[0015] In the above solution, after generating the first service log based on the system information and the module information, the method further includes:

[0016] A second process trajectory is generated based on the first business log; the second process trajectory indicates that the first business process has completed execution.

[0017] In the above solution, the detecting the first process track based on the first business log to determine the fault location of the first business process includes:

[0018] Comparing the first process track with the second process track, determining a faulty module; the faulty module does not include an execution flag and / or a completion flag of a request start;

[0019] The fault location is determined based on the fault module.

[0020] In the above scheme, the method further comprises:

[0021] If the second process track is updated, the storage information of the business process log is corrected based on the updated second process track.

[0022] A fault location device, comprising:

[0023] An acquisition unit, configured to acquire a first service identifier and a first process track; the first service identifier is used to indicate a first service process; the first process track indicates a running failure of the first service process;

[0024] The acquisition unit is further used to acquire a first business log based on the first business identifier; the first business log includes an association log between upstream and downstream modules of the first business process, an execution mark log of the request start, and a completion mark log;

[0025] A processing unit is used to detect the first process trajectory based on the first business log to determine the fault location of the first business process.

[0026] An electronic device comprising: a processor and a memory for storing a computer program that can be run on the processor,

[0027] Wherein, when the processor is used to run the computer program, it executes the steps of any one of the above methods.

[0028] A storage medium having a computer program stored thereon, characterized in that when the computer program is executed by a processor, the steps of any one of the above methods are implemented.

[0029] A computer product comprises a computer program, wherein the computer program implements the steps of any one of the above methods when executed by a processor.

[0030] The present application provides a fault location method, device, equipment, medium and product, which obtains a first business identifier and a first process trajectory; the first business identifier is used to indicate a first business process; the first process trajectory indicates a running fault of the first business process; based on the first business identifier, a first business log is obtained; the first business log includes an association log between upstream and downstream modules of the first business process, an execution mark log of a request to start and a completion mark log; based on the first business log, the first process trajectory is detected to determine the fault location of the first business process. That is to say, the present application obtains the first business identifier and the first process trajectory, obtains the first business log based on the first business identifier, the first business log includes an association log between upstream and downstream modules of the first business process, an execution mark log of a request to start and a completion mark log, detects the first process trajectory based on the first business log, determines the fault location of the first business process, so as to realize the rapid location of business faults by associating business logs, and solves the problem in the related technology that in a multi-system and multi-engineering module environment, the log volume is usually large and cannot be associated, and the fault cannot be quickly located. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1 A flowchart of a fault location method provided in this application;

[0032] Figure 2 A flow chart of a business process trajectory generation provided for this application;

[0033] Figure 3 A schematic diagram of a business process trajectory completed for this application;

[0034] Figure 4 A flowchart of another fault location method provided by the present application;

[0035] Figure 5 A schematic diagram of an abnormal business process trajectory provided for this application;

[0036] Figure 6 A flowchart of a business process log update provided for this application;

[0037] Figure 7 A schematic diagram of the third type of abnormal business process trajectory provided for this application;

[0038] Figure 8 A schematic diagram of the structure of a fault location device provided in this application;

[0039] Fig. 9 A schematic diagram of the structure of an electronic device provided in this application. DETAILED DESCRIPTION

[0040] In order to make the purpose, technical solutions and advantages of the present application clearer, the technical solutions of the present application are further elaborated in detail below in conjunction with the drawings and embodiments. The described embodiments should not be regarded as limiting the present application. All other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present application.

[0041] In the following description, reference is made to “some embodiments”, which describe a subset of all possible embodiments, but it will be understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0042] The terms "first / second / third" involved in the present application are merely used to distinguish similar objects and do not represent a specific ordering of the objects. It can be understood that "first / second / third" can be interchanged with a specific order or sequence where permitted, so that the embodiments of the present application described herein can be implemented in an order other than that illustrated or described herein.

[0043] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used herein are only for the purpose of describing the embodiments of this application and are not intended to limit this application.

[0044] The embodiment of the present application provides a fault location method, referring to Figure 1 As shown, the method comprises the following steps:

[0045] Step S101: Obtain a first service identifier and a first process track.

[0046] The first business identifier is used to indicate the first business process; and the first process trajectory indicates a running failure of the first business process.

[0047] It is understandable that in the field of cloud computing, taking the activation of cloud host services as an example, the entire business process involves multiple tasks such as order activation, cloud host resource activation, network resource activation, etc., spanning multiple systems and multiple engineering modules.

[0048] In actual applications, for environments with multiple systems and multiple engineering modules, when initiating a business request, a business unique identifier can be set for the business process corresponding to the business request at the front end, and the business unique identifier is passed to the back end along with other key information required for the business process, and the log format of the business process log output by each system and engineering module between systems is agreed upon by protocol, for example: requiring the log prefix to contain the business unique identifier, system tag, module tag, request unique identifier (reqID) and request time. The first business identifier can be understood as the business unique identifier.

[0049] The upstream and downstream modules establish a handshake mechanism during the call. When the downstream module receives the request from the upstream module, it prints the information received from the upstream request. When the upstream request is received, an upstream and downstream association log is inserted at the beginning of the log. The log contains the system tags, module tags, and request unique identifiers of the upper and lower engineering modules. Through this association log, the upstream module information of the log can be quickly obtained. At the same time, after receiving the request, the upstream module synchronously returns its own system tag, module tag, and request unique identifier. The upstream module also prints it to the log. Through this association log, the downstream module information of the log can be quickly obtained. You can also insert the execution mark log of the request start and the normal completion mark log in the log. When the request starts, the execution mark log of the request start is printed. When the request is interrupted or an exception is caught halfway through the request execution, the normal completion mark is not printed. Only when the process is completed normally, the corresponding normal completion mark log is printed at the end of the request. In the log traversal process, an engineering module is considered a normal node only if and only if both the execution mark log of the request start and the normal completion mark log of the request exist.

[0050] Step S102: Acquire a first service log based on the first service identifier.

[0051] The first business log includes the association log between the upstream and downstream modules of the first business process, the execution mark log of the request start, and the completion mark log.

[0052] It can be understood that the business process logs generated by all business processes in different systems and different engineering modules can be stored in the search server (Elasticsearch). The index is created through Elasticsearch, and the mapping relationship between the logs of each system and each engineering module and the index of Elasticsearch is stored in the database as the initial log location storage information.

[0053] In actual applications, you can customize the scheduled tasks automatically generated by the business process trajectory through Elasticsearch. For example, you can randomly extract the data of a certain engineering module node of a certain business process on the previous day, find the upstream engineering module node and system information through the correlation logs between the upstream and downstream modules, and combine the mapping relationship between the engineering module and the Elasticsearch index to quickly obtain the log of the previous node. Repeat this cycle until you get the first engineering module node. By looping through the logs of the downstream system and engineering module through the first engineering module node, you can get all the key logs related to the business process. The first business log can be understood as the key log of the first business process.

[0054] Step S103: Detect the first process track based on the first business log to determine the fault location of the first business process.

[0055] In practical applications, reference Figure 2 As shown, by extracting the system and engineering modules in the key logs, the business process trajectory of the entire business process in each system and engineering module can be obtained. If the extracted log is a normal log (all requests have normally printed the execution mark of the start of the request and the normal completion mark), and there is no interruption, then the business process is judged to be normal, and the business process trajectory can be updated to the database, and the first engineering module node and system information of the business process trajectory are updated at the same time. Otherwise, the log of the previous hour is re-extracted, and this is repeated N times until a normal log is extracted. The first business log of the first business process can be obtained in the database through the first business identifier.

[0056] refer to Figure 3 As shown, the business process trajectory generated according to the first business log can be understood as a trajectory generated when the business process is completed. The trajectory can be compared with the first process trajectory to determine the fault location of the first business process.

[0057] It can be seen from the above content that the embodiment of the present application obtains the first business identifier and the first process trajectory, obtains the first business log based on the first business identifier, the first business log includes the association log between the upstream and downstream modules of the first business process, the execution mark log of the request start, and the completion mark log, and detects the first process trajectory based on the first business log to determine the fault location of the first business process, so as to realize the rapid positioning of business faults by associating business logs, and solves the problem in the related technology that in a multi-system and multi-engineering module environment, the log volume is usually large and cannot be associated, and the fault cannot be quickly located.

[0058] In some embodiments of the present application, obtaining a first service log based on a first service identifier includes:

[0059] Obtaining a first service request; the first service request is used to generate a first service identifier;

[0060] Generate a business process log based on the first business identifier; the business process log includes system information and module information called by the first business process;

[0061] A first service log is generated based on the system information and the module information.

[0062] In actual applications, the first business request can be understood as a request to initiate the first business process. When initiating a business request, a business unique identifier can be set on the front end for the business process corresponding to the business request. The business unique identifier is passed to the back end along with other key information required for the business process, and a protocol is agreed upon for the log format of the business process log output by each system and engineering module between systems. For example, the log prefix is ​​required to contain the business unique identifier, system tag, module tag, request unique identifier, and request time. Exemplarily, the business process log prefix can be as follows:

[0063] [Business unique identifier] [Business process name] [System 1] [Engineering module 1] [reqID-20231028-01] [2023-10-28 11:57:20]

[0064] The upstream and downstream modules establish a handshake mechanism during the call. When the downstream module receives a request from the upstream module, it prints the received upstream request and inserts an upstream and downstream association log at the beginning of the log. The log contains the system tags, module tags, and request unique identifiers of the upper and lower engineering modules. The downstream module can be printed as follows:

[0065] [Business unique identifier] [Business process name] [System 2] [Engineering module 2] [reqID-20231028-02] [2023-10-28 11:58:20]: Received request from [System 1] [Engineering module 1] [reqID-20231028-01]

[0066] After receiving the request, the upstream module synchronously returns its own system tag, module tag, and request unique identifier. The upstream module also prints it to the log. The upstream module printing can be as follows:

[0067] [Business unique identifier] [Business process name] [System 1] [Engineering module 1] [reqID-20231028-01] [2023-10-28 11:58:20]: A request has been successfully initiated to [System 2] [Engineering module 2]. The downstream request unique identifier is [reqID-20231028-02]

[0068] You can also insert the execution mark log of the request start and the normal completion mark log in the log. When the request starts, the execution mark log of the request start is printed. When the request is interrupted or an exception is caught in the middle of the request execution, the normal completion mark is not printed. Only when the process is completed normally, the corresponding normal completion mark log is printed at the end of the request. During the log traversal process, the engineering module is considered a normal node only if and only if both the execution mark log of the request start and the normal completion mark log of the request exist.

[0069] In some embodiments of the present application, generating a first service log based on system information and module information includes:

[0070] The first system and the first module are called to traverse the system information and the module information to obtain the first business log; the first system indicates the first business system called by the first business process; the first module indicates the first business module called by the first business process.

[0071] In practical applications, the scheduled tasks automatically generated by customizing the business process trajectory can be generated through Elasticsearch. For example, the data of a certain engineering module node of a certain business process on the previous day can be randomly extracted. Through the associated logs between the upstream and downstream modules, the upstream engineering module node and system information can be found. Combined with the mapping relationship between the engineering module and the Elasticsearch index, the log of the previous node can be quickly obtained, and the loop traversal is repeated until the first engineering module node is obtained. By looping through the logs of the downstream system and engineering module through the first engineering module node, all key logs related to the business process can be obtained. The first business log can be understood as the key log of the first business process. The scheduled task is set to start when the business is idle, which can effectively avoid the access pressure on the log storage cluster during the automatic generation process. Selecting the time as the previous day can effectively avoid the log obtained for the completed process of the day, thereby improving the generation efficiency. If the key log is still not obtained after N times, a prompt message can be generated.

[0072] In some embodiments of the present application, after the first service log is generated based on the system information and the module information, the following steps are included:

[0073] A second process track is generated based on the first business log; the second process track indicates that the first business process has completed execution.

[0074] In practical applications, reference Figure 2As shown, by extracting the system and engineering modules in the key logs, the business process track of the entire business process in each system and engineering module can be obtained. If the extracted log is a normal log (all requests have normally printed the execution mark of the request start and the normal completion mark), and there is no interruption, then the business process is judged to be normal, and the business process track can be updated to the database, and the first engineering module node and system information of the business process track are updated at the same time. Otherwise, the log of the previous hour is re-extracted, and this is repeated N times until a normal log is extracted.

[0075] refer to Figure 3 As shown, the business process trajectory generated according to the first business log can be understood as a trajectory generated when the business process is completed. The trajectory can be compared with the first process trajectory to determine the fault location of the first business process.

[0076] In some embodiments of the present application, detecting the first process trace based on the first business log to determine the fault location of the first business process includes:

[0077] Compare the first process trace with the second process trace to determine the faulty module; the faulty module does not include an execution flag and / or a completion flag of the request start;

[0078] A fault location is determined based on the fault module.

[0079] In practical applications, reference Figure 4 As shown, the first business log of the first business process can be obtained in the database according to the first business identifier, and a second process track, that is, an automatically generated business process track, can be generated. The first process track and the second process track are compared to determine the faulty engineering module. The faulty engineering module does not include the execution flag and / or completion flag of the request start;

[0080] refer to Figure 5 As shown, the first process track is compared with the second process track. If the node contains the execution flag of the request start and the normal completion flag, the node is judged to be normal, otherwise the node is judged to be abnormal. For the business module that is not accessed due to business interruption, it is grayed out. Taking the faulty engineering module as engineering module 6 as an example, the fault location of the business process is determined according to the connection and module position of engineering module 6.

[0081] In some embodiments of the present application, the method further comprises:

[0082] If the second process track is updated, the storage information of the business process log is corrected based on the updated second process track.

[0083] In actual applications, if the second process track is updated, the log storage index will change, so you can customize a scheduled task to automatically correct the log location information. Figure 6 As shown in the figure, through the automatically generated business process track, we can get the system, engineering module, and log keyword features of the next process, traverse all indexes in Elasticsearch, find the logs that meet the conditions, obtain the corresponding index, and automatically correct the mapping relationship between the stored logs of each system and engineering module and the Elasticsearch index. This scheduled task can be executed separately from the scheduled task automatically generated by the business process track to avoid mutual interference.

[0084] In a realistic scenario, refer to Figure 7 As shown, the fault location method of the embodiment of the present application can be implemented in the following manner:

[0085] 1. On the client side of log retrieval, use the unique business ID obtained on the user's web page to specify the corresponding business process name and start querying. The backend can then obtain the automatically generated business process track through the unique business ID.

[0086] 2. Determine the system and engineering nodes called in each step, query all related key logs through the Elasticsearch interface, compare the process trajectory of the running failure with the automatically generated business process trajectory, and quickly locate the system and engineering module with problems.

[0087] 3. Find the project module log that does not have a normal end tag, obtain the associated request log through the request unique identifier, and generate a prompt.

[0088] It can be seen from the above content that the embodiment of the present application obtains the first business identifier and the first process trajectory, and obtains the first business log based on the first business identifier. The first business log includes the association log between the upstream and downstream modules of the first business process, the execution mark log of the request start, and the completion mark log. The first process trajectory is detected based on the first business log to determine the fault location of the first business process, and the log output format of multiple systems and multiple engineering modules is standardized. On the basis of the traditional business request identifier, upstream and downstream association logs, the execution mark log of the request start, and the normal completion mark log are added as key logs. The business trajectory process is automatically generated through the key logs as a reference for the normal business process trajectory, so as to realize the association of business logs to quickly locate business faults, and solves the problem in the related technology that in a multi-system and multi-engineering module environment, the log volume is usually large and cannot be associated, and the fault cannot be quickly located.

[0089] Based on the same inventive concept as above, Figure 8A schematic diagram of the structure of a fault location device provided by an embodiment of the present invention, the fault location device 800 includes:

[0090] The acquisition unit 801 is used to acquire a first service identifier and a first process track; the first service identifier is used to indicate a first service process; the first process track indicates a running failure of the first service process;

[0091] The acquisition unit 801 is further used to acquire a first business log based on the first business identifier; the first business log includes an association log between upstream and downstream modules of the first business process, an execution mark log of the request start, and a completion mark log;

[0092] The processing unit 802 is used to detect the first process track based on the first business log to determine the fault location of the first business process.

[0093] In some embodiments of the present application, the acquisition unit 801 is further used to acquire a first service request; the first service request is used to generate a first service identifier;

[0094] Generate a business process log based on the first business identifier; the business process log includes system information and module information called by the first business process;

[0095] A first service log is generated based on the system information and the module information.

[0096] In some embodiments of the present application, the acquisition unit 801 is also used to call the first system and the first module to traverse the system information and module information to obtain the first business log; the first system indicates the first business system called by the first business process; the first module indicates the first business module called by the first business process.

[0097] In some embodiments of the present application, the processing unit 802 is further configured to generate a second process trajectory based on the first business log; the second process trajectory indicates that the first business process is completed.

[0098] In some embodiments of the present application, the processing unit 802 is further configured to generate a second process trajectory based on the first business log; the second process trajectory indicates that the first business process is completed.

[0099] In some embodiments of the present application, the processing unit 802 is further used to compare the first process trace and the second process trace to determine the faulty module; the faulty module does not include an execution flag and / or a completion flag of the request start;

[0100] A fault location is determined based on the fault module.

[0101] In some embodiments of the present application, the processing unit 802 is further configured to, if the second process track is updated, correct the storage information of the business process log based on the updated second process track.

[0102] Based on the foregoing embodiments, an embodiment of the present application provides an electronic device, Fig. 9 Schematic diagram of the hardware structure of an electronic device according to an embodiment of the present invention. The electronic device 900 includes: at least one processor 901, a memory 902, and optionally, the electronic device 900 may further include at least one communication interface 903. The various components in the electronic device 900 are coupled together via a bus system 904. It can be understood that the bus system 904 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 904 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, Fig. 9 Various buses are labeled as bus system 904.

[0103] Based on the hardware implementation of the above program modules, the communication interface 903 can exchange information with other communication devices;

[0104] The processor 901 is connected to the communication interface 903 to implement information interaction with other communication devices, and is used to execute the method provided by one or more of the above technical solutions when running the computer program;

[0105] A memory 902 on which the computer program is stored.

[0106] Specifically, the processor 901 is used to obtain a first service identifier and a first process track; the first service identifier is used to indicate a first service process; the first process track indicates a running failure of the first service process;

[0107] Acquire a first business log based on the first business identifier; the first business log includes a correlation log between upstream and downstream modules of the first business process, an execution mark log of the request start, and a completion mark log;

[0108] The first process track is detected based on the first business log to determine the fault location of the first business process.

[0109] In some embodiments of the present application, the processor 901 is used to obtain a first service request; the first service request is used to generate a first service identifier;

[0110] Generate a business process log based on the first business identifier; the business process log includes system information and module information called by the first business process;

[0111] A first service log is generated based on the system information and the module information.

[0112] In some embodiments of the present application, the processor 901 is used to call the first system and the first module to traverse the system information and module information to obtain a first business log; the first system indicates the first business system called by the first business process; the first module indicates the first business module called by the first business process.

[0113] In some embodiments of the present application, the processor 901 is used to generate a second process trajectory based on the first business log; the second process trajectory indicates that the first business process is completed.

[0114] In some embodiments of the present application, the processor 901 is used to generate a second process trajectory based on the first business log; the second process trajectory indicates that the first business process is completed.

[0115] In some embodiments of the present application, the processor 901 is used to compare the first process trace and the second process trace to determine the faulty module; the faulty module does not include an execution flag and / or a completion flag of the request start;

[0116] A fault location is determined based on the fault module.

[0117] In some embodiments of the present application, the processor 901 is configured to correct the storage information of the business process log based on the updated second process track if the second process track is updated.

[0118] It can be understood that the memory 902 can be a volatile memory or a non-volatile memory, and can also include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic random access memory (FRAM), a flash memory, a magnetic surface memory, an optical disk, or a compact disc read-only memory (CD-ROM); the magnetic surface memory can be a disk memory or a tape memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), Sync Link Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM).The memory 902 described in the embodiments of the present invention is intended to include, but is not limited to, these and any other suitable types of memories.

[0119] The memory 902 in the embodiment of the present invention is used to store various types of data to support the operation of the electronic device 900. Examples of such data include: any computer program for operating on the electronic device 900. The program for implementing the method of the embodiment of the present invention may be included in the memory 902.

[0120] The method disclosed in the above embodiment of the present invention can be applied to the processor 901, or implemented by the processor 901. The processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in the processor or an instruction in the form of software. The above processor may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The processor can implement or execute the methods, steps and logic block diagrams disclosed in the embodiment of the present invention. The general-purpose processor may be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiment of the present invention, it can be directly embodied as a hardware decoding processor to execute, or it can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium, which is located in a memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0121] In an exemplary embodiment, the electronic device 900 can be implemented by one or more application specific integrated circuits (ASIC), DSP, programmable logic device (PLD), complex programmable logic device (CPLD), field programmable gate array (FPGA), general processor, controller, microcontroller (MCU), microprocessor, or other electronic components to execute the above method.

[0122] Based on the above embodiments, the embodiments of the present application further provide a computer product, including a computer program, which is executed by a processor to implement Figure 1 The corresponding embodiments provide steps in the fault location method.

[0123] Based on the above embodiments, the embodiments of the present application further provide a storage medium, wherein the storage medium stores computer executable instructions, and the computer executable instructions are configured to execute Figure 1 The corresponding embodiment provides a fault location method.

[0124] It should be noted that the above-mentioned computer storage medium can be a memory such as ROM, PROM, EPROM, EEPROM, FRAM, FlashMemory, magnetic surface storage, optical disk, or CD-ROM; it can also be various electronic devices including one or any combination of the above-mentioned memories, such as mobile phones, computers, tablet devices, personal digital assistants, etc.

[0125] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0126] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0127] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, 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 a terminal device (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0128] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0129] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0130] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0131] The above are only preferred embodiments of the present application, and are not intended to limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A fault location method, characterized in that: The method comprises: Obtaining a first service identifier and a first process track; the first service identifier is used to indicate a first service process; the first process track indicates a running failure of the first service process; Acquire a first business log based on the first business identifier; the first business log includes an association log between upstream and downstream modules of the first business process, an execution mark log of the request start, and a completion mark log; The first process trajectory is detected based on the first business log to determine a fault location of the first business process.

2. The method according to claim 1, characterized in that The acquiring the first service log based on the first service identifier includes: Obtaining a first service request; the first service request is used to generate the first service identifier; Generate a business process log based on the first business identifier; the business process log includes system information and module information called by the first business process; The first service log is generated based on the system information and the module information.

3. The method according to claim 2, characterized in that The generating the first service log based on the system information and the module information includes: The first system and the first module are called to traverse the system information and the module information to obtain the first business log; the first system indicates the first business system called by the first business process; the first module indicates the first business module called by the first business process.

4. The method according to claim 2, characterized in that After the first service log is generated based on the system information and the module information, the method includes: A second process trajectory is generated based on the first business log; the second process trajectory indicates that the first business process has completed execution.

5. The method according to claim 4, characterized in that The detecting the first process track based on the first business log to determine the fault location of the first business process includes: Comparing the first process track with the second process track, determining a faulty module; the faulty module does not include an execution flag and / or a completion flag of a request start; The fault location is determined based on the fault module.

6. The method according to claim 4, characterized in that The method further comprises: If the second process track is updated, the storage information of the business process log is corrected based on the updated second process track.

7. A fault location device, characterized in that: The device comprises: An acquisition unit, configured to acquire a first service identifier and a first process track; the first service identifier is used to indicate a first service process; the first process track indicates a running failure of the first service process; The acquisition unit is further used to acquire a first business log based on the first business identifier; the first business log includes an association log between upstream and downstream modules of the first business process, an execution mark log of the request start, and a completion mark log; A processing unit is used to detect the first process trajectory based on the first business log to determine the fault location of the first business process.

8. An electronic device, characterized in that: include: a processor and a memory for storing a computer program capable of being executed on the processor, Wherein, when the processor is used to run the computer program, it executes the steps of the method described in any one of claims 1 to 6.

9. A storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

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

Images