A data processing method, apparatus, device and medium

Abstract

This invention discloses a data processing method, apparatus, device, and medium. The method includes: acquiring user-inputted anomaly detection conditions corresponding to at least one front-end page, and sending them to the corresponding front-end page, so that each front-end page can detect whether abnormal operation behavior has occurred based on the corresponding anomaly detection conditions and report the relevant anomaly detection data; receiving the anomaly detection data reported by each front-end page and storing it in a preset anomaly database; receiving an anomaly data query request input by the user, the anomaly data query request carrying the identification information of the target front-end page; retrieving the anomaly detection data reported by the target front-end page from the anomaly database, and generating a visual chart for the user. This embodiment of the invention processes data related to abnormal operation behavior in front-end pages according to user needs, so that when an anomaly occurs on a front-end page, the user can quickly query data related to a specified abnormal operation behavior.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a data processing method, apparatus, device, and medium. Background Technology

[0002] When the front-end page meets the timing criteria, timing data can be generated and reported to the server. This data can then be used for subsequent user statistics analysis and strategy optimization. The timing criteria can be a specific action performed by the user on the front-end page. The timing data is the data related to the performed action and intended to be recorded on the server.

[0003] In related technologies, whenever the front-end page detects that various preset checkpoint conditions are met, it triggers the reporting of generated checkpoint data. The reported checkpoint data includes data related to each specified operation behavior, which is used for user statistical analysis and strategy optimization.

[0004] The drawback of this technology is that when an anomaly occurs on the front-end page, technical personnel need to search for data related to the abnormal operation in the log data to locate and resolve the problem. Front-end pages have a large number of functions, resulting in a correspondingly large amount of log data reported for user statistical analysis and strategy optimization. Searching for data related to abnormal operations from a large volume of log data is slow and may not even yield results for specific abnormal operations, hindering rapid problem location and resolution, causing significant time loss for users, and ultimately resulting in losses for the company. Summary of the Invention

[0005] This invention provides a data processing method, apparatus, device, and medium to address the problem that when an anomaly occurs on a front-end page, it is necessary to query data related to the abnormal operation behavior from a large amount of data. This query is slow and may not even find the data related to the specified abnormal operation behavior, resulting in the inability to quickly locate and resolve the problem, which affects users for a long time and causes losses to enterprises.

[0006] According to one aspect of the present invention, a data processing method is provided, comprising:

[0007] Get the exception handling conditions input by the user that correspond to at least one front-end page;

[0008] Each abnormal event condition is sent to the corresponding front-end page so that each front-end page can detect whether abnormal operation behavior has occurred based on the corresponding abnormal event condition, and report the abnormal event data related to the abnormal operation behavior when abnormal operation behavior is detected.

[0009] Receive the abnormal data reported by each of the aforementioned front-end pages, and store the abnormal data in a preset abnormal database;

[0010] Receive the abnormal data query request input by the user, wherein the abnormal data query request carries the identification information of the target front-end page;

[0011] Based on the identification information of the target front-end page, the abnormal data reported by the target front-end page is obtained from the preset abnormal database, a visual chart is generated to display the abnormal data reported by the target front-end page, and the visual chart is provided to the user.

[0012] According to another aspect of the present invention, a data processing apparatus is provided, comprising:

[0013] The condition acquisition module is used to acquire the exception handling conditions input by the user that correspond to at least one front-end page;

[0014] The condition sending module is used to send each abnormal point condition to the corresponding front-end page, so that each front-end page can detect whether abnormal operation behavior has occurred according to the corresponding abnormal point condition, and report the abnormal point data related to the abnormal operation behavior when abnormal operation behavior is detected.

[0015] The data storage module is used to receive the abnormal data reported by each of the front-end pages and store the abnormal data in a preset abnormal database.

[0016] The query request acquisition module is used to receive the abnormal data query request input by the user, wherein the abnormal data query request carries the identification information of the target front-end page;

[0017] The data display module is used to retrieve the abnormal data reported by the target front-end page from the preset abnormal database based on the identification information of the target front-end page, generate a visual chart to display the abnormal data reported by the target front-end page, and provide the visual chart to the user.

[0018] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0019] At least one processor; and

[0020] A memory communicatively connected to the at least one processor; wherein,

[0021] The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the data processing method according to any embodiment of the present invention.

[0022] According to another aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions for causing a processor to execute and implement the data processing method described in any embodiment of the present invention.

