Fault processing method and device, computer equipment and storage medium

Abstract

The embodiment of the invention provides a fault processing method and device, computer equipment and a storage medium, and belongs to the technical field of computers. The method comprises the following steps: receiving function error report data which is uploaded by a client and is generated in the running process of an application program; determining corresponding fault repair data in a preset fault repair database according to the function error reporting data, wherein the fault repair data comprises corresponding burying point data when the application program runs; sending the fault recovery data to the client, and receiving operation result data generated by triggering the burying point data in the process that the client operates the application program based on the fault recovery data; and when the function corresponding to the function error data is matched with the function corresponding to the operation result data, and the corresponding function is determined to be repaired according to the operation result data, generating corresponding fault repair knowledge according to the function error data and the fault repair data, and storing the fault repair knowledge in a preset fault repair database. According to the embodiment of the invention, the processing efficiency of the program fault can be improved.

Description

Technical Field

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

[0002] With the development of computer technology, some applications or web pages can now be set with richer functions. However, these program products may encounter some problems during use, such as function crash, page crash, unresponsiveness, etc.

[0003] In related technologies, in order to track functional problems in program products, when a program product fails, the full-link log data of the program product is obtained with the user's consent, and then the fault analysis is performed in combination with the full-link log data in combination with the user's feedback information on the program product, such as text and images, on the feedback page. However, since users are not program product developers, it is difficult for them to describe the specific fault type during the use of the program product, and it is difficult to reproduce the faults that occur in the program product based on the full-link data, resulting in the inability to efficiently analyze and handle the faults. Summary of the invention

[0004] The main purpose of the embodiments of the present application is to provide a fault handling method, apparatus, computer equipment and storage medium, aiming to improve the efficiency of handling program faults.

[0005] To achieve the above object, a first aspect of an embodiment of the present application provides a fault handling method, the method comprising:

[0006] Receive function error data generated during the operation of the application uploaded by the client;

[0007] Determine corresponding fault repair data in a preset fault repair database according to the function error data, wherein the fault repair data includes the corresponding tracking point data when the application is running;

[0008] Sending the fault repair data to a client, and receiving operation result data generated by triggering the tracking data during the client running the application based on the fault repair data;

[0009] When the function corresponding to the function error data matches the function corresponding to the operation result data, and it is determined according to the operation result data that the corresponding function is repaired, corresponding fault repair knowledge is generated according to the function error data and the fault repair data and saved in the preset fault repair database.

[0010] To achieve the above-mentioned purpose, a second aspect of an embodiment of the present application provides a fault handling device, the device comprising:

[0011] A receiving module, used to receive function error data generated during the operation of the application uploaded by the client;

[0012] A determination module, used to determine corresponding fault repair data in a preset fault repair database according to the function error data, wherein the fault repair data includes the corresponding tracking point data when the application is running;

[0013] A sending module, used to send the fault repair data to a client, and receive operation result data generated by triggering the tracking data during the client running the application based on the fault repair data;

[0014] A matching module is used to generate corresponding fault repair knowledge according to the function error data and the fault repair data and save it in the preset fault repair database when the function corresponding to the function error data matches the function corresponding to the operation result data and it is determined according to the operation result data that the corresponding function is repaired.

[0015] In some implementations, the fault handling device further includes a generating module, which is used to:

[0016] Before determining the corresponding fault repair data in the preset fault repair database according to the function error data, combing the functions of the application program to determine all functions of the application program and the operation steps corresponding to each function;

[0017] Generate corresponding triggering points according to the operation steps corresponding to each function, and generate point data based on the triggering points;

[0018] Generate fault repair data for each function according to the repair data corresponding to each function and the buried point data.

[0019] In some embodiments, a determination module is used to:

[0020] Determine a corresponding fault page according to the function error data;

[0021] Determine the target function where the failure occurs according to the failure page and all functions of the application;

[0022] A target function identifier of the target function is determined, and corresponding fault repair data is determined in a preset repair database based on the target function identifier.

[0023] In some embodiments, the matching module is used to:

[0024] After the operation result data generated by the tracking data is triggered in the process of the client running the application based on the fault repair data, when the function corresponding to the function error data does not match the function corresponding to the operation result data, it is determined that the function corresponding to the function error data has not been repaired;

[0025] Determine new fault repair data corresponding to the function error data in the preset fault repair database, and send the new fault repair data to the client.

[0026] In some embodiments, the matching module is used to:

[0027] Obtaining feedback information sent by the client after running the application based on the fault repair data;

[0028] When the feedback information indicates that the function corresponding to the fault repair data is repaired, corresponding fault repair knowledge is generated according to the function error data and the fault repair data and stored in the preset fault repair database.

[0029] In some embodiments, the matching module is used to:

[0030] After the operation result data generated by the tracking data is triggered in the process of the receiving client running the application based on the fault repair data, when the function corresponding to the function error data matches the function corresponding to the operation result data, and it is determined according to the operation result data that the corresponding function has not been repaired, generating abnormal notification information of the function corresponding to the function error data;

[0031] The exception notification information is sent to the developer corresponding to the application.

[0032] In some embodiments, the matching module is used to:

[0033] Determine, according to the function error data, a corresponding function and a function identifier corresponding to the function in all functions of the application program;

[0034] A mapping relationship between the function identifier and the fault repair data is established, and fault repair knowledge is generated based on the mapping relationship, and the fault repair knowledge is stored in the preset fault repair database.

[0035] To achieve the above-mentioned purpose, the third aspect of an embodiment of the present application proposes a computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the fault handling method described in the first aspect above when executing the computer program.

