Business defect checking method, device and equipment and storage medium thereof

Abstract

The embodiment of the invention belongs to the technical field of research and development design, is applied to a business problem troubleshooting scene when multiple processing subsystems cooperatively perform business execution, and relates to a business defect troubleshooting method, device and equipment and a storage medium thereof. Sorting the distinguishing identification information according to the execution priority; obtaining a problem service order number and problem reporting time; receiving service execution logs of all the processing subsystems; retrieving all the service execution logs by taking the problem service number as a retrieval field to obtain a retrieval result; business defects corresponding to the problem business order numbers are checked based on the retrieval result and the serialized distinguishing identification information. According to the business defect troubleshooting method provided by the invention, the business defects can be scientifically and quickly troubleshot and processed by combining the fixed-form execution characterization data recorded in the business execution logs of the plurality of processing subsystems when the business execution error is reported.

Description

Technical Field

[0001] The present application relates to the field of R&D and design technology, and is applied to business problem troubleshooting scenarios when multiple processing subsystems collaborate to perform business, and in particular, to a business defect troubleshooting method, device, equipment, and storage medium thereof. Background Art

[0002] In the business execution involving multiple processing subsystems, for example: the rights and interests system distributes rights and interests, the execution and processing steps involved include: after the user generates a contract or order by executing the rights and interests selection operation, the big data begins to make compliance judgments and pushes the qualified list to the rights and interests system. The rights and interests system then parses the list and screens the users who need to be distributed. After the list is sent out, the subsequent systems perform a lot of complex verifications, and the operation finally calls the third-party coupon distribution interface to distribute coupons. This involves the order generation system, the compliance analysis system, the rights and interests analysis system, the compliance distribution system and the final rights and interests distribution system. Once an execution problem occurs in a certain processing link and an error is generated, it often involves the troubleshooting operation of multiple processing systems.

[0003] There are two main troubleshooting methods at present. One is to perform execution problem troubleshooting on each processing subsystem separately. This method is prone to stand from the perspective of business limitations, resulting in inaccurate troubleshooting results. The other method is to re-follow the business processing logic, set problem identification anchor points, and repeat the previous execution steps. This method leads to the problem of excessive workload in business defect troubleshooting. Therefore, when business execution problems occur, the existing technology still has the problem of being unable to scientifically and quickly troubleshoot business defects. Summary of the invention

[0004] The purpose of the embodiments of the present application is to propose a business defect troubleshooting method, device, equipment and storage medium thereof to solve the problem that the prior art is unable to scientifically and quickly troubleshoot business defects when business execution problems occur.

[0005] In order to solve the above technical problems, the embodiment of the present application provides a service defect troubleshooting method, which adopts the following technical solution:

[0006] A method for troubleshooting business defects comprises the following steps:

[0007] Obtaining distinguishing identification information pre-set for all processing subsystems according to the target business execution logic;

[0008] Sorting the distinguishing identification information according to the execution priorities of all the processing subsystems to obtain serialized distinguishing identification information;

[0009] Obtain the problem business order number and problem reporting time sent by the target monitoring end;

[0010] Receive the business execution logs corresponding to all processing subsystems before the problem reporting time, wherein the business execution logs record<key,value> The execution characterization data of the structure, the value corresponding to the key is used to characterize the target business order number that has been processed by the processing subsystem, and the value corresponding to the value is used to characterize the distinguishing identification information of the processing subsystem;

[0011] Using the problem business order number as a search field, search all business execution logs to obtain search results;

[0012] Based on the search result and the serialized distinguishing identification information, the business defect corresponding to the problematic business order number is checked.

[0013] Furthermore, before executing the step of sorting the distinguishing identification information according to the execution priorities of all the processing subsystems to obtain serialized distinguishing identification information, the method further includes:

[0014] According to the processing sequence of all processing subsystems involved in the target business execution logic, setting execution priorities for all processing subsystems;

[0015] The step of sorting the distinguishing identification information according to the execution priorities of all the processing subsystems to obtain serialized distinguishing identification information specifically includes:

[0016] Constructing a tree-type priority map based on the execution priorities of all the processing subsystems and the distinguishing identification information;

[0017] Sorting the distinguishing identification information according to the node transmission order of all transmission nodes in the tree-type priority map;

[0018] Obtain the serialized distinguishing identification information corresponding to all node transmission lines.

[0019] Furthermore, the step of constructing a tree-type priority map based on the execution priorities of all the processing subsystems and the distinguishing identification information specifically includes:

[0020] Setting the distinguishing identification information as a transfer node of the tree-type priority map;

[0021] According to the trend of execution priority from high to low, the processing subsystems included in different execution priorities are screened out in turn;

[0022] According to the processing subsystems respectively included in the different execution priorities, the transmission nodes respectively included in the different execution priorities are identified;

[0023] According to the trend of execution priority from high to low, hierarchical processing is performed on the transfer nodes respectively contained in different execution priorities to obtain the hierarchical processing results corresponding to all transfer nodes;

[0024] Based on the processing sequence of all processing subsystems involved in the target business execution logic, the transfer nodes in the hierarchical processing results are connected to obtain the tree-type priority map.

[0025] Furthermore, after executing the step of receiving the business execution logs corresponding to all processing subsystems before the problem reporting time, the method further includes:

