Data processing system, method, device and equipment

Abstract

The invention discloses a data processing system, method, device and equipment, and relates to the technical field of computers. The system comprises a management end and a plurality of clients, the management end is used for acquiring dyeing information, and the dyeing information is used for indicating screening conditions when the clients are screened; sending an exception acquisition request to at least one client in a plurality of clients based on the dyeing information; the at least one client is used for receiving an exception collection request; front-end abnormal data is reported to the management end in response to the abnormal collection request, the front-end abnormal data is front-end data which is generated by at least one client in the operation process and meets a preset abnormal condition, and a matching relation exists between the preset abnormal condition and a screening condition corresponding to the dyeing information; the management end is also used for receiving the front-end abnormal data; and under the condition that the client is matched with the dyeing information, the alarm information is generated for the front-end abnormal data meeting the preset alarm condition, so that the alarm efficiency can be improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a data processing system, method, device and equipment. Background Art

[0002] In software development and operation and maintenance practices, log alerts are a key monitoring mechanism used to detect and respond to system anomalies in real time, and are essential for maintaining system stability and reliability.

[0003] In the related technology, full background logs are used to enable the system to analyze all background log data, issue alarms for detected abnormal logs, and comprehensively monitor the system status.

[0004] However, based on the analysis of the full amount of background logs, a large amount of alarm information is easily generated, resulting in alarm fatigue, which leads to low response speed and efficiency to alarms. Summary of the invention

[0005] The embodiment of the present application provides a data processing system, method, device and equipment, which can improve the efficiency of alarm. The technical solution is as follows.

[0006] In one aspect, a data processing system is provided, the system comprising a management terminal and a plurality of clients; The management end is used to obtain coloring information, where the coloring information is used to indicate an identifier screening condition when screening the client identifier; and send the exception collection request to at least one of the multiple clients based on the coloring information; The at least one client is configured to receive the exception collection request; and report front-end exception data to the management end in response to the exception collection request, wherein the front-end exception data is front-end data generated by the at least one client during operation that meets a preset exception condition, and there is a matching relationship between the preset exception condition and the identification screening condition corresponding to the dyeing information; The management end is also used to receive the front-end abnormal data; when the client identifier matches the dyeing information, generate alarm information for the front-end abnormal data that meets the preset alarm conditions.

[0007] In some embodiments, the at least one client is further used to obtain the front-end abnormal data that meets the preset abnormal condition based on the abnormal collection request, and the front-end abnormal data includes at least one front-end data of network quality data, front-end response data, resource quality data, and page loading data; The network quality data is used to indicate the network response status, the front-end response data is used to indicate the response status of the client to the front-end operation, the resource quality data is used to indicate the resource download status of the client, and the page loading data is used to indicate the front-end page loading status of the client.

[0008] In some embodiments, the plurality of clients respectively correspond to client identifiers, and the coloring information is used to indicate an identifier screening condition when screening the clients according to the client identifiers; or, The multiple clients are respectively logged in with client accounts, and the coloring information is used to indicate a screening condition when screening the clients according to the client accounts.

[0009] In some embodiments, the at least one client is further used to report the network quality data that meets the network abnormality condition to the management end when the client matches the first coloring information, the first coloring information is used to indicate that the client has unlocked the network acceleration permission, and the network abnormality condition has the matching relationship with the screening condition indicated by the first coloring information; The at least one client is further used to report the front-end response data that meets the abnormal operation condition to the management end when the client matches the second coloring information, the second coloring information is used to indicate that the account registration time of the client account does not exceed a preset time threshold, or the account activity of the client account reaches a preset activity, and the abnormal operation condition has the matching relationship with the screening condition indicated by the second coloring information; The at least one client is further used to report the resource quality data that meets the resource abnormality condition to the management end when the client matches the third coloring information, the third coloring information is used to indicate that the device model of the client meets the preset model type, and the resource abnormality condition has the matching relationship with the screening condition indicated by the third coloring information; The at least one client is also used to report the page loading data that meets the page exception condition to the management end when the client matches the fourth coloring information. The fourth coloring information is used to indicate that the number of times the client account has exited the client based on the front-end page exception within a historical time period has reached a preset number threshold, and the page exception condition has the matching relationship with the screening condition indicated by the fourth coloring information.

[0010] In some embodiments, the at least one client is further used to mark a coloring tag on the at least one client when the at least one client matches the coloring information, and the coloring tag is used to indicate that the at least one client meets the screening condition; based on the coloring tag, the front-end abnormal data corresponding to the client is reported to the management end, and the front-end abnormal data includes the coloring tag; or The at least one client is further used to report the front-end abnormal data in full to the management end in response to the abnormal collection request, where the front-end abnormal data includes at least one of a client device identifier or a client account.

[0011] In some embodiments, the management end is further used to receive the front-end abnormal data including the coloring label; based on the coloring label, when the front-end abnormal data meets the alarm condition, generate alarm information corresponding to the front-end abnormal data; or The management end is further used to receive the front-end abnormal data; if at least one of the client identifier or the client account matches the coloring information, mark the front-end abnormal data with the coloring label; for the front-end abnormal data marked with the coloring label, generate the alarm information if the front-end abnormal data meets the alarm condition; There is a corresponding relationship between the alarm condition and the dyeing label.

[0012] In some embodiments, the management end is further used to generate a first alarm message for the front-end abnormal data that meets the first alarm condition when the coloring tag indicates that the client has unlocked the network acceleration permission, and the first alarm condition is used to indicate that the front-end abnormal data includes network quality data; The management end is further configured to generate a second alarm message for the front-end abnormal data that meets the second alarm condition, when the colored label indicates that the account registration duration of the client account logged in by the client does not exceed a preset duration threshold, or when the account activity of the client account reaches a preset activity, wherein the second alarm condition is used to indicate that the front-end abnormal data includes the front-end response data; The management end is further configured to generate third alarm information for the front-end abnormal data that meets a third alarm condition when the dyeing label indicates that the device model of the client meets a preset model type, wherein the third alarm condition is used to indicate that the front-end abnormal data includes resource quality data; The management end is also used to generate a fourth alarm information for front-end abnormal data that meets the fourth alarm condition when the number of times the client account logged in by the client as indicated by the colored label reaches a preset number threshold within a historical time period due to front-end page abnormalities. The fourth alarm condition is used to indicate that the front-end abnormal data includes page loading data.

[0013] In some embodiments, the at least one client is also used to obtain the dyeing information from the management end through a dyeing interface, where the dyeing interface is an application programming interface between the management end and the at least one client; or, to obtain the dyeing information from the management end through a long link, where the long link is a real-time communication channel established between the at least one client and the management end.

[0014] In some embodiments, the at least one client is further used to send a dyeing request to the management end according to the dyeing interface, wherein the dyeing request is used to request the management end for the dyeing information; The management end is further used to send the coloring information to the at least one client through the coloring interface in response to the coloring request.

[0015] In some embodiments, the at least one client is further used to establish the long link with the management end, and the long link is used to receive the dyeing information pushed by the management end in real time; The management end is also used to send the dyeing information to the client in real time through the long link.

[0016] On the other hand, a data processing method is provided, the method being executed by a client, the method comprising: Acquire an exception collection request, where the exception collection request is sent by the management end based on the coloring information, where the coloring information is used to indicate a screening condition when the management end screens the client; In response to the abnormal collection request, reporting front-end abnormal data to the management end, wherein the front-end abnormal data is the front-end data generated by the client during operation that meets the preset abnormal conditions, and there is a corresponding relationship between the preset abnormal conditions and the screening conditions corresponding to the dyeing information; The management end is used to generate alarm information for the front-end abnormal data that meets the preset alarm conditions when the client matches the dyeing information.

[0017] On the other hand, a data processing method is provided, the method being executed by a management end, the method comprising: Acquire coloring information, where the coloring information is used to indicate a screening condition when screening clients; Sending the exception collection request to at least one client among the multiple clients based on the staining information; Receiving front-end abnormal data reported by the at least one client based on the abnormal collection request, wherein the front-end abnormal data is front-end data generated by the at least one client during operation and meets a preset abnormal condition, and there is a matching relationship between the preset abnormal condition and the screening condition corresponding to the dyeing information; In the case where the client matches the dyeing information, alarm information is generated for the front-end abnormal data that meets the preset alarm conditions.

[0018] In another aspect, a data processing device is provided, the device comprising: An acquisition module, used for acquiring an exception collection request, wherein the exception collection request is sent by the management end based on the coloring information, and the coloring information is used for indicating a screening condition when the management end screens the client; A reporting module, configured to report front-end abnormal data to the management end in response to the abnormal collection request, wherein the front-end abnormal data is front-end data generated by the client during operation that meets a preset abnormal condition, and there is a corresponding relationship between the preset abnormal condition and the screening condition corresponding to the dyeing information; The management end is used to generate alarm information for the front-end abnormal data that meets the preset alarm conditions when the client matches the dyeing information.

