Data processing methods, electronic devices and storage media

Abstract

This invention discloses a data processing method, electronic device, and storage medium, applicable to the fields of Internet and distributed service technologies. The method includes: receiving complaint information sent by a terminal device, the complaint information including a user identifier and a reason for the complaint regarding a specific service; querying a pre-built operation log database based on the complaint information to retrieve candidate operation logs related to the user identifier and the specific service; wherein the operation log database stores operation logs of a distributed proxy server during the receipt and forwarding of access requests; determining whether the complaint reason is valid based on the candidate operation logs to obtain a verification result; and generating a corresponding complaint processing result based on the verification result and sending the complaint processing result to the terminal device. This method enables real-time processing of complaint information, improving the service response efficiency of a distributed service architecture.

Description

Technical Field

[0001] This disclosure relates to the fields of Internet and distributed service technology, and in particular to a data processing method, electronic device and storage medium. Background Technology

[0002] With the widespread adoption of internet technology and the massive growth of user data, traditional service architectures can no longer meet the high-concurrency requests initiated by a large number of users, leading to the emergence of distributed service architectures. Distributed service architectures typically include multiple service nodes or service clusters. Multiple service nodes within the same service cluster or from different service clusters collaboratively support the task processing of application software (such as processing business data and operational data).

[0003] However, when receiving user complaints about services with high time sensitivity (i.e., high real-time requirements), such as complaints about paid services (e.g., account top-ups not being credited), the synchronization of log data across service nodes is often delayed, making it impossible to process and respond to complaints promptly. Furthermore, it's impossible to filter complaints based on criteria, causing complaining users to wait a long time for a reply. If a human customer service representative were to poll the log data across various servers, the process would be cumbersome, prone to omissions, and inefficient in a distributed service architecture where data for the same task is scattered across service nodes. Summary of the Invention

[0004] To solve the above-mentioned technical problems, or at least partially solve them, embodiments of this disclosure provide a data processing method, an electronic device, and a storage medium.

[0005] In a first aspect, embodiments of this disclosure provide a data processing method. The method includes: receiving complaint information sent by a terminal device, the complaint information including a user identifier and a reason for the complaint regarding a specific service item; querying a pre-built operation log database for candidate operation logs related to the user identifier and the specific service item based on the complaint information; wherein the operation log database stores operation logs from multiple distributed proxy servers during the receipt and forwarding of access requests; determining whether the reason for the complaint is valid based on the candidate operation logs, obtaining a verification result; generating a corresponding complaint processing result based on the verification result, and sending the complaint processing result to the terminal device.

[0006] Secondly, embodiments of this disclosure provide an electronic device. The electronic device includes a processor, a communication interface, a memory, and a communication bus, wherein the processor, communication interface, and memory communicate with each other via the communication bus. The memory stores at least one executable instruction, which causes the processor to perform the following steps: receiving complaint information sent by a terminal device, the complaint information including a user identifier and a reason for the complaint regarding a specific service; querying a pre-built operation log database based on the complaint information to retrieve candidate operation logs related to the user identifier and the specific service; wherein the operation log database stores operation logs of multiple distributed proxy servers during the receipt and forwarding of access requests; determining whether the complaint reason is valid based on the candidate operation logs to obtain a verification result; and generating a corresponding complaint processing result based on the verification result and sending the complaint processing result to the terminal device.

[0007] According to embodiments of this disclosure, in the above-described method or electronic device, the complaint reason includes: nominal access object information, nominal operation information under a specific service item, and nominal processing result; the candidate operation log includes: forwarded access request information. Specifically, determining whether the complaint reason is valid based on the candidate operation log includes: determining, based on the access request information, whether there exists a target operation log in the candidate operation log that matches the nominal access object and the nominal operation; when it is determined that the target operation log does not exist in the candidate operation log, the complaint reason is determined to be invalid.

[0008] According to embodiments of this disclosure, in the above-described method or electronic device, determining whether the above-described complaint reason is valid based on the above-described candidate operation log further includes: when it is determined that the above-described target operation log exists in the above-described candidate operation log, verifying whether there is an error in the access parameter of the target access request information corresponding to the above-described target operation log; when it is verified that there is an error in the access parameter of the target access request information, determining that the above-described complaint reason is valid, and generating a prompt message indicating that there is an error in the access parameter of the specific access parameter.

[0009] According to embodiments of this disclosure, in the above-described method or electronic device, the candidate operation log further includes: service node information to which the access request is distributed. The determination of whether the complaint reason is valid based on the candidate operation log further includes: when verification shows that all access parameters in the target access request information do not have any incorrect event tracking configurations, obtaining the target service log for the target access request from the corresponding target service node based on the target service node information corresponding to the target operation log; determining whether the actual processing result for the target access request is consistent with the nominal processing result based on the target service log; when the actual processing result is consistent with the nominal processing result, determining that the complaint reason is valid; when the actual processing result is inconsistent with the nominal processing result, determining that the complaint reason is invalid.

[0010] According to embodiments of this disclosure, in the above-described method or electronic device, the above-described verification of whether there are any errors in the access parameters in the target access request information corresponding to the target operation log includes: verifying whether the access parameters corresponding to the specific service item in the target access request information are consistent with the predefined parameters in the backend; when the access parameters corresponding to the specific service item are consistent with the predefined parameters, it is determined that there are no errors in the access parameters; when there is a specific access parameter in the access parameters corresponding to the specific service item that is inconsistent with the predefined parameters, it is determined that there is an error in the access parameter configuration for the specific access parameter.

[0011] According to embodiments of this disclosure, the method further includes: constructing an operation log database.

[0012] According to embodiments of this disclosure, in the above-described electronic device, the executable instructions cause the processor to further perform the following step: constructing an operation log database.

[0013] The aforementioned construction of the operation log database includes: defining a target data interface for synchronizing operation logs with multiple distributed proxy servers, wherein the target data interface is used to limit the upload address of the operation logs; and receiving and storing operation log data uploaded from the proxy servers during the process of receiving and forwarding access requests, based on the target data interface.

[0014] According to embodiments of this disclosure, the operation logs corresponding to access requests that are relayed between multiple proxy servers under the same access request carry a redundancy flag.

[0015] In one embodiment, the above-mentioned construction of the operation log database further includes: filtering out redundant operation logs to be uploaded that are related to the above-mentioned redundancy identifier based on the above-mentioned target data interface.

[0016] In another embodiment, the above-mentioned construction of the operation log database further includes: in the already stored operation log data, determining redundant operation logs related to the redundancy identifier based on the redundancy identifier, and deleting the redundant operation logs.

[0017] In another embodiment, the above-mentioned construction of the operation log database further includes: filtering out operation log data to be uploaded that does not meet the preset timeliness requirements based on the target data interface; and / or, filtering out data corresponding to service items to be uploaded that have a timeliness requirement level lower than the preset standard based on the target data interface.