[0023] The technical solution of this invention involves obtaining user-inputted exception handling conditions corresponding to at least one front-end page; then sending each exception handling condition to the corresponding front-end page, so that each front-end page can detect whether abnormal operation behavior has occurred based on the corresponding exception handling conditions, and report the exception handling data related to the abnormal operation behavior when abnormal operation behavior is detected; receiving the exception handling data reported by each front-end page and storing the exception handling data in a preset exception database; and when receiving an exception data query request input by the user, retrieving the exception handling data reported by the target front-end page from the preset exception database based on the identification information of the target front-end page carried in the exception data query request, generating a visualization chart for displaying the exception handling data reported by the target front-end page, and providing the visualization chart to the user. This solves the problem that in related technologies, when an exception occurs on the front-end page, the exception handling data needs to be displayed in a way that is not readily available. Searching for data related to abnormal behavior from a large amount of data is slow and may not yield results for specific abnormal behaviors, hindering quick problem identification and resolution, causing significant time loss for users and potential losses for businesses. This problem can be addressed by allowing users to set abnormal data tracking conditions on the front-end page. The front-end page can automatically detect abnormal behavior based on these personalized settings and report relevant abnormal data in real time. It can also respond quickly to user requests for abnormal data, retrieving data from a dedicated database and visualizing it. This allows users to quickly identify and resolve issues based on the abnormal data, minimizing user downtime and reducing potential losses for businesses.

[0024] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0025] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0026] Figure 1 This is a flowchart of a data processing method provided in Embodiment 1 of the present invention.

[0027] Figure 2 This is a flowchart of a data processing method provided in Embodiment 2 of the present invention.

[0028] Figure 3 This is a schematic diagram of the structure of a data processing device provided in Embodiment 3 of the present invention.

[0029] Figure 4 A schematic diagram of the structure of an electronic device for implementing the data processing method of this embodiment of the invention. Detailed Implementation

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

[0031] It should be noted that the terms "target," "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising," "including," and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0032] Example 1

[0033] Figure 1This is a flowchart of a data processing method provided in Embodiment 1 of the present invention. This embodiment is applicable to situations where, according to user needs, data related to abnormal operation behaviors on a front-end page is processed, so that when an anomaly occurs on the front-end page, the user can quickly query data related to a specified abnormal operation behavior, quickly locate and resolve the problem. This method can be executed by a data processing device, which can be implemented in hardware and / or software and can be configured in an electronic device. For example, the electronic device can be a server for processing data related to abnormal operation behaviors on the front-end page.

[0034] like Figure 1 As shown, the method includes:

[0035] Step 101: Obtain the exception handling conditions input by the user that correspond to at least one front-end page.

[0036] Optionally, the user can be the developer or maintainer of the front-end pages. At least one front-end page is managed by the user.

[0037] Optionally, the exception tracking conditions corresponding to the front-end page are used to detect whether abnormal operations have occurred on the front-end page, and whether it is necessary to report exception tracking data related to abnormal operations. The exception tracking conditions corresponding to the front-end page can be abnormal operations performed by users on the front-end page. Abnormal operations are those actions that cause abnormalities on the front-end page.

[0038] Optionally, obtaining the abnormal event tracking conditions input by the user corresponding to at least one front-end page includes: obtaining an abnormal event tracking configuration file uploaded by the user; wherein the abnormal event tracking configuration file contains abnormal event tracking conditions corresponding to at least one front-end page.

[0039] Optionally, the exception handling configuration file is a file used to store the exception handling conditions corresponding to each front-end page, containing the exception handling conditions for each front-end page. The user encapsulates the exception handling conditions corresponding to each front-end page into an exception handling configuration file, and then uploads the exception handling configuration file to the electronic device. The electronic device obtains the exception handling configuration file uploaded by the user and extracts the exception handling conditions corresponding to each front-end page from the exception handling configuration file.

[0040] Optionally, obtaining the exception handling conditions input by the user corresponding to at least one front-end page includes: obtaining the exception handling conditions input by the user corresponding to at least one front-end page through the exception configuration page.

[0041] Optionally, an exception configuration page is a page set up in an electronic device to obtain exception handling conditions corresponding to at least one front-end page based on user interaction. The exception configuration page contains condition input areas corresponding to each front-end page. These condition input areas are page areas used to input exception handling conditions corresponding to each front-end page. Users can fill in or select exception handling conditions corresponding to each front-end page in these areas. The exception handling conditions for different front-end pages can be the same or different.