[0019] In another aspect, a data processing device is provided, the device comprising: An acquisition module, used for acquiring coloring information, wherein the coloring information is used for indicating a screening condition when screening clients; A sending module, configured to send the abnormality collection request to at least one client among the multiple clients based on the dyeing information; A receiving module, configured to receive front-end abnormal data reported by the at least one client based on the abnormal collection request, wherein the front-end abnormal data is front-end data generated by the at least one client during operation and meets a preset abnormal condition, and there is a matching relationship between the preset abnormal condition and the screening condition corresponding to the dyeing information; The alarm module is used to generate alarm information for the front-end abnormal data that meets the preset alarm conditions when the client matches the dyeing information.

[0020] On the other hand, a computer device is provided, comprising a processor and a memory, wherein the memory stores at least one instruction, at least one program, a code set or an instruction set, and the at least one instruction, the at least one program, the code set or the instruction set is loaded and executed by the processor to implement a data processing method as described in any of the above-mentioned embodiments of the present application.

[0021] On the other hand, a computer-readable storage medium is provided, in which at least one instruction, at least one program, a code set or an instruction set is stored, and the at least one instruction, the at least one program, the code set or the instruction set is loaded and executed by a processor to implement a data processing method as described in any of the above-mentioned embodiments of the present application.

[0022] On the other hand, a computer program product or a computer program is provided, the computer program product or the computer program includes computer instructions, the computer instructions are stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the data processing method described in any of the above embodiments.

[0023] The beneficial effects brought by the technical solution provided by the embodiment of the present application include at least: By filtering specific clients through dyeing information, the management end can obtain the front-end abnormal data corresponding to the specific client, reducing the number of data reports in the data processing process, alleviating the load pressure when abnormal data alarms are generated, and improving the pertinence of alarm information. It can perform front-end abnormal alarms for specific clients, which not only improves the alarm response speed, but also improves the accuracy of alarm information. Different abnormal reporting mechanisms and alarm mechanisms can be used for different dyeing users, thereby improving the abnormal reporting efficiency and alarm efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0025] Figure 1 is a schematic diagram of a computer system provided by an exemplary embodiment of the present application; Figure 2 is an interactive flow chart of a data processing system provided by an exemplary embodiment of the present application; Figure 3 is a data processing logic flow chart provided by an exemplary embodiment of the present application; Figure 4 is a flow chart of a data processing method provided by an exemplary embodiment of the present application; Figure 5 is a flow chart of a data processing method provided by an exemplary embodiment of the present application; Figure 6 is a structural block diagram of a data processing device provided by an exemplary embodiment of the present application; Figure 7 is a structural block diagram of a data processing device provided by an exemplary embodiment of the present application; Figure 8 It is a structural block diagram of a terminal provided by an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0026] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0027] It should be understood that although the terms first, second, etc. may be used in the present disclosure to describe various information, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of the present disclosure, the first parameter may also be referred to as the second parameter, and similarly, the second parameter may also be referred to as the first parameter. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0028] In software development and operation and maintenance practices, log alerts are a key monitoring mechanism used to detect and respond to system anomalies in real time, and are essential for maintaining system stability and reliability. In related technologies, full background logs are used to enable the system to analyze all background log data, issue alerts for detected abnormal logs, and fully monitor the system status. However, based on full background log analysis, a large amount of alert information is easily generated, resulting in alert fatigue, which leads to low response speed and efficiency to alerts.

[0029] The data processing system provided in the embodiment of the present application can filter specific clients through dyeing information, so that the management end can obtain the front-end abnormal data corresponding to the specific client, reduce the number of data reports in the data processing process, reduce the load pressure when abnormal data alarms, improve the pertinence of alarm information, and can perform front-end abnormal alarms for specific clients, which not only improves the alarm response speed, but also improves the accuracy of alarm information. Different abnormal reporting mechanisms and alarm mechanisms can be used for different dyeing users, which improves the abnormal reporting efficiency and alarm efficiency. In addition, by filtering the client through dyeing information, the analysis ability and abnormal perception ability for specific users are also improved.

[0030] In some embodiments, the client account matching the dyeing information reports the background log, and the management end issues an abnormal alarm based on the reported background log. However, the background log is difficult to reflect the real experience of the front end, and the alarm efficiency for the actual user experience is low.

[0031] The system provided in the embodiment of the present application enables the client to issue an alarm for the front-end abnormal data by reporting the front-end abnormal data according to the dyeing information. The front-end abnormal data can reflect the real front-end experience information such as the front-end network quality, front-end operation response, front-end resource download, and front-end page loading, and can improve the accuracy of alarms for specific user front-end experiences, thereby helping to improve the user's front-end experience.

[0032] First, the computer system of this application is introduced. Please refer to Figure 1 , which shows a schematic diagram of a computer system provided by an exemplary embodiment of the present application, and the computer system includes: a terminal 10 and a server 20.

[0033] A client of the first application may be installed in the terminal 10. Optionally, the first application may be an application that needs to be downloaded and installed, or may be a click-to-use application, which is not limited in the embodiment of the present application.

[0034] The first application may be any application with an abnormality reporting function, such as a social application, a data analysis program, an enterprise management program, a virtual game program, or the like.

[0035] The first application is used to collect and report front-end abnormal data that meets preset abnormal conditions during the operation of the client.

[0036] The server 20 is a management terminal corresponding to multiple clients, and the management terminal is used to generate alarm information for front-end abnormal data reported by the clients.

[0037] The server 20 may also be implemented as a terminal device with an alarm function, which is not limited in this embodiment of the present application.

[0038] In some embodiments, the management end is used to obtain coloring information, which is used to indicate the screening conditions when screening client devices; based on the coloring information, an exception collection request is sent to at least one client among multiple clients; at least one client is used to receive the exception collection request; in response to the exception collection request, front-end exception data is reported to the management end, and the front-end exception data is front-end data that meets the preset exception conditions generated by at least one client during the operation process, and there is a matching relationship between the preset exception conditions and the screening conditions corresponding to the coloring information; the management end is also used to receive the front-end exception data, and when the front-end exception data meets the alarm conditions, generate alarm information corresponding to the front-end exception data.

[0039] The above-mentioned terminal is optional. The terminal can be a desktop computer, a laptop computer, a mobile phone, a tablet computer, an e-book reader, a Moving Picture Experts Group Audio Layer III (MP3) player, a Moving Picture Experts Group Audio Layer IV (MP4) player, a smart TV, a smart car, and other terminal devices in various forms, which are not limited in the embodiments of the present application.

[0040] It is worth noting that the above-mentioned servers can be independent physical servers, or they can be server clusters or distributed systems composed of multiple physical servers. They can also be cloud servers that provide basic cloud computing services such as cloud services, cloud security, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDN), as well as big data and artificial intelligence platforms.

[0041] Among them, cloud technology refers to a hosting technology that unifies hardware, software, network and other resources within a wide area network or local area network to achieve data computing, storage, processing and sharing.

[0042] In some embodiments, the above server can also be implemented as a node in a blockchain system.

[0043] It should be noted that the information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.) and signals involved in this application are all authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of the relevant regions. For example, the operation data and account information involved in this application are all obtained with full authorization.

[0044] To further explain, before collecting relevant user data (for example, account information, historical operation data, and real-time operation data involved in this application) and during the process of collecting relevant user data, this application can display a prompt interface, pop-up window, or output voice prompt information. The prompt interface, pop-up window, or voice prompt information is used to prompt the user that its relevant data is currently being collected, so that this application only starts to execute the relevant steps of obtaining user-related data after obtaining the user's confirmation operation on the prompt interface or pop-up window, otherwise (that is, when the user's confirmation operation on the prompt interface or pop-up window is not obtained), the relevant steps of obtaining user-related data are terminated, that is, the user's relevant data is not obtained. In other words, all user data collected by this application are collected with the user's consent and authorization, and the collection, use, and processing of relevant user data need to comply with relevant laws, regulations, and standards in the relevant regions.

[0045] For illustration, please refer to Figure 2 , Figure 2 is an interactive flow chart of a data processing system provided by an exemplary embodiment of the present application, such as Figure 2 As shown, the system includes a management terminal and multiple clients, and the interaction process includes the following steps: Step 211: The management terminal obtains dyeing information.

[0046] The dye information is used to indicate the filtering conditions when filtering clients.

[0047] The filter condition is used to filter the clients that need to report abnormal data.

