Fault positioning method, log format configuration method, device and storage medium

Abstract

Embodiments of the present application provide a fault positioning method, a log format configuration method, a device and a storage medium. The method comprises: receiving a data reporting request sent by a user terminal; determining a data positioning identifier corresponding to the data reporting request; obtaining user data corresponding to the data positioning identifier generated by the user terminal, the user data comprising: user side account information, user side configuration information, user side running environment, application program interface (API) calling log, and user operation log; and performing fault positioning operation based on the user data. The technical solution of the embodiments effectively realizes quick acquisition of running related data of the user terminal, and performs fault positioning operation through the user data. In this way, the communication cost of fault troubleshooting can be reduced, and the fault troubleshooting efficiency can be improved. Moreover, when the user submits a work order, no large amount of inaccurate problem description operation is required, thereby avoiding the problem of difficult fault positioning caused by unclear expression of words.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, in particular to a fault positioning method, a log format configuration method, a device and a storage medium. BACKGROUND

[0002] With the rapid development of network technology, the application range of application programs is becoming more and more extensive. When the user uses the application program or the application platform, it is possible to encounter problems or faults that cannot be solved. At this time, the user can perform problem consultation or fault reporting operation through the preset control platform and the preset communication mode. However, in the process of problem consultation or fault reporting, the user often cannot accurately describe the problem encountered due to different professional term expressions or because the use environment is relatively complex, thereby causing the problem troubleshooting to be difficult. SUMMARY

[0003] The embodiments of the present application provide a fault positioning method, a log format configuration method, a device and a storage medium. When the user raises a work order, the user does not need to perform a large amount of inaccurate problem description operation, thereby avoiding the problem that fault positioning is difficult due to unclear expression of words. In this way, not only can the communication cost in the fault troubleshooting process be reduced, but also the fault troubleshooting efficiency can be improved.

[0004] In a first aspect, the embodiments of the present application provide a fault positioning method, comprising:

[0005] receiving a data reporting request sent by a user end;

[0006] determining a data positioning identifier corresponding to the data reporting request;

[0007] obtaining user data corresponding to the data positioning identifier generated by the user end, the user data comprising: user side account information, user side configuration information, user side running environment, application program interface (API) calling log and user operation log;

[0008] performing fault positioning operation based on the user data.

[0009] In a second aspect, the embodiments of the present application provide a fault positioning device, comprising:

[0010] a first receiving module configured to receive a data reporting request sent by a user end;

[0011] a first determining module configured to determine a data positioning identifier corresponding to the data reporting request;

[0012] The first obtaining module is configured to obtain user data corresponding to the data positioning identifier generated by the user terminal, wherein the user data comprises user-side account information, user-side configuration information, a user-side running environment, application program interface (API) calling logs and user operation logs.

[0013] The first processing module is configured to perform a fault positioning operation based on the user data.

[0014] In a third aspect, an electronic device is provided, comprising a memory and a processor, wherein the memory is configured to store one or more computer instructions, and the one or more computer instructions are configured to implement the fault positioning method in the first aspect when executed by the processor.

[0015] In a fourth aspect, a computer storage medium is provided, configured to store a computer program, and the computer program is configured to implement the fault positioning method in the first aspect when executed by a computer.

[0016] In a fifth aspect, a computer program product is provided, comprising a computer readable storage medium storing computer instructions, and the computer instructions are configured to cause one or more processors to perform the steps of the fault positioning method in the first aspect when executed by the one or more processors.

[0017] In a sixth aspect, a fault positioning method is provided, comprising:

[0018] obtaining a data reporting request, wherein the data reporting request is configured to perform a fault positioning operation;

[0019] determining a preset log format corresponding to the data reporting request;

[0020] generating reporting data based on the preset log format, wherein the reporting data comprises user-side account information, user-side configuration information, a user-side running environment, application program interface (API) calling logs and user operation logs;

[0021] reporting the reporting data, so as to perform a fault positioning operation based on the reporting data.

[0022] In a seventh aspect, a fault positioning device is provided, comprising:

[0023] The second obtaining module is configured to obtain a data reporting request, wherein the data reporting request is configured to perform a fault positioning operation;

[0024] The second determining module is configured to determine a preset log format corresponding to the data reporting request;

[0025] a second generating module, configured to generate report data based on the preset log format, the report data including user-side account information, user-side configuration information, a user-side running environment, application program interface (API) calling logs, and user operation logs;

[0026] a second processing module, configured to report the report data, so as to perform a fault locating operation based on the report data.

[0027] In an eighth aspect, an embodiment of the present application provides an electronic device, including a memory and a processor; the memory is configured to store one or more computer instructions; when the one or more computer instructions are executed by the processor, the fault locating method in the sixth aspect is implemented.

[0028] In a ninth aspect, an embodiment of the present application provides a computer storage medium, configured to store a computer program; when the computer program is executed by a computer, the fault locating method in the sixth aspect is implemented.

[0029] In a tenth aspect, an embodiment of the present application provides a computer program product, including a computer readable storage medium storing computer instructions; when the computer instructions are executed by one or more processors, the one or more processors are caused to perform the steps in the fault locating method shown in the sixth aspect.

[0030] In an eleventh aspect, an embodiment of the present application provides a fault locating method, including:

[0031] obtaining report data used for performing a fault locating operation, the report data including user-side account information, user-side configuration information, a user-side running environment, application program interface (API) calling logs, and user operation logs;

[0032] judging whether the report data can be used to locate fault information through log checking;

[0033] if the report data cannot be used to locate fault information, performing scene restoration based on the report data, so as to perform a fault locating operation.

[0034] In a twelfth aspect, an embodiment of the present application provides a fault locating device, including:

[0035] a third obtaining module, configured to obtain report data used for performing a fault locating operation, the report data including user-side account information, user-side configuration information, a user-side running environment, application program interface (API) calling logs, and user operation logs;

[0036] a third judging module, configured to judge whether the report data can be used to locate fault information through log checking;

[0037] The third processing module is configured to perform scene restoration based on the reported data to perform the fault positioning operation if the fault information cannot be located.

[0038] In a thirteenth aspect, an embodiment of the present application provides an electronic device, comprising a memory and a processor, wherein the memory is configured to store one or more computer instructions, and the one or more computer instructions are configured to implement the fault positioning method in the eleventh aspect when executed by the processor.

[0039] In a fourteenth aspect, an embodiment of the present application provides a computer storage medium configured to store a computer program, and the computer program is configured to implement the fault positioning method in the eleventh aspect when executed by a computer.

[0040] In a fifteenth aspect, an embodiment of the present application provides a computer program product, comprising a computer readable storage medium storing computer instructions, and the computer instructions are configured to cause one or more processors to perform the steps of the fault positioning method in the eleventh aspect when executed by the one or more processors.

[0041] In a sixteenth aspect, an embodiment of the present application provides a log format configuration method, comprising:

[0042] obtaining scene information capable of being run by a user terminal and log configuration information corresponding to the scene information;

[0043] generating a preset log format corresponding to the scene information based on the log configuration information, and the preset log format is configured to obtain at least part of log data of the user terminal.

[0044] In a seventeenth aspect, an embodiment of the present application provides a log format configuration apparatus, comprising:

[0045] a fourth obtaining module configured to obtain scene information capable of being run by a user terminal and log configuration information corresponding to the scene information;

[0046] a fourth processing module configured to generate a preset log format corresponding to the scene information based on the log configuration information, and the preset log format is configured to obtain at least part of log data of the user terminal.

[0047] In an eighteenth aspect, an embodiment of the present application provides an electronic device, comprising a memory and a processor, wherein the memory is configured to store one or more computer instructions, and the one or more computer instructions are configured to implement the log format configuration method in the sixteenth aspect when executed by the processor.

[0048] In a nineteenth aspect, an embodiment of the present application provides a computer storage medium for storing a computer program, which causes a computer to execute the log format configuration method in the sixteenth aspect.

[0049] In a twentieth aspect, an embodiment of the present application provides a computer program product, comprising: a computer readable storage medium storing computer instructions, which, when executed by one or more processors, causes the one or more processors to perform the steps of the log format configuration method shown in the sixteenth aspect.

[0050] The technical solution provided by the embodiment can quickly obtain log running data corresponding to the user end by receiving a data reporting request sent by the user end, determining a data positioning identifier corresponding to the data reporting request, and then obtaining user data corresponding to the data positioning identifier generated by the user end. The user data includes user side account information, user side configuration information, user side running environment, application program interface (API) calling log, and user operation log. Therefore, the technical solution can quickly obtain log running data corresponding to the user end, and then perform fault positioning operation based on the obtained user data. This can reduce communication cost in the fault troubleshooting process and improve fault troubleshooting efficiency. Meanwhile, when the user submits a work order, the user does not need to perform inaccurate problem description operation, thereby effectively avoiding the problem that fault positioning operation is difficult due to unclear expression in words, further improving the quality and efficiency of fault positioning operation, ensuring the practicality of the method, and being conducive to market promotion and application. BRIEF DESCRIPTION OF DRAWINGS

[0051] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or prior art description. Obviously, the drawings in the following description are some embodiments of the present application, and for those skilled in the art, other drawings can also be obtained without creative labor.

[0052] Figure 1 A principle diagram of a fault positioning method provided by an embodiment of the present application;

[0053] Figure 2 A flow diagram of a fault positioning method provided by an embodiment of the present application;

[0054] Figure 3 A flow diagram of a fault positioning operation based on the user data provided by an embodiment of the present application;

[0055] Figure 4 A flow diagram of obtaining user data corresponding to the data positioning identifier generated by the user end provided by an embodiment of the present application;

[0056] Figure 5 A flowchart of a user performing a fault locating method according to an application embodiment of the present application is shown in FIG. 1;

[0057] Figure 6 A flowchart of a developer performing a fault locating method according to an application embodiment of the present application is shown in FIG. 2;

[0058] Figure 7 A principle diagram of a fault locating method according to an application embodiment of the present application is shown in FIG. 3;

[0059] Figure 8 A flowchart of another fault locating method according to an embodiment of the present application is shown in FIG. 4;

[0060] Figure 9 A flowchart of still another fault locating method according to an embodiment of the present application is shown in FIG. 5;

[0061] Figure 10 A flowchart of still another fault locating method according to an embodiment of the present application is shown in FIG. 6;

[0062] Figure 11 A flowchart of still another fault locating method according to an embodiment of the present application is shown in FIG. 7;

[0063] Figure 12 A flowchart of still another fault locating method according to an embodiment of the present application is shown in FIG. 8;

[0064] Figure 13 A flowchart of still another fault locating method according to an embodiment of the present application is shown in FIG. 9;

[0065] Figure 14 A flowchart of a user performing a fault locating method according to an application embodiment of the present application is shown in FIG. 1;