[0042] In a specific example, the first front-end page and the second front-end page are different front-end pages. The electronic device acquires the abnormal point marking conditions corresponding to the first front-end page and the second front-end page, as input by the user. The abnormal point marking conditions corresponding to the first front-end page include: the frequency of click operations by the user on the first front-end page exceeds a first preset frequency threshold; the frequency of swipe operations by the user on the first front-end page exceeds a second preset frequency threshold. The abnormal point marking conditions corresponding to the second front-end page include: the number of times the user modifies the content entered on the second front-end page exceeds a preset number threshold; the time taken by the user to enter content on the second front-end page is less than a preset time threshold.

[0043] Step 102: Send each abnormality checkpoint condition to the corresponding front-end page, so that each front-end page can detect whether abnormal operation behavior has occurred according to the corresponding abnormality checkpoint condition, and report the abnormality checkpoint data related to the abnormal operation behavior when abnormal operation behavior is detected.

[0044] Optionally, the electronic device sends each anomaly tracking condition to the corresponding front-end page. Each front-end page receives the corresponding anomaly tracking condition, and then, based on the corresponding anomaly tracking condition, detects whether any abnormal operation has occurred on the front-end page. When an abnormal operation is detected, the front-end page reports the anomaly tracking data related to the abnormal operation. The anomaly tracking condition corresponding to the front-end page is that the user performs an abnormal operation on the front-end page.

[0045] Optionally, the front-end page detects whether abnormal operation behavior occurs on each front-end page according to the corresponding abnormal operation point conditions, and reports the abnormal operation point data related to the abnormal operation behavior when abnormal operation behavior is detected. This includes: the front-end page detects the operation behavior performed by the user on the front-end page; when the front-end page detects that the user on the front-end page has performed abnormal operation behavior, it determines that abnormal operation behavior has occurred on the front-end page and reports the abnormal operation point data related to the abnormal operation behavior to the electronic device.

[0046] Optionally, the anomaly tracking data related to the abnormal operation is data that is relevant to the abnormal operation and needs to be recorded in the electronic device. The anomaly tracking data related to the abnormal operation includes, but is not limited to: the type and time information of the abnormal operation corresponding to the abnormal operation. The abnormal operation type refers to the type of abnormal operation that occurred.

[0047] Optionally, the abnormal operation behavior is when the click operation frequency exceeds a first preset frequency threshold. The abnormal operation behavior type corresponding to this abnormal operation behavior is abnormal click frequency. The time information corresponding to this abnormal operation behavior includes: the time when the click operation occurred and the click operation frequency.

[0048] Optionally, an abnormal operation is defined as the number of times the entered content is modified exceeds a preset threshold. The abnormal operation type corresponding to this is "Entry Modification Abnormality". The time information corresponding to this abnormal operation includes: the time when the content modification operation occurred.

[0049] In a specific example, the abnormal tracking conditions corresponding to the first front-end page include: the frequency of click operations performed by the user on the first front-end page exceeds a first preset frequency threshold; and the frequency of swipe operations performed by the user on the first front-end page exceeds a second preset frequency threshold. The first front-end page detects the user's actions on the first front-end page. When the first front-end page detects that the frequency of click operations performed by the user on the first front-end page exceeds the first preset frequency threshold, it determines that an abnormal operation has occurred and reports the abnormal tracking data related to this click operation frequency exceeding the first preset frequency threshold to the electronic device. Similarly, when the first front-end page detects that the frequency of swipe operations performed by the user on the first front-end page exceeds the second preset frequency threshold, it determines that an abnormal operation has occurred and reports the abnormal tracking data related to this swipe operation frequency exceeding the second preset frequency threshold to the electronic device.

[0050] In another specific example, the abnormal tracking conditions corresponding to the second front-end page include: the number of times the user modifies the content entered on the second front-end page exceeds a preset threshold; and the time taken by the user to enter content on the second front-end page is less than a preset time threshold. The second front-end page detects the user's actions on the second front-end page. When the second front-end page detects that the number of times the user modifies the content entered on the second front-end page exceeds the preset threshold, it determines that an abnormal operation has occurred and reports the abnormal tracking data related to this abnormal operation to the electronic device. Similarly, when the second front-end page detects that the time taken by the user to enter content on the second front-end page is less than a preset time threshold, it determines that an abnormal operation has occurred and reports the abnormal tracking data related to this abnormal operation to the electronic device.