[0048] In some embodiments, the client may correspond to a client device identifier, or a client account may be logged in the client, and the coloring information is used to indicate at least one of an identifier filtering condition for filtering the client device identifier, or an account filtering condition for filtering the client account.

[0049] Illustratively, multiple clients respectively correspond to client identifiers, and the coloring information is used to indicate the identifier screening conditions when screening client device identifiers; or, multiple clients respectively log in to client accounts, and the coloring information is used to indicate the screening conditions when screening clients.

[0050] Optionally, when a client account is logged in to the client, clients matching the dyeing information are filtered based on at least one of the client device identifier or the client account; when no client account is logged in to the client, clients matching the dyeing information are filtered based on the client device identifier.

[0051] In some embodiments, a management end account is logged in to the management end, and the above-mentioned screening conditions can be preset or configured by the management end account in the management end, which is not limited in the embodiments of the present application.

[0052] The management end may be a background server corresponding to multiple clients, or may be a terminal with client management function, which is not limited in the embodiments of the present application.

[0053] Optionally, the management end may obtain one or more dyeing information, which is not limited in the embodiment of the present application.

[0054] Illustratively, taking filtering clients based on client accounts as an example, for the client internal testing scenario, the filtering conditions are set to include the client account being an internal testing account, and the client logged in with the internal testing account will report abnormal data, wherein the coloring information may include the internal testing account identifier and other information content used to indicate the filtering conditions.

[0055] Furthermore, the internal test accounts can be further divided. Taking the game scene as an example, different coloring information can be set for different virtual character types corresponding to the internal test accounts, so that multiple clients can report abnormal data for the internal test accounts corresponding to different virtual character types according to the coloring information, so that the management end can intuitively obtain the abnormal data of the internal test accounts corresponding to different virtual character types.

[0056] For daily monitoring scenarios of clients, filtering conditions can be set, including the client account being a new account, an old account, an active account, or other specific accounts, and the client logged in with the specific account will report abnormal data. Among them, the coloring information may include the registration time requirements, activity requirements, etc. of the client account to indicate the filtering conditions.

[0057] Illustratively, taking the example of filtering clients according to client device identifiers, the identifier filtering condition is set to that the client device identifier belongs to a preset identifier list.

[0058] Optionally, the method for acquiring the dyeing information includes but is not limited to at least one of reading the dyeing information, automatically generating the dyeing information according to the screening conditions, and manually configuring the dyeing information.

[0059] Illustratively, the data processing system also includes an account management platform, which is used to store dyeing information.

[0060] Optionally, the account management platform is logged in with a platform management account, and the platform management account and the management end account may be the same or different. The management end may include the account management platform, or the account management platform may also be a platform independent of the management end. This embodiment of the application is not limited to this.

[0061] The platform management account is used to manage the coloring information in the account management platform, including but not limited to adding coloring information, deleting coloring information, modifying coloring information, etc.

[0062] The screening conditions may be specified by the account management platform or by the management end, and this embodiment of the present application does not limit this.

[0063] Illustratively, the account management platform determines the screening conditions and sends corresponding coloring information to the management end based on the screening conditions; alternatively, the management end determines the screening conditions and sends a coloring request to the account management platform based on the screening conditions. The coloring request is used to request coloring information from the account management platform. The coloring request includes the screening conditions. The account management platform sends coloring information corresponding to the screening conditions to the management end based on the received coloring request.

[0064] It is worth noting that the above-mentioned application scenarios, screening conditions, staining information and methods for obtaining staining information are only illustrative examples. The management end can obtain staining information corresponding to any screening conditions according to data processing requirements, and the embodiments of the present application are not limited to this.

[0065] Step 212: The management end sends an exception collection request to at least one of the multiple clients based on the staining information.

[0066] The exception collection request is used to request the client to collect and report exception data to the front end.

[0067] Optionally, the abnormal collection request may include coloring information or may not include coloring information, which is not limited in this embodiment of the present application.

[0068] Taking the exception collection request including the coloring information as an example, the management end sends the exception collection request including the coloring information to multiple clients, and the exception collection request is used to instruct the client to report the front-end exception data when the client matches the coloring information.

[0069] Taking the exception collection request not including the coloring information as an example, the management end filters at least one client matching the coloring information based on the coloring information, and sends an exception collection request to the at least one client obtained by the screening, where the exception collection request is used to instruct at least one client to report front-end abnormal data.

[0070] That is, the management end can send an exception collection request to the screened clients based on the staining information, or directly send an exception collection request to multiple clients, and the multiple clients can filter the client accounts that meet the screening conditions according to the staining information to report the exceptions.

[0071] The exception collection request may include data reporting requirements such as data reporting type, reporting cycle, reporting duration, data reporting method, etc., which are not limited in the embodiments of the present application.

[0072] Among them, the data reporting type is used to indicate the data type of the front-end abnormal data reported by the client, the reporting period is used to indicate the time interval for the client to report the front-end abnormal data, the reporting duration is used to indicate that the client continues to report the front-end abnormal data within a preset time period, and the data reporting method is used to indicate the data communication method, data reporting format, etc. when the client reports the front-end abnormal data.

[0073] Optionally, the management end may send an exception collection request to at least one client through a dyeing interface, or may send an exception collection request to at least one client through a long link.

[0074] The dyeing interface is an application programming interface (API) used to transmit dyeing information between the management end and the client. The long polling is a real-time communication channel established between at least one client and the management end.

[0075] The above communication methods are merely illustrative examples and are not limited to the embodiments of the present application.

[0076] Step 221: at least one client receives an exception collection request.

[0077] Optionally, the abnormal collection request may include coloring information or may not include coloring information, which is not limited in this embodiment of the present application.

[0078] Taking the exception collection request including the coloring information as an example, step 221 can be implemented as at least one client obtaining the coloring information from the management end.

[0079] Optionally, at least one client obtains dyeing information from the management end through a dyeing interface, which is an application programming interface API between the management end and at least one client; or, at least one client obtains dyeing information from the management end through a long link, which is a real-time communication channel established between at least one client and the management end.

[0080] API is a request-response mode between the client and the management end. The client sends a request to the management end, and the management end returns a response after processing. This mode is stateless, and the connection will be closed after each request-response ends.

[0081] A long connection is a communication method that keeps the connection open until the manager has data to send to the client. In the long connection mode, after the client initiates a request, the manager will protect the connection in an open state until the data is sent to the client and then the connection is closed. The client can immediately initiate a new request.

[0082] Taking the dyeing interface as an example, the interactive process of the client obtaining dyeing information includes: at least one client sends a dyeing request to the management end according to the dyeing interface, and the dyeing request is used to request the management end to obtain dyeing information; the management end responds to the dyeing request and sends dyeing information to at least one client through the dyeing interface.

[0083] The dyeing interface is pre-built. The management end sends dyeing information to the client through the dyeing interface when and only when it receives a dyeing request sent by the client.

[0084] Optionally, the client may periodically send a dyeing request to the management end according to a preset time interval, thereby periodically acquiring dyeing information.

[0085] The system provided in the embodiment of the present application adopts a dyeing interface to transmit dyeing information, so that the management end can respond immediately based on the dyeing request sent by the client. Since the connection relationship constructed by the dyeing interface will be closed after each request, the resource consumption of data transmission can be reduced.

[0086] Taking the long link as an example, the interactive process of the client obtaining the dyeing information includes at least one client establishing a long link with the management end, which is used to receive the dyeing information pushed by the management end in real time; the management end sends the dyeing information to the client in real time through the long link.

[0087] Optionally, after receiving the dyeing information and closing the long link, the client can immediately initiate a link request to the management end again to re-establish the long link, and always maintain the communication connection between the management end and the client.

[0088] The system provided in the embodiment of the present application transmits dyeing information by adopting a long link, so that the client can obtain the dyeing information issued by the management end in real time, thereby avoiding the client failing to obtain the latest dyeing information in time when the management end updates the dyeing information, resulting in data reporting errors, thereby improving data reporting efficiency and alarm efficiency.

[0089] Step 222: at least one client reports front-end abnormal data to the management end in response to the abnormal collection request.

[0090] The front-end abnormal data is the front-end data generated by at least one client during operation that meets the preset abnormal conditions, and there is a matching relationship between the preset abnormal conditions and the screening conditions corresponding to the dyeing information.

[0091] Optionally, the client can locally determine the matching result with the dyeing information, and report the front-end abnormal data when the client matches the dyeing information; the management end can also filter the clients according to the dyeing information before sending the abnormal collection request, and send the abnormal collection request to the filtered clients, so that the filtered clients report the front-end abnormal data; the front-end abnormal data can also be reported by multiple clients, and the management end can filter the matching clients based on the dyeing information to participate in the alarm processing, which is not limited to the embodiments of the present application.