[0018] In another embodiment, the above-mentioned construction of the operation log database further includes: filtering out operation log data whose timeliness does not meet the preset timeliness requirements from the already stored operation log data; and / or filtering out data corresponding to service items whose timeliness requirement level is lower than the preset standard from the already stored operation log data.

[0019] According to embodiments of this disclosure, the access request carries preset tracking parameters, including a software version number and a channel number. The method further includes: obtaining specific operation log data related to the software version number and the channel number from a pre-built operation log database; and determining the traffic information corresponding to the software version number and the channel number based on the specific operation log data.

[0020] According to embodiments of this disclosure, the access request carries preset tracking parameters, including a software version number and a channel number. In the electronic device, the executable instructions cause the processor to further perform the following steps: obtaining specific operation log data related to the software version number and the channel number from a pre-built operation log database; and determining the traffic information corresponding to the software version number and the channel number based on the specific operation log data.

[0021] Thirdly, embodiments of this disclosure provide a computer-readable storage medium. The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the data processing method described above.

[0022] One or more technical solutions in the above embodiments have at least some or all of the following advantages:

[0023] Because the pre-built operation log database stores the operation logs of multiple distributed proxy servers during the reception and forwarding of access requests, when processing complaint information, the complaint information can be verified based on the operation logs in the aforementioned operation log database, thereby obtaining real-time processing results. This enables real-time processing of complaint information and helps improve the service response efficiency of the distributed service architecture. Attached Figure Description

[0024] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0025] To more clearly illustrate the technical solutions in the embodiments of this disclosure or the prior art, the accompanying drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, those skilled in the art can obtain other drawings based on these drawings without creative effort.

[0026] Figure 1 The system architecture of a data processing method applicable to embodiments of this disclosure is illustrated schematically;

[0027] Figure 2 A flowchart illustrating a data processing method according to an embodiment of the present disclosure is shown schematically.

[0028] Figure 3 A detailed implementation flowchart of step S203 according to an embodiment of the present disclosure is illustrated schematically;

[0029] Figure 4 A flowchart illustrating a data processing method according to another embodiment of this disclosure is shown schematically;

[0030] Figure 5 A detailed implementation flowchart of constructing an operation log database according to an embodiment of the present disclosure is illustrated schematically;

[0031] Figure 6 The flowchart illustrating the filtering of data to be uploaded and the deletion of existing data according to embodiments of the present disclosure is shown schematically.

[0032] Figure 7 A timing diagram of a data processing method according to an embodiment of the present disclosure is shown schematically;

[0033] Figure 8 A flowchart illustrating a data processing method according to yet another embodiment of this disclosure is shown schematically; and

[0034] Figure 9A schematic block diagram of an electronic device provided in an embodiment of the present disclosure is shown. Detailed Implementation

[0035] Embodiments of this disclosure provide a data processing method, electronic device, and storage medium. The method includes: receiving complaint information sent by a terminal device, the complaint information including a user identifier and a reason for the complaint regarding a specific service. Based on the complaint information, querying a pre-built operation log database for candidate operation logs related to the user identifier and the specific service. The operation log database stores operation logs from multiple distributed proxy servers during the receipt and forwarding of access requests. Based on the candidate operation logs, determining whether the complaint reason is valid, and obtaining a verification result. Based on the verification result, generating a corresponding complaint processing result and sending the complaint processing result to the terminal device.

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

[0037] Figure 1 The system architecture of a data processing method applicable to embodiments of this disclosure is illustrated schematically.

[0038] Reference Figure 1 As shown, the system architecture 100 of the data processing method applicable to embodiments of this disclosure includes: a terminal device 110, a proxy server cluster 120 comprising multiple distributed proxy servers, and multiple service clusters subordinate to each of the multiple proxy servers. Figure 1 In the example, two proxy servers 121 and 122 in proxy server cluster 120 are used. Accordingly, the service cluster under proxy server 121 is the first service cluster 130, and the service cluster under proxy server 122 is the second service cluster 140.

[0039] The aforementioned terminal device 110 can be any type of electronic device with a display screen and supporting web browsing, such as... Figure 1 Examples include laptops 111, tablets 112, smartphones 113, and desktop computers 114.

[0040] The aforementioned proxy servers 121 and 122 can be Nginx proxy servers (a high-performance HTTP and reverse proxy server) or other types of proxy servers.

[0041] The first service cluster 130 contains multiple service nodes, for example Figure 1 The example service nodes are 131, 132, 133, 134, 135, and 136; the second service cluster 140 contains multiple service nodes, for example... Figure 1 The service nodes 141, 142, 143, 144, 145, and 146 in the example can be physical servers providing services, cloud servers, or networked terminal devices capable of providing cloud computing services. For example, each of these service nodes could be a backend management server (for example only) providing service support to the application interface or webpage browsed by the user using terminal device 110. The backend management server can analyze and process received requests and feed back the processing results (such as webpages, information, or data obtained or generated according to user requests) to terminal device 110.

[0042] The terminal device 110 and each proxy server (e.g., proxy server 121, 122) in the proxy server cluster 120, as well as each proxy server and its subordinate service clusters (e.g., first service cluster 130, second service cluster 140), all interact with each other via the network.

[0043] Reference Figure 1 As shown, a network is represented by a lightning bolt shape. A network is a medium used to provide communication links and can include various connection types, such as wired or wireless communication links or fiber optic cables.

[0044] Various communication client applications can be installed on the terminal device 110, such as: e-book reading software / applications, shopping applications, payment applications, short video applications, web browser applications, search applications, news client applications, instant messaging tools, food delivery applications, social platform software, etc. (for example only).

[0045] In one application scenario, a user generates an access request by operating the application function interface on the terminal device 110. The terminal device 110 forwards the access request to a proxy server in the proxy server cluster 120, such as proxy server 121. After receiving the access request, proxy server 121 analyzes the load of each service node 131 to 136 in its subordinate first service cluster 130 to determine the service node to which the traffic corresponding to the current access request should be distributed, such as service node 131, so as to achieve load balancing.

[0046] The access requests mentioned above can be of various types. For example, in the scenario of a user operating an e-book reading app, the access requests could be account login requests, e-book purchase requests, e-book service (e.g., monthly free reading service) purchase requests, e-book marking operations (e.g., underlining, favorite, forwarding, etc.) requests, etc.

[0047] In a distributed service architecture, each proxy server (e.g.) Figure 1 In the example, proxy servers 121 and 122 forward access requests to their respective subordinate service nodes based on load balancing. Each service node records its own processing procedure and results for the service requests and generates service logs. However, the synchronization of service logs between service nodes often lags. For example, the service logs of each service node (e.g., service nodes 131-136) are generally not synchronized to their respective proxy servers (corresponding to proxy server 121) in real time; they are typically synchronized with the service log data from the previous day.