[0066] Figure 15 A flowchart of a developer performing a fault locating method according to an application embodiment of the present application is shown in FIG. 2;

[0067] Figure 16 A principle diagram of a fault locating method according to an application embodiment of the present application is shown in FIG. 3;

[0068] Figure 17 A flowchart of a log format configuration method according to an embodiment of the present application is shown in FIG. 10;

[0069] Figure 18 A structure diagram of a fault locating device according to an embodiment of the present application is shown in FIG. 11;

[0070] Figure 19 A structure diagram of a fault locating device according to an embodiment of the present application is shown in FIG. 11; Figure 18A schematic diagram of the electronic device corresponding to the fault location device provided in the embodiment shown.

[0071] Figure 20 This is a schematic diagram of another fault location device provided in an embodiment of the present invention;

[0072] Figure 21 To and Figure 20 A schematic diagram of the electronic device corresponding to the fault location device provided in the embodiment shown.

[0073] Figure 22 This is a schematic diagram of the structure of another fault location device provided in an embodiment of the present invention;

[0074] Figure 23 To and Figure 22 A schematic diagram of the electronic device corresponding to the fault location device provided in the embodiment shown.

[0075] Figure 24 A schematic diagram of a log format configuration device provided in an embodiment of the present invention;

[0076] Figure 25 To and Figure 24 The illustrated embodiment provides a schematic diagram of the electronic device corresponding to the log format configuration device. Detailed Implementation

[0077] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0078] The terminology used in the embodiments of this invention is for the purpose of describing particular embodiments only and is not intended to limit the invention. The singular forms “a,” “the,” and “the” used in the embodiments of this invention and the appended claims are also intended to include the plural forms, unless the context clearly indicates otherwise. “Multiple” generally includes at least two, but does not exclude the inclusion of at least one.

[0079] It should be understood that the term "and / or" used in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0080] Depending on the context, the word "if" as used herein can be interpreted to mean "when" or "while" or "in response to determining" or "in response to detecting." Similarly, the phrase "if it is determined" or "if [a stated condition or event] is detected" can be interpreted to mean "when it is determined" or "in response to determining" or "when [the stated condition or event] is detected" or "in response to detecting [the stated condition or event]."

[0081] It is also noted that the terms "comprises" and / or "comprising," or "includes" and / or "including" when used in this specification, specify the presence of stated features, integers, steps, operations, elements, or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or groups thereof.

[0082] In addition, the sequence of steps in the following method embodiments is only an example, not a strict limitation.

[0083] Term explanation:

[0084] Pre-set data: data needed for problem troubleshooting designed in advance, carried in the form of scripts on the user side, and used for data reporting.

[0085] User ticket: when the user encounters a problem using the console, the user can submit a consultation or perform a fault reporting operation through a ticket platform, a preset communication software, or the like.

[0086] Some embodiments of the present application will be described in detail below with reference to the accompanying drawings. The following embodiments and features in the embodiments can be combined with each other without conflict. In addition, the sequence of steps in the following method embodiments is only an example, not a strict limitation.

[0087] Figure 1 A principle diagram of a fault positioning method provided by an embodiment of the present application; Figure 2 A flow diagram of a fault positioning method provided by an embodiment of the present application; with reference to FIG. 2, Figures 1-2 The embodiment provides a fault positioning method, and an execution subject of the method is a fault positioning device. It can be understood that the fault positioning device can be implemented as software or a combination of software and hardware, and in a specific implementation, the fault positioning device can be implemented as a terminal / server corresponding to a developer. The fault positioning method can include the following steps.

[0088] Step S201: receiving a data reporting request sent by a user terminal.

[0089] The user terminal can be any device capable of providing computing services and performing data processing methods in physical implementation, such as a mobile phone, a tablet computer, a personal computer, a set application, and the like. When the user uses the user terminal, the user terminal can malfunction, for example, unable to perform normal web access operations or unable to perform a certain data processing operation, and the like. When the user terminal malfunctions, the user can report the malfunction or seek advice through a preset platform or a preset communication software. At this time, the user terminal can generate a data reporting request, which can include a user identity corresponding to the user terminal, a data positioning identifier, and the like. Then, the user terminal can send the generated data reporting request to the fault positioning device, so that the fault positioning device can receive the data reporting request sent by the user terminal.

[0090] Step S202: Determine the data positioning identifier corresponding to the data reporting request.

[0091] After obtaining the data reporting request, the data reporting request can be analyzed and processed to determine the data positioning identifier corresponding to the data reporting request, which is used to obtain user data for fault analysis operation. The data positioning identifier can be a data time period corresponding to the malfunction of the user terminal. The data time period can be 5 minutes, 10 minutes, 15 minutes, or 20 minutes, and the like.

[0092] Specifically, when the data reporting request includes the data positioning identifier, after obtaining the data reporting request, the data reporting request can be subjected to data extraction operation, so as to directly obtain the data positioning identifier. Alternatively, when the data reporting request does not include the data positioning identifier, after obtaining the data reporting request, the user can input an execution operation for the data positioning identifier based on the data reporting request, and the data positioning identifier can be obtained based on the execution operation.

[0093] Step S203: Obtain user data corresponding to the data positioning identifier generated by the user terminal, including user side account information, user side configuration information, user side running environment, application program interface API calling log, and user operation log.

[0094] When the user uses the user terminal, the user terminal can generate millions of data, and different data can be generated in different running environments. For example, the user terminal is configured with a browser application, an e-commerce transaction platform, and an instant chat application. When the user uses the browser application, browser data can be generated, when the user uses the e-commerce transaction platform, e-commerce transaction data can be generated, and when the user uses the instant chat application, instant chat data can be generated. It can be understood that the above-mentioned browser data, e-commerce transaction data and instant chat data are different, and the above-mentioned browser data, e-commerce transaction data and instant chat data are all user data.

[0095] When the user terminal fails, in order to enable the R&D personnel to quickly and accurately perform fault positioning operation, after obtaining the data positioning identifier, the user data corresponding to the data positioning identifier generated by the user terminal can be obtained, wherein the user data corresponding to the data positioning identifier can be part of all user data generated by the user terminal. Specifically, the user data can include: user side account information (such as user side account name information, user side account ID information, etc.), user side configuration information (such as operation configuration information, interface configuration information, etc.), user side running environment (such as browser environment, instant chat application environment), application program interface API calling log, user operation log (which can include user input click operation on the operation interface, user file adding, deleting, searching, modifying operation, etc.).

[0096] It should be noted that the user data can include not only the above-mentioned information, but also other data, such as historical fault information, user terminal running state, etc. Those skilled in the art can configure the user data according to specific application requirements, which will not be described here.

[0097] Step S204: performing fault positioning operation based on user data.

[0098] After obtaining the user data, the user data can be analyzed and processed to realize fault positioning operation. In some examples, performing fault positioning operation based on user data can include: obtaining a pre-trained neural network model, the neural network model is trained to be used for fault positioning operation based on user data; inputting the user data into the neural network model, the fault positioning result output by the neural network model can be obtained, thereby realizing fault positioning operation.

[0099] In some examples, after obtaining the user data, in order to ensure the security and reliability of data processing, it can be determined whether there is confidential data in the user data. Specifically, the data security level of the user data can be obtained. If the data security level is greater than or equal to a preset level, the user data corresponding to the data security level is determined to be confidential data, otherwise, it is non-confidential data. Alternatively, the data attribute of the user data can be obtained, and then the data attribute is compared with the data corresponding to the standard confidential data. If there is standard confidential data corresponding to the data attribute, the user data corresponding to the data attribute is determined to be confidential data, otherwise, it is non-confidential data.

[0100] If there is no confidential data in the user data, the fault locating operation can be directly performed based on the user data. If there is confidential data in the user data, the confidential data included in the user data can be obfuscated to obtain obfuscated user data, and then the fault locating operation is performed based on the obfuscated user data. In this way, the security of the user data can be improved, and the illegal leakage of the user data can be effectively avoided.

[0101] The fault locating method provided by the embodiment can receive the data reporting request sent by the user terminal, determine the data locating identifier corresponding to the data reporting request, and then obtain the user data corresponding to the data locating identifier generated by the user terminal. Since the user data includes user-side account information, user-side configuration information, user-side running environment, application program interface (API) call log, and user operation log, the log running data corresponding to the user terminal can be quickly obtained. Then, the fault locating operation can be performed based on the obtained user data. In this way, the communication cost in the fault locating process can be reduced, and the fault locating efficiency can be improved. Meanwhile, when the user submits a work order, the user does not need to perform a large number of inaccurate problem description operations, thereby effectively avoiding the problem that the fault locating operation is difficult due to unclear expression of words, further improving the quality and efficiency of the fault locating operation, ensuring the practicality of the method, and being conducive to market promotion and application.

[0102] Figure 3 The flowchart of the fault locating operation based on user data provided by the embodiment of the application is shown in FIG. 1. Figure 3 The implementation manner of the fault locating operation based on user data provided by the embodiment of the application is shown in FIG. 1.

[0103] Step S301: determining whether the log troubleshooting operation on the user data can locate the fault information.

[0104] Step S302: if the fault information can be located, obtaining the fault information corresponding to the user data.

[0105] Step S303: If the fault information cannot be located, scene restoration is performed based on the user data to perform fault locating operation.

[0106] For the user side, the generated fault can be roughly divided into two types: relatively simple fault and relatively complex fault. When a relatively simple fault occurs at the user side, the fault information can be located with a high probability by performing simple log checking operation on the user data. The log checking operation can be simply understood as checking the obtained user data one by one for characters, data and interface. The checking operation can be manual checking operation or machine checking operation. When a relatively complex fault occurs at the user side, the fault information cannot be located with a high probability by performing log checking operation on the user data. At this time, scene restoration operation based on the user data is needed.

[0107] Different types of faults occurring at the user side correspond to different fault checking methods. Moreover, the log checking operation on the user data requires less data resources, is simple to operate and easy to implement. If the fault information can be directly located, the quality and efficiency of the fault information locating operation can be greatly improved. Therefore, when performing fault locating operation based on the user data, it can be determined whether the log checking operation on the user data can locate the fault information, i.e., the log checking operation on the user data is performed first to detect whether the fault information can be located. If the fault information can be located, the fault information corresponding to the user data can be directly obtained. If the fault information cannot be located, scene restoration operation based on the user data can be performed to realize fault locating operation.

[0108] Specifically, when scene restoration operation based on the user data is needed, the implementation method of the scene restoration operation based on the user data is not limited in the embodiment. In some examples, a machine learning model for implementing scene restoration operation is pre-trained. After the user data is obtained, the user data can be input into the machine learning model to implement scene restoration operation, so as to realize fault locating operation.

[0109] In other examples, the scene restoration based on the user data in the embodiment can include: establishing a simulation running environment same as the user side running environment; in the simulation running environment, generating interface information corresponding to the user data based on the user side account information and the user side configuration information; and in the interface information, performing scene restoration based on the API calling log and the user operation log.