[0036] To achieve the above-mentioned purpose, the fourth aspect of an embodiment of the present application proposes a computer-readable storage medium, which stores multiple instructions, and the instructions are suitable for a processor to load to implement the fault handling method described in the first aspect when executed.

[0037] The present application proposes a fault handling method, apparatus, computer equipment and storage medium, which receive function error data generated during the operation of an application uploaded by a client; determine corresponding fault repair data in a preset fault repair database based on the function error data, and the fault repair data includes corresponding tracking data when the application is running; send the fault repair data to the client, and receive operation result data generated by triggering the tracking data during the process of the client running the application based on the fault repair data; when the function corresponding to the function error data matches the function corresponding to the operation result data, and it is determined according to the operation result data that the corresponding function is repaired, generate corresponding fault repair knowledge according to the function error data and the fault repair data and save it in the preset fault repair database. In this way, when an application fails, you can first obtain the corresponding function error data of the application, and then obtain the corresponding fault repair data in the preset fault repair database, and obtain the operation result data generated by the tracking data triggered in the process of running the application through the fault repair data. The fault repair data can attempt to repair the corresponding function of the application, and the tracking data in the fault repair data can reproduce the corresponding function of the application. Finally, when the function corresponding to the function error data and the function corresponding to the operation result data match, and it is determined according to the operation result data that the corresponding function is repaired, the corresponding fault repair knowledge is generated according to the function error data and the fault repair data and saved in the preset fault repair database. In this way, the function of the application fault can be reproduced and repaired, thereby improving the efficiency of handling program faults. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 is a schematic diagram of a system framework corresponding to the fault handling method provided in an embodiment of the present application;

[0039] Figure 2 It is a scenario diagram of the fault handling method provided in the embodiment of the present application;

[0040] Figure 3 It is a flowchart of a fault handling method provided in an embodiment of the present application;

[0041] Figure 4 is another flowchart of the fault handling method provided in an embodiment of the present application;

[0042] Figure 5 is a structural schematic diagram of a fault handling device provided in an embodiment of the present application;

[0043] Figure 6 It is a schematic diagram of the hardware structure of the computer device provided in the embodiment of the present application. DETAILED DESCRIPTION

[0044] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0045] It should be noted that, although the functional modules are divided in the device schematic diagram and the logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than the module division in the device or the order in the flowchart. The terms "first", "second", etc. in the specification, claims and the above drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0046] 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.

[0047] It should be noted that in each specific implementation of the present application, when it comes to the need to perform relevant processing based on data related to user identity or characteristics such as user information, user behavior data, user historical data, and user location information, the user's permission or consent will be obtained first, and the collection, use, and processing of these data will comply with relevant laws, regulations, and standards. In addition, when the embodiment of the present application needs to obtain the user's sensitive personal information, the user's separate permission or consent will be obtained through a pop-up window or by jumping to a confirmation page. After clearly obtaining the user's separate permission or consent, the necessary user-related data for the normal operation of the embodiment of the present application will be obtained.

[0048] First, some nouns involved in this application are analyzed:

[0049] Event Tracking is a method of data collection, mainly used to capture specific behaviors or events in an application. Event Tracking inserts specific code snippets into the application code to monitor and record user operations, such as page visits, button clicks, form submissions, etc. This data is then sent to the backend server for storage, analysis, and visualization.

[0050] The essence of tracking technology is to monitor events during the operation of software applications, and to judge and capture events that require attention when they occur. For example, the length of time a user clicks on an icon or watches a video. The purpose of tracking is to provide data support for product optimization and operational decisions, and to help discover problems encountered by users when using the product and optimize them.

[0051] Secondly, describe the technical problems existing in related technologies:

[0052] With the development of computer technology, some applications or web pages can now be set with richer functions. However, these program products may encounter some problems during use, such as function crash, page crash, unresponsiveness, etc.

[0053] In related technologies, in order to track functional problems in program products, when a program product fails, the full-link log data of the program product is obtained with the user's consent, and then the fault analysis is performed in combination with the full-link log data in combination with the user's feedback information on the program product, such as text and images, on the feedback page. However, since users are not program product developers, it is difficult for them to describe the specific fault type during the use of the program product, and it is difficult to reproduce the faults that occur in the program product based on the full-link data, resulting in the inability to efficiently analyze and handle the faults.

[0054] For example, in related technologies, when a functional failure occurs when a user uses an application, after providing corresponding log data and feedback information, it is impossible to reproduce the corresponding function of the application and repair it in a timely manner, resulting in low efficiency in troubleshooting the program.

[0055] Based on this, the embodiments of the present application provide a fault handling method, apparatus, computer device and storage medium, aiming to improve the efficiency of handling program faults.

[0056] See also Figure 1 , Figure 1 1 is a schematic diagram of a system framework corresponding to the fault handling method provided in the embodiment of the present application. The fault handling method provided in the embodiment of the present application can be applied to the system framework.

[0057] It includes a terminal 140, the Internet 130, a gateway 120, a server 110, and the like.

[0058] The server 110 may be a device for executing the fault handling method.

[0059] The terminal 140 includes but is not limited to mobile phones, computers, intelligent voice interaction devices, smart home appliances, vehicle-mounted terminals, aircraft, etc. The embodiments of the present application can be applied to various scenarios, including but not limited to application fault repair, web page fault repair, etc. In addition, it can be a single device or a collection of multiple devices. For example, multiple desktop computers are interconnected through a local area network, share a display, etc. to work together, and together constitute a terminal 140. The terminal 140 can communicate with the Internet 130 in a wired or wireless manner to exchange data.

[0060] The server 110 refers to a computer system that can provide certain services to the terminal 140. Compared with the ordinary terminal 140, the server 110 has higher requirements in terms of stability, security, performance, etc. The server 110 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms.