[0051] Optionally, after sending each exception tracking condition to the corresponding front-end page, the method further includes: obtaining the update exception tracking conditions input by the user corresponding to each of the front-end pages; sending each update exception tracking condition to the corresponding front-end page, so that each of the front-end pages can detect whether an abnormal operation has occurred based on the corresponding update exception tracking condition, and when an abnormal operation is detected, reporting the exception tracking data related to the abnormal operation.

[0052] Optionally, the update anomaly tracking conditions corresponding to each of the aforementioned front-end pages are new anomaly tracking conditions determined by the user based on business needs. The electronic device acquires the update anomaly tracking conditions input by the user for each of the aforementioned front-end pages and sends these conditions to the corresponding front-end pages. Each front-end page detects whether any abnormal operation has occurred based on the corresponding update anomaly tracking conditions, and reports the anomaly tracking data related to the detected abnormal operation. Therefore, users can not only personalize the anomaly tracking conditions for each front-end page but also update these conditions in real time according to business needs.

[0053] Step 103: Receive the abnormal data reported by each of the front-end pages and store the abnormal data in a preset abnormal database.

[0054] Optionally, the preset exception database is a library used to store exception tracking data reported by each of the aforementioned front-end pages. The preset exception database can be a third-party library for storing exception tracking data reported by each of the aforementioned front-end pages, or it can be a relational database or a non-relational database for storing exception tracking data reported by each of the aforementioned front-end pages. The electronic device receives the exception tracking data reported by each of the aforementioned front-end pages and stores the exception tracking data in the preset exception database.

[0055] Optionally, the electronic device receives service tracking data uploaded by the user and stores the service tracking data in a preset service database. Users can collect service tracking data from various front-end pages and upload this data to the electronic device for storage.

[0056] Optionally, after obtaining the abnormal event tracking conditions input by the user corresponding to at least one front-end page, the method further includes: receiving business event tracking data reported by each of the front-end pages, and storing the business event tracking data in a preset business database; wherein, the business event tracking data reported by each of the front-end pages is event tracking data reported by each of the front-end pages according to preset business event tracking conditions. Each front-end page is also used to report business event tracking data for user statistical analysis and strategy optimization according to preset business event tracking conditions.

[0057] Optionally, the preset business trigger conditions are that the user performs a business operation on the front-end page. Business operations include, but are not limited to: clicking the registration control, clicking the login control, and clicking the payment control on the front-end page.

[0058] Optionally, the front-end page reports business tracking data based on preset business tracking conditions, including: the front-end page detecting the operations performed by users on the front-end page; when the front-end page detects that users are performing business operations on the front-end page, it determines that a business operation has occurred and reports the business tracking data related to the business operation to the electronic device.

[0059] Optionally, business tracking data related to the occurring business operations are data that is relevant to the occurring business operations and needs to be recorded in the electronic device. Business tracking data related to the occurring business operations includes, but is not limited to: the type and time information of the business operation corresponding to the occurring business operation. The business operation type refers to the type of business operation that occurred.

[0060] Optionally, the business operation is clicking the registration control on the front-end page. The business operation type is "registration". The time information corresponding to this business operation includes the time when the operation of clicking the registration control on the front-end page occurred.

[0061] Optionally, the electronic device receives the service tracking data reported by each of the aforementioned front-end pages and stores the service tracking data in a preset service database. The preset service database is a library used to store the service tracking data reported by each of the aforementioned front-end pages. The service tracking data reported by each of the aforementioned front-end pages can be used for user statistical analysis and strategy optimization.

[0062] Step 104: Receive the abnormal data query request input by the user, wherein the abnormal data query request carries the identification information of the target front-end page.

[0063] Optionally, an exception data query request is used to request exception tracking data reported by a target front-end page. The target front-end page can be one or more front-end pages where an exception has occurred and exception tracking data needs to be queried. The identification information of each front-end page is used to distinguish between different front-end pages. Each front-end page has unique identification information.

[0064] Optionally, users can enter an abnormal data query request by filling in or selecting the identifier information of the target front-end page on the abnormal data processing page provided by the electronic device. The abnormal data processing page is used to interact with the user, obtain information related to the front-end page entered by the user, or display various information related to the abnormal data reported by the front-end page.