[0110] Since the user data can include: user side account information, user side configuration information, user side running environment, application program interface API calling log, user operation log, in order to be able to realize scene restoration operation, can first establish the same simulation running environment with the user side running environment, and then in the simulation running environment, based on the user side account information and the user side configuration information, the interface information corresponding to the user data is generated, and the interface information is the same as the interface of the user when using the user terminal. After generating the interface information, the scene restoration operation can be performed in the interface information based on the API calling log and the user operation log, so that the R&D personnel can intuitively view all operation behaviors of the user in a specific time period when the user terminal fails, which is beneficial to improve the quality and efficiency of fault positioning operation.

[0111] In the embodiment, whether the log checking operation on the user data can locate the fault information is judged, if the fault information can be located, the fault information corresponding to the user data is obtained, if the fault information cannot be located, the scene is restored based on the user data, so that the user data can be analyzed and processed based on different implementation manners, and the fault positioning operation is realized, which not only improves the flexibility and reliability of the fault positioning method, but also improves the quality and efficiency of the fault checking operation.

[0112] Figure 4 The flowchart for obtaining the user data corresponding to the data positioning identifier generated by the user terminal is provided in the embodiment of the application. Figure 4 As shown in the figure, in the process of fault positioning operation, the embodiment provides an implementation manner for obtaining the user data corresponding to the data positioning identifier, specifically, the user data corresponding to the data positioning identifier generated by the user terminal in the embodiment can include:

[0113] Step S401: obtaining user side real-time data generated by the user terminal.

[0114] After the user terminal is connected with the fault positioning device, in order to reduce the operation required to be performed by the user, the fault positioning device can collect all the data generated by the user terminal in real time, that is, the fault positioning device can obtain the user side real-time data generated by the user terminal, and can store the user side real-time data in a preset area.

[0115] In some examples, obtaining the user side real-time data generated by the user terminal can include: obtaining a preset log format corresponding to the user terminal; based on the preset log format, the data generated by the user terminal is collected in real time to obtain the user side real-time data.

[0116] The preset log format is used to define the data types included in the obtained user-side real-time data, for example: the preset log format at least includes: a log format for obtaining user-side account information, a log format for obtaining user-side configuration information, a log format for obtaining a user-side running environment, a log format for obtaining API calling behavior, a log format for obtaining user operation behavior, and the like. Since the user-side real-time data required to be obtained is different when the user terminal is in different running environments, in order to be able to obtain the user-side real-time data generated by the user terminal, the preset log format corresponding to the user terminal can be obtained first. In some examples, the fault locating device can be configured with multiple preset log formats, after the user terminal is communicatively connected with the fault locating device, the preset log format corresponding to the user terminal can be determined. The preset log format corresponding to the user terminal can be any one of the multiple preset log formats configured in advance, and different user terminals can correspond to the same or different preset log formats.

[0117] In other examples, obtaining the preset log format corresponding to the user terminal can include: obtaining scenario information corresponding to the user terminal; determining the preset log format corresponding to the user terminal based on the scenario information.

[0118] Since the user terminal can run in different scenario information based on the use demand or design demand of the user, and different scenario information can correspond to different preset log formats, in order to accurately obtain the preset log format corresponding to the user terminal, the scenario information corresponding to the user terminal can be obtained first. Specifically, the scenario information can be obtained by analyzing and processing the data reporting request, wherein the data reporting request includes a scenario identifier, and the scenario information can be determined through the scenario identifier in the data reporting request. Alternatively, after obtaining the data reporting request, scenario data corresponding to the data reporting request can be obtained, and the scenario information corresponding to the user terminal can be determined based on the scenario data.

[0119] After obtaining the scenario information, the scenario information can be analyzed and processed to determine the preset log format corresponding to the user terminal. Specifically, a mapping relationship between different scenario information and respective corresponding preset log formats is configured in advance, and the preset log format corresponding to the user terminal can be determined based on the scenario information and the above mapping relationship.

[0120] After obtaining the preset log format, the data generated by the user terminal can be collected in real time based on the preset log format, so that the user-side real-time data corresponding to the user terminal and the scenario information can be obtained. It should be noted that the user-side real-time data generated by different user terminals is different, and the user-side real-time data corresponding to different scenario information is different.

[0121] Step S402: Based on the data positioning identifier, determine the data identifier time period corresponding to the data reporting request.

[0122] Since the data volume of the user-side real-time data is large, and the data required for the troubleshooting operation only needs the data corresponding to the abnormal operation period of the user end, in order to improve the quality and efficiency of fault positioning, after determining the data positioning identifier corresponding to the data reporting request, the data positioning identifier can be analyzed and processed to determine the data identifier time period corresponding to the data reporting request. When the data identifier time period is included in the data reporting request, the data identifier time period can be obtained by performing information extraction operation on the data reporting request; or when there is a mapping relationship between the data reporting request and the data identifier time period, the data identifier time period can be determined through the mapping relationship.

[0123] In addition, the length of the data identifier time period can be different based on the fault type and application scenario of the user end. Specifically, when the fault type of the user end is complex, the time period can be preferably a relatively long time period; when the application scenario of the user end is typical and simple, the time period can be preferably a relatively short time period.

[0124] Step S403: In the user-side real-time data, obtain the user data corresponding to the data identifier time period.

[0125] After obtaining the data identifier time period and the user-side real-time data, the user data corresponding to the data identifier time period can be obtained in the user-side real-time data, wherein each data in the user-side real-time data corresponds to a time identifier, thereby effectively ensuring the accuracy and reliability of the user data acquisition.

[0126] In this embodiment, by obtaining the user-side real-time data generated by the user end, determining the data identifier time period corresponding to the data reporting request based on the data positioning identifier, and then obtaining the user data corresponding to the data identifier time period in the user-side real-time data, the accuracy and reliability of the user data acquisition are effectively ensured, and since the data volume of the user data for fault positioning operation is relatively small, the quality and efficiency of fault positioning are improved.

[0127] In specific application, the application embodiment provides a fault positioning method, and the execution subject of the fault positioning method can include a user end corresponding to a user and a fault positioning device corresponding to a developer, wherein the user end and the fault positioning device are in communication connection. Referring to FIG. 1, when the user executes the above fault positioning method through the user end, the following steps are included: Figure 5

[0128] Step 1: The operation of the user on the user end encounters a fault / problem.​

[0129] Step 2: Trigger the submission operation of the fault ticket based on the encountered fault / issue.

[0130] Step 3: When submitting the ticket data, the problem can be described according to the problem template in the preset ticket.

[0131] Specifically, after the user enters the bill page, the reporting operation of the fault ticket can be triggered immediately, and then some necessary information for log analysis can be provided according to the bill template. The bill template generally includes user account, problem period, and other information.

[0132] Step 4: After filling in the ticket data, the filled ticket data can be submitted to the fault positioning device, so that the R&D personnel can perform fault positioning operation based on the ticket data.

[0133] Referring to FIG. 8, when the R&D personnel (developer) performs the above fault positioning method through the fault positioning device (i.e. platform side), the following steps are included: Figures 6-7

[0134] Step 11: Receive the ticket data sent by the user end.

[0135] Among them, the fault positioning device includes a log storage system and a ticket system. Before the fault positioning device receives the ticket data sent by the user end, the fault positioning device can be in communication connection with the user end. At this time, the fault positioning device can perform configuration operation of the preset log format based on the application environment of the user end. Specifically, the fault positioning device can include a plurality of preset log formats. The corresponding preset log format is configured based on the application environment of the user end, and then the preset log format is sent to the user end, or the user end actively pulls the configured preset log format. It should be noted that when the user end enters a specific page, it will actively pull and apply the preset log format.

[0136] After the user end obtains the preset log format, log information can be recorded based on the preset log format, including but not limited to: user account information, user side basic configuration information, front-end loading resource record, API calling log, user operation log, etc. After the user end records the log information, the fault positioning device can obtain the log information recorded by the user end in real time or in real time. At this time, the amount of log data reported to the fault positioning device is large, and the fault positioning device can store the log information in the log storage system.

[0137] Step 12: Trigger the automatic diagnosis task according to the problem template included in the ticket data, and restore the user behavior.

[0138] ​After the work order system receives the work order data sent by the user end, the corresponding log data can be pulled from the stored log information according to the user slip template, that is, the log data can be filtered based on the application scenario time and other characteristics corresponding to the user end failure to obtain target log information for fault positioning operation.

[0139] Step 13: Quickly locate the problem based on the automatic diagnosis result.

[0140] Based on the target log information, the fault positioning operation is performed to quickly locate the fault. Specifically, after the user side slip is successful, the work order process reaches the platform side R&D personnel, and the fault positioning device (i.e. the platform side) can perform fault positioning operation based on the obtained target log information. First, a local container can be started on the platform side, which can automatically pull the target log information corresponding to the time period according to the user account and the time period when the problem occurs. Since the data volume of the target log information is huge, in order to quickly identify the user's fault problem, the platform side can first use intelligent algorithms to quickly extract abnormal logs and perform intelligent diagnosis. The intelligent algorithm can be realized based on rule matching mode or autonomous learning form.

[0141] If the intelligent algorithm cannot locate the fault information, scene restoration operation can be performed based on the target log information. Specifically, a simulation running environment identical to the user side running environment can be established first. Then, based on the user side account information and the user side configuration information, interface information corresponding to the user data is generated in the simulation running environment. In the interface information, scene restoration is performed based on API call log and user operation log to perform fault positioning operation. Specifically, when performing scene restoration operation, the number of js error logs and API error logs used in the problem time period can be analyzed. Taking a js error log as an example, the user click behavior and API request before and after the user js error log occurs are pulled and injected into the user scene restoration container, which can quickly reproduce the js error problem and give the js error reason.

[0142] Step 14: Solve the located fault / problem to ensure normal operation of the user end.

[0143] After determining the fault information, the preset operation and maintenance method can be used to solve the fault, so that the user end can perform normal data processing operation, thereby realizing quick positioning and solving of the user end fault, and improving the good experience of the user end.

[0144] The technical scheme provided by the application embodiment comprises the following steps: a developer provides a fault reporting script tool, which is injected in an operation interface of a fault positioning device and a user terminal; after the fault positioning device and the user terminal are connected in communication, if the user terminal enters a preset application or a preset interface, the user's current operation can be recorded according to a preset log format, and the log can be directly uploaded to the fault positioning device, so that the fault positioning device can perform fault positioning operation based on the uploaded log, thereby effectively realizing that when the user submits a work order, there is no need to perform a large amount of inaccurate problem description, and the problem of unclear expression is avoided; in addition, all relevant operation logs on the user side can be quickly obtained, so that the user scene can be quickly restored, the communication cost in the problem troubleshooting process is reduced, the troubleshooting efficiency is improved, and the practicability of the method is further improved.