[0061] The gateway 120 is also called an internetwork connector or a protocol converter. The gateway realizes network interconnection at the transport layer and is a computer system or device that acts as a converter. The gateway is a translator between two systems that use different communication protocols, data formats or languages, or even completely different architectures. At the same time, the gateway can also provide filtering and security functions. The message sent by the terminal 140 to the server 110 must be sent to the corresponding server 110 through the gateway 120. The message sent by the server 110 to the terminal 140 must also be sent to the corresponding terminal 140 through the gateway 120.

[0062] The fault handling method in the embodiment of the present application can be applied to a variety of scenarios, such as application fault repair, web page function fault repair, etc. The scenario to which the fault handling method in the present application is applied is not limited here.

[0063] The present application may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0064] See also Figure 2 , Figure 2It is a scenario diagram of the fault handling method provided in an embodiment of the present application.

[0065] In the fault handling scenario, it includes the client and the server. The client can be electronic devices such as mobile phones, computers, tablets, etc., and the server can be a server.

[0066] In the client, during the use of applications or web pages, some functions may malfunction due to unstable code or the influence of the operating environment. For example, during the use of an online video playback application, the video suddenly cannot be loaded and the message "network connection failed" is displayed. For another example, taking a graphic editing application as an example, after the operating system is updated, the interface display is chaotic when the application is opened, and some functions cannot be used normally. For another example, during a promotional event, a large number of users access an e-commerce shopping application at the same time, resulting in slow response of the application, longer loading time for product lists and detail pages, and even freezes.

[0067] When a program failure occurs, the user generally uses a separate feedback page to describe the functional failure page encountered in his own language and selects the corresponding log data to generate functional error data and send it to the server.

[0068] The server receives function error data generated during the operation of the application uploaded by the client, wherein the function error data includes the user ID, the terminal device ID and the page data where the function failure occurs.

[0069] Then, the corresponding fault repair data is determined in the preset fault repair database according to the function error data, and the fault repair data includes the corresponding tracking data when the application is running. For example, the preset fault repair database contains the function identifier corresponding to each function in the application, and the fault repair data corresponding to each function identifier. The faulty function that has failed can be determined according to the function error data, and then the function identifier of the faulty function can be determined. Then, the corresponding fault repair data can be found in the preset fault repair database according to the function identifier of the faulty function, where the fault data includes the tracking data corresponding to the application running, and the tracking data can be triggered when the application is running to record the corresponding running data.

[0070] The server sends the fault repair data to the client, and receives the operation result data generated by the tracking data triggered by the client in the process of running the application based on the fault repair data. For example, the client can determine the function that needs to be repaired based on the fault repair data, and then repair the function that needs to be repaired based on the fault repair data, and try to run the application to execute the function after the repair. At this time, the tracking data will be triggered, thereby recording the corresponding operation result data when the application runs the function, where the operation result data contains the function identifier that triggers the function when the application runs again and the data on whether the function is running normally.

[0071] When the function corresponding to the function error data matches the function corresponding to the operation result data, and it is determined according to the operation result data that the corresponding function is repaired, the corresponding fault repair knowledge is generated according to the function error data and the fault repair data and saved in the preset fault repair database. For example, the function corresponding to the function error data is the faulty function determined by the server according to the function error data, and the function corresponding to the operation result data is the function that the application attempts to run after the application is tried to be repaired. If the faulty function and the attempted function match, it means that the fault repair data is an attempted repair of the faulty function. When it is determined according to the operation result data that the corresponding function is repaired, the corresponding fault repair knowledge is generated according to the function error data and the fault repair data and saved in the preset fault repair database.

[0072] In this way, it is possible to automatically attempt to repair the faulty function of the application, and attempt to run the repaired application to reproduce the application function. If the running result data after the application function is reproduced indicates a successful repair, then the application fault is considered to have been repaired. Compared with the related art in which the faulty function and the corresponding problem are determined only based on the log data, and then repaired manually, the efficiency of handling program faults is greatly improved in this application, and it is possible to quickly attempt to repair the faulty function of the application.

[0073] The above is a scenario description of the fault handling method provided in the embodiment of the present application.

[0074] The fault handling method, apparatus, computer device and storage medium provided in the embodiments of the present application are specifically described through the following embodiments. First, the fault handling method in the embodiments of the present application is described.

[0075] See also Figure 3 , Figure 3 : is a flowchart of a fault handling method provided in an embodiment of the present application. The fault handling method may include the following steps:

[0076] Step 210: receiving function error data generated during the running of the application program uploaded by the client;

[0077] Step 220: Determine corresponding fault repair data in a preset fault repair database according to the function error data, where the fault repair data includes corresponding point data when the application is running;

[0078] Step 230: Send the fault repair data to the client, and receive the operation result data generated by triggering the tracking data during the client running the application based on the fault repair data;

[0079] Step 240: When the function corresponding to the function error data matches the function corresponding to the operation result data, and it is determined according to the operation result data that the corresponding function is repaired, corresponding fault repair knowledge is generated according to the function error data and the fault repair data and saved in a preset fault repair database.

[0080] The following will describe in detail steps 210 to 240. These steps are mainly executed at the server end.

[0081] In step 210, function error data generated during the running of the application program uploaded by the client is received.

[0082] Among them, when the client is using the corresponding functions of a web page or application, the application's functions fail due to internal code reasons or external operating environment reasons. For example, when a user is opening a page, the page cannot be loaded and the display is unresponsive. For another example, taking a graphic editing application as an example, after the operating system is updated, the interface display is chaotic when the application is opened, and some functions cannot be used normally. For another example, during a promotional event, a large number of users access an e-commerce shopping application at the same time, resulting in slow response of the application, longer time to load product lists and detail pages, and even freezes.