[0048] In scenarios with high timeliness requirements, such as receiving user complaints about paid services (e.g., unpaid account credits), the synchronization of log data across service nodes often lags, hindering timely processing and feedback of complaints. Furthermore, it prevents the filtering of complaints based on criteria, causing complaining users to wait a long time for a response. If a human customer service representative were to poll the log data across various servers, the process would be cumbersome, prone to omissions, and inefficient in a distributed service architecture where processing data for the same task is scattered across multiple service nodes.

[0049] In view of this, refer to Figure 1 As shown, the system architecture 100 provided in this embodiment further includes a server 150 for processing complaint requests, which has a pre-built operation log database 151. This operation log database 151 stores operation logs from multiple distributed proxy servers (e.g., proxy servers 121 and 122) during the receipt and forwarding of access requests. For example, see... Figure 1 As shown, proxy servers 121 and 122 in the proxy server cluster 120 synchronize their operation logs for receiving and forwarding access requests to the operation log database 151 in real time. Therefore, when the server 150 processes complaint information, it can verify the complaint information based on the operation logs in the operation log database 151, thus obtaining a real-time processing result.

[0050] It should be noted that the data processing method provided in this embodiment can generally be executed by the server 150 in the system framework 100, or by other servers or service clusters that can communicate with the terminal device 110 and have access and creation permissions to the operation log database 151.

[0051] It should be understood that Figure 1 The number of terminal devices, networks, proxy servers, and service nodes shown is merely illustrative. Depending on implementation needs, there can be any number of terminal devices, networks, proxy servers, and service nodes.

[0052] Although the above scenario uses information recommendation in an e-reading context as an example, it is understood that the application scenarios of the technical solutions provided in this disclosure are not limited to e-reading scenarios, but can be extended to any scenario that requires real-time data processing.

[0053] The embodiments of this disclosure will now be described in detail with reference to the accompanying drawings.

[0054] The first exemplary embodiment of this disclosure provides a method for data processing.

[0055] Figure 2 A flowchart illustrating a data processing method according to an embodiment of the present disclosure is shown schematically.

[0056] Reference Figure 2 As shown, the data processing method provided in this embodiment includes the following steps: S201, S202, S203, and S204. Steps S201 to S204 can be performed by... Figure 1 The example server 150 is executed.

[0057] In step S201, a complaint message sent by a terminal device is received. The complaint message includes: user identification and reasons for the complaint regarding a specific service item.

[0058] For example, the specific service items mentioned above include, but are not limited to: business service items, operation and maintenance service items, software development service items, etc. The aforementioned business service items, for example, are recharge services. The reasons for the complaints mentioned above could be: the recharged account has not received the funds, unjustified deductions, or the service received does not match the actual recharge transaction, etc.

[0059] The aforementioned specific services may be services attached to application software installed on the terminal device. For example, if an e-book reading app is installed on the terminal device, the aforementioned specific services may include: recharging the account corresponding to the e-book reading account, purchasing e-books, purchasing e-book services (such as monthly free reading services), etc.

[0060] The following examples use electronic devices and customer service hosts as two instances of terminal devices in step S201. In one implementation scenario, a user initiates a complaint request by operating on a customer service interface on an electronic device with installed application software (e.g., an e-book reading app). Alternatively, in another implementation scenario, a user files a complaint via customer service hotline or online complaint, and the complaint request is received on the corresponding customer service host. Accordingly, the electronic device or customer service host (both corresponding to the terminal devices in step S201) sends the complaint information to the server used to process the complaint request, for example, a... Figure 1 The example server 150 receives the complaint information sent by the terminal device.

[0061] The aforementioned complaint request includes complaint information, which includes: a user identifier and the reason for the complaint regarding a specific service. The user identifier may be, for example, a user ID, user name, or user account.

[0062] In an exemplary embodiment, the complaint information includes: User A (user identifier), the reason for the complaint regarding the recharge item (specific service item), which is: under the recharge item in the account wallet of the e-book reading app, 100 yuan was recharged on the morning of the same day (the date corresponding to the date when the complaint request is received, for example, August 29, 2021), but the money was not credited to the account.

[0063] In step S202, based on the above complaint information, a query is performed in the pre-built operation log database to retrieve candidate operation logs related to the above user identifier and the above specific service item; wherein, the above operation log database is used to store operation logs of multiple distributed proxy servers in the process of receiving and forwarding access requests.

[0064] Reference Figure 1 As shown, after receiving the above complaint information, the server 150 can query the candidate operation logs related to the complaint information in the operation log database. Specifically, by querying the operation log database, the server can determine the candidate operation logs related to user A (user ID) and recharge item (specific service item) in the historical access requests of the user received and forwarded by the proxy server.

[0065] The operation logs in the aforementioned operation log database include: forwarded access request information and service node information to which the access requests are distributed. In one embodiment, the aforementioned access request information includes: URL (Uniform Resource Locator, also known as a web address, is the standard address of a resource on the Internet. Every file on the Internet has a unique URL, which contains information indicating the location of the file and how the browser processes it) information and access parameters with suffixes (used for user information statistics).