[0092] Taking the exception collection request including coloring information as an example, at least one client receiving the exception collection request needs to confirm whether the client matches the coloring information. If so, it responds to the exception collection request to report the front-end abnormal data; if not, it does not respond to the exception collection request.

[0093] Taking the example that the exception collection request does not include coloring information, the management end sends an exception collection request to at least one client obtained by screening based on the coloring information, automatically determines that at least one client that receives the exception collection request matches the coloring information, and at least one client directly responds to the exception collection request to report the front-end abnormal data; or, the management end sends an exception collection request to multiple clients, and multiple clients respond to the exception collection request and report the front-end abnormal data. After receiving the front-end abnormal data, the management end screens the front-end abnormal data corresponding to the matching client based on the coloring information to participate in alarm processing.

[0094] The exception collection request may include data reporting requirements such as data reporting type, reporting cycle, reporting duration, data reporting method, etc., which are not limited in the embodiments of the present application.

[0095] At least one client may report the front-end abnormal data according to the data reporting requirement in the abnormal collection request.

[0096] In some embodiments, at least one client obtains front-end exception data that meets preset exception conditions based on an exception collection request.

[0097] Optionally, the front-end abnormal data includes but is not limited to at least one of network quality data, front-end response data, resource quality data, and page loading data.

[0098] Among them, network quality data is used to indicate network response conditions, such as network quality, service custom error codes, and network latency.

[0099] Taking the implementation of network quality data as Hypertext Transfer Protocol (HTTP) status code as an example, the HTTP status code is used to indicate the server's response status to the client's request. When the front-end calls the back-end service, the server returns an HTTP status code to indicate whether the request is successfully processed, for example: Status code 2xx indicates that the request was successfully processed, for example, 200 OK indicates that the request was successful; Status code 3xx indicates a redirection and further action is required to complete the request; Status codes 4xx indicate client errors, such as 404 Not Found, which means the requested resource does not exist; Status code 5xx indicates a server error, such as 500 Internal Server Error, which indicates an internal server error.

[0100] Among them, even if the HTTP status code is 2xx, indicating that the request is successfully processed, the background server can also return some custom error codes to provide more detailed error information. For example, even if the request successfully returns 200 OK, the background service may also return a custom error code, such as 1001, indicating "user authentication failed", with an error message such as "user name or password is incorrect".

[0101] The front-end response data is used to indicate the client's response to the front-end operations. Account operations include but are not limited to startup, login, listening to songs, downloading, commenting, entering the homepage and other front-end user operations.

[0102] Resource quality data is used to indicate the resource download status of the client, such as whether the front-end resources such as pictures or static resources in the front-end interface are downloaded successfully, the resource download delay, etc.

[0103] Page loading data is used to indicate the front-end page loading status of the client, such as whether the page loading is successful, page loading delay, etc.

[0104] It is worth noting that the data type of the above-mentioned front-end abnormal data is only an illustrative example and is not limited to this in the embodiments of the present application.

[0105] In the client front-end experience alarm scenario, for different dyeing clients (i.e., clients that match the dyeing information), it is usually necessary to pay attention to front-end abnormal data of different dimensions. Therefore, different abnormal conditions can be preset for different dyeing information, that is, there is a matching relationship between the preset abnormal conditions and the filtering conditions corresponding to the dyeing information, thereby improving the alarm accuracy for different dyeing clients and improving data processing efficiency.

[0106] In an illustrative example, taking the matching relationship between the reported data type indicated by the preset abnormal condition and the screening condition as an example, the front-end abnormal data reporting includes at least the following four situations: In the first, when the at least one client matches the first coloring information, the at least one client reports the network quality data that meets the network abnormality condition to the management end.

[0107] The first coloring information is used to indicate that the client has unlocked the network acceleration permission.

[0108] There is a matching relationship between the network abnormality condition and the screening condition indicated by the first coloring information.

[0109] When the first coloring information is used to indicate that the client has unlocked the network acceleration permission, the client has high requirements for network response. In order to maintain the network response experience of the client, it is necessary to monitor the network response situation by reporting network quality data that meets the network abnormality conditions and issue timely alarms. In this way, when the network response experience of the client is poor, the network response situation of the client can be improved in time based on the alarm information.

[0110] Optionally, the network abnormality condition includes but is not limited to the network quality data indicating that the network delay reaches a preset delay threshold, the HTTP status code in the network quality data indicates that the request response fails, and the network quality data includes at least one of an HTTP error code.

[0111] Second, at least one client reports front-end response data that meets the operation abnormality condition to the management end when the client matches the second coloring information.

[0112] The second coloring information is used to indicate that the account registration duration of the client account does not exceed a preset duration threshold, or that the account activity of the client account reaches a preset activity.

[0113] There is a matching relationship between the abnormal operation condition and the screening condition indicated by the second staining information.

[0114] When the second coloring information indicates that the account registration duration of the client account does not exceed the preset duration threshold, or the account activity of the client account reaches the preset activity, it means that the client account is a key user, and it is necessary to pay attention to the front-end operation experience of these users and promptly improve the client's response to the front-end operations. Therefore, it is necessary to report the front-end response data that meets the operation abnormality conditions and issue an abnormal alarm.

[0115] Optionally, the abnormal operation condition includes but is not limited to at least one of an account operation failure, an account operation including an abnormal feedback operation, and an account operation response delay reaching a preset delay threshold.

[0116] The reported front-end response data is used to indicate the client's response to the front-end operations. Account operations include but are not limited to front-end user operations such as startup, login, listening to songs, downloading, commenting, and entering the homepage.

[0117] Illustratively, different operation identifiers can be set for different front-end operations. By identifying the operation identifier in the front-end response data, it is determined to which front-end operation the front-end response data is responding. The operation abnormality condition can specify the operation identifier of the front-end operation that needs to be reported.

[0118] In a third manner, at least one client reports resource quality data that meets resource abnormality conditions to the management end when the client matches the third coloring information.

[0119] The third coloring information is used to indicate that the device model of the client conforms to the preset model type.

[0120] There is a matching relationship between the resource abnormality condition and the screening condition indicated by the third coloring information.

[0121] When the third coloring information indicates that the client's device model meets the preset model type, the resource download quality of the client needs to meet the resource download requirements corresponding to the preset model type. Therefore, it is necessary to report resource quality data that meets the resource abnormality conditions and issue an abnormality alarm.

[0122] The preset model type is used to indicate the client's resource download requirements, including but not limited to resource download speed, resource download delay threshold, image resource resolution, resource download compression rate, resource download channel, etc.

[0123] Optionally, the resource abnormality condition includes but is not limited to at least one of the following: the resource quality score does not reach a preset score threshold, the resource download fails, the resource download delay reaches a preset delay threshold, and the like.

[0124] Among them, the resource quality score is determined based on the difference between the actual downloaded resources and the resources to be downloaded. Taking picture resources as an example, the resource quality score can be determined based on the difference between the clarity of the actually downloaded picture and the preset clarity of the picture to be downloaded. The resource quality score is negatively correlated with the difference.

[0125] Illustratively, the third coloring information is used to indicate that the device model of the client conforms to the first device model, and the first device model is used to indicate that the front-end image resources downloaded by the client reach the first resolution. When the device model of the first client is the first device model, the first client reports resource quality data that meets the resource abnormality condition, wherein the resource abnormality condition includes that the front-end image resources downloaded by the first client do not reach the first resolution, and the reported resource quality data is the actual resolution of the front-end image resources downloaded by the first client.

[0126] In a fourth embodiment, at least one client reports page loading data that meets the page abnormality condition to the management end when the client matches the fourth coloring information.

[0127] The fourth coloring information is used to indicate that the number of times the client account has exited the client due to front-end page abnormalities within a historical time period has reached a preset number threshold.

[0128] There is a matching relationship between the page abnormality condition and the screening condition indicated by the fourth staining information.

[0129] The fourth coloring information indicates that the client finds it difficult to accept the page loading abnormality. In order to reduce user loss, it is necessary to report page loading data that meets the page abnormality conditions and issue an alarm in time so that the client can improve the page loading situation.

[0130] Optionally, the page abnormality condition includes but is not limited to at least one of page loading failure, page loading delay reaching a preset delay threshold, page loading error, etc.

[0131] It is worth noting that the above-mentioned preset abnormal conditions and screening conditions are only illustrative examples. In the abnormal reporting scenario, any abnormal condition can be preset for any screening condition, and the embodiments of the present application are not limited to this.