[0083] When an application fails, the client can send personal feedback information and the application's log data as function error data to the server. For example, the client can package and compress personal feedback information and log data into function error data, and then send it to the server. Among them, personal feedback information includes the user's personal information, such as the number, and device information, such as the device identification, and can also include pictures, text, videos, etc. The log data can be a log of the most recent period of time since the application's fault function occurred. The log data can record the relevant parameters of the application when it is running and the function triggering steps, etc.

[0084] In some implementations, before determining corresponding fault repair data in a preset fault repair database according to the function error data, the method further includes:

[0085] (1.1) Sort out the functions of the application, determine all the functions of the application and the corresponding operation steps for each function;

[0086] (1.2) Generate corresponding trigger points according to the operation steps corresponding to each function, and generate point data based on the trigger points;

[0087] (1.3) Generate fault repair data for each function based on the repair data and buried point data corresponding to each function.

[0088] An application contains multiple functions. All functions of the application can be sorted out to obtain all functions. For example, code analysis tools can be used to scan the source code of the application to identify the modules, classes and methods in the code, so as to infer potential functional units. For example, in an application developed in Java, the tool can analyze a series of methods related to user login, such as validateUsername, validatePassword, etc. These methods combined may constitute the user login function.

[0089] For example, in the debugger in the development environment, by setting breakpoints at key code locations, you can observe the execution flow and variable changes of the program at runtime. For example, by setting breakpoints in the shopping cart function code of an e-commerce application, when the user adds an item to the shopping cart, you can observe how the related data structures (such as the shopping cart item list, item quantity and other variables) are updated, so as to better understand the implementation details of the shopping cart function.

[0090] Another example is to find event monitors in applications, which are used to respond to various user operations and system events. For example, in a graphical interface application, a button click event monitor can trigger the corresponding function. By analyzing the corresponding processing method of the button click event, the function and operation steps performed by each button can be determined. For example, in a video playback application, the click event monitor of the play and pause buttons will call the corresponding play and pause function code, which may include operations such as pausing video playback and updating the playback status display.

[0091] Through the above method, you can obtain all the functions of the application and the operation steps of each function. Then generate corresponding trigger tracking points according to the operation steps corresponding to each function, and generate tracking point data based on the trigger tracking points. Taking the user logging into the application as an example, the function operation steps of logging in are divided into the following steps: The user opens the application and enters the login page. Enter the user name in the user name input box. Enter the password in the password input box. Click the "Login" button. There are four steps in total.

[0092] You can set a trigger tracking point for the login page. When the user successfully opens the login page, this tracking point can be set at the code logic where the login page is loaded to record the starting point of the user's login process.

[0093] A trigger tracking point is set for user name input. In the text change event of the user name input box, every time the user enters a character or deletes a character, the trigger tracking point will be triggered to record the process of the user entering the user name.

[0094] Set a trigger tracking point for password input. Similarly, in the text change event of the password input box, every time the user enters a character or deletes a character, the trigger tracking point will be triggered to determine the password input situation.

[0095] Click the login button to set a trigger tracking point. In the click event of the "Login" button, when the user clicks the button and tries to log in, the trigger tracking point will be triggered, indicating the completion of the login operation attempt.

[0096] It should be noted that, in each operation step of each function, at least one trigger tracking point can be set for each operation step, and tracking point data can be generated based on these trigger tracking points.

[0097] In addition, there is repair data corresponding to each function of the application. These fault repair data can be the experience data accumulated when the application previously sent faults. For example, when the developer repairs the function of the application, the data used to repair the corresponding function can be saved and used as the repair data corresponding to the function.

[0098] Finally, fault repair data can be generated based on the repair data and embedded data of each function, where the repair data in the fault repair data can repair the faulty function, and the embedded data is used to monitor the function after the repair data is repaired, so as to obtain the corresponding operation result data.

[0099] A corresponding function identifier can also be set for each function of the application. The function identifier can be the code corresponding to each function, such as a code calculated by a hash function. Each function identifier is unique, and then the function identifier and the fault repair data are associated and saved in a preset fault repair database.

[0100] In step 220, corresponding fault repair data is determined in a preset fault repair database according to the function error data, and the fault repair data includes the corresponding tracking data when the application is running.

[0101] The server can determine the function of the application program that fails based on the function error data, then determine the function identifier of the failed function, and then determine the corresponding fault repair data in a preset fault repair database based on the function identifier.

[0102] In some implementations, determining corresponding fault repair data in a preset fault repair database according to the function error data includes:

[0103] (1.1) Determine the corresponding fault page based on the function error data;

[0104] (1.2) Determine the target function where the failure occurs based on the faulty page and all functions of the application;

[0105] (1.3) Determine a target function identifier of the target function, and determine corresponding fault repair data in a preset repair database based on the target function identifier.

[0106] For example, page information is obtained from the function error data, such as a screenshot of the faulty function page, so as to preliminarily determine the undetermined function that may fail, and then match the undetermined function with all the functions of the application. If a function that matches the function is matched among all the functions, the undetermined function is determined as the target function that fails.

[0107] Then, a target function identifier for determining the target function is obtained, and corresponding fault repair data is determined in a preset repair database based on the target function identifier. For example, the target function identifier can be matched in the preset repair database based on the association between the function identifier and the fault repair data, and the target function identifier of the target function can be matched in the preset repair database to determine the corresponding fault repair data in the preset repair database.

[0108] The advantage of doing so is that the fault repair data of the faulty function corresponding to the function error data can be accurately and quickly located, thereby improving the processing efficiency of the faulty function.

