Processing method of even occurrence problem and computing equipment

Abstract

The embodiment of the invention provides an even problem processing method and computing equipment, and the method comprises the steps: obtaining and storing operation information of user operation, the operation information comprising one or more of operation time, operation events, operation elements, and routing information of a target page; when a coupling problem meeting a preset condition is detected, determining target operation information corresponding to the coupling problem in the stored operation information; and outputting the target operation information, wherein the target operation information is used for restoring the user operation indicated by the target operation information. According to the method provided by the embodiment of the invention, the operation of the user is monitored and stored, so that developers can be assisted to quickly position and solve the problem when the problem occurs.

Description

Technical Field

[0001] The embodiments of the present application relate to the technical field of computing devices, and in particular to a method for processing occasional problems and a computing device. Background Art

[0002] Incidental Problems mainly refer to some problems that may occur under certain conditions during the development and use of software products, but cannot always be reproduced stably. Incidental problems do not have a fixed time or frequency of occurrence. When trying to reproduce the problem, they do not always appear. They may also be related to certain specific environmental conditions, operating steps or input data. They have strong randomness and uncertainty, which makes it difficult for developers to locate and solve incidental problems in a timely manner.

[0003] In the related art, when encountering occasional problems, it is generally the user who raises a ticket, and then the developer analyzes and tracks the background operation logs to determine and solve the occasional problem; or the user provides a detailed description or reproduction of the specific scenario and operation process when the occasional problem occurs, so that the developer can reproduce the problem according to the user's instructions and thus solve the occasional problem.

[0004] However, analyzing the operation logs requires a lot of manpower and material resources, and users generally do not understand the specific operations, which makes it difficult for developers to solve sporadic problems in a timely and effective manner. Therefore, how to deal with sporadic problems in a timely and effective manner has become an urgent problem to be solved. Summary of the invention

[0005] The embodiments of the present application provide a method for handling occasional problems and a computing device. By monitoring and saving user operations, the problem can be quickly located when the occasional problem occurs, so as to assist developers in problem handling.

[0006] In a first aspect, an embodiment of the present application provides a method for handling sporadic problems, the method comprising: obtaining and saving operation information of user operations, the operation information comprising one or more of operation time, operation event, operation element, and routing information of a target page; when an sporadic problem that meets preset conditions is detected, determining target operation information corresponding to the sporadic problem in the saved operation information; and outputting the target operation information, the target operation information being used to restore the user operation indicated by the target operation information.

[0007] The beneficial effects of this implementation method are as follows: by saving the user's operation information, when an occasional problem occurs, the operation information corresponding to the occasional problem can be sent to the developer's terminal device, and the developer can also conduct targeted analysis based on the operation information, and reproduce and handle the occasional problem in a targeted manner, without having to locate the occasional problem from a large number of background operation logs, which effectively improves the efficiency of handling occasional problems; in addition, there is no need for users of the software to provide detailed descriptions of the scenarios and specific operations in which the occasional problem occurs, effectively avoiding the situation where the occasional problem cannot be solved due to a lack of explanation.

[0008] In a possible implementation, obtaining the operation information of the user operation includes: using an event listener pre-implanted by an embedding technology to monitor the user operation to obtain the operation information of the user operation.

[0009] The beneficial effect of this implementation method is as follows: by using the event listener pre-implanted by the embedding technology to monitor the user operation, the user's operation information can be quickly obtained, thereby providing a data basis for subsequent occasional problems.

[0010] In a possible implementation, the determining the target operation information corresponding to the occasional problem includes: based on the occurrence time of the occasional problem, determining operation information within a preset time before the occurrence time as the target operation information.

[0011] The beneficial effect of this implementation method is that the target operation information corresponding to the occasional problem can be quickly determined according to the occurrence time of the occasional problem, thereby improving data processing efficiency.

[0012] In a possible implementation manner, the preset condition includes any one of the following: an occurrence probability less than or equal to a preset value, any one of being in a preset occasional problem set, and any one of not being in a preset non-occasional problem set.

[0013] The beneficial effect of this implementation is that by judging occasional problems based on preset conditions, occasional problems can be identified more accurately, thereby improving the accuracy of data processing.