[0066] For example, by querying the operation log database, three candidate operation logs are obtained. Parsing these three candidate operation logs yields candidate operation logs 1-3 in the following format: Candidate Operation Log 1: {On March 5, 2021, a recharge request was forwarded. The recharge request was: User A to personal account wallet W.} A A recharge request of 30 yuan was made; the IP address of proxy server 121 is 19×.163.×.×.×; the request was sent to service node 131. Candidate operation log 2: {On June 1, 2021, a recharge request was forwarded, user A to user B's account wallet W.} B A recharge request of 100 yuan was made; the IP address of proxy server 122 is 19×.168.×.×.×; sent to service node 142}. Candidate operation log 3: {August 29, 2021: Forwarded a recharge request. The recharge request is: User A to personal account wallet W} A Recharge 100 yuan; IP address of proxy server 121: 19×.163.×.×.×; Send to service node 135}.

[0067] In step S203, based on the above candidate operation log, it is determined whether the above complaint reason is valid, and the verification result is obtained.

[0068] Reference Figure 1 As shown, the server 150 can determine whether the above-mentioned complaint reason is valid based on the above-mentioned candidate operation logs 1 to 3, and obtain the verification result. In one embodiment, the server determines that the above-mentioned complaint reason is valid based on the above-mentioned candidate operation logs 1 to 3, and obtains the corresponding verification result; or, in another embodiment, the server determines that the above-mentioned complaint reason is invalid based on the above-mentioned candidate operation logs 1 to 3, and obtains the corresponding verification result.

[0069] In step S204, based on the above verification results, a corresponding complaint handling result is generated and sent to the above terminal device.

[0070] If the verification result confirms that the complaint is valid, the corresponding complaint processing result will be, for example: The complaint request has been accepted, and the result will be displayed in User A's e-book reading app account wallet W. A The user has successfully recharged 100 yuan. If the verification result indicates the complaint is unfounded, the corresponding complaint handling result will be, for example: "After verification, the complaint is found to be unfounded, and the user is advised not to file false complaints."

[0071] Based on steps S201-S204 above, since the pre-built operation log database stores the operation logs of multiple distributed proxy servers during the receipt and forwarding of access requests, when processing complaint information, the complaint information can be verified based on the operation logs in the aforementioned operation log database, thereby obtaining real-time processing results. This enables real-time processing of complaint information and helps improve the service response efficiency of the distributed service architecture. In complaint or query scenarios applied to paid projects, it can significantly improve the query efficiency of account logs in the distributed service system architecture, enabling rapid response when users complain about account recharge issues.

[0072] Figure 3 A detailed implementation flowchart of step S203 according to an embodiment of the present disclosure is illustrated schematically.

[0073] According to embodiments of this disclosure, the aforementioned complaint reasons include: nominal access object information, nominal operation information under a specific service item, and nominal processing result. The aforementioned candidate operation log includes: forwarded access request information and service node information to which the access request was distributed. Specifically, for the server, the received user complaint reasons are unverified information; therefore, the access object information claimed by the user in the complaint is described as nominal access object information, the operation information claimed by the user in the complaint is described as nominal operation information, and the processing result claimed by the user in the complaint is described as a nominal processing result.

[0074] For example, nominal access object information might be: an e-book reading app, a specific book on the e-book reading app, or a specific account / wallet on the e-book reading app. Nominal operation information under a specific service might be: under the recharge item, recharged ×× yuan; under the purchase item, purchased a specific book. Nominal processing results might be: recharge not credited, purchase not effective, or the service duration claimed by the e-book reading app not matching the actual service duration received.

[0075] Reference Figure 3 As shown, determining whether the above-mentioned complaint reason is valid based on the above candidate operation log includes the following steps: S301, S302b. Further steps may be included: S302a and S303a; further steps may be included: S303b, S304b, S305a and S305b.

[0076] In step S301, based on the access request information, it is determined whether there is a target operation log in the candidate operation log that matches the nominal access object and the nominal operation.

[0077] In one embodiment, determining whether a target operation log matching the nominal access object and the nominal operation exists in the candidate operation logs based on the access request information includes: parsing the access request information to obtain parsing information, the parsing information including: actual access object information and actual operation information; matching the parsing information with the nominal access object information and the nominal operation information; if there is target parsing information that matches both the nominal access object information and the nominal operation information, determining the candidate operation log corresponding to the target parsing information as the target operation log; if, after traversing the parsing information, there is no parsing information that matches both the nominal access object information and the nominal operation information, determining that the target operation log does not exist in the candidate operation logs.

[0078] In step S302b, when it is determined that the target operation log does not exist in the candidate operation logs, the complaint reason is determined to be invalid.

[0079] If there is no target operation log in the candidate operation log that matches the aforementioned nominal access object and nominal operation, it means that the user behavior in the complaint reason did not occur. That is, the nominal access object and nominal operation did not occur and are not true. This indicates that the user may be lying or the complaint information entered by the user when initiating the complaint request is incorrect. In this case, the complaint reason can be considered invalid.

[0080] In step S302a, when it is determined that the target operation log exists in the candidate operation log, the access parameters in the target access request information corresponding to the target operation log are checked for any errors in the instrumentation configuration.

[0081] Considering that client-side event tracking parameter configuration is done by front-end developers, such as PHP developers, and that front-end developers and back-end (server-side) developers are two separate groups, inconsistencies may arise between the front-end and back-end event tracking parameters. This could cause the application system to fail to execute expected steps. For example, back-end business developers might define "Account" as "account" to trigger a recharge operation, but PHP developers might define the account parameter as "wallet" or "Accout" during event tracking. In this case, a parameter mismatch will prevent the service node from triggering the recharge operation.

[0082] Based on the above, if target operation logs exist, it indicates that the nominal access object and nominal operation mentioned in the complaint reason did indeed occur, and the corresponding user behavior is real. It is necessary to further verify whether there are any errors in the access parameters in the target access request information to determine whether the application software's execution process is normal.

[0083] In step S303a, when the verification shows that there is an error in the configuration of a specific access parameter in the target access request information, the complaint reason is determined to be valid, and a prompt message indicating that there is an error in the configuration of the specific access parameter is generated.

[0084] If a specific access parameter has an incorrect tracking configuration, it indicates an anomaly in the application software's execution process, leading to the aforementioned nominal processing result (e.g., recharge not received). Therefore, in this case, the complaint is considered valid. Simultaneously, a prompt message will be generated on the server side to alert the relevant developers on the front end (e.g., the terminal device) or back end (e.g., the application server) to promptly correct the tracking configuration error.

[0085] In one embodiment, verifying whether there are any errors in the access parameters in the target access request information corresponding to the target operation log includes: verifying whether the access parameters corresponding to the specific service project in the target access request information are consistent with the predefined parameters in the backend; when the access parameters corresponding to the specific service project are consistent with the predefined parameters, it is determined that there are no errors in the access parameters; when there is a specific access parameter in the access parameters corresponding to the specific service project that is inconsistent with the predefined parameters, it is determined that there is an error in the access parameter configuration for the specific access parameter.

[0086] The aforementioned specific service items have predefined parameters in the backend, which are described as predefined parameters. There can be one or more predefined parameters corresponding to the specific service item, and correspondingly, the number of access parameters can also be one or more. For example, if the specific service item is a recharge item, the predefined parameter corresponding to the aforementioned specific service item is "Account". In the actual target access request information, the access parameter corresponding to the recharge item is "wallet". There is a discrepancy between the access parameter "wallet" and the predefined parameter "Account", which indicates a configuration error in the specific access parameter "wallet". The specific reason for the configuration error may be due to the frontend or backend. Therefore, generating a prompt message indicating a configuration error in the aforementioned specific access parameter can prompt frontend or backend developers to correct the configuration error in a timely manner.

[0087] In step S303b, when the verification shows that there are no errors in the instrumentation configuration of any of the access parameters in the target access request information, the target service log for the target access request is obtained from the corresponding target service node based on the target service node information corresponding to the target operation log.

[0088] In specific implementation, refer to Figure 1As shown, server 150 (an example of an execution entity) can determine the IP address information of the target proxy server and the relevant information (such as port information) of the target service node used for forwarding based on the target service node information corresponding to the target operation log; thus, server 150 can directly find a specific service node to pull service logs by communicating with the target proxy server to obtain / query the service logs of the target service node regarding the target access request, without polling among multiple service nodes.

[0089] In step S304b, based on the aforementioned target service log, it is determined whether the actual processing result for the aforementioned target access request is consistent with the aforementioned nominal processing result.

[0090] The server 150 can obtain the actual processing result based on the target service logs mentioned above, and can determine whether the actual processing result is consistent with the nominal processing result by comparison.

[0091] In step S305a, when the actual processing result is consistent with the nominal processing result, the complaint reason is determined to be valid.

[0092] In step S305b, when the actual processing result is inconsistent with the nominal processing result, it is determined that the complaint reason is not valid.

[0093] Based on the above embodiments, a progressive judgment logic is adopted. First, the authenticity of the nominal behavior is determined by whether there is a target operation log in the operation log database corresponding to the nominal behavior in the complaint reason. If the nominal behavior is authentic, the execution process of the application software is further determined to be normal. If the execution process of the application software is normal, the corresponding service log is obtained based on the service node information in the operation log to obtain the actual processing result. Then, the actual processing result is compared with the nominal processing result to determine whether the nominal processing result in the complaint reason is authentic. If both the nominal behavior and the nominal processing result in the complaint reason are authentic, the complaint reason is deemed valid.

[0094] Figure 4 A flowchart illustrating a data processing method according to another embodiment of this disclosure is shown schematically.

[0095] In addition to the steps S201 to S204 described above, the data processing method provided in this embodiment also includes the following step S401: constructing an operation log database. For simplicity, in... Figure 4 Only steps S401 and S202 are shown in the diagram.

[0096] It is understandable that step S401 is executed before steps S201 and S202; that is, the step of building the operation log database is performed in advance before receiving the complaint information corresponding to the complaint request. It should be noted that step S401, which builds the operation log database, only needs to be executed once. Subsequently, the operation log database can be directly called, without needing to build it every time a complaint request is processed. Furthermore, the data in the operation log database is updated in real time based on the data uploaded by the proxy server.

[0097] Figure 5 A detailed implementation flowchart of constructing an operation log database according to an embodiment of this disclosure is illustrated schematically.

[0098] Reference Figure 5 As shown, in step S401 above, the operation log database is constructed, which includes the following steps: S501 and S502.

[0099] In step S501, a target data interface is defined for data synchronization of operation logs with multiple distributed proxy servers. The target data interface is used to limit the upload address of the operation logs.

[0100] In step S502, based on the aforementioned target data interface, data from the operation log uploaded by the proxy server during the process of receiving and forwarding access requests is received and stored.

[0101] Reference Figure 1 As shown, steps S501 and S502 are executed on server 150. In this embodiment, after the uploaded operation logs are stored, they form the data in the operation log database. Correspondingly, on the proxy servers 121 and 122, the following steps are performed: during the reception and forwarding of access requests, based on the forwarded access request information and the forwarded service node information, corresponding operation logs are generated; based on the upload address (corresponding to the target data interface in step S501 above), the operation logs are synchronously stored in the storage space corresponding to the upload address, so as to obtain the operation log database on the server.

[0102] In order to reduce the data capacity burden on the operation log database and ensure high-performance service, the embodiments of this disclosure also filter the data to be uploaded or filter out existing data.

[0103] When filtering existing data or filtering data to be uploaded, the following technical problems were also found: (1) When implementing collaborative processing of the same processing task, there may be traffic forwarding between multiple proxy servers, referring to Figure 1As shown by the dashed lightning bolt symbol (which represents a network), in this scenario, multiple proxy servers forwarding traffic for the same access request will store multiple operation logs in the operation log database. For example, if the traffic forwarding path for user access request Req1 is: terminal device → proxy server 121 → proxy server 122 → service node 143, then proxy server 121 will send forwarding log 1 corresponding to access request Req1 to the operation log database 151 of server 150 for storage; at the same time, proxy server 122 will also send forwarding log 2 corresponding to access request Req1 to the operation log database 151 of server 150 for storage. In fact, forwarding log 1 and forwarding log 2 are for the same traffic path, which leads to data redundancy in the operation log database 151.

[0104] According to embodiments of this disclosure, the operation logs corresponding to access requests that are relayed between multiple proxy servers under the same access request carry a redundancy flag.

[0105] On the proxy servers 121 and 122 side, in one embodiment, based on the forwarded access request information and the forwarded service node information, a corresponding operation log is generated, including: determining, based on the aforementioned access request information, whether the direct source of the received current access request is a terminal device or a proxy server; if the direct source of the current access request is a proxy server, then a redundancy flag is added when generating the operation log corresponding to the current access request. Alternatively, in another embodiment, based on the forwarded access request information and the forwarded service node information, a corresponding operation log is generated, including: determining, based on the aforementioned access request information, whether the direct backend to which the current access request is sent is a proxy server or a service node; if the direct backend to which the current access request is sent is a proxy server, then a redundancy flag is added to the address redirection (URL forwarding, which is the process of redirecting users accessing the current domain name to a specified network address through special server settings) of the current access request.

[0106] Figure 6 The flowchart illustrating the filtering of data to be uploaded and the deletion of existing data according to embodiments of the present disclosure is shown schematically.

[0107] Based on the above, in the embodiments of this disclosure, on the server 150 side, the step S401 of constructing the operation log database includes not only the steps S501 and S502, but also S601 or S602. For the sake of simplicity, Figure 6 Only steps S601 and S602 are shown in the diagram.

[0108] In step S601, at the aforementioned target data interface, the data to be uploaded is filtered out based on the first preset condition.

[0109] The aforementioned first preset condition includes at least one of the following conditions: In the operation logs related to the aforementioned redundancy identifier, redundant operation logs corresponding to the same access request are not allowed to be uploaded; data in operation logs whose data timeliness meets the preset timeliness requirements are allowed to be uploaded, otherwise, they are not allowed to be uploaded; data corresponding to service items whose data timeliness requirements are higher than the preset standard are allowed to be uploaded, otherwise, they are not allowed to be uploaded.

[0110] In step S602, the stored data is deleted based on the second preset condition.

[0111] The aforementioned second preset condition includes at least one of the following conditions: in the operation logs related to the aforementioned redundant identifier, delete the redundant operation logs corresponding to the same access request; delete the data whose timeliness exceeds the preset period; delete the data corresponding to service items whose data timeliness requirement level is less than the preset standard.

[0112] In this embodiment, after implementing upload restrictions or filtering out already stored data, the stored operation log data constitutes the operation log database.

[0113] The implementation process of the above preset conditions is exemplified as follows.

[0114] In one embodiment, the above-mentioned construction of the operation log database, in addition to steps S501 and S502, also includes: filtering out redundant operation logs to be uploaded that are related to the above-mentioned redundancy identifier based on the above-mentioned target data interface.

[0115] In another embodiment, the above-described construction of the operation log database, in addition to steps S501 and S502, also includes: in the already stored operation log data, determining redundant operation logs related to the redundancy identifier based on the redundancy identifier, and deleting the redundant operation logs.

[0116] By employing one of the two embodiments described above to eliminate redundant operation logs, the operation log database is configured so that each access request corresponds to only one operation log, eliminating redundant data, saving capacity, and preventing the generation of multiple records under the same access request, thus ensuring the reliability of data processing.

[0117] In another embodiment, the above-mentioned construction of the operation log database, in addition to steps S501 and S502, also includes: filtering out operation log data to be uploaded that does not meet the preset timeliness requirements based on the above-mentioned target data interface; and / or, filtering out data corresponding to service items to be uploaded that have a timeliness requirement level lower than the preset standard based on the above-mentioned target data interface.

[0118] In another embodiment, the above-mentioned construction of the operation log database, in addition to steps S501 and S502, also includes: filtering out operation log data whose timeliness does not meet the preset timeliness requirements from the already stored operation log data; and / or, filtering out data corresponding to service items whose timeliness requirement level is lower than the preset standard from the already stored operation log data.

[0119] In the two embodiments described above, one of them is used to filter for timeliness, restricting the uploading of data with low timeliness requirements or deleting existing data, saving storage memory in the operation log database, and ensuring that there are sufficient space resources for data processing.

[0120] Since customer complaints are generally time-sensitive, the operation log database can maintain only log information for specific time periods. For example, filtering out operation logs older than one month can effectively ensure that the database doesn't consume too much space. By restricting uploads to only business projects with high processing time (such as account projects), the database's size can be further reduced. Furthermore, by setting restrictions on redundant log uploads or deleting redundant operation logs during regular uploads, the database ensures that only operation logs from single requests are stored. This saves space and prevents multiple records from the same access request being backed up to the database simultaneously across different service clusters (i.e., traffic loops), ensuring data processing reliability.

[0121] Figure 7 A timing diagram of a data processing method according to an embodiment of the present disclosure is shown schematically.

[0122] exist Figure 7 In the context, the server containing the operation log database can be... Figure 1 The example server 150 uses an Nginx proxy server as an example and a client host as an example of a terminal device.

[0123] Reference Figure 7As shown, during the process of receiving and forwarding access requests, the Nginx proxy server generates corresponding operation logs based on the forwarded access request information and the service node information to which the requests are forwarded. Based on the server's upload address (corresponding to the target data interface used to build the operation log database on the server), the operation logs are synchronously stored in the storage space corresponding to that upload address, thus obtaining the operation log database on the server side. (Refer to...) Figure 7 The process is illustrated in step S701. This operation log database is updated in real time based on data uploaded by the Nginx proxy server.

[0124] When the customer service host receives a user's complaint request, it determines the corresponding complaint information based on the request and sends this information to the server, where it receives the complaint information. (Refer to...) Figure 7 As shown in step S711, the above complaint information includes: User A (user identifier) ​​and the reason for the complaint regarding the recharge item (specific service item).

[0125] Upon receiving the aforementioned complaint information, the server queries a pre-built operation log database for candidate operation logs related to the aforementioned user identifier and the aforementioned specific service item. Then, it determines whether the complaint reason is valid based on the aforementioned candidate operation logs.

[0126] In the specific implementation process, refer to Figure 7 As shown in step S712, the server determines whether the target operation log exists in the operation log database in order to determine whether the user access behavior in the complaint reason is real.

[0127] The aforementioned complaint reasons include: nominal access object information, nominal operation information under a specific service item, and nominal processing result. The aforementioned candidate operation logs include: forwarded access request information and service node information to which the access request was distributed. A method to determine whether a target operation log exists in the operation log database can be: first, query the operation log database for candidate operation logs related to the aforementioned user identifier and the aforementioned specific service item; then, based on the access request information, determine whether a target operation log matching the aforementioned nominal access object and the aforementioned nominal operation exists among the aforementioned candidate operation logs.

[0128] Reference Figure 7 As shown, in the absence of the target operation log, step S713b is executed to determine that the complaint reason is invalid, and the corresponding complaint handling result is fed back to the customer service host. For example, the complaint handling result corresponding to an invalid complaint reason is: "After verification, the complaint reason is invalid, and the user is informed not to file a false complaint."

[0129] Reference Figure 7As shown, if a target operation log exists, step S713a is executed to determine if there are any errors in the access parameters' event tracking configuration. The aforementioned access parameters are the event tracking parameters corresponding to the above-mentioned recharge project in the target access request information corresponding to the target operation log.

[0130] Reference Figure 7 As shown, if there is an error in the configuration of the access parameters, step S714a is executed to determine that the complaint reason is valid, and the complaint processing result corresponding to the valid complaint reason is fed back to the customer service host.

[0131] Reference Figure 7 As shown, if there is no error in the configuration of the access parameters, step S714b is executed. Based on the target service node information corresponding to the target operation log, the target service log for the target access request is obtained from the corresponding target service node.

[0132] Next, step S715 is executed to determine whether the actual processing result is consistent with the nominal processing result based on the target service log, thereby determining whether the complaint reason is valid, and generating the corresponding complaint processing result based on whether the complaint reason is valid, and feeding the complaint processing result back to the customer service host.

[0133] Therefore, by verifying the reasons for complaints based on complaint information and operation logs in the operation log database, such as verifying the authenticity of the nominal behavior in the complaint reasons and whether the execution process of the application software is normal, and if the above two verification results are correct, the service log can be directly located to the target service node based on the target operation log to pull the service log without polling among multiple service nodes. This can significantly improve the query efficiency of account logs in the distributed service system architecture and enable a rapid response when users complain about account recharge issues.

[0134] Figure 8 A flowchart illustrating a data processing method according to yet another embodiment of the present disclosure is shown schematically.

[0135] According to embodiments of this disclosure, the access request carries preset tracking parameters, which include: software version number and channel number.

[0136] Based on the above embodiments, the data processing method provided in this disclosure may further include the following steps: S801 and S802. For the sake of simplicity, Figure 8Only steps S801 and S802 are shown in the diagram. It can be understood that steps S801 and S802 can be implemented in parallel or sequentially with steps S201 to S204. The timing of the execution of steps S801 and S802 can be: when the user operates the application software and generates traffic corresponding to the access request, steps S801 and S802 are executed.

[0137] In step S801, specific operation log data related to the software version number and the channel number are obtained from the pre-built operation log database.

[0138] In step S802, based on the specific operation log data mentioned above, the traffic information corresponding to the software version number and the channel number is determined.

[0139] The implementation scenario for steps S801 to S802 above is, for example, by having front-end developers, such as PHP developers, add more types of parameter information, such as software version number and channel number, in addition to the access parameters when implementing front-end event tracking. Thus, referring to... Figure 1 As shown, when a terminal device 110 (e.g., a client) sends an access request, it can add the corresponding version number and channel number to the suffix of the URL, and this information can be stored in the operation logs of proxy servers 121 and 122. By querying the above operation log database through the server 150, the traffic situation under the corresponding software version number and different channel numbers can be analyzed in real time and intuitively.

[0140] The technical solutions provided in the embodiments of this disclosure can be implemented in whole or in part in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art will understand that microprocessors or digital signal processors (DSPs) can be used in practice to implement some or all of the functions of some or all of the components in the electronic devices according to the embodiments of this disclosure. The embodiments of this disclosure can also be implemented as device or apparatus programs (e.g., computer programs and computer program products) for performing some or all of the methods described herein. Programs implementing the embodiments of this disclosure can be stored on a computer-readable medium or can be in the form of one or more signals. Such signals can be downloaded from an Internet website, provided on a carrier signal, or provided in any other form.

[0141] A second exemplary embodiment of this disclosure provides an electronic device.

[0142] Figure 9 A schematic block diagram of an electronic device provided in an embodiment of the present disclosure is shown.

[0143] Reference Figure 9As shown, the electronic device 900 provided in this embodiment includes a processor 901, a communication interface 902, a memory 903, and a communication bus 904. The processor 901, the communication interface 902, and the memory 903 communicate with each other through the communication bus 904. The memory 903 is used to store at least one executable instruction. When the processor 901 executes the executable instruction stored in the memory, it implements the various steps in the data processing method described above.

[0144] Specifically, the executable instructions cause the processor to perform the following steps: receiving complaint information sent by a terminal device, the complaint information including a user identifier and a reason for the complaint regarding a specific service item; querying a pre-built operation log database based on the complaint information to retrieve candidate operation logs related to the user identifier and the specific service item; wherein the operation log database stores operation logs of multiple distributed proxy servers during the receipt and forwarding of access requests; determining whether the complaint reason is valid based on the candidate operation logs to obtain a verification result; and generating a corresponding complaint processing result based on the verification result and sending the complaint processing result to the terminal device. Detailed implementation processes and further executable steps described above can be found in the description of the first embodiment, and will not be repeated here.

[0145] According to embodiments of this disclosure, the aforementioned electronic device 900 may be: a server providing support for complaint requests from application software installed on a terminal device, as described above. Figure 1 The example system framework 100 includes a server 150, or other server or service cluster implementation capable of communicating with the aforementioned terminal device 110 and having access and creation permissions to the aforementioned operation log database 151. In an exemplary scenario, the aforementioned application software is, for example, one or more of the following: e-reading software, short video software, search software, food delivery software, etc.

[0146] The aforementioned memory 903 may be an electronic memory such as flash memory, EEPROM (Electrically Erasable Programmable Read-Only Memory), EPROM, hard disk, or ROM. Memory 903 has storage space for program code used to perform any of the method steps described above. For example, the storage space for program code may include individual program codes for implementing the various steps in the methods described above. This program code can be read from or written to one or more computer program products. These computer program products include program code carriers such as hard disks, optical discs (CDs), memory cards, or floppy disks. Such computer program products are typically portable or fixed storage units. The storage unit may have storage segments or storage spaces arranged similarly to memory 903 in the aforementioned electronic device. The program code may be compressed, for example, in a suitable form. Typically, the storage unit includes programs for performing the method steps according to embodiments of this disclosure, i.e., code that can be read by a processor such as 901, which, when run by the electronic device, causes the electronic device to perform the various steps in the methods described above.

[0147] A third exemplary embodiment of this disclosure also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program that, when executed by a processor, implements the data processing method described above.

[0148] The computer-readable storage medium may be included in the device / apparatus described in the above embodiments; or it may exist independently and not assembled into the device / apparatus. The computer-readable storage medium carries one or more programs that, when executed, implement the method according to the embodiments of this disclosure.

[0149] According to embodiments of this disclosure, the computer-readable storage medium can be a non-volatile computer-readable storage medium, such as including, but not limited to: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this disclosure, the computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0150] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising a…" does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0151] The above description is merely a specific embodiment of this disclosure, enabling those skilled in the art to understand or implement it. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this disclosure. Therefore, this disclosure is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A data processing method, characterized in that, include: The system receives complaint information sent by the terminal device, the complaint information including: user identifier and reasons for the complaint regarding a specific service item; Based on the complaint information, a query is performed in the pre-built operation log database to retrieve candidate operation logs related to the user identifier and the specific service item. The operation log database is used to store operation logs of multiple distributed proxy servers during the process of receiving and forwarding access requests. The proxy servers are used to forward access requests to their respective subordinate service nodes for processing based on the corresponding service nodes. Based on the candidate operation log, determine whether the complaint reason is valid and obtain the verification result; and Based on the verification results, a corresponding complaint handling result is generated and sent to the terminal device.