[0145] Figure 8 Another flowchart of a fault positioning method provided by the embodiment of the application is shown in FIG. 6. Figure 8 The embodiment provides another fault positioning method, and the execution subject of the method is a fault positioning device. It can be understood that the fault positioning device can be implemented as software or a combination of software and hardware, and in specific implementation, the fault positioning device can be implemented as a user terminal. In physical implementation, the user terminal can be any device that can provide computing services and processing, such as a mobile phone, a tablet computer, a personal computer, a set application program, and the like. Specifically, the fault positioning method can comprise the following steps.

[0146] Step S801: Obtain a data reporting request, the data reporting request being used for fault positioning operation.

[0147] When the user uses the user terminal, a fault may occur, for example, normal web access operation cannot be implemented or a certain data processing operation cannot be performed, and the like. When a fault occurs in the user terminal, the user can perform fault reporting operation through a preset platform or a preset communication software, at this time, the user terminal can generate a data reporting request used for fault positioning operation based on the execution operation input by the user, the data reporting request can comprise a user identity corresponding to the user terminal, a data positioning identifier, and the like, and then the user terminal can send the generated data reporting request to the fault positioning device, so that the fault positioning device can receive the data reporting request sent by the user terminal.

[0148] Step S802: Determine a preset log format corresponding to the data reporting request.

[0149] Since different user terminals can correspond to different scene information, and different scene information needs to generate different log data for fault positioning operation, in order to accurately perform fault positioning operation, after obtaining the data reporting request, the data reporting request can be analyzed and processed to determine the preset log format corresponding to the data reporting request. It should be noted that the preset log format is used to limit the data types included in the obtained user-side real-time data, for example: the preset log format at least includes: log format for obtaining user-side account information, log format for obtaining user-side configuration information, log format for obtaining user-side running environment, log format for obtaining API calling behavior, log format for obtaining user operation behavior, etc.

[0150] In some examples, the platform side is configured with a plurality of preset log formats, after the user terminal and the platform side are communicatively connected, the preset log format corresponding to the user terminal can be determined based on the type or attribute information of the user terminal. The preset log format corresponding to the user terminal can be any one of the plurality of preset log formats configured in advance, and different user terminals can correspond to the same or different preset log formats.

[0151] In other examples, the preset log format can be determined based on the scene information corresponding to the data reporting request. Specifically, determining the preset log format corresponding to the data reporting request includes: obtaining the scene information corresponding to the data reporting request; based on the scene information, determining the preset log format corresponding to the data reporting request.

[0152] Since the user terminal can run in different application scenarios based on the user's use demand, and different application scenarios can correspond to different preset log formats, in order to accurately obtain the preset log format corresponding to the data reporting request, the scene information corresponding to the data reporting request can be obtained first. When the scene identifier is included in the data reporting request, the scene information can be determined by extracting the scene identifier in the data reporting request. Alternatively, after obtaining the data reporting request, the scene data corresponding to the data reporting request can be obtained, and the scene information corresponding to the data reporting request can be determined based on the scene data.

[0153] After obtaining the scene information, the scene information can be analyzed and processed to determine the preset log format corresponding to the data reporting request. Specifically, a mapping relationship between different scene information and preset log format is configured in advance, and the preset log format corresponding to the data reporting request can be determined based on the scene information and the above mapping relationship.

[0154] Step S803: based on the preset log format, generate the reporting data, and the reporting data includes the user side account information, the user side configuration information, the user side running environment, the application program interface API calling log, and the user operation log.

[0155] After obtaining the preset log format, the log collection operation can be performed based on the preset log format, so as to generate the reporting data. Specifically, the reporting data can include: user side account information (for example, user side account name information, user side account ID information, etc.), user side configuration information (for example, operation configuration information, interface configuration information, etc.), user side running environment (for example, browser environment, and instant chat application environment), application program interface API calling log, and user operation log (which can include: user input click operation on the operation interface, user file adding, deleting, searching, and modifying operation, etc.).

[0156] It should be noted that the content included in the reporting data can be flexibly configured based on the preset log format, so that the fault positioning method can be applied to different scenarios. Specifically, the reporting data can not only include the information described above, but also include other data, such as historical fault information, user end running state, etc. Those skilled in the art can configure the reporting data according to the specific application requirements, which will not be described here.

[0157] Step S804: report the reporting data to perform fault positioning operation based on the reporting data.

[0158] After obtaining the reporting data, the reporting data can be reported to the platform side, so that the platform side can perform fault positioning operation based on the received reporting data. At this time, the execution subject of the fault positioning operation is the platform side.

[0159] In some other examples, before obtaining the reporting data, in order to ensure the security and reliability of data use, it can be identified whether there is confidential data (or sensitive data) in the user data, wherein the confidential data (or sensitive data) can include: user account password, user identity information, etc. If there is no confidential data in the user data, the fault positioning operation can be performed based on the user data. If there is confidential data in the user data, the confidential data included in the user data can be obfuscated to obtain obfuscated data, and then the obfuscated data is reported to the platform side, so that the platform side can perform fault positioning operation based on the obfuscated data. In this way, the security of user data use can be improved, and the illegal leakage of user data can be effectively avoided.

[0160] The fault positioning method provided by the embodiment can quickly obtain the reporting data related to the fault in the user end, and then the reporting data can be reported to perform the fault positioning operation based on the reporting data, which can reduce the communication cost in the fault troubleshooting process and improve the fault troubleshooting efficiency; meanwhile, when the user submits a work order, the user does not need to perform the inaccurate problem description operation again, thereby effectively avoiding the problem that the fault positioning operation is difficult due to unclear expression in words; in addition, the embodiment provides a method for determining different preset log formats based on the data reporting request in different scenarios, and the different preset log formats are used to obtain different log data in different scenarios, thereby effectively solving the problem in the prior art that the problem of an individual user can only be reproduced in a specific browser or a specific scenario, and the developer often has difficulty in reproducing the scenario, thereby failing to perform the fault troubleshooting operation, further improving the quality and efficiency of the fault positioning operation, ensuring the practicality of the method, and being conducive to the market promotion and application.

[0161] Figure 9 The flowchart of another fault positioning method provided by the embodiment of the application is shown in FIG. 9. Figure 9 After the preset log format corresponding to the data reporting request is determined, the method in the embodiment can further include the following steps.

[0162] Step S901: generating a log collection prompt corresponding to the preset log format.

[0163] For the user end, the generated fault can be roughly divided into a relatively simple fault and a relatively complex fault. When the relatively simple fault occurs in the user end, the log collection operation is not needed, and the fault positioning operation can be performed through the simple fault description operation. When the relatively complex fault occurs in the user end, the fault positioning operation cannot be performed through the simple fault description operation, and therefore the log collection operation is needed to obtain the reporting data to perform the fault positioning operation based on the reporting data.

[0164] Since different types of faults can occur in the user end, after the preset log format corresponding to the data reporting request is determined, the log collection prompt corresponding to the preset log format can be generated first. The log collection prompt can be displayed in the interface in the form of a pop-up window or a dialog box. The log collection prompt can be used to inquire whether the reporting data is generated based on the preset log format, that is, whether the log collection operation is performed based on the preset log format.

[0165] Step S902: When the confirmation execution information corresponding to the log collection prompt is acquired, the reporting data is allowed to be generated based on the preset log format.

[0166] The log collection prompt can be "whether to perform the log collection operation based on the preset log format". After the log collection prompt corresponding to the preset log format is generated, the user can input the confirmation execution information based on the log collection prompt. For example, the log collection prompt can include the control "Yes" for identifying the confirmation execution information and the control "No" for identifying the cancellation execution operation. When the user inputs the clicking operation on the control "Yes", the confirmation execution information corresponding to the log collection prompt is acquired. At this time, it is indicated that the log collection operation is needed to generate the reporting data for the fault positioning operation based on the reporting data, and then the reporting data is allowed to be generated based on the preset log format.

[0167] Step S903: When the cancellation execution information corresponding to the log collection prompt is acquired, the reporting data is prohibited to be generated based on the preset log format.

[0168] After the log collection prompt corresponding to the preset log format is generated, when the user inputs the clicking operation on the control "No", the cancellation execution information corresponding to the log collection prompt is acquired. When the cancellation execution information corresponding to the log collection prompt is acquired, it is indicated that the fault positioning operation can be implemented without the log collection operation at this time, and then the reporting data is prohibited to be generated based on the preset log format.

[0169] In the embodiment, the log collection prompt corresponding to the preset log format is generated. When the confirmation execution information corresponding to the log collection prompt is acquired, the reporting data is allowed to be generated based on the preset log format. When the cancellation execution information corresponding to the log collection prompt is acquired, the reporting data is prohibited to be generated based on the preset log format. Therefore, the fault positioning operation can be flexibly selected based on different fault types generated by the user end, and the flexibility and reliability of the method are further improved.

[0170] Figure 10 Another flowchart of the fault positioning method provided by the embodiment is shown in FIG. 10. Based on the above embodiment, the flowchart of the fault positioning method provided by the embodiment is shown in FIG. 10. Figure 10 As shown in FIG. 10, in order to further improve the quality and efficiency of the fault positioning, the method in the embodiment can further include the following steps.

[0171] Step S1001: In the process of generating the reporting data, the screenshot information and / or the video recording information corresponding to the user operation behavior are acquired.

[0172] Step S1002: The screenshot information and / or the video recording information are added to the reporting data.

[0173] Since the reported data has diversity, in order to enable the R&D personnel to perform the fault positioning operation more quickly and accurately, in the process of generating the reported data, the screenshot information and / or the video recording information corresponding to the user operation behavior can be acquired, specifically, in the process of generating the reported data, the screenshot operation and / or the screen recording operation can be enabled based on the user input execution operation, so that when the user operation behavior is displayed on the display interface, the screenshot information and / or the video recording information can be obtained, that is, the image information and / or the video information of the user operation behavior is acquired, after the screenshot information and / or the video recording information is acquired, the screenshot information and / or the video recording information can be added to the reported data, so that not only the acquisition accuracy and reliability of the reported data are ensured, but also the diversity of the reported data is ensured.

[0174] In the embodiment, the screenshot or screen recording mode is combined with the log collection operation to generate the reported information, so that the R&D personnel can intuitively obtain the user operation behavior through the screenshot information and / or the video recording information, thereby facilitating the improvement of the quality and efficiency of the fault positioning.

[0175] Figure 11 Another flowchart of the fault positioning method provided by the embodiment is shown in FIG. 10. Figure 11 The embodiment provides another fault positioning method, and the execution subject of the method is a fault positioning device, which can be understood as being implemented as software or a combination of software and hardware, and specifically, the fault positioning device can be implemented as a terminal / server (platform side) corresponding to an R&D personnel. Specifically, the fault positioning method can include the following steps.