[0014] In a possible implementation, the method further includes: the operation information also includes information of a background operation log interface.

[0015] The beneficial effects of this implementation method are as follows: when the operation information includes information of the background operation log interface, if the developer cannot solve the occasional problem through other user operation information, the background operation log can be quickly found through the background operation log interface to solve the occasional problem by analyzing the background operation log, thereby improving the probability and efficiency of solving the occasional problem.

[0016] In a possible implementation, after determining the target operation information corresponding to the sporadic problem, the method further includes: converting the target operation information into a target format; the target format is a JSON format or a Hypertext Markup Language HTML format.

[0017] The beneficial effect of this implementation is that the target operation information corresponding to the occasional problem is converted into a target format, which can reduce the workload of developers in identifying the operation information, thereby improving the efficiency of solving the occasional problem.

[0018] In a possible implementation manner, outputting the target operation information includes: outputting the target operation information presented in the target format.

[0019] The beneficial effect of this implementation method is that by sending operation information corresponding to occasional problems to developers in a variety of feasible ways, the probability of missed / wrong transmission can be reduced, so that developers can solve as many occasional problems as possible and improve the quality of software products.

[0020] In a possible implementation, before outputting the target operation information, the method further includes: generating an automatic sending instruction in response to a user's setting operation; wherein the automatic sending instruction is used to instruct the computing device to output the target operation information when an occasional problem that meets preset conditions is detected.

[0021] The beneficial effect of this implementation method is that the user can determine whether to send the target operation information corresponding to the occasional problem to the developer, which can enable the user to have full privacy autonomy and improve the user experience.

[0022] In a possible implementation, the method further includes: periodically clearing the saved operation information; or automatically clearing the saved operation information when the target page is closed; or clearing the saved operation information in response to a manual clear processing instruction from the user; or storing the operation information in a stack.

[0023] The beneficial effects of this implementation method are as follows: by clearing useless operation information, the storage pressure of the database can be reduced and the waste of storage resources can be effectively avoided; by storing operation information in a stack manner, the amount of stored operation information can be limited, so that the operation information can be saved based on actual needs, thereby avoiding the waste of storage resources.

[0024] In a second aspect, an embodiment of the present application further provides a computing device, comprising a processor, wherein the processor is connected to a memory; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory to implement a method as described in any one of the first aspects.

[0025] The beneficial effects of this embodiment are as follows: when the processor executes the method for handling occasional problems described in any one of the first aspects, the user's operation information is saved. Then, when an occasional problem occurs, the operation information corresponding to the occasional problem can be sent to the developer's terminal device, and the developer can also perform targeted analysis based on the operation information, and reproduce and handle the occasional problem in a targeted manner. There is no need to locate the occasional problem from a large number of background operation logs, which effectively improves the efficiency of handling occasional problems. In addition, there is no need for users of the software to provide detailed descriptions of the scenarios and specific operations in which occasional problems occur, which effectively avoids the situation where the occasional problem cannot be solved due to unclear explanation of the occasional problem. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the following is a brief introduction to the drawings required for use in the embodiments or the related technical descriptions. 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 creative labor.

[0027] Figure 1 A flowchart of a method for handling occasional problems provided in an embodiment of the present application;

[0028] Figure 2 A flowchart of another method for processing an occasional problem provided in an embodiment of the present application;

[0029] Figure 3 A schematic diagram of a presentation effect of target operation information corresponding to an occasional problem provided in an embodiment of the present application;

[0030] Figure 4 A schematic diagram of another presentation effect of target operation information corresponding to an occasional problem provided in an embodiment of the present application;

[0031] Figure 5 A schematic diagram of the structure of a device for processing occasional problems provided in an embodiment of the present application;

[0032] Figure 6 A schematic diagram of the structure of a computing device is provided for an embodiment of the present application. DETAILED DESCRIPTION

[0033] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments made by ordinary technicians in this field under the enlightenment of the embodiments belong to the scope of protection of the present application.