[0026] identifying the processing subsystem with the highest execution priority according to the serialized distinguishing identification information;

[0027] Filter out the business execution logs corresponding to the processing subsystem with the highest execution priority;

[0028] Using the problem business order number as a search field, the business execution start time is retrieved from the business execution log;

[0029] The business execution log between the business execution start time and the problem reporting time is displayed on a preset front-end analysis interface.

[0030] Furthermore, the step of searching all business execution logs using the problem business order number as a search field to obtain search results specifically includes:

[0031] Using the problem business order number as a search field, all business execution logs are searched in sequence;

[0032] Get the business execution start time, business execution end time and<key,value> Execution characterization data of the structure;

[0033] The business execution start time, business execution end time and<key,value> The execution representation data of the structure serves as the retrieval result corresponding to the corresponding processing subsystem.

[0034] Furthermore, the step of troubleshooting the business defect corresponding to the problematic business order number based on the search result and the serialized distinguishing identification information specifically includes:

[0035] Identify whether the search results corresponding to the current processing subsystem contain the problem business order number as the key value<key,value> Execution characterization data of the structure;

[0036] If the search result corresponding to the current processing subsystem does not contain the problem business order number as the key value<key,value> The execution characterization data of the structure is used to mark the current processing subsystem as the processing subsystem that has not been executed by the problematic business order number;

[0037] If the search results corresponding to the current processing subsystem contain the problem business order number as the key value<key,value> The execution characterization data of the structure is used to mark the current processing subsystem as the processing subsystem to which the problematic business order number has been executed;

[0038] According to the serialized distinguishing identification information, all processing subsystems where the problematic business order number has been executed are sorted and arranged to obtain a sorting and arrangement result;

[0039] According to the sorting and arranging results, the business defects corresponding to the problematic business order number are checked.

[0040] Furthermore, the step of troubleshooting the business defects corresponding to the problematic business order number according to the sorting and arranging results specifically includes:

[0041] Identifying all processing subsystems corresponding to the serialized distinguishing identification information;

[0042] Performing a serial comparison between all processing subsystems in the sorting result and all processing subsystems corresponding to the serialized distinguishing identification information;

[0043] According to the comparison result, identifying whether there is a processing subsystem that should be executed but is not executed among all the processing subsystems in the sorting and arranging result;

[0044] If there is no processing subsystem that should be executed but is not executed among all the processing subsystems in the sorting and arranging results, all the processing subsystems in the sorting and arranging results are fed back to the preset business defect processing terminal in reverse order to check each processing subsystem one by one;

[0045] If there is a processing subsystem that should be executed but is not executed among all the processing subsystems in the sorting and arranging results, the processing subsystem that should be executed but is not executed is marked as the target subsystem, and the upper-level processing subsystem of the target subsystem and the lower-level processing subsystem of the target subsystem are marked, and the upper-level processing subsystem of the target subsystem, the target subsystem and the lower-level processing subsystem of the target subsystem are fed back to the preset business defect processing end as a business defect troubleshooting system.

[0046] In order to solve the above technical problems, the embodiment of the present application also provides a service defect troubleshooting device, which adopts the following technical solution:

[0047] A service defect troubleshooting device, comprising:

[0048] A distinguishing identification information acquisition module is used to acquire distinguishing identification information that is pre-set for all processing subsystems according to the target business execution logic;

[0049] A distinguishing identification information sorting module, used to sort the distinguishing identification information according to the execution priorities of all the processing subsystems to obtain serialized distinguishing identification information;

[0050] The problem business information acquisition module is used to obtain the problem business order number and problem reporting time sent by the target monitoring end;

[0051] The business execution log receiving module is used to receive the business execution logs corresponding to all processing subsystems before the problem reporting time, wherein the business execution log records<key,value> The execution characterization data of the structure, the value corresponding to the key is used to characterize the target business order number that has been processed by the processing subsystem, and the value corresponding to the value is used to characterize the distinguishing identification information of the processing subsystem;

[0052] A business execution log retrieval module is used to search all business execution logs using the problem business order number as a search field to obtain search results;

[0053] A business defect troubleshooting module is used to troubleshoot the business defects corresponding to the problematic business order number based on the search results and the serialized distinguishing identification information.

[0054] In order to solve the above technical problems, the embodiment of the present application further provides a computer device, which adopts the following technical solution:

[0055] A computer device includes a memory and a processor, wherein the memory stores computer-readable instructions, and the processor implements the steps of the above-mentioned service defect troubleshooting method when executing the computer-readable instructions.

[0056] In order to solve the above technical problems, the embodiment of the present application further provides a computer-readable storage medium, which adopts the following technical solution:

[0057] A computer-readable storage medium stores computer-readable instructions, which, when executed by a processor, implement the steps of the service defect troubleshooting method as described above.

[0058] Compared with the prior art, the embodiments of the present application have the following beneficial effects:

[0059] The business defect troubleshooting method described in the embodiment of the present application is to obtain the distinguishing identification information that is pre-set for all processing subsystems according to the target business execution logic; sort the distinguishing identification information according to the execution priority of all processing subsystems to obtain serialized distinguishing identification information; obtain the problem business order number and the problem reporting time sent by the target monitoring terminal; receive the business execution logs corresponding to all processing subsystems before the problem reporting time; use the problem business order number as the search field to search all business execution logs to obtain the search results; and troubleshoot the business defects corresponding to the problem business order number based on the search results and the serialized distinguishing identification information. The business defect troubleshooting method provided by the present application is convenient for scientifically and quickly troubleshooting business defects when business execution errors occur, combined with the fixed-form execution representation data recorded in the business execution logs of multiple processing subsystems. BRIEF DESCRIPTION OF THE DRAWINGS

[0060] In order to more clearly illustrate the scheme in the present application, a brief introduction is given below to the drawings required for use in the description of the embodiments of the present application. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0061] Figure 1 is an exemplary system architecture diagram to which the present application may be applied;

[0062] Figure 2 is a flow chart of an embodiment of a method for troubleshooting business defects according to the present application;

[0063] Figure 3 yes Figure 2 A flowchart of a specific embodiment of step 202 is shown;

[0064] Figure 4 yes Figure 3 A flowchart of a specific embodiment of step 301 is shown;

[0065] Figure 5It is a flowchart of a specific embodiment of front-end display of business execution logs in the business defect troubleshooting method described in this application;

[0066] Figure 6 yes Figure 2 A flowchart of a specific embodiment of step 205 is shown;

[0067] Figure 7 yes Figure 2 A flowchart of a specific embodiment of step 206 is shown;

[0068] Figure 8 yes Figure 7 A flowchart of a specific embodiment of step 705 is shown;

[0069] Fig. 9 It is a structural schematic diagram of an embodiment of a service defect troubleshooting device according to the present application;

[0070] Fig.10 It is a structural diagram of an embodiment of a computer device according to the present application. DETAILED DESCRIPTION

[0071] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by technicians in the technical field of the present application; the terms used in the specification of the application herein are only for the purpose of describing specific embodiments and are not intended to limit the present application; the terms "including" and "having" and any variations thereof in the specification and claims of the present application and the above-mentioned drawings are intended to cover non-exclusive inclusions. The terms "first", "second", etc. in the specification and claims of the present application or the above-mentioned drawings are used to distinguish different objects, not to describe a specific order.

[0072] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0073] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings.

[0074] like Figure 1As shown, the system architecture 100 may include a terminal device 101, a network 102 and a server 103. The terminal device 101 may be a laptop 1011, a tablet computer 1012 or a mobile phone 1013. The network 102 is used to provide a medium for a communication link between the terminal device 101 and the server 103. The network 102 may include various connection types, such as wired, wireless communication links or optical fiber cables.

[0075] The user can use the terminal device 101 to interact with the server 103 through the network 102 to receive or send messages, etc. Various communication client applications can be installed on the terminal device 101, such as web browser applications, shopping applications, search applications, instant messaging tools, email clients, social platform software, etc.

[0076] The terminal device 101 can be any electronic device with a display screen and supporting web browsing. In addition to a laptop computer 1011, a tablet computer 1012 or a mobile phone 1013, the terminal device 101 can also be an e-book reader, an MP3 player (Moving Picture Experts Group Audio Layer III), an MP4 (Moving Picture Experts Group Audio Layer IV), a laptop computer, a desktop computer, etc.

[0077] The server 103 may be a server that provides various services, such as a background server that provides support for a web page displayed on the terminal device 101 .

[0078] It should be noted that the service defect troubleshooting method provided in the embodiment of the present application is generally executed by a server, and accordingly, the service defect troubleshooting device is generally arranged in the server.

[0079] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0080] Continue to refer Figure 2 , shows a flow chart of an embodiment of a method for troubleshooting service defects according to the present application. The method for troubleshooting service defects includes the following steps:

[0081] Step 201 : obtaining distinguishing identification information pre-set for all processing subsystems according to the target business execution logic.

[0082] Specifically, distinguishing identification information is set in advance for all processing subsystems according to the target business execution logic, so as to facilitate subsequent distinction and search of all processing subsystems.

[0083] Step 202: sort the distinguishing identification information according to the execution priorities of all the processing subsystems to obtain serialized distinguishing identification information.

[0084] Specifically, the distinguishing identification information is sorted according to the execution priority of all the processing subsystems. It should be understood that, assuming that all the processing subsystems include A, B, C, D and E, a total of 5 processing subsystems, and all the processing subsystems correspond to only one execution route A, B, C, D, E, then the serialized distinguishing identification information is A, B, C, D, E; assuming that all the processing subsystems include A, B, C, D and E, a total of 5 processing subsystems, and all the processing subsystems correspond to two execution routes A, B, D, E and A, C, D, E, that is, B and C are optional branch processing subsystems after A, then the serialized distinguishing identification information is two serialized results of A, B, D, E and A, C, D, E. It is applicable to the sorting of processing subsystems under multiple execution logics, and can perform serialization processing of distinguishing identification information regardless of whether it is multiple processing subsystems with a single execution logic or multiple processing subsystems with multiple branch execution logics.

[0085] The distinguishing identification information is sorted and processed according to the execution priorities of all the processing subsystems to obtain serialized distinguishing identification information, so as to facilitate the subsequent troubleshooting of business problem defects in combination with the serialized distinguishing identification information.

[0086] Step 203: Obtain the problem service order number and problem reporting time sent by the target monitoring terminal.