[0176] Step S1101: acquiring reported data for performing a fault positioning operation, the reported data including user side account information, user side configuration information, user side running environment, application program interface API calling log, and user operation log.

[0177] After the user end generates the reported data and reports the reported data, the fault positioning device (platform side) can acquire the reported data for performing the fault positioning operation, and the reported data includes: user side account information (for example, user side account name information, user side account ID information, etc.), user side configuration information (for example, operation configuration information, interface configuration information, etc.), user side running environment (for example, browser environment, and instant chat application environment), application program interface API calling log, and user operation log (including: click operation input by the user on the operation interface, and add, delete, search, and modify operations of the user on the file, etc.).

[0178] Step S1102: determining whether the log checking operation on the reported data can locate fault information.

[0179] Step S1103: If the fault information cannot be located, scene restoration is performed based on the reported data to perform fault locating operation.

[0180] In some examples, the method in this embodiment can further include: if the fault information can be located, obtaining the fault information corresponding to the reported data.

[0181] For the user side, the generated fault can be roughly divided into a relatively simple fault and a relatively complex fault. When the relatively simple fault occurs on the user side, the fault information can be located by performing log checking operation on the user data. When the relatively complex fault occurs on the user side, the fault information can not be located by performing log checking operation on the user data, and scene restoration operation based on the user data is needed at this time.

[0182] Since different types of faults can occur on the user side, and the log checking operation on the user data is relatively easy to implement and simple to operate, if the fault information can be directly located, the quality and efficiency of the fault information locating operation can be greatly improved. Therefore, when the fault locating operation is performed based on the user data, it can be determined whether the log checking operation on the user data can locate the fault information, i.e., the log checking operation on the user data is performed first to detect whether the fault information can be located, if the fault information can be located, the fault information corresponding to the user data can be directly obtained. If the fault information cannot be located, scene restoration operation based on the user data can be performed to realize the fault locating operation.

[0183] Specifically, the implementation manner of the scene restoration operation based on the user data in this embodiment is not limited, in some examples, a machine learning model for implementing the scene restoration operation is pre-trained, after the user data is obtained, the user data can be input into the machine learning model to implement the scene restoration operation, so as to realize the fault locating operation.

[0184] In some examples, the scene restoration based on the user data in this embodiment can include: establishing a simulation running environment same as the user side running environment; in the simulation running environment, generating interface information corresponding to the user data based on the user side account information and the user side configuration information; in the interface information, performing scene restoration based on the API calling log and the user operation log.

[0185] Since the user data can include: user side account information, user side configuration information, user side running environment, application program interface API calling log, user operation log, in order to be able to realize the scene restoration operation, the same simulation running environment as the user side running environment can be established first, and then in the simulation running environment, the interface information corresponding to the user data is generated based on the user side account information and the user side configuration information, and the interface information is the same as the interface of the user when using the user terminal. After generating the interface information, the scene restoration operation can be performed in the interface information based on the API calling log and the user operation log, so that the R&D personnel can intuitively view and understand all operation behaviors of the user in a specific time period of the user terminal running failure, which is beneficial to improve the quality and efficiency of fault positioning.

[0186] The fault positioning method provided by the embodiment can obtain the reported data for performing the fault positioning operation, and then judge whether the log checking operation on the user data can locate the fault information. If the fault information can be located, the fault information corresponding to the user data is obtained. If the fault information cannot be located, the scene is restored based on the user data, so that the fault positioning operation can be realized based on different implementation manners, which not only improves the flexibility and reliability of the fault positioning method, but also improves the quality and efficiency of fault locating, and further improves the practicability of the method.

[0187] Figure 12 The flowchart of another fault positioning method provided by the embodiment of the application is shown in FIG. 12. Figure 12 As shown in FIG. 12, the user terminal can correspond to different scene information, and different scene information can obtain different reported data. When obtaining the reported data, the reported data can be obtained by using different preset log formats. In order to realize the collection operation of the reported data of each application scene of the user terminal, the method in the embodiment can further include configuring a preset log format for the user terminal. Specifically, the method in the embodiment can include:

[0188] Step S1201: Obtain the scene information capable of being run by the user terminal and the log configuration information corresponding to the scene information.

[0189] Step S1202: Establish a preset log format corresponding to the scene information based on the log configuration information, and the preset log format is at least used to obtain the reported data.

[0190] The preset log format is used to define the data types included in the obtained user-side real-time data, for example, the preset log format at least includes: a log format for obtaining user-side account information, a log format for obtaining user-side configuration information, a log format for obtaining a user-side running environment, a log format for obtaining API calling behavior, a log format for obtaining user operation behavior, and the like.

[0191] In order to be able to configure different preset log formats for different user terminals and different scene information, the scene information that the user terminal can run can be obtained first. The scene information that the user terminal can run can refer to all the scene information that the user terminal can run that the R&D personnel can foresee, or all the scene information that the user terminal can actually run. In order to cover all the scene information and perform the preset log format configuration operation on all the application scenarios, the scene information that the user can run can be classified by scene category, and the preset log format configuration operation can be performed by the scene category.

[0192] In addition, in order to be able to implement the preset log format configuration operation, the log configuration information corresponding to the scene information also needs to be obtained, which can include the execution operation input by the user in the configuration page. After obtaining the log configuration information and the scene information, the preset log format corresponding to the scene information can be established based on the log configuration information, and the preset log format is at least used to obtain the reported data.

[0193] It should be noted that when the fault positioning device is connected to the user terminal, the user terminal is in a new scene information, and the fault positioning device does not perform the preset log format configuration operation on the above new scene information. In order to be able to implement the fault positioning operation for the user terminal, the above new scene information can be determined as a pre-configured bottom-scene type, for example, “other scene”, and then the preset log format corresponding to the above “other scene” can be determined as the preset log format corresponding to the above new scene information, so that stable fault positioning operation can be implemented for all user terminals and all application scenarios.

[0194] For example, the scene information obtained by the fault positioning device can include a browser scene, a social software scene, an e-commerce platform scene, a specific software scene, and other scenes, the preconfigured preset log format can include log format one, log format two, and log format three, after obtaining the log configuration information corresponding to each of the above scene information, the preset log format corresponding to each of the above scene information can be configured based on the log configuration information, for example, the preset log format corresponding to the browser scene can be configured as log format two, the preset log format corresponding to the social software scene can be configured as log format three, the preset log format corresponding to the e-commerce platform scene and the specific software scene can be configured as log format one, and the preset log format corresponding to other scenes can be configured as log format two, thereby completing the configuration operation of the preset log format for each scene information of the user end.

[0195] When the application scene of the user end connected by the fault positioning device is an automatic driving scene, since there is no separate configuration operation of the automatic driving scene in the fault positioning device, the automatic driving scene can be determined as “other scene”, and then the preset log format (i.e., log format two) corresponding to other scenes can be determined as the preset log format corresponding to the automatic driving scene.

[0196] In this embodiment, by obtaining the scene information that the user end can run and the log configuration information corresponding to the scene information, the preset log format corresponding to the scene information is established based on the log configuration information, thereby effectively realizing the configuration operation of the preset log format for each scene information of the user end, which effectively realizes the flexible collection operation of the log in different scenes and further improves the accuracy and reliability of obtaining the reported data.

[0197] Figure 13 Another flowchart of a fault positioning method provided by the embodiment of the present application is provided. Figure 13 Before obtaining the reported data for fault positioning operation, the method in this embodiment can further include:

[0198] Step S1301: In response to the data reporting request sent by the user end, the preset log format corresponding to the data reporting request is determined.

[0199] When the user end fails, the user can perform a fault reporting operation through a preset platform or a preset communication software, at this time, the user end can generate a data reporting request, which can include a user identity corresponding to the user end, a data positioning identifier, and the like, and then the user end can send the generated data reporting request to the fault positioning device, so that the fault positioning device can receive the data reporting request sent by the user end.

[0200] Since the user terminal can correspond to multiple scene information, and the data reporting request in different scene information can correspond to different preset log formats, in order to accurately perform fault positioning operation, after obtaining the data reporting request sent by the user terminal, the data reporting request can be analyzed and processed to determine the preset log format corresponding to the data reporting request. In some examples, the platform side is configured with multiple preset log formats, after the user terminal and the platform side are communicatively connected, the preset log format corresponding to the user terminal can be determined based on the type or attribute information of the user terminal. The preset log format corresponding to the user terminal can be any one of the multiple preset log formats configured in advance, and different user terminals can correspond to the same or different preset log formats.

[0201] In other examples, determining the preset log format corresponding to the data reporting request comprises: obtaining scene information corresponding to the data reporting request; determining the preset log format corresponding to the data reporting request based on the scene information.

[0202] Since the user terminal can run in different application scenarios based on the user's use demand, and different application scenarios can correspond to different preset log formats, in order to accurately obtain the preset log format corresponding to the data reporting request, the scene information corresponding to the data reporting request can be obtained first, wherein when the scene information is included in the data reporting request, the scene information can be determined through the scene identifier extracted in the data reporting request. Or, after obtaining the data reporting request, the scene data corresponding to the data reporting request can be obtained, and the scene information corresponding to the data reporting request can be determined based on the scene data.

[0203] After obtaining the scene information, the scene information can be analyzed and processed to determine the preset log format corresponding to the data reporting request. Specifically, a mapping relationship between different scene information and the respective corresponding preset log format is configured in advance, and the preset log format corresponding to the data reporting request can be determined based on the scene information and the above mapping relationship.

[0204] Step S1302: sending the preset log format to the user terminal to obtain the reporting data corresponding to the user terminal based on the preset log format.

[0205] After obtaining the preset log format, in order to stably obtain the reporting data corresponding to the user end, the preset log format can be sent to the user end, and after the user end obtains the preset log format, log collection operation can be performed based on the preset log format, so as to obtain the reporting data corresponding to the user end, thereby realizing that different reporting data can be obtained in different scenes, and further improving the flexibility and reliability of obtaining the reporting data.

[0206] In this embodiment, in response to the data reporting request sent by the user end, the preset log format corresponding to the data reporting request is determined, and then the preset log format is sent to the user end, so as to obtain the reporting data corresponding to the user end based on the preset log format, thereby effectively realizing that different reporting data can be obtained in different scenes, and further improving the flexibility and reliability of obtaining the reporting data.

[0207] In specific application, the application embodiment provides a fault positioning method, and the execution subject of the fault positioning method can include a user end corresponding to a user and a fault positioning device corresponding to a research and development personnel, wherein the user end is in communication connection with the fault positioning device. Figure 14 As shown in the accompanying drawings, when the user executes the above fault positioning method through the user end, the following steps are included:

[0208] Step 21: The operation of the user on the user end encounters a fault / problem.

[0209] Step 22: The submission operation of the fault work order is triggered based on the encountered fault / problem.

