Method and system for collecting client problem logs

Abstract

The invention relates to a client feedback data collection technology, in particular to a client problem log collection method and system, and the method comprises the steps: a user clicks a customer service entrance on a client, and the client requests a server to generate a log report path; the server generates a log reporting path and returns the log reporting path to the client; the client carries a log reporting path to open a problem feedback page, a user clicks submission feedback after inputting feedback content, the client searches a latest file name under a log directory of the local client, and requests a problem feedback interface of the server after splicing the latest file name into a final log reporting address; the server stores the user identifier, the submitted content and the final log reporting address, and returns a confirmation that the operation is successful to the client; after receiving successful confirmation, the client starts a thread, and asynchronously uploads the log file in the latest time period in the local log directory to a final log reporting address; according to the invention, the local log file of the client can be obtained, so that the progress of troubleshooting work is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of client feedback data collection, and in particular to a method and system for collecting client problem logs. Background Art

[0002] Due to some unknown anomalies, the game client may cause the user to be interrupted during the game or unable to experience the game normally. After the user reports the problem through customer service, the game company usually asks the user to provide the specific log files in the game installation directory in order to troubleshoot the problem more quickly. However, the user may not be contacted due to leaving the wrong contact information, or may not know how to obtain the log files, or may even be unwilling to cooperate. These situations will make it difficult for the game company to obtain the local log files of the client, making the troubleshooting work difficult. Summary of the invention

[0003] In order to overcome the problem that it is difficult for game companies to obtain log files from the user's client after an unknown anomaly occurs in the game, the purpose of the present invention is to provide a method and system for collecting client problem logs, which can meet the needs of obtaining local log files on the client, thereby improving the progress of troubleshooting work.

[0004] The present invention is implemented by the following scheme:

[0005] A method for collecting client problem logs, the method steps are as follows:

[0006] Step 1: The user clicks the customer service portal on the client, and the client requests the server to generate a log reporting path; the server generates the log reporting path and returns it to the client;

[0007] Step 2: The client opens the problem feedback page with the log reporting path. After the user enters the feedback content, clicks Submit Feedback. The client searches for the latest file name in the local client log directory, concatenates it into the final log reporting address, and then requests the server problem feedback interface. The server saves the user ID, submitted content, and final log reporting address, and returns a confirmation of successful operation to the client.

[0008] Step 3: After receiving the successful confirmation, the client will start a thread to asynchronously upload the log files of the latest period in the local log directory to the final log reporting address.

[0009] Furthermore, the log reporting path includes current time, user identification and random characters.

[0010] Furthermore, in step 2, if the request to the server fails, the client will re-report and retry within n times to implement a retry mechanism.

[0011] A system for collecting client problem logs, the system comprising: a feedback module, a content splicing module and a content collection module;

[0012] The feedback module is used for the user to click on the customer service entrance on the client, and the client requests the server to generate a log reporting path; the server generates the log reporting path and returns it to the client;

[0013] The content splicing module is used for the client to carry the log reporting path to open the problem feedback page. After the user enters the feedback content, clicks to submit the feedback. The client searches for the latest file name in the local client log directory, splices it into the final log reporting address, and then requests the server-side problem feedback interface. The server saves the user identifier, submitted content and final log reporting address, and returns a confirmation of successful operation to the client.

[0014] The content collection module is used to start a thread after the client receives a successful confirmation, and asynchronously upload the log files of the latest period in the local log directory to the final log reporting address.

[0015] Furthermore, the log reporting path includes current time, user identification and random characters.

[0016] Furthermore, in the content splicing module, if the request to the server fails, the client will re-report and retry within n times to implement a retry mechanism.

[0017] The beneficial effects of the present invention are:

[0018] The present invention provides a method and system for collecting client problem logs, which can save the tedious process of frequently communicating with users to request client local log files and realize the automation of the feedback process. By pre-generating a log reporting path and adopting a delayed asynchronous reporting log method, the waiting time caused by uploading logs when users submit feedback is avoided. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 is a flow chart of the method of the present invention;

[0020] Figure 2 It is a structural block diagram of the system of the present invention. DETAILED DESCRIPTION

[0021] The present invention will be further described below in conjunction with the accompanying drawings.

[0022] See also Figure 1 , a method for collecting client problem logs, the method steps are as follows:

[0023] Step 1: The user clicks the customer service portal on the client, and the client requests the server to generate a log reporting path; the server generates the log reporting path and returns it to the client;

[0024] Step 2: The client opens the problem feedback page with the log reporting path. After the user enters the feedback content, clicks Submit Feedback. The client searches for the latest file name in the local client log directory, concatenates it into the final log reporting address, and then requests the server problem feedback interface. The server saves the user ID, submitted content, and final log reporting address, and returns a confirmation of successful operation to the client.

[0025] Step 3: After receiving the successful confirmation, the client will start a thread to asynchronously upload the log files of the latest period in the local log directory to the final log reporting address.

[0026] The present invention will be further described below in conjunction with a specific embodiment:

[0027] A method for collecting client problem logs, the method comprising the following steps:

[0028] Step 1: The user clicks on the customer service portal, and the client requests the server to generate a log reporting path. The server generates a log reporting path based on the current time, user ID, and random characters, and returns it to the client.

[0029] Users often encounter flashback problems when using the client and hope to give feedback to the game company. To this end, the user clicks on the customer service entrance, and the client carries the authorization token to request the server to generate a log reporting path. The request URL format is: `https: / / server.xxx.com / log / createPath? token={token}`. After receiving the request, the server will read the current server time and convert it to the `yyyy / MM / dd / HH` format, for example: `2024 / 10 / 13 / 21`, recorded as `s1`; then use the token to obtain the user ID, recorded as `s2`, for example: `889880`; then generate a random string, recorded as `s3`, for example: `sUmw`. Finally, the above three parts are concatenated in the format of ` / {s1} / {s2} / {s3}` to obtain the path ` / 2024 / 10 / 13 / 21 / 889880 / sUmw`, and return it to the client.