2. The method according to claim 1, characterized in that, The reasons for the complaint include: nominal access object information, nominal operation information under a specific service item, and nominal processing result; the candidate operation log includes: forwarded access request information; The step of determining whether the complaint reason is valid based on the candidate operation log includes: Based on the access request information, determine whether there is a target operation log in the candidate operation log that matches the nominal access object and the nominal operation; If it is determined that the target operation log does not exist in the candidate operation logs, the complaint reason is deemed invalid.

3. The method according to claim 2, characterized in that, The step of determining whether the complaint reason is valid based on the candidate operation log further includes: When it is determined that the target operation log exists in the candidate operation log, check whether there is an error in the access parameter configuration of the target access request information corresponding to the target operation log. When the verification reveals that a specific access parameter in the target access request information has an incorrect tracking configuration, the complaint reason is determined to be valid, and a prompt message indicating that the specific access parameter has an incorrect tracking configuration is generated.

4. The method according to claim 3, characterized in that, The candidate operation log also includes: information about the service node to which the access request is distributed; The step of determining whether the complaint reason is valid based on the candidate operation log further includes: When the verification shows that there are no errors in the instrumentation configuration of all access parameters in the target access request information, the target service log about the target access request is obtained from the corresponding target service node according to the target service node information corresponding to the target operation log. Based on the target service log, determine whether the actual processing result for the target access request is consistent with the nominal processing result; When the actual processing result is consistent with the nominal processing result, the complaint reason is determined to be valid; When the actual processing result is inconsistent with the nominal processing result, the complaint reason is determined to be invalid.