[0034] The terms "first", "second", "third", "fourth", etc. (if any) in the specification and claims 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 that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0035] During the development and use of software products, some technical problems may occur unexpectedly under certain conditions, but they are not always reproducible. These problems are generally called incidental problems. Although the probability of incidental problems is generally low, and they are usually not foreseen by developers in the initial design or planning stage, incidental problems may have a significant impact on product performance, quality, safety, etc. during actual operation or testing. Therefore, it is necessary to solve incidental problems in a timely and effective manner.

[0036] In the related art, when an occasional problem occurs, it is generally raised by the user, and then the developer analyzes and tracks the background operation logs to determine and solve the occasional problem; or the user describes or reproduces the specific scenario and operation process when the occasional problem occurs in detail, so that the developer can reproduce the problem according to the user's instructions and thus solve the occasional problem.

[0037] However, analyzing the operation logs requires a lot of manpower and resources, which is not only costly and inefficient, but also causes the problem ticket to stay for a long time, and forcibly closing the problem ticket cannot solve the fundamental problem; and users generally do not understand the specific scenarios and operation processes, which also makes it difficult for developers to solve sporadic problems in a timely manner. Therefore, it is particularly important to provide an effective method for handling sporadic problems.

[0038] To this end, an embodiment of the present application provides a method for handling occasional problems, and the technical concept is as follows: when a user uses a software product, the user's operation information is saved. When an occasional problem occurs, the corresponding operation record is searched from the saved operation information and output to the developer's terminal device. In this way, the developer can handle the occasional problem based on the user's operation record, solving the problem that occasional problems are difficult to reproduce and solve.

[0039] The technical solution of the present application is described in detail below through specific embodiments. It should be noted that the following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments.

[0040] Figure 1 A flowchart of a method for handling occasional problems provided in an embodiment of the present application. Figure 1 The method for processing the occasional problem may be executed by a processor of a computing device, and may specifically include the following steps:

[0041] S101. Acquire and save operation information of user operations.

[0042] The operation information is used to indicate the specific operation status of the user on the target page.

[0043] For example, the user may be a software tester, a software maintenance person, a person who uses the software on the client side, etc. In the embodiment of the present application, when the user uses the software, he or she will perform corresponding actual operations based on the target page displayed on the device interface, and then the processor can monitor the user operation in real time, thereby obtaining the operation information of the user operation, and then saving the operation information of the user operation.

[0044] Optionally, in order to more clearly know the specific operation of the user on the target page, the acquired user operation information may include one or more of the operation time, operation event, operation element, routing information of the target page, etc. of the user's operation.

[0045] The operation time may be the time when the user performs the operation event, which is usually recorded in the form of a timestamp and may include the date and time, such as "2024-07-05 14:30:00". The user's operation may include, but is not limited to, click, input, page jump, etc. The corresponding operation events may include a mouse click event click, a mouse double-click event dblclick, a keyboard press event keydown, a scroll event scroll, a trigger event change when the value of a form element changes and loses focus, a trigger event focus when an element gains focus, etc.

[0046] Operation elements refer to the specific HTML elements that users operate on the page. The full name of HTML in English is HyperText Markup Language, and the full name in Chinese is Hypertext Markup Language. For example, when a user clicks a button, link, input box or other interactive element, these elements are operation elements. Operation elements are usually identified by tag name, ID, class name or other attributes. The corresponding operation elements can be located through these attribute identifiers. In addition, when the operation elements are displayed on the page, they can be presented as icons, pictures, text, symbols and other identification types. The identification types can be converted to each other. For example, if the operation element is a picture type, the displayed tag may be svg or img. After the svg is converted accordingly, the corresponding icon can be seen, and so on. I will not go into details here.

[0047] Among them, the operation elements operated by the user are different, and their corresponding operation events are different. Therefore, when monitoring the user's operation events, it can be achieved by distinguishing the operation elements operated by the user. Optionally, the operation elements can be distinguished by the label attribute (type) of the operation element. In actual applications, various types of label attributes can be created for different operation elements. For example, you can create: text represents a single-line text input box; checkbox represents a check box, allowing the user to select multiple options; radio represents a radio button, and the user can only select one from a group of options; date represents a date selection input box, providing a date selector; and so on. When the label attribute of the operation element is determined, the corresponding operation event that the user can perform can also be determined. For example, when the operated operation element belongs to a single-line text input box, the user can click the single-line text input box to perform operations such as text input.