[0087] Specifically, the target monitoring end can be understood as a monitoring end that performs preliminary monitoring of the business execution status. This monitoring end can at least obtain the problem business order number and problem reporting time when a problem occurs in the execution of the target business. The problem business order number can be concretely understood as a distinguishing identification number used to distinguish the executed business when the business is executed, including a task identification number or a task order number, etc. The problem reporting time is generally the business execution interruption time reported when the business has an execution problem.

[0088] By obtaining the problem business order number sent by the target monitoring end, it is convenient to subsequently search and filter the business execution log according to the problem business order number. By obtaining the problem reporting time, it is convenient to set the corresponding time boundary when receiving the business execution logs of all processing subsystems in the future to avoid blindly obtaining too many business execution logs.

[0089] Step 204: Receive the business execution logs corresponding to all processing subsystems before the problem is reported.

[0090] The business execution log records<key,value> The execution characterization data of the structure, the value corresponding to the key is used to characterize the target business order number that has been processed by the processing subsystem, and the value corresponding to the value is used to characterize the distinguishing identification information of the processing subsystem.

[0091] Step 205: Using the problem business order number as a search field, search all business execution logs to obtain search results.

[0092] Specifically, it is understandable that if the current business execution log records<key,value> If the execution characterization data of the structure is found, it means that the processing subsystem corresponding to the current business execution log has processed the business process corresponding to the problem business order number. The purpose of steps 204 to 205 is to identify all subsystems that have executed the tasks corresponding to the problem business order number before the business defect is reported and all subsystems that have not executed the tasks corresponding to the problem business order number. This is to facilitate the subsequent business defect investigation and analysis in combination with the actual execution situation.

[0093] Step 206: Check the business defects corresponding to the problematic business order number based on the search result and the serialized distinguishing identification information.

[0094] In this embodiment, by obtaining the distinguishing identification information that is pre-set for all processing subsystems according to the target business execution logic; sorting the distinguishing identification information according to the execution priority of all processing subsystems to obtain serialized distinguishing identification information; obtaining the problem business order number and the problem reporting time sent by the target monitoring terminal; receiving the business execution logs corresponding to all processing subsystems before the problem reporting time; using the problem business order number as the search field, searching all business execution logs to obtain the search results; and troubleshooting the business defects corresponding to the problem business order number based on the search results and the serialized distinguishing identification information. The business defect troubleshooting method provided by the present application is convenient for scientifically and quickly troubleshooting business defects when business execution errors occur, combined with the fixed-form execution representation data recorded in the business execution logs of multiple processing subsystems.

[0095] In this embodiment, before executing the step of sorting the distinguishing identification information according to the execution priorities of all the processing subsystems to obtain serialized distinguishing identification information, the method also includes: setting execution priorities for all the processing subsystems according to the processing sequence of all the processing subsystems involved in the target business execution logic.

[0096] Specifically, when setting execution priorities for all the processing subsystems, the processing order of the processing subsystems may be branch processing. In this case, the execution priorities of the branch processing subsystems are the same, thereby ensuring the applicability of the business defect troubleshooting method.

[0097] Continue to refer Figure 3 , Figure 3 yes Figure 2 The flowchart of a specific embodiment of step 202 shown includes the following steps:

[0098] Step 301, constructing a tree-type priority map based on the execution priorities of all the processing subsystems and the distinguishing identification information;

[0099] Step 302, sorting the distinguishing identification information according to the node transfer order of all transfer nodes in the tree-type priority map;

[0100] Step 303: Obtain serialized distinguishing identification information corresponding to all node transmission lines.

[0101] By constructing a tree-type priority map, it is easier to serialize and organize the distinguishing identification information more intuitively.

[0102] Continue to refer Figure 4 , Figure 4 yes Figure 3 The flowchart of a specific embodiment of step 301 shown includes the following steps:

[0103] Step 401, setting the distinguishing identification information as a transfer node of the tree-type priority map;

[0104] Step 402, according to the trend of execution priority from high to low, the processing subsystems respectively included in different execution priorities are screened out in sequence;

[0105] Step 403, identifying the transfer nodes respectively included in the different execution priorities according to the processing subsystems respectively included in the different execution priorities;

[0106] Step 404, according to the trend of execution priority from high to low, hierarchical processing is performed on the transfer nodes respectively included in different execution priorities to obtain hierarchical processing results corresponding to all transfer nodes;

[0107] Step 405, based on the processing sequence of all processing subsystems involved in the target business execution logic, the transfer nodes in the hierarchical processing result are connected to obtain the tree-type priority map.

[0108] By setting the distinguishing identification information as the transfer node of the tree-type priority map, the transfer nodes respectively contained in different execution priorities are identified, and a tree-type priority map is constructed, so as to facilitate more intuitive serialization and arrangement of the distinguishing identification information.

[0109] Continue to refer Figure 5 In some optional implementations, after step 204, a step of displaying the business execution log on the front end is also included. Figure 5 This is a flowchart of a specific embodiment of the front-end display of the business execution log in the business defect troubleshooting method described in this application, including the following steps:

[0110] Step 501, identifying the processing subsystem with the highest execution priority according to the serialized distinguishing identification information;

[0111] Step 502, filtering out the business execution log corresponding to the processing subsystem with the highest execution priority;