[0132] The system provided in the embodiment of the present application provides a method for determining preset abnormal conditions based on multiple screening conditions and reporting front-end abnormal data. It can adopt different front-end abnormal reporting mechanisms for different dyeing clients, improve the flexibility of abnormal reporting, and realize classified reporting of front-end abnormal data, thereby simplifying the processing flow during data alarms, improving alarm efficiency, and the accuracy of alarms for abnormal data of specific clients.

[0133] Step 213, the management end receives the front-end abnormal data; when the client matches the dyeing information, an alarm message is generated for the front-end abnormal data that meets the preset alarm conditions.

[0134] Optionally, the client can directly report the front-end abnormal data to the management end, and the management end directly receives the front-end abnormal data for alarm processing; the client can also report the front-end abnormal data to the server, and the server will clean the data and send it to the management end for alarm processing, or the server can also perform alarm processing after receiving the front-end abnormal data and send the generated alarm information to the management end for display.

[0135] It is worth noting that the above interaction methods are only illustrative examples and are not limited to this in the embodiments of the present application.

[0136] In some embodiments, the client locally filters the client-reported front-end abnormal data that matches the staining information.

[0137] Schematically, when at least one client matches the coloring information, a coloring label is marked on at least one client, and the coloring label is used to indicate that at least one client meets the screening conditions. Based on the coloring label, the front-end abnormal data corresponding to the client is reported to the management end, and the front-end abnormal data includes the coloring label.

[0138] In some embodiments, the management terminal filters the clients that match the staining information.

[0139] Illustratively, at least one client reports all front-end abnormal data to the management end in response to the abnormal collection request, and the front-end abnormal data includes at least one of a client device identifier or a client account.

[0140] Optionally, the front-end abnormal data includes a coloring label, or the front-end abnormal data is reported in association with the coloring label, or the front-end abnormal data includes at least one client information in the client account or the client device identification and the association relationship between the client information and the coloring label is stored in the management end. The embodiments of the present application are not limited to this.

[0141] The management end can determine the colored user corresponding to the front-end abnormal data by identifying the colored label or the match between the client information and the colored information.

[0142] Optionally, the data processing system may include multiple management terminals, and the multiple management terminals are used to respectively process the front-end abnormal data corresponding to different dyeing information.

[0143] Taking the front-end abnormal data reported by the client that is locally filtered by the client and matches the coloring information as an example, the management end receives the front-end abnormal data including the coloring label. The alarm information generation process includes, based on the coloring label, generating alarm information corresponding to the front-end abnormal data when the front-end abnormal data meets the alarm conditions.

[0144] Taking the front-end abnormal data of the client that is screened by the management end and matches the coloring information as an example, the management end receives the front-end abnormal data including the client information, and the client information includes at least one of the client account and the client device identification. The alarm information generation process includes marking the front-end abnormal data with a coloring label when at least one of the client identification or the client account matches the coloring information; and generating alarm information for the front-end abnormal data marked with the coloring label when the front-end abnormal data meets the alarm conditions.

[0145] There is a corresponding relationship between the alarm condition and the coloring label.

[0146] That is, the management end can adopt different alarm mechanisms for different dyeing clients.

[0147] Indicatively, the customized alarm mechanism for the dyeing client includes at least the following four situations: First, when the colored label indicates that the client has unlocked the network acceleration permission, the management end generates a first alarm message for the front-end abnormal data that meets the first alarm condition.

[0148] The first alarm condition is used to indicate that the front-end abnormal data includes network quality data that meets the network abnormal condition.

[0149] There is a corresponding relationship between the first alarm condition and the above-mentioned dyeing label.

[0150] Optionally, the first alarm condition may be preset by the management end for unlocking the client with network acceleration permission, or may be automatically determined by the management end based on reported network quality data, which is not limited in this embodiment of the present application.

[0151] The first alarm information is used to prompt the client that an abnormality occurs in the network response of the front end.

[0152] Second, when the colored label indicates that the registration duration of the client account does not exceed a preset duration threshold, or the account activity of the client account reaches a preset activity, the management end generates a second alarm message for the front-end abnormal data that meets the second alarm condition.

[0153] The second alarm condition is used to indicate that the front-end abnormal data includes front-end response data that meets the operation abnormality condition.

[0154] The second alarm condition corresponds to the above-mentioned dyeing label.

[0155] Optionally, the second alarm condition may be preset by the management end account for key accounts such as new accounts or active accounts, or may be automatically determined by the management end for front-end response data that meets the abnormal operation conditions. This embodiment of the present application is not limited to this.

[0156] The second warning information is used to prompt that the front-end operation of the client generates a response exception.

[0157] The third type is that when the dyeing label indicates that the device model of the client meets the preset model type, the management end generates the third alarm information for the front-end abnormal data that meets the third alarm condition.

[0158] The third alarm condition is used to indicate that the front-end abnormal data includes resource quality data that meets the resource abnormality condition.

[0159] The third alarm condition corresponds to the above-mentioned dyeing label.

[0160] Optionally, the third alarm condition may be preset by the management account for a preset model type of device, or may be automatically determined by the management end for resource quality data that meets the resource abnormality condition, which is not limited in this embodiment of the present application.

[0161] The third warning information is used to prompt the client that an abnormality occurs in the front-end resource download.

[0162] Fourthly, when the colored label indicates that the number of times the client account exits the client based on the front-end page abnormality within the historical time period reaches a preset number threshold, the management end generates a fourth alarm information for the front-end abnormal data that meets the fourth alarm condition.

[0163] The fourth alarm condition is used to indicate that the front-end abnormal data includes page loading data that meets the page abnormality condition.

[0164] The fourth alarm condition corresponds to the above-mentioned coloring label.

[0165] Optionally, the fourth alarm condition can be preset by the management end account for the client account whose number of times of exiting the client based on the front-end page abnormality within a historical time period reaches a preset number threshold, or it can be automatically determined by the management end for the front-end abnormal data that meets the page abnormality condition. The embodiment of the present application is not limited to this.

[0166] The fourth warning information is used to prompt that an exception occurs in the page loading in the client.

[0167] It is worth noting that the above-mentioned alarm conditions and the matching relationship with the dyeing labels are only illustrative examples and are not limited to the embodiments of the present application.

[0168] For illustration, please refer to Figure 3 , Figure 3 is a data processing logic flow chart provided by an exemplary embodiment of the present application, such as Figure 3 As shown, step 310 is executed in sequence during the data processing process, and the front end obtains the coloring information through an interface or a long link; in step 320, when the front end encounters an abnormal experience or an abnormal service / resource request in the user experience, the abnormal log is reported; in step 330, the backend server receives the front-end abnormal log, cleans the log and issues an alarm according to the rules.

[0169] In some embodiments, the management end can also automatically generate a management end repair plan based on the alarm information. The management end repair plan is used to repair the front-end experience according to the front-end abnormal situation, reduce the front-end abnormal data reporting, and reduce the number of alarm information.

[0170] Optionally, the management end may dynamically change at least one of the coloring information, the alarm condition, and the preset abnormal condition according to the number of alarm information or the generation frequency.

[0171] In an illustrative manner, during the launch phase of a new function, priority is given to the front-end experience of key users such as new users or active users. After generating alarm information based on the front-end abnormal data for this type of user and repairing the client, if the number of alarm messages generated by the front-end abnormal data for this type of user is less than the preset number threshold within the preset time period, the repair effect is considered to be good, and the focus can be shifted to other users such as old users by changing the coloring information.

[0172] It is worth noting that the above-mentioned dynamic change scheme is only an illustrative example and is not limited to this in the embodiments of the present application.

[0173] To sum up, the system provided in the embodiment of the present application filters specific clients through staining information, so that the management end can obtain the front-end abnormal data corresponding to the specific client, reduces the number of data reports in the data processing process, alleviates the load pressure during abnormal data alarms, improves the pertinence of alarm information, and can perform front-end abnormal alarms for specific clients, which not only improves the alarm response speed, but also improves the accuracy of the alarm information. Different abnormal reporting mechanisms and alarm mechanisms can be used for different dyeing clients, thereby improving the abnormal reporting efficiency and alarm efficiency.

[0174] For illustration, please refer to Figure 4 , which shows a flowchart of a data processing method provided by an exemplary embodiment of the present application. The method can be executed by a terminal, or by a server, or by both a terminal and a server. The present application embodiment takes the method executed by a client in a data processing system as an example for explanation. Figure 4 As shown, the method comprises the following steps: Step 410: Obtain an exception collection request.

[0175] The exception collection request is sent by the management end based on the coloring information, and the coloring information is used to indicate the filtering conditions when the server filters the clients.

[0176] The exception collection request is used to instruct the client to report front-end exception data.