[0048] The route of the target page refers to the page path or Uniform Resource Locator (URL) that can navigate to the target page after the user's operation. For example, " / home" may represent the home page, " / profile" may represent the user's personal profile page, and so on. These terms can be customized by the front-end developer, and the embodiments of the present application are not limited to this.

[0049] In a possible implementation, obtaining operation information of user operations may include: using an event listener pre-implanted by an embedding technology to monitor user operations to obtain operation information of user operations.

[0050] Exemplarily, the embedding technology is a technology that embeds information into a product. In the embodiment of the present application, the event listener can be pre-implanted into the processor through the embedding technology, and the event listener can monitor the user's operation to obtain the user's operation information. Optionally, the event listener can be a "document.addEventListener" tool. The "document.addEventListener" tool can be used to monitor the user's operation time, and can also distinguish the operation elements to monitor the user's operation events, and then save the user's operation information.

[0051] Among them, not all operations will lead to the occurrence of occasional problems. Therefore, in some possible implementation schemes, developers can analyze users' usage habits of the software and do corresponding embedding according to the actual usage scenarios and usage frequency, so that the "document.addEventListener" tool only records part of the user's operation information. In this way, when the problem recurs, more targeted operations can be performed to reduce blind and random operations on the page, which can not only reduce the cost of reproducing occasional problems, but also increase the probability of reproducing occasional problems.

[0052] In some possible implementations, the operations that a user can perform are limited. In order to avoid missing user operation information, corresponding embedding can be performed so that the "document.addEventListener" tool can record and save all user operations.

[0053] Exemplarily, after the processor obtains the user's operation information, the operation information can be saved in a preset database. In a possible implementation, the preset database can be a local memory, and saving the user's operation information can include: saving the user's operation information in the local memory.