[0112] Step 503, using the problem business order number as a search field, and retrieving the business execution start time from the business execution log;

[0113] Step 504: Display the business execution log between the business execution start time and the problem reporting time on a preset front-end analysis interface.

[0114] By obtaining the business execution start time of the processing subsystem with the highest execution priority and displaying the business execution log on the front end in combination with the problem reporting time, it is ensured that the business execution log to be analyzed can be fully displayed while avoiding the problem of displaying too few or too many business execution logs.

[0115] Continue to refer Figure 6 , Figure 6 yes Figure 2 The flowchart of a specific embodiment of step 205 shown includes the following steps:

[0116] Step 601, using the problem business order number as a search field, searching all business execution logs in sequence;

[0117] Step 602: Obtain the business execution start time, business execution end time and<key,value> Execution characterization data of the structure;

[0118] Step 603: The business execution start time, business execution end time and<key,value> The execution representation data of the structure serves as the retrieval result corresponding to the corresponding processing subsystem.

[0119] By including the business execution start time, business execution end time and<key,value> The execution representation data of the structure is used as the search result corresponding to the corresponding processing subsystem, so as to facilitate the subsequent business defect troubleshooting based on the execution representation data in a fixed form.

[0120] Continue to refer Figure 7 , Figure 7 yes Figure 2 The flowchart of a specific embodiment of step 206 shown includes the following steps:

[0121] Step 701, identifying whether the search result corresponding to the current processing subsystem contains a problem business order number as the key value.<key,value> Execution characterization data of the structure;

[0122] Step 702: If the search result corresponding to the current processing subsystem does not contain the problem business order number as the key value,<key,value> The execution characterization data of the structure is used to mark the current processing subsystem as the processing subsystem that has not been executed by the problematic business order number;

[0123] Step 703: If the search result corresponding to the current processing subsystem contains the problem business order number as the key value,<key,value> The execution characterization data of the structure is used to mark the current processing subsystem as the processing subsystem to which the problematic business order number has been executed;

[0124] Step 704, sorting and arranging all processing subsystems to which the problematic business order number has been executed according to the serialized distinguishing identification information to obtain a sorting and arranging result;

[0125] Step 705: According to the sorting result, the business defects corresponding to the problematic business order number are checked.

[0126] By identifying whether the search result corresponding to the current processing subsystem contains the problem business order number as the key value<key,value> The execution characterization data of the structure can be used to identify the processing subsystems that have not been executed by the problematic business order number and the processing subsystems that have been executed by the problematic business order number, ensuring that only all the processing subsystems that have been executed need to be checked for business defects in the future, avoiding a full check of all execution processing subsystems, and reasonably reducing the workload of business defect troubleshooting.

[0127] Continue to refer Figure 8 , Figure 8 yes Figure 7 The flowchart of a specific embodiment of step 705 shown includes the following steps:

[0128] Step 801, identifying all processing subsystems corresponding to the serialized distinguishing identification information;

[0129] Step 802, performing a serial comparison between all processing subsystems in the sorting result and all processing subsystems corresponding to the serialized distinguishing identification information;

[0130] Step 803, based on the comparison result, identifying whether there is a processing subsystem among all the processing subsystems in the sorting result that should be executed but has not been executed;

[0131] Step 804: If there is no processing subsystem that should be executed but is not executed among all the processing subsystems in the sorting and arranging results, all the processing subsystems in the sorting and arranging results are fed back to the preset business defect processing terminal in reverse order to check each processing subsystem one by one;

[0132] Step 805: If there is a processing subsystem that should be executed but is not executed among all the processing subsystems in the sorting and arranging results, the processing subsystem that should be executed but is not executed is marked as the target subsystem, and the upper-level processing subsystem of the target subsystem and the lower-level processing subsystem of the target subsystem are marked, and the upper-level processing subsystem of the target subsystem, the target subsystem and the lower-level processing subsystem of the target subsystem are fed back to the preset business defect processing end as a business defect troubleshooting system.

[0133] Through the serialized distinguishing identification information, all processing subsystems that have been executed by the problematic business order number are sorted and organized to obtain the sorting and organizing results, and based on the sorting and organizing results, the business defects corresponding to the problematic business order number are checked, thereby ensuring the rational business defect checking of all processing subsystems that have been executed.

[0134] The present application obtains the distinguishing identification information that is pre-set for all processing subsystems according to the target business execution logic; sorts the distinguishing identification information according to the execution priority of all processing subsystems to obtain serialized distinguishing identification information; obtains the problem business order number and the problem reporting time sent by the target monitoring terminal; receives the business execution logs corresponding to all processing subsystems before the problem reporting time; uses the problem business order number as the search field to search all business execution logs to obtain the search results; and based on the search results and the serialized distinguishing identification information, checks the business defects corresponding to the problem business order number. The business defect troubleshooting method provided by the present application is convenient for scientifically and quickly troubleshooting business defects when business execution errors occur, combined with the fixed-form execution representation data recorded in the business execution logs of multiple processing subsystems.

[0135] The embodiments of the present application can acquire and process relevant data based on artificial intelligence technology. Among them, artificial intelligence (AI) is the theory, method, technology and application system that uses digital computers or machines controlled by digital computers to simulate, extend and expand human intelligence, perceive the environment, acquire knowledge and use knowledge to obtain the best results.