[0177] Optionally, the exception collection request may include coloring information or may not include coloring information, which is not limited in this embodiment of the present application.

[0178] Taking the abnormal collection request including unstained information as an example, the client is a client that has been filtered by the management end based on the stained information, that is, the client account meets the filtering conditions.

[0179] Taking the exception collection request including coloring information as an example, the client can be any client among multiple clients, and the client locally determines the matching result between the client account and the coloring information, or the management end screens the front-end exception data corresponding to the client matching the coloring information after receiving the front-end exception data.

[0180] When the exception collection request includes coloring information, step 410 may be implemented as obtaining the coloring information.

[0181] Optionally, the client may obtain the dyeing information from the management end through a dyeing interface, or may obtain the dyeing information from the management end through a long link, which is not limited in the embodiments of the present application.

[0182] Among them, the dyeing interface is the application programming interface between the management end and the client, and the long link is the real-time communication channel built between the client and the management end.

[0183] Step 420: In response to the abnormal collection request, report the front-end abnormal data to the management end.

[0184] The front-end abnormal data is the front-end data generated by the client during operation that meets the preset abnormal conditions. There is a corresponding relationship between the preset abnormal conditions and the screening conditions corresponding to the dyeing information.

[0185] Among them, the management end is used to issue an alarm for the front-end abnormal data when the front-end abnormal data meets the alarm conditions.

[0186] In some embodiments, before reporting the front-end abnormal data, it is necessary to obtain the front-end abnormal data that meets the preset abnormal conditions based on the abnormal collection request.

[0187] Optionally, the front-end abnormal data includes but is not limited to at least one of network quality data, front-end response data, resource quality data, and page loading data.

[0188] Among them, network quality data is used to indicate network response status, front-end response data is used to indicate the client's response to front-end operations, resource quality data is used to indicate the client's resource download status, and page loading data is used to indicate the client's front-end page loading status.

[0189] It is worth noting that the data type of the above-mentioned front-end abnormal data is only an illustrative example and is not limited to this in the embodiments of the present application.

[0190] In some embodiments, the client may sample and report the acquired front-end abnormal data according to preset sampling rules.

[0191] Optionally, the preset sampling rule may be preset by the management end, or may be automatically determined by the client end.

[0192] Taking the automatic determination of the preset sampling rule by the client as an example, the client may automatically determine the preset sampling rule according to at least one of the device model type and the dyeing information.

[0193] The device model type is used to indicate the data reporting capability of the client device, and the coloring information is used to indicate the data reporting requirements of the client.

[0194] In the client front-end experience alarm scenario, for different dyeing clients (i.e., clients that match the dyeing information), it is usually necessary to pay attention to front-end abnormal data of different dimensions. Therefore, different abnormal conditions can be preset for different dyeing information, that is, there is a matching relationship between the preset abnormal conditions and the filtering conditions corresponding to the dyeing information, thereby improving the alarm accuracy for different dyeing accounts and improving data processing efficiency.

[0195] In an illustrative example, taking the matching relationship between the reported data type indicated by the preset abnormal condition and the screening condition as an example, the front-end abnormal data reporting includes at least the following four situations: In the first, when the at least one client matches the first coloring information, the at least one client reports the network quality data that meets the network abnormality condition to the management end.

[0196] The first coloring information is used to indicate that the client has unlocked the network acceleration permission.

[0197] There is a matching relationship between the network abnormality condition and the screening condition indicated by the first coloring information.

[0198] Second, at least one client reports front-end response data that meets the operation abnormality condition to the management end when the client matches the second coloring information.

[0199] The second coloring information is used to indicate that the account registration duration of the client account does not exceed a preset duration threshold, or that the account activity of the client account reaches a preset activity.

[0200] There is a matching relationship between the abnormal operation condition and the screening condition indicated by the second staining information.

[0201] In a third manner, at least one client reports resource quality data that meets resource abnormality conditions to the management end when the client matches the third coloring information.

[0202] The third coloring information is used to indicate that the device model of the client conforms to the preset model type.

[0203] There is a matching relationship between the resource abnormality condition and the screening condition indicated by the third coloring information.

[0204] In a fourth embodiment, at least one client reports page loading data that meets the page abnormality condition to the management end when the client matches the fourth coloring information.

[0205] The fourth coloring information is used to indicate that the number of times the client account has exited the client due to front-end page abnormalities within a historical time period has reached a preset number threshold.

[0206] There is a matching relationship between the page abnormality condition and the screening condition indicated by the fourth staining information.

[0207] It is worth noting that the above-mentioned preset abnormal conditions and screening conditions are only illustrative examples. In the abnormal reporting scenario, any abnormal condition can be preset for any screening condition, and the embodiments of the present application are not limited to this.

[0208] For other implementation details, please refer to any of the above embodiments and will not be described in detail here.

[0209] To sum up, the method provided in the embodiment of the present application filters specific clients through staining information, so that the management end can obtain the front-end abnormal data corresponding to the specific client, reduces the number of data reports in the data processing process, alleviates the load pressure during abnormal data alarms, improves the pertinence of alarm information, and can perform front-end abnormal alarms for specific clients, which not only improves the alarm response speed, but also improves the accuracy of the alarm information. Different abnormal reporting mechanisms and alarm mechanisms can be used for different dyeing clients, thereby improving the abnormal reporting efficiency and alarm efficiency.

[0210] For illustration, please refer to Figure 5 , which shows a flowchart of a data processing method provided by an exemplary embodiment of the present application. The method can be executed by a terminal, or by a server, or by both a terminal and a server. The present application embodiment takes the method executed by a management terminal in a data processing system as an example for explanation. Figure 5 As shown, the method comprises the following steps: Step 510, obtaining dyeing information.

[0211] The dye information is used to indicate the filtering conditions when filtering clients.

[0212] The filter condition is used to filter the clients that need to report abnormal data.

[0213] In some embodiments, a management end account is logged in to the management end, and the above-mentioned screening conditions can be preset or configured by the management end account in the management end, which is not limited in the embodiments of the present application.

[0214] The management end may be a background server corresponding to multiple clients, or may be a terminal with client management function, which is not limited in the embodiments of the present application.

[0215] Optionally, the management end may obtain one or more dyeing information, which is not limited in the embodiment of the present application.

[0216] Step 520: Send an exception collection request to at least one of the multiple clients based on the staining information.

[0217] The exception collection request is used to request the client to collect and report exception data to the front end.

[0218] Optionally, the abnormal collection request may include coloring information or may not include coloring information, which is not limited in this embodiment of the present application.

[0219] Taking the exception collection request including the coloring information as an example, the management end sends an exception collection request including the coloring information to multiple clients, and the exception collection request is used to instruct the client to report the front-end abnormal data when the client account matches the coloring information.

[0220] Taking the exception collection request not including the coloring information as an example, the management end filters at least one client matching the coloring information based on the coloring information, and sends an exception collection request to the at least one client obtained by the screening, where the exception collection request is used to instruct at least one client to report front-end abnormal data.

[0221] That is, the management end can send an exception collection request to the filtered clients based on the coloring information, or directly send an exception collection request to multiple clients, and multiple clients can filter the client accounts that meet the filtering conditions according to the coloring information to report the exceptions, or the management end receives the full amount of front-end exception data, and the management end filters the front-end exception data corresponding to the clients that match the coloring information.

[0222] Step 530: Receive front-end abnormal data reported by at least one client based on the abnormal collection request.

[0223] The front-end abnormal data is the front-end data generated by at least one client during operation that meets the preset abnormal conditions, and there is a matching relationship between the preset abnormal conditions and the screening conditions corresponding to the dyeing information.

[0224] In some embodiments, after receiving the front-end abnormal data reported by at least one client, the management end performs data cleaning according to the data cleaning rules, and outputs readable data that conforms to a preset data format to participate in alarm processing.

[0225] Optionally, the data cleaning rule may be preset by the management account for at least one of the coloring information, the reported data type, or the alarm condition.

[0226] Step 540, when the client matches the dyeing information, an alarm message is generated for the front-end abnormal data that meets the preset alarm condition.

[0227] In some embodiments, when the client account logged in by at least one client matches the coloring information, a coloring label is marked on the client account, and the coloring label is used to indicate that the client meets the screening conditions. At least one client reports the front-end abnormal data corresponding to the client account to the management end based on the coloring label.

[0228] Optionally, the front-end abnormal data includes a coloring label, or the front-end abnormal data is reported in association with the coloring label, or the front-end abnormal data includes a client account identifier and the management end stores an association relationship between the client identifier and the coloring label.

[0229] The management end can determine the colored user corresponding to the front-end abnormal data by identifying the colored label.