[0109] In some embodiments, after obtaining the function error data, the function error data can be decompressed, and the server can combine the personal feedback information and log data to preliminarily determine the module in the application where the functional failure occurs. For example, the corresponding function module can be determined by identifying the function interface, and then the target log associated with the function module is obtained from the log data, and then the target log is analyzed to determine the function operation steps corresponding to the function module. These function operation steps can be matched with the preset function operation steps saved in the preset fault repair database to match the target preset function operation steps that are the same as the function operation steps. The preset function fault repair database saves the mapping relationship between the preset function operation steps and the fault repair data, and the fault repair data of the function module can be found in all the fault repair data according to the mapping and the target preset function operation steps.

[0110] The advantage of doing so is that the fault repair data of the faulty function corresponding to the function error data can be accurately and quickly located, thereby improving the processing efficiency of the faulty function.

[0111] In step 230, the fault repair data is sent to the client, and the operation result data generated by the triggering point data in the process of the client running the application based on the fault repair data is received.

[0112] The server can send fault repair data to the client.

[0113] After receiving the fault repair data, the client can read the fault repair data to obtain the repair data and the tracking data, and then repair the application based on the repair data. After the corresponding functions of the application are repaired, the application can be tried again. During the operation of the application being repaired, each tracking point in the tracking data will be triggered, so as to monitor the operation result data of the application. The client sends the operation result data to the server.

[0114] The server can receive the operation result data and process the operation result data later.

[0115] In step 240, when the function corresponding to the function error data matches the function corresponding to the operation result data, and it is determined according to the operation result data that the corresponding function is repaired, corresponding fault repair knowledge is generated according to the function error data and the fault repair data and saved in a preset fault repair database.

[0116] After receiving the operation result data, the server can determine the function corresponding to the operation result data. For example, if the operation result data contains the function identifier of the application runtime function after the attempted repair, the server can then determine the function corresponding to the operation result data based on the function identifier.

[0117] Then, the function corresponding to the function error data and the function corresponding to the operation result data are matched, for example, to determine whether the function corresponding to the function error data and the function corresponding to the operation result data are the same.

[0118] When the function corresponding to the function error data matches the function corresponding to the operation result data, and it is determined according to the operation result data that the corresponding function is repaired, for example, the function identifier of the function corresponding to the function error data is the same as the function identifier of the function corresponding to the operation result data, and the operation result data indicates that the corresponding function has been repaired, then it is determined that the function corresponding to the function error data has been repaired by the fault repair data. Finally, the corresponding fault repair knowledge is generated according to the function error data and the fault repair data and saved in a preset fault repair database.

[0119] In some implementations, after receiving the operation result data generated by triggering the tracking data in the process of the client running the application based on the fault repair data, the method further includes:

[0120] (1.1) When the function corresponding to the function error data does not match the function corresponding to the operation result data, it is determined that the function corresponding to the function error data has not been repaired;

[0121] (1.2) Determine new fault repair data corresponding to the function error data in a preset fault repair database, and send the new fault repair data to the client.

[0122] For example, when the function identifier of the function corresponding to the function error data and the function identifier of the function corresponding to the operation result data do not match, that is, the function identifier of the function corresponding to the function error data and the function identifier of the function corresponding to the operation result data are different, then it is considered that the fault repair data does not perform targeted repairs on the function corresponding to the function error data. It is possible that the server determined an error when determining the fault repair data for the function corresponding to the function error data. At this time, it is considered that the function corresponding to the function error data has not been repaired.

[0123] Then, new fault repair data corresponding to the function error data is determined in a preset fault repair database, and the new fault repair data is sent to the client, so that the client attempts to repair the function corresponding to the function error data again according to the new fault repair data.

[0124] The advantage of doing so is that it can improve the accuracy of fault repair processing and prevent the function corresponding to the error data reported by the erroneous confirmation function from being repaired.

[0125] In some implementations, corresponding fault repair knowledge is generated according to the function error data and the fault repair data and stored in a preset fault repair database, including:

[0126] (2.1) Obtaining feedback information sent by the client after running the application based on the fault repair data;

[0127] (2.1) When the feedback information indicates that the function corresponding to the fault repair data is repaired, corresponding fault repair knowledge is generated according to the function error data and the fault repair data and stored in a preset fault repair database.

[0128] Among them, after the server receives the operation result data, the server can also receive feedback information sent by the client after running the application based on the fault repair data, wherein the feedback information is sent by the user and contains information on whether the function corresponding to the function error data is repaired.

[0129] When the function corresponding to the function error data and the function corresponding to the operation result data match, and it is determined according to the operation result data that the corresponding function is repaired, and the feedback information indicates that the function corresponding to the fault repair data is repaired, corresponding fault repair knowledge is generated according to the function error data and the fault repair data and saved in a preset fault repair database.

[0130] The advantage of doing this is that it prevents people from mistakenly believing that the function corresponding to the function error data has been repaired, thereby improving the accuracy of fault handling.

[0131] In some implementations, corresponding fault repair knowledge is generated according to the function error data and the fault repair data and stored in a preset fault repair database, including:

[0132] (3.1) Determine the corresponding function and the corresponding function identifier of the function in all functions of the application according to the function error data;

[0133] (3.2) A mapping relationship between the function identifier and the fault repair data is established, and fault repair knowledge is generated based on the mapping relationship, and the fault repair knowledge is preset in a fault repair database.