[0136] AI basic technologies generally include sensors, dedicated AI chips, cloud computing, distributed storage, big data processing technology, operation / interaction systems, mechatronics, etc. AI software technologies mainly include computer vision technology, robotics technology, biometrics technology, speech processing technology, natural language processing technology, and machine learning / deep learning.

[0137] In an embodiment of the present application, by obtaining the distinguishing identification information that is pre-set for all processing subsystems according to the target business execution logic; sorting the distinguishing identification information according to the execution priority of all processing subsystems to obtain serialized distinguishing identification information; obtaining the problem business order number and the problem reporting time sent by the target monitoring terminal; receiving the business execution logs corresponding to all processing subsystems before the problem reporting time; using the problem business order number as the search field, searching all business execution logs to obtain the search results; and troubleshooting the business defects corresponding to the problem business order number based on the search results and the serialized distinguishing identification information. The business defect troubleshooting method provided by the present application is convenient for scientifically and quickly troubleshooting business defects when business execution errors occur, combined with the fixed-form execution representation data recorded in the business execution logs of multiple processing subsystems.

[0138] Further references Fig. 9 , as a response to the above Figure 2 In order to realize the method shown in the figure, the present application provides an embodiment of a service defect troubleshooting device, and the device embodiment is Figure 2 Corresponding to the method embodiment shown, the device can be specifically applied to various electronic devices.

[0139] like Fig. 9 As shown, the service defect troubleshooting device 900 described in this embodiment includes: a distinguishing identification information acquisition module 901, a distinguishing identification information sorting module 902, a problem service information acquisition module 903, a service execution log receiving module 904, a service execution log retrieval module 905 and a service defect troubleshooting module 906. Among them:

[0140] The distinguishing identification information acquisition module 901 is used to acquire distinguishing identification information pre-set for all processing subsystems according to the target business execution logic;

[0141] A distinguishing identification information sorting module 902, configured to sort the distinguishing identification information according to the execution priorities of all the processing subsystems to obtain serialized distinguishing identification information;

[0142] The problem business information acquisition module 903 is used to obtain the problem business order number and problem reporting time sent by the target monitoring terminal;

[0143] The business execution log receiving module 904 is used to receive the business execution logs corresponding to all processing subsystems before the problem reporting time, wherein the business execution log records<key,value> The execution characterization data of the structure, the value corresponding to the key is used to characterize the target business order number that has been processed by the processing subsystem, and the value corresponding to the value is used to characterize the distinguishing identification information of the processing subsystem;

[0144] A business execution log search module 905 is used to search all business execution logs using the problem business order number as a search field to obtain search results;

[0145] The business defect troubleshooting module 906 is used to troubleshoot the business defect corresponding to the problematic business order number based on the search result and the serialized distinguishing identification information.

[0146] The present application obtains the distinguishing identification information that is pre-set for all processing subsystems according to the target business execution logic; sorts the distinguishing identification information according to the execution priority of all processing subsystems to obtain serialized distinguishing identification information; obtains the problem business order number and the problem reporting time sent by the target monitoring terminal; receives the business execution logs corresponding to all processing subsystems before the problem reporting time; uses the problem business order number as the search field to search all business execution logs to obtain the search results; and based on the search results and the serialized distinguishing identification information, checks the business defects corresponding to the problem business order number. The business defect troubleshooting method provided by the present application is convenient for scientifically and quickly troubleshooting business defects when business execution errors occur, combined with the fixed-form execution representation data recorded in the business execution logs of multiple processing subsystems.

[0147] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through computer-readable instructions, and the computer-readable instructions can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, the aforementioned storage medium can be a non-volatile storage medium such as a disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

[0148] It should be understood that, although the steps in the flowchart of the accompanying drawings are displayed in sequence as indicated by the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least a part of the steps in the flowchart of the accompanying drawings may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be executed in turn or alternately with other steps or at least a part of the sub-steps or stages of other steps.

[0149] To solve the above technical problems, the present application also provides a computer device. Fig.10 , Fig.10 This is a basic structural block diagram of the computer device in this embodiment.

[0150] The computer device 10 includes a memory 10a, a processor 10b, and a network interface 10c which are interconnected and communicated via a system bus. It should be noted that: Fig.10 Only a computer device 10 having a component memory 10a, a processor 10b, and a network interface 10c is shown, but it should be understood that it is not required to implement all the components shown, and more or fewer components may be implemented instead. Among them, those skilled in the art can understand that the computer device here is a device that can automatically perform numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes but is not limited to a microprocessor, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a digital processor (DSP), an embedded device, etc.

[0151] The computer device may be a computing device such as a desktop computer, a notebook, a PDA, a cloud server, etc. The computer device may interact with a user through a keyboard, a mouse, a remote controller, a touch pad, or a voice control device.