5. The method according to claim 3, characterized in that, The verification process, which checks whether there are any errors in the configuration of the access parameters in the target access request information corresponding to the target operation log, includes: Verify whether the access parameters corresponding to the specific service item in the target access request information are consistent with the predefined parameters in the backend; When the access parameters corresponding to the specific service item are consistent with the predefined parameters, it is determined that there are no errors in the instrumentation configuration of all access parameters; When a specific access parameter in the access parameters corresponding to the specific service item is inconsistent with the predefined parameter, it is determined that there is a problem with the instrumentation configuration of the specific access parameter.

6. The method according to any one of claims 1-5, characterized in that, Also includes: Build an operation log database; The construction of the operation log database includes: Define a target data interface for synchronizing operation logs with multiple distributed proxy servers, wherein the target data interface is used to limit the upload address of the operation logs; Based on the target data interface, data from the operation logs uploaded by the proxy server during the process of receiving and forwarding access requests are received and stored.

7. The method according to claim 6, characterized in that, For the same access request, the operation logs of access requests that are relayed between multiple proxy servers carry a redundancy flag. The construction operation log database further includes: Based on the target data interface, redundant operation logs related to the redundancy identifier are filtered out from the logs to be uploaded.

8. The method according to claim 6, characterized in that, For the same access request, the operation logs of access requests that are relayed between multiple proxy servers carry a redundancy flag. The construction operation log database further includes: In the already stored operation log data, based on the redundancy identifier, identify the redundant operation logs associated with the redundancy identifier, and delete the redundant operation logs.