[0134] Among them, the corresponding function and the function identifier corresponding to the function in all functions of the application can be determined according to the function error data, and then a mapping relationship between the function identifier and the fault repair data is established, and fault repair knowledge is generated based on the mapping relationship. For example, the function identifier is used as the key and the fault repair data is used as the value to generate a key-value pair data structure, obtain fault repair knowledge, and preset the fault repair knowledge in the fault repair database.

[0135] A corresponding hash value can also be generated through a hash function according to the function identifier, and the hash value is used as a key. The key is unique. The advantage of this is that it can improve the speed and accuracy of the server's search for fault repair knowledge.

[0136] In some implementations, after receiving the operation result data generated by triggering the tracking data in the process of the client running the application based on the fault repair data, the method further includes:

[0137] (4.1) when the function corresponding to the function error data matches the function corresponding to the operation result data, and it is determined according to the operation result data that the corresponding function has not been repaired, generating abnormal notification information of the function corresponding to the function error data;

[0138] (4.2) Send the exception notification information to the corresponding developer of the application.

[0139] Among them, when the function corresponding to the function error data matches the function corresponding to the operation result data, and it is determined according to the operation result data that the corresponding function has not been repaired, it means that the fault repair data cannot repair the function corresponding to the function error data. At this time, the server can no longer actively repair the function that has failed. At this time, the abnormal notification information of the function corresponding to the function error data is generated, and the abnormal notification information is sent to the corresponding developer of the application. For example, the fault message is pushed to the developer through email, SMS, message, etc., so that the developer can find the fault in time and handle it.

[0140] In some implementations, after subsequent developers repair the function corresponding to the function error data, the corresponding repair data can be saved in a preset fault repair database to facilitate subsequent repair of faults of the same function, thereby improving the efficiency of fault repair processing.

[0141] From the above, it can be seen that in the present application, function error data generated during the operation of an application uploaded by a client is received; corresponding fault repair data is determined in a preset fault repair database based on the function error data, and the fault repair data includes the corresponding tracking data when the application is running; the fault repair data is sent to the client, and the operation result data generated by the tracking data triggered during the client running the application based on the fault repair data is received; when the function corresponding to the function error data matches the function corresponding to the operation result data, and it is determined according to the operation result data that the corresponding function is repaired, corresponding fault repair knowledge is generated according to the function error data and the fault repair data and saved in the preset fault repair database. In this way, when an application fails, you can first obtain the corresponding function error data of the application, and then obtain the corresponding fault repair data in the preset fault repair database, and obtain the operation result data generated by the tracking data triggered in the process of running the application through the fault repair data. The fault repair data can attempt to repair the corresponding function of the application, and the tracking data in the fault repair data can reproduce the corresponding function of the application. Finally, when the function corresponding to the function error data and the function corresponding to the operation result data match, and it is determined according to the operation result data that the corresponding function is repaired, the corresponding fault repair knowledge is generated according to the function error data and the fault repair data and saved in the preset fault repair database. In this way, the function of the application fault can be reproduced and repaired, thereby improving the efficiency of handling program faults.

[0142] See also Figure 4 , Figure 4 is another flowchart of the fault handling method provided in an embodiment of the present application. The fault handling method may also include the following steps:

[0143] Step 301: receiving function error data generated during the operation of an application uploaded by a client;

[0144] Step 302: determine the corresponding fault page according to the function error data;

[0145] Step 303: Determine the target function where the failure occurs according to the failure page and all functions of the application program;

[0146] Step 304: determine the target function identifier of the target function, and determine corresponding fault repair data in a preset repair database based on the target function identifier, where the fault repair data includes corresponding tracking point data when the application is running;

[0147] Step 305: Send the fault repair data to the client, and receive the operation result data generated by triggering the buried data during the process of the client running the application based on the fault repair data;

[0148] Step 306: when the function corresponding to the function error data matches the function corresponding to the operation result data, and it is determined according to the operation result data that the corresponding function is repaired, corresponding fault repair knowledge is generated according to the function error data and the fault repair data and stored in a preset fault repair database;

[0149] Step 307: When the function corresponding to the function error data does not match the function corresponding to the operation result data, it is determined that the function corresponding to the function error data has not been repaired;

[0150] Step 308: determine new fault repair data corresponding to the function error data in a preset fault repair database, and send the new fault repair data to the client;

[0151] Step 309: when the function corresponding to the function error data matches the function corresponding to the operation result data, and it is determined according to the operation result data that the corresponding function has not been repaired, generating abnormal notification information of the function corresponding to the function error data;

[0152] Step 310: Send the exception notification information to the developer of the application.

[0153] The specific implementation of the fault handling method in this embodiment is basically the same as the specific implementation of the fault handling method described above, and will not be repeated here.

[0154] See also Figure 5 The embodiment of the present application further provides a fault handling device, which can implement the above fault handling method, and the device includes:

[0155] The receiving module 410 is used to receive function error data generated during the operation of the application uploaded by the client;

[0156] A determination module 420 is used to determine corresponding fault repair data in a preset fault repair database according to the function error data, where the fault repair data includes corresponding tracking data when the application is running;

[0157] The sending module 430 is used to send the fault repair data to the client, and receive the operation result data generated by the triggering point data during the client running the application based on the fault repair data;

[0158] The matching module 440 is used to generate corresponding fault repair knowledge according to the function error data and the fault repair data and save it in a preset fault repair database when the function corresponding to the function error data matches the function corresponding to the operation result data and it is determined according to the operation result data that the corresponding function is repaired.

[0159] In some implementations, the fault handling device 400 further includes a generating module 450, which is used to:

[0160] Before determining the corresponding fault repair data in the preset fault repair database according to the function error data, sort out the functions of the application program to determine all the functions of the application program and the operation steps corresponding to each function;