[0210] Step 23: Based on the operation of submitting the work order, the user is asked whether to adopt the recording form to submit the work order.

[0211] Among them, the log reporting script is pre-embedded on the user end, when the user selects the work order process, the log collection or recording operation is started, and after the user end pulls the preset log type corresponding to the scene information of the user end through the platform side, the user can be reminded to start the log recording operation based on the preset log format.

[0212] Step 24: If the user adopts the recording form to submit the work order, the log recording operation can be started, so that the log data can be obtained.

[0213] If the user does not adopt the recording form to submit the work order, the traditional work order mode is used to submit the work order, specifically, after the user enters the work order page, the reporting operation of the fault work order is triggered immediately, and then some necessary information for log analysis can be provided according to the work order template, and the work order template generally includes: user account, problem occurring period.

[0214] Step 25: When starting the log recording operation, the problem can be reproduced in the operation interface of the user terminal to obtain the log data of the problem occurring in the user terminal.

[0215] After the log recording starts, the user can perform relevant operations on the display interface to reproduce the problem encountered, and the pre-embedded log reporting script can record the relevant required logs during the log recording process, such as: user-side account information, user-side basic configuration data, user-side running environment information, API call logs, and user operation logs.

[0216] Step 26: After completing the log data, the log recording operation can be ended, and the log data can be submitted to the fault positioning device, so that the R&D personnel can perform fault positioning operations.

[0217] After the user selects to record the end, the log reporting script pops up a work order interface, and the user can supplement some other related information. After clicking submit, the collected log data can be uploaded to the platform side for storage, so that the platform side can perform fault positioning operations based on log information.

[0218] Referring to the accompanying Figures 15-16 When the R&D personnel execute the above-mentioned fault positioning method through the fault positioning device (i.e. the platform side), the following steps are included:

[0219] Step 31: Receive the work order data (including log data and other related information) sent by the user terminal.

[0220] Among them, the fault positioning device includes a log storage system and a work order system. Before the fault positioning device receives the work order data sent by the user terminal, the fault positioning device can be in communication connection with the user terminal. At this time, the fault positioning device can perform configuration operations on the pre-set log format based on the application environment of the user terminal. Specifically, the fault positioning device can include multiple pre-set log formats, and the corresponding pre-set log format can be configured based on the application environment of the user terminal. Then the pre-set log format is sent to the user terminal, or the user terminal actively pulls the configured pre-set log format. It should be noted that when the user terminal enters a specific page, it will actively pull and apply the pre-set log format.

[0221] After the user terminal obtains the pre-set log format, log information can be recorded based on the pre-set log format, including but not limited to: user account information, user-side basic configuration information, front-end loading resource records, API call logs, and user operation logs. After the user terminal records the log information, the fault positioning device can obtain the log information recorded by the user terminal in real time or in real time. At this time, the amount of log data reported to the fault positioning device is large, and the fault positioning device can store the log information in the log storage system.

[0222] Step 32: Perform a scene restoration operation according to the work order data to enable quick fault location of the problem.

[0223] When the user-side shipping order is successful, the work order process reaches the platform-side R&D personnel, and the fault location device (i.e., the platform side) can perform a fault location operation based on the obtained target log information. First, a local container can be started on the platform side, which can automatically pull the target log information corresponding to the time period when the problem occurred according to the user account and the time period when the problem occurred. Since the data volume of the target log information is huge, in order to quickly identify the user's fault problem, the platform side can first use an intelligent algorithm to quickly extract abnormal logs and perform intelligent diagnosis. The intelligent algorithm can be implemented based on a rule matching mode or autonomous learning form.

[0224] If the intelligent algorithm cannot locate the fault information, a scene restoration operation can be performed based on the target log information. Specifically, a simulation running environment that is the same as the user-side running environment can be established first. Then, based on the user-side account information and the user-side configuration information, interface information corresponding to the user data is generated in the simulation running environment. In the interface information, scene restoration is performed based on the API call log and the user operation log to perform fault location operation. Specifically, when performing the scene restoration operation, the number of js error logs and API error logs used in the problem time period can be analyzed. Taking a js error log as an example, the user click behavior and API request before and after the user js error log occurs are pulled and injected into the user scene restoration container, which can quickly reproduce the js error problem and provide the js error reason.

[0225] Step 33: Solve the located fault / problem to ensure normal operation of the user end.

[0226] After determining the fault information, the preset operation and maintenance method can be used to solve the fault, so that the user end can perform normal data processing operation, thereby realizing quick location and solution of the fault of the user end and improving the good experience of the user end.

[0227] In addition, before receiving the work order data sent by the user end, the method in the application embodiment can further include the operation of configuring the preset log format for each scene information of the user end. Specifically, the method can include:

[0228] Step 41: Obtain the scene information that the user end can run and the log configuration information corresponding to the scene information.

[0229] The platform side can define the preset log format in advance according to each application scenario corresponding to the user side to perform troubleshooting operation. Specifically, the preset log format can generally include the following types of logs: user side account information, user side basic configuration data, user side running environment information, API calling log, user operation log (page clicking, page switching information, etc.). Each application scenario and the configured preset log format can be saved on the platform side.

[0230] Step 42: Establishing a preset log format corresponding to the scene information based on the log configuration information, and the preset log format is at least used to obtain the reported data.

[0231] It should be noted that, in the process of generating the reported data, for the confidential data or high confidential data included in the reported data, the obfuscation processing operation of the confidential data can be added in the reporting script, so that the platform side obtains the data after the obfuscation processing, thereby avoiding the exposure of the user confidential problem.

[0232] The fault positioning method provided by the application embodiment is provided by a developer (research and development personnel) to provide a fault reporting script tool, the fault reporting script tool is injected into the platform side interface, and the fault reporting script opening process is added to the fault ticket process of the user side. When the user performs the fault ticket, the user can be reminded to perform the log collection operation of the user operation behavior. Specifically, after the user uniformly opens the fault ticket operation, the fault reporting script can record the related log of the current operation of the user according to the preset log format, so as to obtain the log reporting data, and the log reporting data can be directly uploaded to the platform side (server), so that the platform side can perform the fault positioning operation based on the log reporting information.

[0233] In general, the fault positioning method provided by the application embodiment can realize the following effects: the user scene is restored by the platform side container combined with the user reported log, direct access to the user system is avoided, and thus the misoperation of the user configuration behavior will not occur; when the user submits the work order, a large amount of inaccurate problem description is not required, and the problem of unclear text expression is avoided; all the running logs related to the fault on the user side can be quickly obtained, the user scene can be quickly restored based on the reported log data, the communication cost in the problem troubleshooting process is reduced, and the troubleshooting efficiency is improved; the reporting content of the log can be flexibly configured, and is suitable for different scenes; the log definition can distinguish the confidential data, the user data security is improved, the practicability of the method is further improved, and the market promotion and application are facilitated.

[0234] Figure 17 A flowchart of a log format configuration method provided by the embodiment of the application is shown in FIG. 1. Figures 1-2As shown, the embodiment provides a log format configuration method, the execution subject of the method is a log format configuration device. It can be understood that the log format configuration device can be implemented as software or a combination of software and hardware. In specific implementation, the log format configuration device can be implemented as a terminal / server corresponding to a developer. The log format configuration method can include the following steps.

[0235] Step S1701: Obtain scenario information that a user terminal can run and log configuration information corresponding to the scenario information.

[0236] The preset log format is used to limit the data types included in the obtained real-time data on the user terminal. For example, the preset log format at least includes a log format for obtaining user side account information, a log format for obtaining user side configuration information, a log format for obtaining user side running environment, a log format for obtaining API calling behavior, a log format for obtaining user operation behavior, and the like. Since different user terminals and different scenario information need to obtain different types of real-time data, in order to configure different preset log formats for different user terminals and different scenario information, the scenario information that the user terminal can run can be obtained first. The scenario information that the user terminal can run can refer to all scenario information that the user terminal can run that can be foreseen or pre-configured by the developer, or all scenario information that the user terminal can actually run. In order to cover all scenario information and perform preset log format configuration operation for all application scenarios, the scenario information that the user terminal can run can be classified by scenario category, and the preset log format configuration operation is performed by scenario category. In addition, in order to implement the preset log format configuration operation, the log configuration information corresponding to the scenario information also needs to be obtained. The log configuration information can include the execution operation input by the user in the configuration page.

[0237] Step S1702: Generate a preset log format corresponding to the scenario information based on the log configuration information, the preset log format being used to obtain at least part of log data of the user terminal.

[0238] After obtaining the log configuration information and the scenario information, the preset log format corresponding to the scenario information can be established based on the log configuration information. The preset log format is at least used to obtain the reported data.

[0239] It should be noted that when the log format configuration device is connected to the user terminal, the user terminal is in a new scene information, and the log format configuration device does not perform the preset log format configuration operation on the new scene information. In order to be able to realize accurate log collection operation for the user terminal, the new scene information can be determined as a preconfigured bottom-up scene type, such as "other scene", and the preset log format corresponding to the "other scene" can be determined as the preset log format corresponding to the new scene information, so that stable log format configuration operation can be realized for all user terminals and all application scenarios.

[0240] For example, the scene information obtained by the log format configuration device can include browser scene, social software scene, e-commerce platform scene, specific software scene, and other scene, and the preconfigured preset log format can include log format one, log format two, and log format three. After obtaining the log configuration information corresponding to each of the above scene information, the preset log format corresponding to each of the above scene information can be configured based on the log configuration information, for example, the preset log format corresponding to the browser scene can be configured as log format two, the preset log format corresponding to the social software scene can be configured as log format three, the preset log format corresponding to the e-commerce platform scene and the specific software scene can be configured as log format one, and the preset log format corresponding to the other scene can be configured as log format two, thereby completing the preset log format configuration operation for each scene information of the user terminal.

[0241] When the application scenario of the user terminal connected by the log format configuration device is an automatic driving scene, since there is no separate configuration operation for the automatic driving scene in the log format configuration device, the automatic driving scene can be determined as "other scene", and the preset log format corresponding to the other scene (i.e. log format two) can be determined as the preset log format corresponding to the automatic driving scene.

[0242] In some examples, the method in the embodiment can further include:

[0243] Step 1801: Obtain a data reporting request sent by a user terminal.

[0244] Step 1802: Determine a preset log format corresponding to the data reporting request.

[0245] Step 1803: Send the preset log format to the user terminal to obtain reporting data corresponding to the user terminal based on the preset log format.

[0246] The specific implementation manners and implementation effects of the above steps in this embodiment are similar to those of steps S1301-S1302 in the above embodiment, and reference can be made to the above statements, which are not described here again.