9. The method according to claim 6, characterized in that, The construction operation log database also includes: Based on the target data interface, data from operation logs that are to be uploaded and whose timeliness does not meet the preset timeliness requirements are filtered out; and / or, Based on the target data interface, data corresponding to service items that are to be uploaded and whose data timeliness requirements are lower than the preset standard are filtered out.

10. The method according to claim 6, characterized in that, The construction operation log database also includes: In the existing operation log data, delete operation log data whose timeliness does not meet the preset timeliness requirements; and / or, In the stored operation logs, delete the data corresponding to service items whose data timeliness requirements are lower than the preset standard.

11. The method according to claim 1, characterized in that, The access request carries preset tracking parameters, which include: software version number and channel number; The method further includes: Retrieve specific operation log data related to the software version number and the channel number from a pre-built operation log database; Based on the specific operation log data, determine the traffic information corresponding to the software version number and the channel number.

12. An electronic device, characterized in that, include: The processor, communication interface, memory, and communication bus are connected, with the processor, communication interface, and memory communicating with each other via the communication bus. The memory is used to store at least one executable instruction, which causes the processor to perform the following steps: The system receives complaint information sent by the terminal device, the complaint information including: user identifier and reasons for the complaint regarding a specific service item; Based on the complaint information, a query is performed in the pre-built operation log database to retrieve candidate operation logs related to the user identifier and the specific service item. The operation log database is used to store operation logs of multiple distributed proxy servers during the process of receiving and forwarding access requests. The proxy servers are used to forward access requests to their respective subordinate service nodes for processing based on the corresponding service nodes. Based on the candidate operation log, determine whether the complaint reason is valid and obtain the verification result; and Based on the verification results, a corresponding complaint handling result is generated and sent to the terminal device.