[0152] The memory 10a includes at least one type of readable storage medium, and the readable storage medium includes flash memory, hard disk, multimedia card, card-type memory (for example, SD or DX memory, etc.), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, disk, optical disk, etc. In some embodiments, the memory 10a can be an internal storage unit of the computer device 10, such as a hard disk or memory of the computer device 10. In other embodiments, the memory 10a can also be an external storage device of the computer device 10, such as a plug-in hard disk, smart memory card (Smart Media Card, SMC), secure digital (Secure Digital, SD) card, flash card (Flash Card), etc. equipped on the computer device 10. Of course, the memory 10a can also include both the internal storage unit of the computer device 10 and its external storage device. In this embodiment, the memory 10a is generally used to store the operating system and various application software installed on the computer device 10, such as a computer-readable instruction of a business defect troubleshooting method, etc. In addition, the memory 10a can also be used to temporarily store various types of data that have been output or are to be output.

[0153] The processor 10b may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chips in some embodiments. The processor 10b is generally used to control the overall operation of the computer device 10. In this embodiment, the processor 10b is used to run computer-readable instructions stored in the memory 10a or process data, such as computer-readable instructions for running the service defect troubleshooting method.

[0154] The network interface 10c may include a wireless network interface or a wired network interface. The network interface 10c is generally used to establish a communication connection between the computer device 10 and other electronic devices.

[0155] The computer device proposed in this embodiment belongs to the field of research and development design technology, and is used in business problem troubleshooting scenarios when multiple processing subsystems collaborate to perform business execution. This application obtains the distinguishing identification information that is pre-set for all processing subsystems according to the target business execution logic; sorts and processes the distinguishing identification information according to the execution priority of all processing subsystems to obtain serialized distinguishing identification information; obtains the problem business order number and the problem reporting time sent by the target monitoring terminal; receives the business execution logs corresponding to all processing subsystems before the problem reporting time; uses the problem business order number as the search field to search all business execution logs to obtain the search results; and based on the search results and the serialized distinguishing identification information, troubleshoots the business defects corresponding to the problem business order number. The business defect troubleshooting method provided by this application is convenient for scientifically and quickly troubleshooting business defects when business execution errors occur, combined with the fixed-form execution representation data recorded in the business execution logs of multiple processing subsystems.

[0156] The present application also provides another implementation, namely, providing a computer-readable storage medium, wherein the computer-readable storage medium stores computer-readable instructions, and the computer-readable instructions can be executed by a processor to enable the processor to perform the steps of the business defect troubleshooting method as described above.

[0157] The computer-readable storage medium proposed in this embodiment belongs to the field of research and development design technology, and is applied to business problem troubleshooting scenarios when multiple processing subsystems collaborate to perform business execution. This application obtains the distinguishing identification information that is pre-set for all processing subsystems according to the target business execution logic; sorts and processes the distinguishing identification information according to the execution priority of all processing subsystems to obtain serialized distinguishing identification information; obtains the problem business order number and the problem reporting time sent by the target monitoring terminal; receives the business execution logs corresponding to all processing subsystems before the problem reporting time; uses the problem business order number as the search field to search all business execution logs to obtain the search results; and based on the search results and the serialized distinguishing identification information, troubleshoots the business defects corresponding to the problem business order number. The business defect troubleshooting method provided by this application is convenient for scientifically and quickly troubleshooting business defects when business execution errors occur, combined with the fixed-form execution representation data recorded in the business execution logs of multiple processing subsystems.

[0158] 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, magnetic disk, optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0159] Obviously, the embodiments described above are only some embodiments of the present application, rather than all embodiments. The preferred embodiments of the present application are given in the accompanying drawings, but they do not limit the patent scope of the present application. The present application can be implemented in many different forms. On the contrary, the purpose of providing these embodiments is to make the understanding of the disclosure of the present application more thorough and comprehensive. Although the present application is described in detail with reference to the aforementioned embodiments, for those skilled in the art, it is still possible to modify the technical solutions recorded in the aforementioned specific implementation methods, or to perform equivalent replacement of some of the technical features therein. Any equivalent structure made using the contents of the specification and drawings of this application, directly or indirectly used in other related technical fields, is similarly within the scope of patent protection of this application.

Claims

1. A method for troubleshooting business defects, characterized in that: The steps include: Obtaining distinguishing identification information pre-set for all processing subsystems according to the target business execution logic; Sorting the distinguishing identification information according to the execution priorities of all the processing subsystems to obtain serialized distinguishing identification information; Obtain the problem business order number and problem reporting time sent by the target monitoring end; Receive the business execution logs corresponding to all processing subsystems before the problem is reported, wherein the business execution logs record<key,value> The execution characterization data of the structure, the value corresponding to the key is used to characterize the target business order number that has been processed by the processing subsystem, and the value corresponding to the value is used to characterize the distinguishing identification information of the processing subsystem; Using the problem business order number as a search field, search all business execution logs to obtain search results; Based on the search result and the serialized distinguishing identification information, the business defect corresponding to the problematic business order number is checked.

2. The method for troubleshooting business defects according to claim 1, characterized in that: Before executing the step of sorting the distinguishing identification information according to the execution priorities of all the processing subsystems to obtain serialized distinguishing identification information, the method further includes: According to the processing sequence of all processing subsystems involved in the target business execution logic, setting execution priorities for all processing subsystems; The step of sorting the distinguishing identification information according to the execution priorities of all the processing subsystems to obtain serialized distinguishing identification information specifically includes: Constructing a tree-type priority map based on the execution priorities of all the processing subsystems and the distinguishing identification information; Sorting the distinguishing identification information according to the node transmission order of all transmission nodes in the tree-type priority map; Obtain the serialized distinguishing identification information corresponding to all node transmission lines.