[0161] Generate corresponding trigger tracking points according to the operation steps corresponding to each function, and generate tracking point data based on the trigger tracking points;

[0162] Generate fault repair data for each function based on the repair data and tracking data corresponding to each function.

[0163] In some implementations, the determination module 420 is configured to:

[0164] Determine the corresponding fault page based on the function error data;

[0165] Determine the target function where the failure occurs based on the faulty page and all functions of the application;

[0166] A target function identifier of the target function is determined, and corresponding fault repair data is determined in a preset repair database based on the target function identifier.

[0167] In some implementations, the matching module 440 is configured to:

[0168] After receiving the operation result data generated by the tracking data triggered in the process of the client running the application based on the fault repair data, when the function corresponding to the function error data does not match the function corresponding to the operation result data, it is determined that the function corresponding to the function error data has not been repaired;

[0169] New fault repair data corresponding to the function error data is determined in a preset fault repair database, and the new fault repair data is sent to the client.

[0170] In some implementations, the matching module 440 is configured to:

[0171] Get feedback information sent by the client after running the application based on the fault repair data;

[0172] When the feedback information indicates that the function corresponding to the fault repair data is repaired, corresponding fault repair knowledge is generated according to the function error data and the fault repair data and stored in a preset fault repair database.

[0173] In some implementations, the matching module 440 is configured to:

[0174] After receiving the operation result data generated by the tracking data triggered by the client in the process of running the application based on the fault repair data, when the function corresponding to the function error data matches the function corresponding to the operation result data, and it is determined according to the operation result data that the corresponding function has not been repaired, generate abnormal notification information of the function corresponding to the function error data;

[0175] Send exception notification information to the corresponding application developer.

[0176] In some implementations, the matching module 440 is configured to:

[0177] Determine the corresponding function and the function identifier corresponding to the function in all functions of the application program according to the function error data;

[0178] A mapping relationship between the function identifier and the fault repair data is established, and fault repair knowledge is generated based on the mapping relationship, and the fault repair knowledge is preset in a fault repair database.

[0179] The specific implementation of the fault handling device is basically the same as the specific implementation of the above-mentioned fault handling method, and will not be repeated here.

[0180] As can be seen from the above, the receiving module 410 in the present application is used to receive function error data generated during the operation of an application uploaded by a client; the determining module 420 is used to determine corresponding fault repair data in a preset fault repair database based on the function error data, and the fault repair data includes the corresponding tracking data when the application is running; the sending module 430 is used to send the fault repair data to the client, and receive the operation result data generated by the tracking data triggered by the client in the process of running the application based on the fault repair data; the matching module 440 is used to generate corresponding fault repair knowledge based on the function error data and the fault repair data and save it in a preset fault repair database when the function corresponding to the function error data matches the function corresponding to the operation result data, and when it is determined according to the operation result data that the corresponding function is repaired. In this way, when an application fails, you can first obtain the corresponding function error data of the application, and then obtain the corresponding fault repair data in the preset fault repair database, and obtain the operation result data generated by the tracking data triggered in the process of running the application through the fault repair data. The fault repair data can attempt to repair the corresponding function of the application, and the tracking data in the fault repair data can reproduce the corresponding function of the application. Finally, when the function corresponding to the function error data and the function corresponding to the operation result data match, and it is determined according to the operation result data that the corresponding function is repaired, the corresponding fault repair knowledge is generated according to the function error data and the fault repair data and saved in the preset fault repair database. In this way, the function of the application fault can be reproduced and repaired, thereby improving the efficiency of handling program faults.

[0181] The embodiment of the present application also provides a computer device, the computer device includes a memory and a processor, the memory stores a computer program, and the processor implements the above fault handling method when executing the computer program. The computer device can be any intelligent terminal including a tablet computer, a car computer, etc.

[0182] See also Figure 6 , Figure 6 The hardware structure of a computer device according to another embodiment is shown, and the computer device includes:

[0183] The processor 501 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present application;

[0184] The memory 502 can be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 502 can store an operating system and other application programs. When the technical solution provided in the embodiment of this specification is implemented by software or firmware, the relevant program code is stored in the memory 502, and the processor 501 calls and executes the fault handling method of the embodiment of this application;

[0185] Input / output interface 503, used to implement information input and output;

[0186] Communication interface 504, used to realize communication interaction between the device and other devices, which can be realized by wired mode (such as USB, network cable, etc.) or wireless mode (such as mobile network, WIFI, Bluetooth, etc.);

[0187] A bus 505 that transmits information between the various components of the device (e.g., the processor 501, the memory 502, the input / output interface 503, and the communication interface 504);

[0188] The processor 501 , the memory 502 , the input / output interface 503 and the communication interface 504 are connected to each other in communication within the device via the bus 505 .

[0189] An embodiment of the present application further provides a computer-readable storage medium, which stores a computer program, and the computer program implements the above-mentioned fault handling method when executed by a processor.

[0190] The memory, as a non-transient computer-readable storage medium, can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory may optionally include a memory remotely disposed relative to the processor, and these remote memories may be connected to the processor via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0191] The present application proposes a fault handling method, apparatus, computer equipment and storage medium, which receive function error data generated during the operation of an application uploaded by a client; determine corresponding fault repair data in a preset fault repair database based on the function error data, and the fault repair data includes corresponding tracking data when the application is running; send the fault repair data to the client, and receive operation result data generated by triggering the tracking data during the process of the client running the application based on the fault repair data; when the function corresponding to the function error data matches the function corresponding to the operation result data, and it is determined according to the operation result data that the corresponding function is repaired, generate corresponding fault repair knowledge according to the function error data and the fault repair data and save it in the preset fault repair database. In this way, when an application fails, you can first obtain the corresponding function error data of the application, and then obtain the corresponding fault repair data in the preset fault repair database, and obtain the operation result data generated by the tracking data triggered in the process of running the application through the fault repair data. The fault repair data can attempt to repair the corresponding function of the application, and the tracking data in the fault repair data can reproduce the corresponding function of the application. Finally, when the function corresponding to the function error data and the function corresponding to the operation result data match, and it is determined according to the operation result data that the corresponding function is repaired, the corresponding fault repair knowledge is generated according to the function error data and the fault repair data and saved in the preset fault repair database. In this way, the function of the application fault can be reproduced and repaired, thereby improving the efficiency of handling program faults.