[0065] Step 105: Based on the identification information of the target front-end page, obtain the abnormal data reported by the target front-end page from the preset abnormal database, generate a visualization chart to display the abnormal data reported by the target front-end page, and provide the visualization chart to the user.

[0066] Optionally, the electronic device establishes a correspondence between the identification information of each front-end page and the abnormal data reported by each front-end page, and stores the identification information of each front-end page and the abnormal data reported by each front-end page in a preset abnormal database.

[0067] Optionally, based on the identification information of the target front-end page, the abnormal data reported by the target front-end page can be obtained from the preset abnormal database. This includes: the electronic device queries all the identification information stored in the preset abnormal database for target identification information that is the same as the identification information of the target front-end page, and then obtains the abnormal data corresponding to the target identification information.

[0068] Optionally, generating a visualization chart to display the abnormal data reported on the target front-end page includes: generating a visualization chart to display the abnormal data reported on the target front-end page based on the abnormal data reported on the target front-end page and preset chart configuration information.

[0069] Optionally, the preset chart configuration information includes all the information required to generate a specified visualization, including the chart type and chart generation rules. The chart type refers to the type of visualization. The visualization type can be a table. The chart generation rules are the rules used to generate the visualization based on the data to be displayed.

[0070] Optionally, providing the visualization chart to the user includes displaying the visualization chart on an anomaly data processing page. The anomaly data processing page is used to interact with the user, obtain information input by the user related to the front-end page, or display various types of information related to the anomaly data reported on the front-end page.

[0071] Optionally, after receiving the abnormal data query request input by the user, the method further includes: verifying the identity and permissions of the abnormal data query request; if the identity verification and permission verification are successful, then based on the identification information of the target front-end page, the abnormal data reported by the target front-end page is obtained from the preset abnormal database, a visual chart for displaying the abnormal data reported by the target front-end page is generated, and the visual chart is provided to the user.

[0072] Optionally, the abnormal data query request is authenticated, including: obtaining a preset set of identity information, which contains identity information of each queried abnormal data point; determining whether there is identity information in the preset set of identity information that is the same as the identity information in the abnormal data query request; if so, then the authentication is confirmed to be successful; if not, then the authentication is confirmed to be successful.

[0073] Optionally, the abnormal data query request is subject to permission verification, including: obtaining a preset set of permission identifier information, which contains permission identifier information for querying abnormal data; determining whether there is permission identifier information in the preset set of permission identifier information that is the same as the permission identifier information in the abnormal data query request; if yes, then the permission verification is deemed successful; if no, then the permission verification is deemed successful.

[0074] Optionally, after verifying identity and permissions for the abnormal data query request, the method further includes: if identity verification or permission verification fails, providing a query failure message to the user. The query failure message indicates that identity verification or permission verification failed, and the abnormal data reported on the target front-end page cannot be queried.

[0075] The technical solution of this invention involves obtaining user-inputted exception handling conditions corresponding to at least one front-end page; then sending each exception handling condition to the corresponding front-end page, so that each front-end page can detect whether abnormal operation behavior has occurred based on the corresponding exception handling conditions, and report the exception handling data related to the abnormal operation behavior when abnormal operation behavior is detected; receiving the exception handling data reported by each front-end page and storing the exception handling data in a preset exception database; and when receiving an exception data query request input by the user, retrieving the exception handling data reported by the target front-end page from the preset exception database based on the identification information of the target front-end page carried in the exception data query request, generating a visualization chart for displaying the exception handling data reported by the target front-end page, and providing the visualization chart to the user. This solves the problem that in related technologies, when an exception occurs on the front-end page, the exception handling data needs to be displayed in a way that is not readily available. Searching for data related to abnormal behavior from a large amount of data is slow and may not yield results for specific abnormal behaviors, hindering quick problem identification and resolution, causing significant time loss for users and potential losses for businesses. This problem can be addressed by allowing users to set abnormal data tracking conditions on the front-end page. The front-end page can automatically detect abnormal behavior based on these personalized settings and report relevant abnormal data in real time. It can also respond quickly to user requests for abnormal data, retrieving data from a dedicated database and visualizing it. This allows users to quickly identify and resolve issues based on the abnormal data, minimizing user downtime and reducing potential losses for businesses.

[0076] Example 2