[0230] Optionally, the data processing system may include multiple management terminals, and the multiple management terminals are used to respectively process the front-end abnormal data corresponding to different dyeing information.

[0231] The alarm information generation process includes, based on the coloring label, generating alarm information corresponding to the front-end abnormal data when the front-end abnormal data meets the alarm condition.

[0232] In some embodiments, at least one client reports all front-end exception data to the management end in response to an exception collection request, and the front-end exception data includes at least one of a client device identifier or a client account; the management end receives the front-end exception data including client information, and the client information includes at least one of a client account and a client device identifier. The alarm information generation process includes marking the front-end exception data with a coloring label when at least one of the client identifier or the client account matches the coloring information; and generating alarm information for the front-end exception data marked with the coloring label when the front-end exception data meets the alarm conditions.

[0233] There is a corresponding relationship between the alarm condition and the coloring label.

[0234] That is, the management end can adopt different alarm mechanisms for different dyeing clients.

[0235] Indicatively, the customized alarm mechanism for the dyeing client includes at least the following four situations: First, when the colored label indicates that the client has unlocked the network acceleration permission, the management end generates a first alarm message for the front-end abnormal data that meets the first alarm condition.

[0236] Among them, the first alarm condition is used to indicate that the front-end abnormal data includes network quality data that meets the network abnormality condition.

[0237] Second, when the colored label indicates that the registration duration of the client account does not exceed a preset duration threshold, or the account activity of the client account reaches a preset activity, the management end generates a second alarm message for the front-end abnormal data that meets the second alarm condition.

[0238] Among them, the second alarm condition is used to indicate that the front-end abnormal data includes front-end response data that meets the operation abnormality condition.

[0239] The third type is that when the dyeing label indicates that the device model of the client meets the preset model type, the management end generates the third alarm information for the front-end abnormal data that meets the third alarm condition.

[0240] Among them, the third alarm condition is used to indicate that the front-end abnormal data includes resource quality data that meets the resource abnormality condition.

[0241] Fourthly, when the colored label indicates that the number of times the client account exits the client based on the front-end page abnormality within the historical time period reaches a preset number threshold, the management end generates a fourth alarm information for the front-end abnormal data that meets the fourth alarm condition.

[0242] Among them, the fourth alarm condition is used to indicate that the front-end abnormal data includes page loading data that meets the page abnormality condition.

[0243] It is worth noting that the above-mentioned alarm conditions and the matching relationship with the dyeing labels are only illustrative examples and are not limited to the embodiments of the present application.

[0244] For other implementation details, please refer to any of the above embodiments and will not be described in detail here.

[0245] To sum up, the method provided in the embodiment of the present application filters specific clients through coloring information, so that the management end can obtain the front-end abnormal data corresponding to the specific client, reduces the number of data reports in the data processing process, reduces the load pressure during abnormal data alarms, and improves the pertinence of alarm information. It can perform front-end abnormal alarms for specific clients, which not only improves the alarm response speed, but also improves the accuracy of the alarm information. Different abnormal reporting mechanisms and alarm mechanisms can be used for different colored accounts, thereby improving the abnormal reporting efficiency and alarm efficiency.

[0246] Figure 6 is a structural block diagram of a data processing device provided by an exemplary embodiment of the present application, such as Figure 6 As shown, the device includes the following parts: The acquisition module 610 is used to acquire an exception collection request, where the exception collection request is sent by the management end based on the coloring information, where the coloring information is used to indicate a screening condition when the management end screens the client; A reporting module 620, configured to report front-end abnormal data to the management end in response to the abnormal collection request, wherein the front-end abnormal data is front-end data generated by the client during operation that meets a preset abnormal condition, and there is a corresponding relationship between the preset abnormal condition and the screening condition corresponding to the dyeing information; The management end is used to generate alarm information for the front-end abnormal data that meets the preset alarm conditions when the client matches the dyeing information.

[0247] To sum up, the device provided in the embodiment of the present application filters specific client accounts through coloring information, so that the management end can obtain the front-end abnormal data corresponding to the specific account, reduces the number of data reports in the data processing process, reduces the load pressure during abnormal data alarms, improves the pertinence of alarm information, and can perform front-end abnormal alarms for specific accounts, which not only improves the alarm response speed, but also improves the accuracy of the alarm information. Different abnormal reporting mechanisms and alarm mechanisms can be used for different colored accounts, thereby improving the abnormal reporting efficiency and alarm efficiency.

[0248] Figure 7 is a structural block diagram of a data processing device provided by an exemplary embodiment of the present application, such as Figure 7 As shown, the device includes the following parts: An acquisition module 710 is used to acquire coloring information, where the coloring information is used to indicate a screening condition when screening clients; A sending module 720, configured to send the abnormality collection request to at least one of the multiple clients based on the dyeing information; A receiving module 730 is used to receive front-end abnormal data reported by the at least one client based on the abnormal collection request, wherein the front-end abnormal data is front-end data generated by the at least one client during operation that meets a preset abnormal condition, and there is a matching relationship between the preset abnormal condition and the screening condition corresponding to the dyeing information; The alarm module 740 is used to generate alarm information for the front-end abnormal data that meets the preset alarm conditions when the client matches the dyeing information.

[0249] To sum up, the device provided in the embodiment of the present application filters specific clients through staining information, so that the management end can obtain the front-end abnormal data corresponding to the specific client, reduces the number of data reports in the data processing process, alleviates the load pressure during abnormal data alarms, improves the pertinence of alarm information, and can perform front-end abnormal alarms for specific clients, which not only improves the alarm response speed, but also improves the accuracy of the alarm information. Different abnormal reporting mechanisms and alarm mechanisms can be used for different dyeing clients, thereby improving the abnormal reporting efficiency and alarm efficiency.

[0250] It should be noted that the data processing device provided in the above embodiment is only illustrated by the division of the above functional modules. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0251] Figure 8 The structure block diagram of a terminal 800 provided by an exemplary embodiment of the present application is shown. The terminal 800 may be: a smart phone, a tablet computer, an MP3 player, an MP4 player, a notebook computer or a desktop computer. The terminal 800 may also be called a user equipment, a portable terminal, a laptop terminal, a desktop terminal or other names.

[0252] Typically, the terminal 800 includes a processor 801 and a memory 802 .

[0253] The processor 801 may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor 801 may be implemented in at least one hardware form of digital signal processing (DSP), field-programmable gate array (FPGA), and programmable logic array (PLA). The processor 801 may also include a main processor and a coprocessor. The main processor is a processor for processing data in the awake state, also known as a central processing unit (CPU); the coprocessor is a low-power processor for processing data in the standby state. In some embodiments, the processor 801 may be integrated with a graphics processing unit (GPU), and the GPU is responsible for rendering and drawing the content to be displayed on the display screen. In some embodiments, the processor 801 may also include an artificial intelligence (AI) processor, which is used to process computing operations related to machine learning.

[0254] The memory 802 may include one or more computer-readable storage media, which may be non-transitory. The memory 802 may also include a high-speed random access memory, and a non-volatile memory, such as one or more disk storage devices, flash memory storage devices. In some embodiments, the non-transitory computer-readable storage medium in the memory 802 is used to store at least one instruction, which is used to be executed by the processor 801 to implement the data processing method provided in the method embodiment of the present application.

[0255] In some embodiments, the terminal 800 further includes other components 803, which can be understood by those skilled in the art. Figure 8 The structure shown in the figure does not constitute a limitation on the terminal 800, and the terminal 800 may include more or less components than those shown in the figure, or combine some components, or adopt a different component arrangement.

[0256] The embodiment of the present application also provides a computer device, which can be implemented as follows: Figure 1 The computer device includes a processor and a memory, wherein at least one instruction, at least one program, code set or instruction set is stored in the memory, and the at least one instruction, at least one program, code set or instruction set is loaded and executed by the processor to implement the data processing methods provided by the above-mentioned method embodiments.

[0257] An embodiment of the present application also provides a computer-readable storage medium, on which is stored at least one instruction, at least one program, code set or instruction set, and the at least one instruction, at least one program, code set or instruction set is loaded and executed by a processor to implement the data processing methods provided by the above-mentioned method embodiments.

[0258] The embodiments of the present application also provide a computer program product or a computer program, which includes a computer instruction stored in a computer-readable storage medium. The processor of the computer device reads the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the computer device executes the data processing method provided by the above-mentioned method embodiments.

[0259] Optionally, the computer readable storage medium may include: a read-only memory (ROM), a random access memory (RAM), a solid state drive (SSD) or an optical disk, etc. Among them, the random access memory may include a resistance random access memory (ReRAM) and a dynamic random access memory (DRAM). The serial numbers of the above embodiments of the present application are only for description and do not represent the advantages and disadvantages of the embodiments.