[0247] The log format configuration method provided in this embodiment, by acquiring the scenario information capable of being run by the user terminal and the log configuration information corresponding to the scenario information, establishing the preset log format corresponding to the scenario information based on the log configuration information, effectively realizes the configuration operation of the preset log format for each scenario information of the user terminal, that is, the preset log format is configured based on the scenario information capable of being run by the user terminal, so that flexible collection operation of logs in different scenarios is effectively realized, and the accuracy and reliability of log data acquisition are further improved.

[0248] Figure 18 A structural schematic diagram of a fault positioning device provided in an embodiment of the present application is shown in FIG. 1. Figure 18 As shown in FIG. 1, the embodiment provides a fault positioning device, which is used to execute the fault positioning method shown in FIG. 1. Figure 2 Specifically, the fault positioning device can include:

[0249] The first receiving module 11 is configured to receive a data reporting request sent by a user terminal.

[0250] The first determining module 12 is configured to determine a data positioning identifier corresponding to the data reporting request.

[0251] The first obtaining module 13 is configured to obtain user data corresponding to the data positioning identifier generated by the user terminal, wherein the user data includes user side account information, user side configuration information, user side running environment, application program interface (API) calling log, and user operation log.

[0252] The first processing module 14 is configured to perform fault positioning operation based on the user data.

[0253] In some examples, when the first processing module 14 performs fault positioning operation based on the user data, the first processing module 14 is configured to perform the following operation: judging whether the log checking operation on the user data can locate fault information; if the fault information can be located, obtaining the fault information corresponding to the user data; if the fault information cannot be located, performing scenario restoration based on the user data to perform fault positioning operation.

[0254] In some instances, when the first processing module 14 performs scene reconstruction based on user data, the first processing module 14 is used to perform: establishing a simulated operating environment identical to the user-side operating environment; in the simulated operating environment, generating interface information corresponding to the user data based on user-side account information and user-side configuration information; and performing scene reconstruction based on API call logs and user operation logs in the interface information.

[0255] In some instances, when the first acquisition module 13 acquires user data generated by the user terminal corresponding to the data location identifier, the first acquisition module 13 is used to perform the following: acquire real-time user-side data generated by the user terminal; determine the data identifier time period corresponding to the data reporting request based on the data location identifier; and acquire user data corresponding to the data identifier time period from the real-time user-side data.

[0256] In some instances, when the first acquisition module 13 acquires real-time user-side data generated by the user terminal, the first acquisition module 13 is used to perform the following: acquire a preset log format corresponding to the user terminal; and collect the data generated by the user terminal in real time based on the preset log format to obtain real-time user-side data.

[0257] In some instances, when the first acquisition module 13 acquires the preset log format corresponding to the user terminal, the first acquisition module 13 is used to perform: acquire the scenario information corresponding to the user terminal; and determine the preset log format corresponding to the user terminal based on the scenario information.

[0258] Figure 18 The device shown can perform Figures 1-7 For the methods shown in the embodiments, the parts not described in detail in this embodiment can be referred to the following: Figures 1-7 The relevant descriptions of the illustrated embodiments are provided below. For the execution process and technical effects of this technical solution, please refer to [link / reference]. Figures 1-7 The descriptions in the illustrated embodiments will not be repeated here.

[0259] In one possible design, Figure 18 The fault location device shown can be implemented as an electronic device, which can be various devices such as terminals and servers used by researchers. Figure 19 As shown, the electronic device may include a first processor 21 and a first memory 22. The first memory 22 is used to store data executed by the corresponding electronic device. Figures 1-7 In the fault location method program provided in the illustrated embodiment, the first processor 21 is configured to execute the program stored in the first memory 22.

[0260] The program comprises one or more computer instructions, wherein the one or more computer instructions are executed by the first processor 21 to implement the following steps: receiving a data reporting request sent by the user end; determining a data positioning identifier corresponding to the data reporting request; obtaining user data corresponding to the data positioning identifier generated by the user end, the user data comprising: user side account information, user side configuration information, user side running environment, application program interface API calling log, and user operation log; and performing a fault positioning operation based on the user data.

[0261] Further, the first processor 21 is further configured to execute all or part of the steps of the above-mentioned Figures 1-7 embodiments.

[0262] The electronic device further comprises a first communication interface 23, configured to communicate with other devices or communication networks.

[0263] In addition, the embodiment of the present application provides a computer storage medium for storing computer software instructions for the electronic device, which comprises a program for executing the above-mentioned Figures 1-7 method embodiments.

[0264] In addition, the embodiment of the present application provides a computer program product, comprising: a computer readable storage medium storing computer instructions, when the computer instructions are executed by one or more processors, causing the one or more processors to execute the steps of the above-mentioned Figures 1-7 method embodiments.

[0265] Figure 20 Another structure diagram of the fault positioning device provided by the embodiment of the present application is shown in the accompanying drawings. Figure 20 The embodiment provides another fault positioning device, which is configured to execute the above-mentioned Figure 8 fault positioning method, and specifically, the fault positioning device can comprise:

[0266] The second acquisition module 31 is configured to acquire a data reporting request, and the data reporting request is configured to perform a fault positioning operation.

[0267] The second determination module 32 is configured to determine a preset log format corresponding to the data reporting request.

[0268] The second generation module 33 is configured to generate reporting data based on the preset log format, and the reporting data comprises user side account information, user side configuration information, user side running environment, application program interface API calling log, and user operation log.

[0269] The second processing module 34 is used to report the reported data so as to perform fault location operations based on the reported data.

[0270] In some instances, after determining the preset log format corresponding to the data reporting request, the second generation module 33 and the second processing module 34 in this embodiment are used to perform the following steps:

[0271] The second generation module 33 is used to generate log collection prompts corresponding to the preset log format;

[0272] The second processing module 34 is used to allow the generation of reporting data based on a preset log format when a confirmation execution information corresponding to the log collection prompt is obtained; and to prohibit the generation of reporting data based on a preset log format when a cancellation execution information corresponding to the log collection prompt is obtained.

[0273] In some instances, the second generation module 33 and the second processing module 34 in this embodiment are used to perform the following steps:

[0274] The second generation module 33 is used to obtain screenshot information and / or video recording information corresponding to user operation behavior during the process of generating and reporting data;

[0275] The second processing module 34 is used to add screenshot information and / or video recording information to the reported data.

[0276] Figure 20 The device shown can perform Figures 8-10 , Figures 14-16 For the methods shown in the embodiments, the parts not described in detail in this embodiment can be referred to the following: Figures 8-10 , Figures 14-16 The relevant descriptions of the illustrated embodiments are provided below. For the execution process and technical effects of this technical solution, please refer to [link / reference]. Figures 8-10 , Figures 14-16 The descriptions in the illustrated embodiments will not be repeated here.

[0277] In one possible design, Figure 20 The fault location device shown can be implemented as an electronic device, which can be various devices such as a user terminal, personal computer, or smart terminal. Figure 21 As shown, the electronic device may include a second processor 41 and a second memory 42. The second memory 42 is used to store data executed by the corresponding electronic device. Figures 8-10 , Figures 14-16 In the fault location method program provided in the illustrated embodiment, the second processor 41 is configured to execute the program stored in the second memory 42.

[0278] The program comprises one or more computer instructions, wherein the one or more computer instructions are executed by the second processor 41 to implement the following steps: obtaining a data reporting request, the data reporting request being used for a fault positioning operation; determining a preset log format corresponding to the data reporting request; generating reported data based on the preset log format, the reported data comprising user-side account information, user-side configuration information, a user-side running environment, application program interface (API) call logs, and user operation logs; and reporting the reported data to perform the fault positioning operation based on the reported data.

[0279] Further, the second processor 41 is further configured to execute all or part of the steps in the embodiments shown in the foregoing Figure 11 .

[0280] The electronic device can further comprise a second communication interface 43 for communication between the electronic device and other devices or communication networks.

[0281] In addition, the embodiment of the present application provides a computer storage medium for storing computer software instructions for the electronic device, which comprises a program for implementing the fault positioning method in the foregoing Figures 8-10 , Figures 14-16 embodiment of the method shown in the foregoing.

[0282] In addition, the embodiment of the present application provides a computer program product, comprising: a computer readable storage medium storing computer instructions, when the computer instructions are executed by one or more processors, causing the one or more processors to execute the steps in the fault positioning method in the foregoing Figures 8-10 , Figures 14-16 embodiment of the method shown in the foregoing.

[0283] Figure 22 Another structural diagram of a fault positioning device provided by the embodiment of the present application; referring to the embodiment shown in the foregoing Figure 22 , the embodiment provides another fault positioning device, which is used for executing the fault positioning method shown in the foregoing Figure 11 , specifically, the fault positioning device can comprise:

[0284] The third obtaining module 51 is configured to obtain reported data used for a fault positioning operation, the reported data comprising user-side account information, user-side configuration information, a user-side running environment, application program interface (API) call logs, and user operation logs;

[0285] The third determining module 52 is configured to determine whether the log checking operation on the reported data can locate fault information.

[0286] The third processing module 53 is configured to, if the fault information cannot be located, perform scene restoration based on the reported data to perform the fault positioning operation.

[0287] In some examples, the third processing module 53 in this embodiment is configured to perform the following: if the fault information can be located, obtaining the fault information corresponding to the reported data.

[0288] In some examples, when the third processing module 53 restores the scene based on the reported data, the third processing module 53 is configured to perform the following: establishing a simulated running environment that is the same as the running environment on the user side; in the simulated running environment, generating interface information corresponding to the reported data based on the user side account information and the user side configuration information; and in the interface information, restoring the scene based on the API call log and the user operation log.

[0289] In some examples, the third obtaining module 51 and the third processing module 53 in this embodiment are configured to perform the following steps:

[0290] The third obtaining module 51 is configured to obtain scene information that can be run by the user terminal and log configuration information corresponding to the scene information.

[0291] The third processing module 53 is configured to establish a preset log format corresponding to the scene information based on the log configuration information, and the preset log format is at least used to obtain the reported data.

[0292] In some examples, before obtaining the reported data used for the fault locating operation, the third processing module 53 in this embodiment is configured to perform the following: in response to a data reporting request sent by the user terminal, determining a preset log format corresponding to the data reporting request; and sending the preset log format to the user terminal to obtain the reported data corresponding to the user terminal based on the preset log format.

[0293] Figure 22 The apparatus shown can perform Figures 11-16 The method of the embodiment shown, the parts not described in detail in this embodiment can refer to the related description of Figures 11-16 The embodiment shown. The execution process and technical effects of this technical solution are described in the embodiment shown, which will not be described here. Figures 11-16

[0294] In one possible design, Figure 22 The structure of the fault locating apparatus shown can be implemented as an electronic device, which can be various devices such as a terminal device and a server corresponding to a developer. As Figure 23 The electronic device can include a third processor 61 and a third memory 62. The third memory 62 is configured to store programs for the electronic device to perform the above Figures 11-16 The third processor 61 is configured to execute the programs stored in the third memory 62. ​