[0030] Step 2: The client opens the problem feedback page with the log reporting path. After the user enters the feedback content, click Submit Feedback. The client searches for the latest file name in the local client log directory, splices it into the final log reporting address, and then requests the server problem feedback interface. The server saves the user ID, submitted content, and final log reporting address, and returns a confirmation of successful operation to the client.

[0031] After receiving the log reporting path `path` returned by the server, the client will open the problem feedback page with the `path`. The user enters the feedback content and clicks the Submit Feedback button. At this time, the client will search for the latest file name under the local log directory (for example: `C:\AppData\GameLog\`), such as `2024101321_error.log`. Then, the client concatenates the file name into the final log reporting address `logFile= / 2024 / 10 / 13 / 21 / 889880 / sUmw_2024101321_error.log`. Subsequently, the client carries the final log reporting address `logFile`, user feedback content and `token`, and initiates a request to the problem feedback interface `https: / / server.xxx.com / log / submit? token={token}&text={text}&logFile={logFile}`. After receiving the request, the server will use `token` to exchange for the user ID `uid=889880`, organize the user feedback content `text` and the final log reporting address `logFile` into a new feedback data, save it to the database, and feedback the successful processing information to the client.

[0032] Among them, if the request to the server fails, the client will re-report and retry within n times (the size of n is a custom setting) to implement a retry mechanism to cope with network fluctuations or other unexpected situations, ensuring that user feedback information and related log data can be smoothly transmitted to the server, providing an important basis for subsequent problem investigation and resolution.

[0033] Step 3: After receiving the successful confirmation, the client will start a thread to asynchronously upload the log files of the latest period in the local log directory to the final log reporting address.

[0034] After receiving the message from the server about the successful submission of user feedback content, the client will immediately start an independent thread to ensure that the background upload operation will not affect the user experience. In this thread, the client compresses the log file `2024101321_error.log`, and then the client will prepare to upload the log file to the specified final log reporting address in the format of `logFile= / 2024 / 10 / 13 / 21 / 889880 / sUmw_2024101321_error.log`. At the same time, in order to improve the reliability of the upload, the client may implement a retry mechanism to cope with network fluctuations or other unexpected situations. Ensure that user feedback information and related log data can be smoothly transmitted to the server, providing an important basis for the investigation and resolution of subsequent problems.

[0035] See also Figure 2 ,A system for collecting client problem logs, characterized in that the system includes: a feedback module, a content splicing module and a content collection module;

[0036] The feedback module is used for the user to click on the customer service entrance on the client, and the client requests the server to generate a log reporting path; the server generates the log reporting path and returns it to the client;

[0037] The content splicing module is used for the client to carry the log reporting path to open the problem feedback page. After the user enters the feedback content, clicks to submit the feedback. The client searches for the latest file name in the local client log directory, splices it into the final log reporting address, and then requests the server-side problem feedback interface. The server saves the user identifier, submitted content and final log reporting address, and returns a confirmation of successful operation to the client.

[0038] The content collection module is used to start a thread after the client receives a successful confirmation, and asynchronously upload the log files of the latest period in the local log directory to the final log reporting address.

[0039] In one embodiment of the present invention, the log reporting path includes current time, user identification and random characters.

[0040] In one embodiment of the present invention, in the content splicing module, if the request to the server fails, the client will re-report and retry within n times to implement a retry mechanism.

[0041] The above description is only a preferred embodiment of the present invention. All equivalent changes and modifications made according to the scope of the patent application of the present invention should fall within the scope of the present invention.

Claims

1. A method for collecting client problem logs, characterized in that: The method steps are as follows: Step 1: The user clicks the customer service portal on the client, and the client requests the server to generate a log reporting path; the server generates the log reporting path and returns it to the client; Step 2: The client opens the problem feedback page with the log reporting path. After the user enters the feedback content, clicks Submit Feedback. The client searches for the latest file name in the local client log directory, concatenates it into the final log reporting address, and then requests the server problem feedback interface. The server saves the user ID, submitted content, and final log reporting address, and returns a confirmation of successful operation to the client. Step 3: After receiving the successful confirmation, the client will start a thread to asynchronously upload the log files of the latest period in the local log directory to the final log reporting address.

2. A method for collecting client problem logs according to claim 1, characterized in that: The log reporting path includes the current time, user identification and random characters.

3. A method for collecting client problem logs according to claim 1, characterized in that: In step 2, if the request to the server fails, the client will re-report and retry within n times to implement the retry mechanism.

4. A system for collecting client problem logs, characterized in that: The system includes: a feedback module, a content splicing module and a content collection module; The feedback module is used for the user to click on the customer service entrance on the client, and the client requests the server to generate a log reporting path; the server generates the log reporting path and returns it to the client; The content splicing module is used for the client to carry the log reporting path to open the problem feedback page. After the user enters the feedback content, clicks to submit the feedback. The client searches for the latest file name in the local client log directory, splices it into the final log reporting address, and then requests the server-side problem feedback interface. The server saves the user identifier, submitted content and final log reporting address, and returns a confirmation of successful operation to the client. The content collection module is used to start a thread after the client receives a successful confirmation, and asynchronously upload the log files of the latest period in the local log directory to the final log reporting address.

5. A client problem log collection system according to claim 3, characterized in that: The log reporting path includes the current time, user identification and random characters.

6. A client problem log collection system according to claim 3, characterized in that: In the content splicing module, if the request to the server fails, the client will re-report and retry within n times to implement a retry mechanism.

Images