3. The method for troubleshooting business defects according to claim 2, characterized in that: The step of constructing a tree-type priority map based on the execution priorities of all the processing subsystems and the distinguishing identification information specifically includes: Setting the distinguishing identification information as a transfer node of the tree-type priority map; According to the trend of execution priority from high to low, the processing subsystems included in different execution priorities are screened out in turn; According to the processing subsystems respectively included in the different execution priorities, the transmission nodes respectively included in the different execution priorities are identified; According to the trend of execution priority from high to low, hierarchical processing is performed on the transfer nodes respectively contained in different execution priorities to obtain the hierarchical processing results corresponding to all transfer nodes; Based on the processing sequence of all processing subsystems involved in the target business execution logic, the transfer nodes in the hierarchical processing results are connected to obtain the tree-type priority map.

4. The service defect troubleshooting method according to claim 1 or 2, characterized in that: After executing the step of receiving the business execution logs respectively corresponding to all processing subsystems before the problem reporting time, the method further includes: identifying the processing subsystem with the highest execution priority according to the serialized distinguishing identification information; Filter out the business execution logs corresponding to the processing subsystem with the highest execution priority; Using the problem business order number as a search field, the business execution start time is retrieved from the business execution log; The business execution log between the business execution start time and the problem reporting time is displayed on a preset front-end analysis interface.

5. The method for troubleshooting business defects according to claim 1, characterized in that: The step of using the problem business order number as a search field to search all business execution logs and obtain the search results specifically includes: Using the problem business order number as a search field, all business execution logs are searched in sequence; Get the business execution start time, business execution end time and<key,value> Execution characterization data of the structure; The business execution start time, business execution end time and<key,value> The execution representation data of the structure serves as the retrieval result corresponding to the corresponding processing subsystem.

6. The service defect troubleshooting method according to claim 1 or 5, characterized in that: The step of troubleshooting the business defect corresponding to the problematic business order number based on the search result and the serialized distinguishing identification information specifically includes: Identify whether the search results corresponding to the current processing subsystem contain the problem business order number as the key value<key,value> Execution characterization data of the structure; If the search result corresponding to the current processing subsystem does not contain the problem business order number as the key value<key,va lue> The execution characterization data of the structure is used to mark the current processing subsystem as the processing subsystem that has not been executed by the problematic business order number; If the search results corresponding to the current processing subsystem contain the problem business order number as the key value<key,va lue> The execution characterization data of the structure is used to mark the current processing subsystem as the processing subsystem to which the problematic business order number has been executed; According to the serialized distinguishing identification information, all processing subsystems where the problematic business order number has been executed are sorted and arranged to obtain a sorting and arrangement result; According to the sorting and arranging results, the business defects corresponding to the problematic business order number are checked.

7. The service defect troubleshooting method according to claim 6, characterized in that: The step of troubleshooting the business defects corresponding to the problematic business order number according to the sorting and arranging results specifically includes: Identifying all processing subsystems corresponding to the serialized distinguishing identification information; Performing a serial comparison between all processing subsystems in the sorting result and all processing subsystems corresponding to the serialized distinguishing identification information; According to the comparison result, identifying whether there is a processing subsystem that should be executed but is not executed among all the processing subsystems in the sorting and arranging result; If there is no processing subsystem that should be executed but is not executed among all the processing subsystems in the sorting and arranging results, all the processing subsystems in the sorting and arranging results are fed back to the preset business defect processing terminal in reverse order to check each processing subsystem one by one; If there is a processing subsystem that should be executed but is not executed among all the processing subsystems in the sorting and arranging results, the processing subsystem that should be executed but is not executed is marked as the target subsystem, and the upper-level processing subsystem of the target subsystem and the lower-level processing subsystem of the target subsystem are marked, and the upper-level processing subsystem of the target subsystem, the target subsystem and the lower-level processing subsystem of the target subsystem are fed back to the preset business defect processing end as a business defect troubleshooting system.

8. A service defect troubleshooting device, characterized in that: include: A distinguishing identification information acquisition module is used to acquire distinguishing identification information that is pre-set for all processing subsystems according to the target business execution logic; A distinguishing identification information sorting module, used to sort the distinguishing identification information according to the execution priorities of all the processing subsystems to obtain serialized distinguishing identification information; The problem business information acquisition module is used to obtain the problem business order number and problem reporting time sent by the target monitoring end; The business execution log receiving module is used to receive the business execution logs corresponding to all processing subsystems before the problem reporting time, wherein the business execution log records<key,value> The execution characterization data of the structure, the value corresponding to the key is used to characterize the target business order number that has been processed by the processing subsystem, and the value corresponding to the value is used to characterize the distinguishing identification information of the processing subsystem; A business execution log retrieval module is used to search all business execution logs using the problem business order number as a search field to obtain search results; A business defect troubleshooting module is used to troubleshoot the business defects corresponding to the problematic business order number based on the search results and the serialized distinguishing identification information.

9. A computer device, characterized in that: It comprises a memory and a processor, wherein the memory stores computer-readable instructions, and when the processor executes the computer-readable instructions, the steps of the service defect troubleshooting method as described in any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the steps of the service defect troubleshooting method according to any one of claims 1 to 7 are implemented.

Images