[0295] The program comprises one or more computer instructions, wherein the one or more computer instructions are executed by the third processor 61 to implement the following steps: obtaining reported data for performing a fault locating operation, the reported data comprising user side account information, user side configuration information, user side running environment, application program interface API calling log, and user operation log; determining whether the reported data can be used to locate fault information through log checking; and if not, performing scene restoration based on the reported data to perform the fault locating operation.

[0296] Further, the third processor 61 is further configured to execute all or part of the steps of the method shown in the above Figures 11-16

[0297] The electronic device can further comprise a third communication interface 63 for communication between the electronic device and other devices or communication networks.

[0298] In addition, the embodiment of the present application provides a computer storage medium for storing computer software instructions for the electronic device, which comprises a program for implementing the fault locating method in the above Figures 11-16

[0299] In addition, the embodiment of the present application provides a computer program product, comprising: a computer readable storage medium storing computer instructions, when the computer instructions are executed by one or more processors, causing the one or more processors to execute the steps of the fault locating method in the above Figures 11-16

[0300] Figure 24 FIG. 1 is a structural schematic diagram of a log format configuration device according to an embodiment of the present application; and Figure 24 The embodiment of the present application provides a log format configuration device, which is used to execute the log format configuration method shown in the above Figure 17 The log format configuration device can comprise:

[0301] The fourth obtaining module 71 is configured to obtain scene information capable of being run by a user terminal and log configuration information corresponding to the scene information;

[0302] The fourth processing module 72 is configured to generate a preset log format corresponding to the scene information based on the log configuration information, wherein the preset log format is used to obtain at least part of log data of the user terminal.

[0303] In some examples, the fourth obtaining module 71 and the fourth processing module 72 in the embodiment are further configured to execute the following steps:

[0304] ​​​The fourth acquisition module 71 is used to acquire data reporting requests sent by the user terminal.

[0305] The fourth processing module 72 is used to determine the preset log format corresponding to the data reporting request; and send the preset log format to the user terminal to obtain the reporting data corresponding to the user terminal based on the preset log format.

[0306] Figure 24 The device shown can perform Figure 17 For the methods shown in the embodiments, the parts not described in detail in this embodiment can be referred to the following: Figure 17 The relevant descriptions of the illustrated embodiments are provided below. For the execution process and technical effects of this technical solution, please refer to [link / reference]. Figure 17 The descriptions in the illustrated embodiments will not be repeated here.

[0307] In one possible design, Figure 24 The configuration device for the log format shown can be implemented as an electronic device, which can be various devices such as terminal devices and servers used by researchers. Figure 25 As shown, the electronic device may include a fourth processor 81 and a fourth memory 82. The fourth memory 82 is used to store data executed by the corresponding electronic device. Figure 17 In the illustrated embodiment, the program for configuring the log format is provided, and the fourth processor 81 is configured to execute the program stored in the fourth memory 82.

[0308] The program includes one or more computer instructions, wherein when the one or more computer instructions are executed by the fourth processor 81, they can perform the following steps: obtain scene information that the user terminal can run and log configuration information corresponding to the scene information; based on the log configuration information, generate a preset log format corresponding to the scene information, wherein the preset log format is used to obtain at least a portion of the log data of the user terminal.

[0309] Furthermore, the fourth processor 81 is also used to perform the aforementioned... Figure 17 All or part of the steps in the illustrated embodiments.

[0310] The structure of the electronic device may also include a fourth communication interface 83 for communication between the electronic device and other devices or communication networks.

[0311] In addition, embodiments of the present invention provide a computer storage medium for storing computer software instructions used by an electronic device, which includes instructions for executing the above-described... Figure 17 The program involved in the log format configuration method in the illustrated embodiment.

[0312] In addition, the embodiment of the present application provides a computer program product, comprising: a computer readable storage medium storing computer instructions, when the computer instructions are executed by one or more processors, causing the one or more processors to execute the above method. Figure 1 The step in the configuration method of the log format in the method embodiment is shown.

[0313] The device embodiments described above are only schematic, wherein the units shown as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, i.e., can be located in one place, or can be distributed on a plurality of network units. Part or all of the modules can be selected according to actual needs to achieve the purpose of the embodiment. Those skilled in the art can understand and implement without creative labor.

[0314] Through the description of the above embodiments, those skilled in the art can clearly understand that each embodiment can be realized by means of a general hardware platform as necessary, and of course can also be realized by means of combination of hardware and software. Based on such understanding, the above technical solutions can be embodied in the form of a computer product, and the present application can be in the form of a computer program product implemented on one or more computer usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer usable program codes.

[0315] The present application is described with reference to flowcharts and / or block diagrams of the method, device (system), and computer program product according to the embodiments of the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and the combination of the flows and / or blocks in the flowcharts and / or block diagrams can be realized by computer program instructions. These computer program instructions can be provided to a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable devices to produce a machine, so that the instructions executed by the computer or other programmable devices produce a device implemented in the flowcharts and / or block diagrams. Figure 1 one or more flows and / or blocks Figure 1 an apparatus that implements the functions specified in the flow(s) or block(s).

[0316] These computer program instructions can also be stored in a computer readable storage medium capable of guiding the computer or other programmable devices to work in a specific manner, so that the instructions stored in the computer readable storage medium produce a product including instruction apparatus, which implements the flowcharts and / or block diagrams. Figure 1 one or more flows and / or blocks Figure 1 an apparatus that implements the functions specified in the flow(s) or block(s).

[0317] These computer program instructions can also be loaded onto a computer or other programmable device to cause a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process such that the instructions which execute on the computer or other programmable device provide steps for implementing the functions specified in the flowchart block or blocks. Figure 1 ​ The computer program instructions can also be loaded onto a computer or other programmable device to cause a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process such that the instructions which execute on the computer or other programmable device provide steps for implementing the functions specified in the flowchart block or blocks.

[0318] In one typical configuration, the computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory. The memory can include non-persistent memory and / or volatile memory, e.g., random access memory (RAM), for storing

[0319] Computer-readable media includes permanent and non-permanent, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD), or other optical storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information accessible to computing devices. According to the definition herein, computer-readable media does not include transitory media such as modulated data signals and carrier waves.

[0320] Finally, it should be noted that the above embodiments are merely used to illustrate the technical solutions of the present application, rather than limiting them; although the above-mentioned embodiments are described in detail, those skilled in the art should understand that the technical solutions recorded in the above-mentioned embodiments can be modified, or some technical features can be replaced by equivalent replacements; and these modifications or replacements do not make the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application.​

Claims

1. A fault location method characterized by, The method comprises: receiving a data reporting request sent by a user terminal; determining a data positioning identifier corresponding to the data reporting request; obtaining user data generated by the user terminal and corresponding to the data positioning identifier, the user data comprising: user-side account information, user-side configuration information, a user-side running environment, application program interface (API) call logs, and user operation logs; performing a fault positioning operation based on the user data; The method further comprises: obtaining scene information corresponding to the user terminal; based on the scene information, determining a preset log format corresponding to the user terminal; based on the preset log format, collecting data generated by the user terminal in real time to obtain user-side real-time data, the user-side real-time data being used to obtain user data corresponding to a data identifier time period, the data identifier time period being determined based on the data positioning identifier.

2. The method of claim 1, wherein, Performing a fault positioning operation based on the user data comprises: determining whether the user data can be used to locate fault information through log checking; if the user data can be used to locate fault information, obtaining fault information corresponding to the user data; if the user data cannot be used to locate fault information, performing scene restoration based on the user data to perform a fault positioning operation.

3. The method of claim 2, wherein, Performing scene restoration based on the user data comprises: establishing a simulated running environment identical to the user-side running environment; in the simulated running environment, generating interface information corresponding to the user data based on the user-side account information and the user-side configuration information; in the interface information, performing scene restoration based on the API call logs and the user operation logs.

4. The method according to any one of claims 1 to 3, characterized in that, Obtaining user data generated by the user terminal and corresponding to the data positioning identifier comprises: obtaining user-side real-time data generated by the user terminal; based on the data positioning identifier, determining a data identifier time period corresponding to the data reporting request; in the user-side real-time data, obtaining user data corresponding to the data identifier time period.

5. A fault locating method characterized by, The method comprises: obtaining a data reporting request, the data reporting request being used to perform a fault positioning operation; determining a preset log format corresponding to the data reporting request; based on the preset log format, generating reporting data, the reporting data comprising user-side account information, user-side configuration information, a user-side running environment, application program interface (API) call logs, and user operation logs; reporting the reporting data to perform a fault positioning operation based on the reporting data; wherein determining a preset log format corresponding to the data reporting request comprises: obtaining scene information corresponding to the data reporting request; based on the scene information, determining a preset log format corresponding to the data reporting request.

6. The method of claim 5, wherein, After determining the preset log format corresponding to the data reporting request, the method further comprises: generating a log collection prompt corresponding to the preset log format; when obtaining confirmation execution information corresponding to the log collection prompt, allowing the reporting data to be generated based on the preset log format; When the cancel execution information corresponding to the log collection prompt is acquired, the generation of the report data based on the preset log format is prohibited.

7. The method of claim 5, wherein, The method further includes: During the generation of the report data, the screenshot information and / or the video information corresponding to the user operation behavior are acquired; The screenshot information and / or the video information are added to the report data.

8. A fault locating method characterized by, The method includes: Acquiring report data for performing a fault positioning operation, the report data including user-side account information, user-side configuration information, a user-side running environment, application program interface (API) call logs, and user operation logs; Determining whether the log checking operation on the report data can locate fault information; If the fault information cannot be located, performing scene restoration based on the report data to perform the fault positioning operation; Before the acquisition of the report data for performing the fault positioning operation, the method further includes: In response to a data report request sent by a user terminal, determining a preset log format corresponding to the data report request; Sending the preset log format to the user terminal to obtain report data corresponding to the user terminal based on the preset log format.

9. The method of claim 8, wherein, The method further includes: If the fault information can be located, obtaining fault information corresponding to the report data.

10. The method of claim 9, wherein, Performing scene restoration based on the report data includes: Establishing a simulated running environment identical to the user-side running environment; In the simulated running environment, generating interface information corresponding to the report data based on the user-side account information and the user-side configuration information; In the interface information, performing scene restoration based on the API call logs and the user operation logs.

11. The method according to any one of claims 8-10, characterized in that, The method further includes: Acquiring scene information that can be run by the user terminal and log configuration information corresponding to the scene information; Based on the log configuration information, establishing a preset log format corresponding to the scene information, the preset log format being used at least for acquiring the report data.

12. An electronic device, comprising: The method includes: A memory and a processor; the memory is configured to store one or more computer instructions; when the one or more computer instructions are executed by the processor, the fault positioning method in any one of claims 1-4 is implemented.

Images