[0260] A person skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware or by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a disk or an optical disk, etc.

[0261] The above description is only an optional embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the protection scope of the present application.

Claims

1. A data processing system, characterized in that: The system includes a management terminal and multiple clients; The management end is used to obtain coloring information, where the coloring information is used to indicate a screening condition when screening the client; Sending the exception collection request to at least one client among the multiple clients based on the coloring information; The at least one client is used to receive the exception collection request; In response to the abnormal collection request, reporting front-end abnormal data to the management end, wherein the front-end abnormal data is front-end data generated by the at least one client during operation that meets a preset abnormal condition, and there is a matching relationship between the preset abnormal condition and the screening condition corresponding to the dyeing information; The management end is also used to receive the front-end abnormal data; In the case where the client matches the dyeing information, alarm information is generated for the front-end abnormal data that meets the preset alarm conditions.

2. The system according to claim 1, characterized in that The at least one client is further configured to obtain the front-end abnormal data that meets the preset abnormal condition based on the abnormal collection request, wherein the front-end abnormal data includes at least one of network quality data, front-end response data, resource quality data, and page loading data; The network quality data is used to indicate the network response status, the front-end response data is used to indicate the response status of the client to the front-end operation, the resource quality data is used to indicate the resource download status of the client, and the page loading data is used to indicate the front-end page loading status of the client.

3. The system according to claim 2, characterized in that The plurality of clients respectively correspond to client identifiers, and the coloring information is used to indicate an identifier screening condition when screening the clients according to the client identifiers; or, The multiple clients are respectively logged in with client accounts, and the coloring information is used to indicate a screening condition when screening the clients according to the client accounts.

4. The system according to claim 3, characterized in that The at least one client is further configured to report the network quality data that meets the network abnormality condition to the management end when the client matches the first coloring information, the first coloring information is used to indicate that the client has unlocked the network acceleration permission, and the network abnormality condition has the matching relationship with the screening condition indicated by the first coloring information; The at least one client is further used to report the front-end response data that meets the abnormal operation condition to the management end when the client matches the second coloring information, the second coloring information is used to indicate that the account registration time of the client account does not exceed a preset time threshold, or the account activity of the client account reaches a preset activity, and the abnormal operation condition has the matching relationship with the screening condition indicated by the second coloring information; The at least one client is further used to report the resource quality data that meets the resource abnormality condition to the management end when the client matches the third coloring information, the third coloring information is used to indicate that the device model of the client meets the preset model type, and the resource abnormality condition has the matching relationship with the screening condition indicated by the third coloring information; The at least one client is also used to report the page loading data that meets the page exception condition to the management end when the client matches the fourth coloring information. The fourth coloring information is used to indicate that the number of times the client account has exited the client based on the front-end page exception within a historical time period has reached a preset number threshold, and the page exception condition has the matching relationship with the screening condition indicated by the fourth coloring information.

5. The system according to any one of claims 1 to 4, characterized in that: The at least one client is further used to mark a coloring tag on the at least one client when the at least one client matches the coloring information, and the coloring tag is used to indicate that the at least one client meets the screening condition; based on the coloring tag, report the front-end abnormal data corresponding to the client to the management end, and the front-end abnormal data includes the coloring tag; or, The at least one client is further used to report the front-end abnormal data in full to the management end in response to the abnormal collection request, where the front-end abnormal data includes at least one of a client device identifier or a client account.

6. The system according to claim 5, characterized in that The management end is further used to receive the front-end abnormal data including the coloring label; based on the coloring label, when the front-end abnormal data meets the alarm condition, generate alarm information corresponding to the front-end abnormal data; or, The management end is further used to receive the front-end abnormal data; and mark the front-end abnormal data with the coloring label when at least one of the client identifier or the client account matches the coloring information; For the front-end abnormal data marked with the dyeing label, generating the alarm information when the front-end abnormal data meets the alarm condition; There is a corresponding relationship between the alarm condition and the dyeing label.

7. The system according to claim 6, characterized in that The management end is further configured to generate a first alarm message for the front-end abnormal data that meets a first alarm condition when the coloring tag indicates that the client has unlocked the network acceleration permission, wherein the first alarm condition is used to indicate that the front-end abnormal data includes network quality data; The management end is further configured to generate a second alarm message for the front-end abnormal data that meets the second alarm condition, when the colored label indicates that the account registration duration of the client account logged in by the client does not exceed a preset duration threshold, or when the account activity of the client account reaches a preset activity, wherein the second alarm condition is used to indicate that the front-end abnormal data includes the front-end response data; The management end is further configured to generate third alarm information for the front-end abnormal data that meets a third alarm condition when the dyeing label indicates that the device model of the client meets a preset model type, wherein the third alarm condition is used to indicate that the front-end abnormal data includes resource quality data; The management end is also used to generate a fourth alarm information for front-end abnormal data that meets the fourth alarm condition when the number of times the client account logged in by the client as indicated by the colored label reaches a preset number threshold within a historical time period due to front-end page abnormalities. The fourth alarm condition is used to indicate that the front-end abnormal data includes page loading data.

8. The system according to any one of claims 1 to 4, characterized in that: The at least one client is further configured to obtain the dyeing information from the management end through a dyeing interface, wherein the dyeing interface is an application programming interface between the management end and the at least one client; Alternatively, the dyeing information is obtained from the management end via a long link, where the long link is a real-time communication channel established between the at least one client and the management end.

9. The system according to claim 8, characterized in that The at least one client is further used to send a dyeing request to the management end according to the dyeing interface, wherein the dyeing request is used to request the management end for the dyeing information; The management end is further used to send the coloring information to the at least one client through the coloring interface in response to the coloring request.

10. The system according to claim 8, characterized in that The at least one client is further used to establish the long link with the management end, and the long link is used to receive the dyeing information pushed by the management end in real time; The management end is also used to send the dyeing information to the at least one client in real time through the long link.

11. A data processing method, characterized in that: The method is executed by a client, and includes: Acquire an exception collection request, where the exception collection request is sent by the management end based on the coloring information, where the coloring information is used to indicate a screening condition when the management end screens the client; In response to the abnormal collection request, reporting front-end abnormal data to the management end, wherein the front-end abnormal data is the front-end data generated by the client during operation that meets the preset abnormal conditions, and there is a corresponding relationship between the preset abnormal conditions and the screening conditions corresponding to the dyeing information; The management end is used to generate alarm information for the front-end abnormal data that meets the preset alarm conditions when the client matches the dyeing information.

12. A data processing method, characterized in that: The method is executed by a management terminal, and the method includes: Acquire coloring information, where the coloring information is used to indicate a screening condition when screening clients; Sending the exception collection request to at least one client among the multiple clients based on the staining information; Receiving front-end abnormal data reported by the at least one client based on the abnormal collection request, wherein the front-end abnormal data is front-end data generated by the at least one client during operation and meets a preset abnormal condition, and there is a matching relationship between the preset abnormal condition and the screening condition corresponding to the dyeing information; In the case where the client matches the dyeing information, alarm information is generated for the front-end abnormal data that meets the preset alarm conditions.

13. A data processing device, characterized in that: The device comprises: An acquisition module, used for acquiring an exception collection request, wherein the exception collection request is sent by the management end based on the coloring information, and the coloring information is used for indicating a screening condition when the management end screens the client; A reporting module, configured to report front-end abnormal data to the management end in response to the abnormal collection request, wherein the front-end abnormal data is front-end data generated by the client during operation that meets a preset abnormal condition, and there is a corresponding relationship between the preset abnormal condition and the screening condition corresponding to the dyeing information; The management end is used to generate alarm information for the front-end abnormal data that meets the preset alarm conditions when the client matches the dyeing information.

14. A data processing device, characterized in that: The device comprises: An acquisition module, used for acquiring coloring information, wherein the coloring information is used for indicating a screening condition when screening clients; A sending module, configured to send the abnormality collection request to at least one client among the multiple clients based on the dyeing information; A receiving module, configured to receive front-end abnormal data reported by the at least one client based on the abnormal collection request, wherein the front-end abnormal data is front-end data generated by the at least one client during operation and meets a preset abnormal condition, and there is a matching relationship between the preset abnormal condition and the screening condition corresponding to the dyeing information; The alarm module is used to generate alarm information for the front-end abnormal data that meets the preset alarm conditions when the client matches the dyeing information.

15. A computer device, characterized in that: The computer device includes a processor and a memory, wherein the memory stores at least one computer program, and the at least one computer program is loaded and executed by the processor to implement the data processing method according to claim 11 or 12.

Images