[0077] Figure 2 This is a flowchart of a data processing method provided in Embodiment 2 of the present invention. This embodiment of the present invention can be combined with various optional solutions from one or more of the above embodiments. For example... Figure 2 As shown, the method includes:

[0078] Step 201: Obtain the exception handling conditions input by the user that correspond to at least one front-end page.

[0079] Step 202: Send each abnormality tracking condition to the corresponding front-end page, so that each front-end page can detect whether abnormal operation behavior has occurred according to the corresponding abnormality tracking condition, and report the abnormality tracking data related to the abnormal operation behavior when abnormal operation behavior is detected.

[0080] Step 203: Receive the abnormal data reported by each of the front-end pages and store the abnormal data in a preset abnormal database.

[0081] Step 204: Receive the abnormal data query request input by the user, wherein the abnormal data query request carries the identification information of the target front-end page.

[0082] Step 205: Verify the identity and permissions of the abnormal data query request.

[0083] Optionally, the abnormal data query request is authenticated, including: obtaining a preset set of identity information, which contains identity information of each queried abnormal data point; determining whether there is identity information in the preset set of identity information that is the same as the identity information in the abnormal data query request; if so, then the authentication is confirmed to be successful; if not, then the authentication is confirmed to be successful.

[0084] Optionally, the abnormal data query request is subject to permission verification, including: obtaining a preset set of permission identifier information, which contains permission identifier information for querying abnormal data; determining whether there is permission identifier information in the preset set of permission identifier information that is the same as the permission identifier information in the abnormal data query request; if yes, then the permission verification is deemed successful; if no, then the permission verification is deemed successful.

[0085] Step 206: If the identity verification and permission verification are successful, then based on the identification information of the target front-end page, retrieve the abnormal data reported by the target front-end page from the preset abnormal database, generate a visualization chart to display the abnormal data reported by the target front-end page, and provide the visualization chart to the user.

[0086] Optionally, based on the identification information of the target front-end page, the abnormal data reported by the target front-end page can be obtained from the preset abnormal database. This includes: the electronic device queries all the identification information stored in the preset abnormal database for target identification information that is the same as the identification information of the target front-end page, and then obtains the abnormal data corresponding to the target identification information.

[0087] Optionally, generating a visualization chart to display the abnormal data reported on the target front-end page includes: generating a visualization chart to display the abnormal data reported on the target front-end page based on the abnormal data reported on the target front-end page and preset chart configuration information.

[0088] Optionally, the preset chart configuration information includes all the information required to generate a specified visualization, including the chart type and chart generation rules. The chart type refers to the type of visualization. The visualization type can be a table. The chart generation rules are the rules used to generate the visualization based on the data to be displayed.

[0089] Optionally, providing the visualization chart to the user includes displaying the visualization chart on an anomaly data processing page. The anomaly data processing page is used to interact with the user, obtain information input by the user related to the front-end page, or display various types of information related to the anomaly data reported on the front-end page.

[0090] Optionally, after verifying identity and permissions for the abnormal data query request, the method further includes: if identity verification or permission verification fails, providing a query failure message to the user. The query failure message indicates that identity verification or permission verification failed, and the abnormal data reported on the target front-end page cannot be queried.

[0091] The technical solution of this invention allows users to set abnormal event tracking conditions for the front-end page according to their needs. This enables the front-end page to automatically detect abnormal operations based on these personalized conditions. Upon detecting abnormal operations, it reports relevant abnormal event tracking data in real time. The system can also respond to user requests for abnormal data by performing identity and permission verification. Once both verification and permission verification are successful, the system quickly retrieves the abnormal event tracking data from a dedicated database and displays it visually. This allows users to quickly locate and resolve problems based on the abnormal event tracking data, reducing user downtime and minimizing losses for businesses.

[0092] Example 3

[0093] Figure 3 This is a schematic diagram of a data processing device according to Embodiment 3 of the present invention. The device can be configured in an electronic device. Figure 3 As shown, the device includes: a condition acquisition module 301, a condition sending module 302, a data storage module 303, a query request acquisition module 304, and a data display module 305.