13. The electronic device according to claim 12, characterized in that, The reasons for the complaint include: nominal access object information, nominal operation information under a specific service item, and nominal processing result; the candidate operation log includes: forwarded access request information; The step of determining whether the complaint reason is valid based on the candidate operation log includes: Based on the access request information, determine whether there is a target operation log in the candidate operation log that matches the nominal access object and the nominal operation; If it is determined that the target operation log does not exist in the candidate operation logs, the complaint reason is deemed invalid.

14. The electronic device according to claim 13, characterized in that, The step of determining whether the complaint reason is valid based on the candidate operation log further includes: When it is determined that the target operation log exists in the candidate operation log, check whether there is an error in the access parameter configuration of the target access request information corresponding to the target operation log. When the verification reveals that a specific access parameter in the target access request information has an incorrect tracking configuration, the complaint reason is determined to be valid, and a prompt message indicating that the specific access parameter has an incorrect tracking configuration is generated.

15. The electronic device according to claim 14, characterized in that, The candidate operation log also includes: information about the service node to which the access request is distributed; The step of determining whether the complaint reason is valid based on the candidate operation log further includes: When the verification shows that there are no errors in the instrumentation configuration of all access parameters in the target access request information, the target service log about the target access request is obtained from the corresponding target service node according to the target service node information corresponding to the target operation log. Based on the target service log, determine whether the actual processing result for the target access request is consistent with the nominal processing result; When the actual processing result is consistent with the nominal processing result, the complaint reason is determined to be valid; When the actual processing result is inconsistent with the nominal processing result, the complaint reason is determined to be invalid.

16. The electronic device according to claim 14, characterized in that, The verification process, which checks whether there are any errors in the configuration of the access parameters in the target access request information corresponding to the target operation log, includes: Verify whether the access parameters corresponding to the specific service item in the target access request information are consistent with the predefined parameters in the backend; When the access parameters corresponding to the specific service item are consistent with the predefined parameters, it is determined that there are no errors in the instrumentation configuration of all access parameters; When a specific access parameter in the access parameters corresponding to the specific service item is inconsistent with the predefined parameter, it is determined that there is a problem with the instrumentation configuration of the specific access parameter.

17. The electronic device according to any one of claims 12-16, characterized in that, The executable instructions cause the processor to further perform the following steps: constructing an operation log database; The construction of the operation log database includes: Define a target data interface for synchronizing operation logs with multiple distributed proxy servers, wherein the target data interface is used to limit the upload address of the operation logs; Based on the target data interface, data from the operation logs uploaded by the proxy server during the process of receiving and forwarding access requests are received and stored.

18. The electronic device according to claim 17, characterized in that, For the same access request, the operation logs of access requests that are relayed between multiple proxy servers carry a redundancy flag. The construction operation log database further includes: Based on the target data interface, redundant operation logs related to the redundancy identifier are filtered out from the logs to be uploaded.

19. The electronic device according to claim 17, characterized in that, For the same access request, the operation logs of access requests that are relayed between multiple proxy servers carry a redundancy flag. The construction operation log database further includes: In the already stored operation log data, based on the redundancy identifier, identify the redundant operation logs associated with the redundancy identifier, and delete the redundant operation logs.

20. The electronic device according to claim 17, characterized in that, The construction operation log database also includes: Based on the target data interface, data from operation logs that are to be uploaded and whose timeliness does not meet the preset timeliness requirements are filtered out; and / or, Based on the target data interface, data corresponding to service items that are to be uploaded and whose data timeliness requirements are lower than the preset standard are filtered out.

21. The electronic device according to claim 17, characterized in that, The construction operation log database also includes: In the existing operation log data, delete operation log data whose timeliness does not meet the preset timeliness requirements; and / or, In the stored operation logs, delete the data corresponding to service items whose data timeliness requirements are lower than the preset standard.

22. The electronic device according to claim 12, characterized in that, The access request carries preset tracking parameters, which include: software version number and channel number; The executable instructions cause the processor to further perform the following steps: Retrieve specific operation log data related to the software version number and the channel number from a pre-built operation log database; Based on the specific operation log data, determine the traffic information corresponding to the software version number and the channel number.

23. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method of any one of claims 1-11.

Images