[0054] Among them, local storage is a way to store data in the client (i.e., the user's browser), which allows data to be stored in the user's browser in the form of key-value pairs, with a larger data storage capacity, and the data will not disappear with the end of the browser session. In the embodiment of the present application, using local storage to save the user's operation information can ensure that data is not lost as much as possible, thereby improving data security. In this way, when occasional problems occur, the target operation information corresponding to the occasional problem can be found as soon as possible, so that developers can solve the occasional problem.

[0055] In a possible implementation, in order to reduce the storage pressure of the database, the saved operation information can be cleared periodically; or the saved operation information can be automatically cleared when the target page is closed; or the saved operation information can be cleared in response to the user's manual clearing processing instruction; or the operation information can be stored in a stack. By clearing useless operation information, the storage pressure of the database can be reduced and the waste of storage resources can be effectively avoided; by storing the operation information in a stack, the amount of stored operation information can be limited, so that the operation information can be saved based on actual needs, thereby avoiding the waste of storage resources.

[0056] S102: When an occasional problem that meets a preset condition is detected, target operation information corresponding to the occasional problem is determined in the stored operation information.

[0057] In the embodiment of the present application, since the user's operation information is saved, when an occasional problem occurs, the processor can search in the saved operation information to determine the target operation information corresponding to the occasional problem.

[0058] Among them, the embodiment of the present application does not limit how to determine the target operation information corresponding to the sporadic problem. In a possible embodiment, determining the target operation information corresponding to the sporadic problem may include: based on the occurrence time of the sporadic problem, determining the operation information within a preset time before the occurrence time as the target operation information. Exemplarily, the preset time can be a specific value such as 3 minutes / 5 minutes, and the embodiment of the present application does not limit this.

[0059] Optionally, the preset time can also be dynamically adjusted according to the actual usage of the user. For example, if the interval between each use of the software by the user is long, the operation information of the user using the software when the occasional problem occurs can be determined as the target operation information corresponding to the occasional problem; or, if the user continues to use the software, the user operation information within a few minutes before the occasional problem occurs can be determined as the target operation information corresponding to the occasional problem. By the occurrence time of the occasional problem, the target operation information corresponding to the occasional problem can be quickly determined, thereby improving data processing efficiency.

[0060] In a possible implementation, the processor also needs to determine whether the current problem is an occasional problem. Exemplarily, the processor can determine whether the current problem meets the preset conditions. If so, the current problem is determined to be an occasional problem; if not, the current problem is determined not to be an occasional problem. Optionally, the preset conditions include any one of the following: the probability of occurrence is less than or equal to a preset value, any one of the preset occasional problem set, and any one of the preset non-occasional problem set.

[0061] For example, the processor can count the number of all problems that occur within a certain time interval, such as a month, and determine the proportion of problems of the same category, which is the probability of occurrence of this type of problem. If the probability of the current problem is less than or equal to a preset value, such as less than or equal to 1%, it can be determined that the current problem is an occasional problem, otherwise, it is a non-occasional problem. Judging whether it is an occasional problem by the probability of the problem can achieve data management and accurately judge occasional problems.

[0062] Optionally, various known occasional problems may be stored in a preset occasional problem set in advance. When a problem occurs, the processor compares the occurring problem with the occasional problems in the preset occasional problem set. If it is determined that the currently occurring problem is any one of the preset occasional problem set, then the currently occurring problem is determined to be an occasional problem.

[0063] Optionally, various known non-occurring problems can be stored in a preset non-occurring problem set in advance. When a problem occurs, the processor compares the problem with the occasional problems in the preset non-occurring problem set. If the current problem does not belong to any of the preset non-occurring problem set, the current problem is determined to be an occasional problem.

[0064] By determining and verifying the type of problem that occurs, you can more accurately handle occasional problems.

[0065] S103: Output target operation information.

[0066] The target operation information is used to restore the user operation indicated by the target operation information. When the user operation is restored, it can be used to assist developers in dealing with occasional problems.

[0067] In an embodiment of the present application, after the processor determines the target operation information corresponding to the occasional problem, the target operation information will be output. For example, the target operation information corresponding to the occasional problem is sent to the terminal device of the developer, so that the developer can know the target operation information corresponding to the occasional problem. Among them, the developer of the embodiment of the present application generally refers to the personnel who can handle occasional problems. After the developer receives the target operation information corresponding to the occasional problem, the developer can restore the user operation indicated by the target operation information based on the target operation information, or can perform targeted analysis based on the target operation information, and carry out targeted reproduction and processing of the occasional problem, without locating the occasional problem from a large number of background operation logs, thereby effectively improving the efficiency of processing the occasional problem; in addition, based on the method of the embodiment of the present application, there is no need for the user to further explain the scene and specific operation when the occasional problem occurs in detail, effectively avoiding the situation where the occasional problem cannot be solved due to the inability to explain the occasional problem.

[0068] In the processing method of occasional problems provided in this embodiment, it includes: obtaining and saving operation information of user operations, the operation information includes one or more of operation time, operation event, operation element, and routing information of the target page; when an occasional problem that meets the preset conditions is detected, the target operation information corresponding to the occasional problem is determined in the saved operation information; the target operation information is output, and the target operation information is used to restore the user operation indicated by the target operation information. Compared with the related art, since the operation information of the user is saved in this embodiment, when an occasional problem occurs, the target operation information corresponding to the occasional problem can be output, so that the developer can obtain the target operation information, and the developer can also conduct targeted analysis based on the target operation information, and reproduce and process the occasional problem in a targeted manner, without locating the occasional problem from a large number of background operation logs, which effectively improves the efficiency of processing occasional problems; in addition, there is no need for users of the software to explain in detail the scenarios and specific operations of the occasional problem, which effectively avoids the situation where the occasional problem cannot be solved due to unclear explanation of the occasional problem.

[0069] Figure 2 A flowchart of another method for handling occasional problems provided in an embodiment of the present application. Figure 2 The method for processing the occasional problem may be executed by a processor of a computing device, and may specifically include the following steps:

[0070] S201: Monitor user operations and obtain operation information of the user operations.

[0071] S202: Save the operation information in the local memory.

[0072] It should be noted that the specific implementation of steps S201 to S202 may refer to step S101 and will not be described in detail here.

[0073] S203: Determine whether the current problem is an occasional problem.

[0074] If yes, execute step S204, if no, continue to execute step S201.

[0075] S204: Search in the saved operation information to determine the target operation information corresponding to the occasional problem.

[0076] S205: Convert target operation information corresponding to the occasional problem into a target format.

[0077] The target format is JSON format or Hypertext Markup Language HTML format.

[0078] Understandably, the database generally stores operation information in a string format. In order to facilitate developers to understand the user's operation information faster and better, in an embodiment of the present application, after determining the target operation information corresponding to the occasional problem, the processor can also convert the target operation information to be output to the developer into a JSON format or a hypertext markup language HTML format that can be directly understood. In this way, after receiving the target operation information corresponding to the occasional problem, the developer can directly handle the occasional problem without converting the target operation information corresponding to the occasional problem into a JSON format or a hypertext markup language HTML format that can be directly and clearly understood, thereby reducing the workload of the developer.

[0079] In a possible implementation, after the processor converts the target operation information corresponding to the sporadic problem into a target format, it can also display the target operation information presented in the target format on the user interface. In this way, the operating user can also know what operations he performed before the sporadic problem occurred, thereby reducing the probability of sporadic problems caused by user operation errors.

[0080] For example, Figure 3 A schematic diagram of a presentation effect of target operation information corresponding to an occasional problem provided in an embodiment of the present application; Figure 4 A schematic diagram of another presentation effect of target operation information corresponding to an occasional problem provided in an embodiment of the present application. Figure 3 As shown, the operation information can be presented in the form of each operation event as a data record. Figure 3 The "focus / blur / click / keydown" in the first column are user operation events, the "search 123 / A supercomputing data center / search 123w" in the second column are the operation elements operated by the user, the "2024-06-28 16:47:41" in the third column are the operation time when the user triggered the operation event, and the "https: / / localhost:5137 / device / machine room" in the fourth column are the routes of the corresponding pages currently operated by the user. Figure 4 As shown, the operation information can also be presented in a table format, recording the operation event, operation element, operation time, and route of the target page in a table format.

[0081] The embodiment of the present application does not limit the presentation method of the target operation information after it is converted into the target format. Optionally, the developer can also customize and expand the displayed information and method according to actual needs. For example, the routing information for the target page can be as follows: Figure 3 The full name can be displayed as shown. Figure 4 Only the abbreviation is shown. Figure 3 and Figure 4 The displayed user operation information, such as the operation events, operation elements, operation time, and routing information of the target page, can also display other information that may be needed. For example, it can also display information such as the background operation log interface of the software operated by the user, so that when developers cannot solve occasional problems through other user operation information, they can quickly find the background operation log through the background operation log interface and solve occasional problems by analyzing the background operation log.

[0082] S206: Output target operation information presented in a target format.

[0083] Optionally, the target operation information presented in the target format can be sent to the developer's terminal device through a preset notification method. The preset notification method can include email and / or information push. Sending the target operation information corresponding to the occasional problem to the developer through a variety of feasible methods can reduce the probability of missing / wrong sending, so that the developer can solve as many occasional problems as possible and improve the quality of the software product.

[0084] In this embodiment, the processor also converts the target operation information corresponding to the occasional problem into the target format, so when the target operation information corresponding to the occasional problem is sent to the developer via email and / or information push, the operation information sent may be presented in the target format. In this way, after receiving the operation information corresponding to the occasional problem, the developer does not need to convert the operation information corresponding to the occasional problem into a format that can be directly and clearly understood, thereby reducing the workload of the developer.

[0085] In a possible implementation, before outputting the target operation information, the method for handling occasional problems provided in the embodiment of the present application may also include: generating an automatic sending instruction in response to a user's setting operation; wherein the automatic sending instruction is used to instruct the computing device to output the target operation information when an occasional problem that meets preset conditions is detected.

[0086] For example, a switch that controls whether to send target operation information corresponding to occasional problems to the developer's terminal device can be displayed in the device interface, and the user can independently set whether to send target operation information corresponding to occasional problems to the developer's terminal device. If the user allows the processor to automatically send target operation information corresponding to occasional problems to the developer's terminal device, turn on the switch; if not, turn off the switch. This method in which the user determines whether to send target operation information corresponding to occasional problems to the developer can give the user full privacy autonomy and improve the user experience.

[0087] The method for handling occasional problems provided in this embodiment includes: monitoring user operations to obtain operation information of user operations; saving the operation information in a local memory; determining whether the current problem is an occasional problem; if so, searching in the saved operation information to determine the target operation information corresponding to the occasional problem; converting the target operation information corresponding to the occasional problem into a target format; and outputting the target operation information presented in the target format. In this embodiment, not only the user's operation information is saved, but also the target operation information corresponding to the occasional problem is converted into a visual target format that can be directly understood before sending the target operation information corresponding to the occasional problem to the developer's terminal device. Developers can handle occasional problems more quickly, which not only reduces the workload of developers, but also improves the efficiency of handling occasional problems.

[0088] The following is an embodiment of the device of the present application, which can be used to execute the embodiment of the method of the present application. For details not disclosed in the embodiment of the device of the present application, please refer to the embodiment of the method of the present application.

[0089] Figure 5 A schematic diagram of a device for processing occasional problems provided in an embodiment of the present application. Figure 5 As shown, the device 50 for processing occasional problems provided in the embodiment of the present application includes a monitoring unit 501 , a processing unit 502 and an output unit 503 .

[0090] The monitoring unit 501 is used to obtain and save the operation information of the user operation, where the operation information includes one or more of the operation time, operation event, operation element, and routing information of the target page.

[0091] The processing unit 502 is configured to determine target operation information corresponding to the occasional problem in the stored operation information when an occasional problem that meets a preset condition is detected.

[0092] The output unit 503 is used to output target operation information, where the target operation information is used to restore the user operation indicated by the target operation information.

[0093] In a possible implementation, the monitoring unit 501 is specifically configured to:

[0094] Use the event listener pre-implanted through the embedding technology to monitor the user operation to obtain the operation information of the user operation.

[0095] In a possible implementation, the processing unit 502 is specifically configured to:

[0096] Based on the occurrence time of the sporadic problem, operation information within a preset time before the occurrence time is determined as target operation information.

[0097] In a possible implementation, the preset condition includes any one of the following: the probability of occurrence is less than or equal to a preset value, any one of being in a preset set of occasional problems, and any one of not being in a preset set of non-occurring problems.

[0098] In a possible implementation, the operation information also includes information of a background operation log interface.

[0099] In a possible implementation, the processing unit 502 is further configured to:

[0100] Convert the target operation information into a target format; the target format is a JSON format or a Hypertext Markup Language HTML format.

[0101] In a possible implementation, the output unit 503 is specifically configured to:

[0102] Outputs target operation information in the target format.

[0103] In a possible implementation, the processing unit 502 is further configured to:

[0104] In response to a user's setting operation, an automatic sending instruction is generated; the automatic sending instruction is used to instruct the computing device to output target operation information when an occasional problem that meets preset conditions is detected.

[0105] In a possible implementation, the monitoring unit 501 is further configured to:

[0106] Clear the saved operation information regularly;

[0107] Alternatively, the saved operation information is automatically cleared when the target page is closed;

[0108] Alternatively, in response to a manual clearing processing instruction from a user, the stored operation information is cleared;

[0109] Alternatively, the operation information is stored in a stack.

[0110] The device provided in this embodiment can be used to execute the method of the above embodiment. Its implementation principle and technical effect are similar and will not be described in detail here.

[0111] It should be noted that it should be understood that the division of the various modules of the above device is only a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. And these modules can all be implemented in the form of software called by processing elements; they can also be all implemented in the form of hardware; some modules can also be implemented in the form of software called by processing elements, and some modules can be implemented in the form of hardware. In addition, it can also be stored in the memory of the above device in the form of program code, and the functions of the above data processing modules can be called and executed by a processing element of the above device. The implementation of other modules is similar. In addition, all or part of these modules can be integrated together, or they can be implemented independently. The processing element here can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each module above can be completed by an integrated logic circuit of hardware in the processor element or instructions in the form of software.

[0112] Figure 6 A schematic diagram of the structure of a computing device is provided for an embodiment of the present application. Figure 6 As shown, the computing device 60 includes a processor 601 , and the processor 601 is connected to a memory 602 .

[0113] The memory 602 is used to store computer-executable instructions. The memory 602 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.

[0114] The processor 601 is used to execute the computer-executable instructions stored in the memory 602 to implement the network configuration method described in the aforementioned method embodiment. The processor 601 may be a central processing unit (CPU), or an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application.

[0115] The computing device 60 may further include a communication interface 603, so as to communicate and interact with an external device through the communication interface 603. The external device may be, for example, a server or other computing devices.

[0116] In specific implementation, if the communication interface 603, the memory 602 and the processor 601 are implemented independently, the communication interface 603, the memory 602 and the processor 601 can be connected to each other through a bus and communicate with each other. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The bus can be divided into an address bus, a data bus, a control bus, etc., but it does not mean that there is only one bus or one type of bus.

[0117] Optionally, in a specific implementation, if the communication interface 603, the memory 602 and the processor 601 are integrated on a chip, the communication interface 603, the memory 602 and the processor 601 can communicate through an internal interface.

[0118] The computing device provided in this embodiment may be a server or other device, which may execute the technical solution in the above method embodiment, and its beneficial effects are similar, which will not be described in detail here.

[0119] An embodiment of the present application also provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the technical solution provided by any of the aforementioned method embodiments.

[0120] An embodiment of the present application also provides a computer program product, including a computer program, which is used to implement the technical solution provided by the aforementioned method embodiment when executed by a processor.

[0121] Those skilled in the art can understand that all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, disk or optical disk and other media that can store program codes.

[0122] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the embodiments of the present application, rather than to limit them. Although the embodiments of the present application have been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein by equivalents. These modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for handling occasional problems, characterized in that: The method comprises: Acquire and save operation information of user operations, wherein the operation information includes one or more of operation time, operation event, operation element, and routing information of a target page; When an occasional problem that meets a preset condition is detected, determining target operation information corresponding to the occasional problem in the stored operation information; The target operation information is output, where the target operation information is used to restore the user operation indicated by the target operation information.

2. The method according to claim 1, characterized in that The obtaining of operation information of user operation includes: Use the event listener pre-implanted through the embedding technology to monitor the user operation to obtain the operation information of the user operation.

3. The method according to claim 1, characterized in that The determining of target operation information corresponding to the occasional problem includes: Based on the occurrence time of the sporadic problem, operation information within a preset time before the occurrence time is determined as target operation information.

4. The method according to claim 1, characterized in that: The preset conditions include any one of the following: the probability of occurrence is less than or equal to a preset value, any one of being in a preset set of occasional problems, and any one of not being in a preset set of non-occasional problems.

5. The method according to any one of claims 1 to 4, characterized in that The operation information also includes information of the background operation log interface.

6. The method according to any one of claims 1 to 4, characterized in that After determining the target operation information corresponding to the occasional problem, the method further includes: The target operation information is converted into a target format; the target format is a JSON format or a Hypertext Markup Language HTML format.

7. The method according to claim 6, characterized in that Outputting the target operation information includes: Output target operation information presented in the target format.

8. The method according to any one of claims 1 to 4, characterized in that Before outputting the target operation information, the method further includes: In response to a user's setting operation, an automatic sending instruction is generated; the automatic sending instruction is used to instruct the computing device to output the target operation information when an occasional problem that meets a preset condition is detected.

9. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: Clear the saved operation information regularly; Alternatively, the saved operation information is automatically cleared when the target page is closed; Alternatively, in response to a manual clearing processing instruction from a user, the stored operation information is cleared; Alternatively, the operation information is stored in a stack.

10. A computing device, characterized in that: The computing device includes a processor connected to a memory; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the method according to any one of claims 1 to 9.

Images