[0094] The system includes the following modules: a condition acquisition module 301, used to acquire user-inputted exception handling conditions corresponding to at least one front-end page; a condition sending module 302, used to send each exception handling condition to the corresponding front-end page, so that each front-end page can detect whether an abnormal operation has occurred based on the corresponding exception handling condition, and report the exception handling data related to the abnormal operation when an abnormal operation is detected; a data storage module 303, used to receive the exception handling data reported by each front-end page and store the exception handling data in a preset exception database; a query request acquisition module 304, used to receive the user-input exception data query request, the exception data query request carrying the identification information of the target front-end page; and a data display module 305, used to acquire the exception handling data reported by the target front-end page from the preset exception database based on the identification information of the target front-end page, generate a visual chart for displaying the exception handling data reported by the target front-end page, and provide the visual chart to the user.

[0095] The technical solution of this invention involves obtaining user-inputted exception handling conditions corresponding to at least one front-end page; then sending each exception handling condition to the corresponding front-end page, so that each front-end page can detect whether abnormal operation behavior has occurred based on the corresponding exception handling conditions, and report the exception handling data related to the abnormal operation behavior when abnormal operation behavior is detected; receiving the exception handling data reported by each front-end page and storing the exception handling data in a preset exception database; and when receiving an exception data query request input by the user, retrieving the exception handling data reported by the target front-end page from the preset exception database based on the identification information of the target front-end page carried in the exception data query request, generating a visualization chart for displaying the exception handling data reported by the target front-end page, and providing the visualization chart to the user. This solves the problem that in related technologies, when an exception occurs on the front-end page, the exception handling data needs to be displayed in a way that is not readily available. Searching for data related to abnormal behavior from a large amount of data is slow and may not yield results for specific abnormal behaviors, hindering quick problem identification and resolution, causing significant time loss for users and potential losses for businesses. This problem can be addressed by allowing users to set abnormal data tracking conditions on the front-end page. The front-end page can automatically detect abnormal behavior based on these personalized settings and report relevant abnormal data in real time. It can also respond quickly to user requests for abnormal data, retrieving data from a dedicated database and visualizing it. This allows users to quickly identify and resolve issues based on the abnormal data, minimizing user downtime and reducing potential losses for businesses.

[0096] In an optional embodiment of the present invention, the condition acquisition module 301 is specifically used to: acquire the abnormal point configuration file uploaded by the user; wherein the abnormal point configuration file contains abnormal point conditions corresponding to at least one front-end page.

[0097] In an optional embodiment of the present invention, the condition acquisition module 301 is specifically used to: acquire, through the exception configuration page, the exception marking conditions input by the user that correspond to at least one front-end page.

[0098] In an optional embodiment of the present invention, the condition sending module 302 may be further configured to: obtain update exception marking conditions input by the user corresponding to each of the front-end pages; send each update exception marking condition to the corresponding front-end page, so that each of the front-end pages can detect whether an abnormal operation has occurred based on the corresponding update exception marking condition, and report the exception marking data related to the abnormal operation when an abnormal operation is detected.

[0099] In an optional embodiment of the present invention, the data processing device may further include: a request verification module, configured to perform identity verification and permission verification on the abnormal data query request; and a first data providing module, configured to, if the identity verification and permission verification are successful, obtain the abnormal data reported by the target front-end page from the preset abnormal database according to the identification information of the target front-end page, generate a visualization chart for displaying the abnormal data reported by the target front-end page, and provide the visualization chart to the user.

[0100] In an optional embodiment of the present invention, the data processing device may further include: a second data providing module, configured to provide a query failure message to the user if authentication or authorization fails.

[0101] In an optional embodiment of the present invention, the data processing device may further include: a business tracking data receiving module, configured to receive business tracking data reported by each of the front-end pages and store the business tracking data in a preset business database; wherein the business tracking data reported by each of the front-end pages is tracking data reported by each of the front-end pages according to preset business tracking conditions.

[0102] Regarding the apparatus in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0103] The above-described data processing device can execute the data processing method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects for executing the data processing method.

[0104] Example 4

[0105] Figure 4A schematic diagram of an electronic device 10, which can be used to implement the data processing method of embodiments of the present invention, is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0106] like Figure 4 As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or a computer program constructed from storage unit 18 into the RAM 13. The RAM 13 can also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0107] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0108] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as data processing methods.

[0109] In some embodiments, the data processing method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or mounted on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is built into RAM 13 and executed by processor 11, one or more steps of the data processing method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform the data processing method by any other suitable means (e.g., by means of firmware).