[0192] The embodiments described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Those skilled in the art will appreciate that with the evolution of technology and the emergence of new application scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0193] Those skilled in the art will appreciate that the technical solutions shown in the figures do not constitute a limitation on the embodiments of the present application, and may include more or fewer steps than shown in the figures, or a combination of certain steps, or different steps.

[0194] The device embodiments described above are merely illustrative, and the units described as separate components may or may not be physically separated, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0195] Those skilled in the art will appreciate that all or some of the steps in the methods disclosed above, and the functional modules / units in the systems and devices may be implemented as software, firmware, hardware, or a suitable combination thereof.

[0196] The terms "first", "second", "third", "fourth", etc. (if any) in the specification of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0197] It should be understood that in the present application, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0198] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the above units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0199] The units described above as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0200] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0201] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including multiple instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, referred to as ROM), random access memory (Random Access Memory, referred to as RAM), disk or optical disk and other media that can store programs.

[0202] The preferred embodiments of the present application are described above with reference to the accompanying drawings, but the scope of the rights of the present application is not limited thereto. Any modification, equivalent substitution and improvement made by a person skilled in the art without departing from the scope and essence of the present application should be within the scope of the rights of the present application.

Claims

1. A fault handling method, characterized in that: include: Receive function error data generated during the operation of the application uploaded by the client; Determine corresponding fault repair data in a preset fault repair database according to the function error data, wherein the fault repair data includes the corresponding tracking point data when the application is running; Sending the fault repair data to a client, and receiving operation result data generated by triggering the tracking data during the client running the application based on the fault repair data; When the function corresponding to the function error data matches the function corresponding to the operation result data, and it is determined according to the operation result data that the corresponding function is repaired, corresponding fault repair knowledge is generated according to the function error data and the fault repair data and saved in the preset fault repair database.

2. The fault handling method according to claim 1, characterized in that: Before determining corresponding fault repair data in a preset fault repair database according to the function error data, the method further includes: Sorting out the functions of the application to determine all the functions of the application and the operation steps corresponding to each function; Generate corresponding triggering points according to the operation steps corresponding to each function, and generate point data based on the triggering points; Generate fault repair data for each function according to the repair data corresponding to each function and the buried point data.

3. The fault handling method according to claim 2, characterized in that: The determining corresponding fault repair data in a preset fault repair database according to the function error data includes: Determine a corresponding fault page according to the function error data; Determine the target function where the failure occurs according to the failure page and all functions of the application; A target function identifier of the target function is determined, and corresponding fault repair data is determined in a preset repair database based on the target function identifier.

4. The fault handling method according to claim 1, characterized in that: After receiving the operation result data generated by triggering the tracking data in the process of the client running the application based on the fault repair data, the method further includes: When the function corresponding to the function error data does not match the function corresponding to the operation result data, determining that the function corresponding to the function error data has not been repaired; Determine new fault repair data corresponding to the function error data in the preset fault repair database, and send the new fault repair data to the client.

5. The fault handling method according to claim 1, characterized in that: The generating corresponding fault repair knowledge according to the function error data and the fault repair data and storing the knowledge in the preset fault repair database includes: Obtaining feedback information sent by the client after running the application based on the fault repair data; When the feedback information indicates that the function corresponding to the fault repair data is repaired, corresponding fault repair knowledge is generated according to the function error data and the fault repair data and stored in the preset fault repair database.

6. The fault handling method according to claim 1, characterized in that: After receiving the operation result data generated by triggering the tracking data in the process of the client running the application based on the fault repair data, the method further includes: When the function corresponding to the function error data matches the function corresponding to the operation result data, and it is determined according to the operation result data that the corresponding function has not been repaired, generating abnormal notification information of the function corresponding to the function error data; The exception notification information is sent to the developer corresponding to the application.

7. The fault handling method according to claim 1, characterized in that: The generating corresponding fault repair knowledge according to the function error data and the fault repair data and storing the knowledge in the preset fault repair database includes: Determine, according to the function error data, a corresponding function and a function identifier corresponding to the function in all functions of the application program; A mapping relationship between the function identifier and the fault repair data is established, and fault repair knowledge is generated based on the mapping relationship, and the fault repair knowledge is stored in the preset fault repair database.

8. A fault handling device, characterized in that: include: A receiving module, used to receive function error data generated during the operation of the application uploaded by the client; A determination module, used to determine corresponding fault repair data in a preset fault repair database according to the function error data, wherein the fault repair data includes the corresponding buried point data when the application is running; A sending module, used to send the fault repair data to a client, and receive operation result data generated by the tracking data triggered by the client in the process of running the application based on the fault repair data; A matching module is used to generate corresponding fault repair knowledge according to the function error data and the fault repair data and save it in the preset fault repair database when the function corresponding to the function error data matches the function corresponding to the operation result data and it is determined according to the operation result data that the corresponding function is repaired.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor to execute the fault handling method according to any one of claims 1 to 7.

10. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the fault handling method according to any one of claims 1 to 7 is implemented.

Images