[0110] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0111] Computer programs for implementing the data processing methods of the present invention can be written in any combination of one or more programming languages. These computer programs can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The computer programs can be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0112] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0113] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0114] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0115] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through a communication network. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0116] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0117] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A data processing method, characterized in that, include: Get the exception handling conditions input by the user that correspond to at least one front-end page; Each abnormal event condition is sent to the corresponding front-end page so that each front-end page can detect whether abnormal operation behavior has occurred based on the corresponding abnormal event condition, and report the abnormal event data related to the abnormal operation behavior when abnormal operation behavior is detected. Receive the abnormal data reported by each of the aforementioned front-end pages, and store the abnormal data in a preset abnormal database; Receive the abnormal data query request input by the user, wherein the abnormal data query request carries the identification information of the target front-end page; Based on the identification information of the target front-end page, retrieve the abnormal data reported by the target front-end page from the preset abnormal database, generate a visualization chart to display the abnormal data reported by the target front-end page, and provide the visualization chart to the user. After sending each exception handling condition to the corresponding front-end page, the following is also included: Obtain the update exception handling conditions corresponding to each of the aforementioned front-end pages, as input by the user; wherein, the update exception handling conditions corresponding to each of the aforementioned front-end pages are new exception handling conditions determined by the user according to business requirements and corresponding to each of the aforementioned front-end pages. Each update anomaly tracking condition is sent to the corresponding front-end page, so that each front-end page can detect whether an abnormal operation has occurred based on the corresponding update anomaly tracking condition, and report the anomaly tracking data related to the abnormal operation when an abnormal operation is detected.

2. The method according to claim 1, characterized in that, The method for obtaining user-input exception handling conditions corresponding to at least one front-end page includes: Retrieve the user-uploaded exception handling configuration file; The exception handling configuration file contains exception handling conditions corresponding to at least one front-end page.

3. The method according to claim 1, characterized in that, The method for obtaining user-input exception handling conditions corresponding to at least one front-end page includes: The exception configuration page retrieves the exception handling conditions input by the user that correspond to at least one front-end page.

4. The method according to claim 1, characterized in that, After receiving the abnormal data query request input by the user, the method further includes: The abnormal data query request is subject to identity verification and permission verification. If authentication and permission verification are successful, the system retrieves the anomaly tracking data reported by the target front-end page from the preset anomaly database based on the identification information of the target front-end page, generates a visualization chart to display the anomaly tracking data reported by the target front-end page, and provides the visualization chart to the user.

5. The method according to claim 4, characterized in that, After verifying the identity and permissions of the abnormal data query request, the process also includes: If authentication or authorization fails, a query failure message will be provided to the user.

6. The method according to claim 1, characterized in that, After obtaining the exception handling conditions corresponding to at least one front-end page from the user input, the following is also included: Receive business tracking data reported by each of the aforementioned front-end pages and store the business tracking data in a preset business database; The business tracking data reported by each of the aforementioned front-end pages is the tracking data reported by each of the aforementioned front-end pages according to preset business tracking conditions.

7. A data processing apparatus, characterized in that, include: The condition acquisition module is used to acquire the exception handling conditions input by the user that correspond to at least one front-end page; The condition sending module is used to send each abnormal point condition to the corresponding front-end page, so that each front-end page can detect whether abnormal operation behavior has occurred according to the corresponding abnormal point condition, and report the abnormal point data related to the abnormal operation behavior when abnormal operation behavior is detected. The data storage module is used to receive the abnormal data reported by each of the front-end pages and store the abnormal data in a preset abnormal database. The query request acquisition module is used to receive the abnormal data query request input by the user, wherein the abnormal data query request carries the identification information of the target front-end page; The data display module is used to obtain the abnormal point data reported by the target front-end page from the preset abnormal database according to the identification information of the target front-end page, generate a visual chart for displaying the abnormal point data reported by the target front-end page, and provide the visual chart to the user. The condition sending module is also used for: Obtain the update exception handling conditions corresponding to each of the aforementioned front-end pages, as input by the user; wherein, the update exception handling conditions corresponding to each of the aforementioned front-end pages are new exception handling conditions determined by the user according to business requirements and corresponding to each of the aforementioned front-end pages. Each update anomaly tracking condition is sent to the corresponding front-end page, so that each front-end page can detect whether an abnormal operation has occurred based on the corresponding update anomaly tracking condition, and report the anomaly tracking data related to the abnormal operation when an abnormal operation is detected.

8. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the data processing method according to any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that cause a processor to execute the data processing method according to any one of claims 1-6.

Images