Page operation replay method, device, client, equipment and storage medium

By automatically acquiring and recombining the URLs of target pages, generating new processing chains, and replaying operations, the problem of low efficiency in manually acquiring root cause analysis data is solved, achieving efficient and cost-effective data acquisition.

CN112836151BActive Publication Date: 2024-11-12INDUSTRIAL AND COMMERCIAL BANK OF CHINA
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202110341315.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-03-30
Publication Date
2024-11-12
Estimated Expiration
2041-03-30

AI Technical Summary

Technical Problem

In existing technologies, obtaining data for root cause analysis requires manual access to multiple websites, resulting in slow data acquisition, cumbersome procedures, and low efficiency.

Method used

By automatically obtaining the URL of the target page, generating a new URL based on preset filtering conditions and configuration files, and reorganizing it into a new processing chain, automatic replay operation is achieved to obtain data.

Benefits of technology

This significantly reduced the time required to obtain data for root cause analysis, improved efficiency, saved labor costs, and provided a favorable foundation for quickly locating system problems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN112836151B_ABST
    Figure CN112836151B_ABST
Patent Text Reader

Abstract

The embodiment of the present specification provides a page operation replay method, device, client, equipment and storage medium, the method comprising: obtaining the uniform resource locator URL of the target page and forming a URL set; identifying one or more target URLs that meet the preset screening conditions from the URL set; parsing the target URL to obtain corresponding URL parameters; reconfiguring the URL parameters according to a preset configuration file, and generating one or more new URLs accordingly; reorganizing the new URLs into a new processing chain; replaying the operation of the new processing chain to obtain the data returned after the replay. The embodiment of the present specification can improve the efficiency of obtaining root cause analysis preparation data and save labor costs.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of Internet technology, and in particular to a page operation replay method, device, client, equipment and storage medium. Background Art

[0002] When the system encounters program errors, data errors, monitoring alarms, and other faults, the troubleshooting usually relies on manual operations to obtain the corresponding error files and data from the maintenance system and database system (that is, developers need to manually log in to each relevant website page to download the corresponding error files and data from the system) as preparation data for subsequent root cause analysis. However, since the relevant website pages generally have many levels and scattered menus, data acquisition is slow and the actions are cumbersome (even repetitive), and it often takes a lot of time and effort to obtain these data. Summary of the invention

[0003] The purpose of the embodiments of this specification is to provide a page operation replay method, apparatus, browser client, device and storage medium to improve the efficiency of obtaining root cause analysis preparation data and save labor costs.

[0004] To achieve the above objectives, on the one hand, an embodiment of this specification provides a page operation replay method, including:

[0005] Get the uniform resource locator URL of the target page and form a URL set;

[0006] Identify one or more target URLs that meet preset screening conditions from the URL set;

[0007] Parse the target URL and obtain corresponding URL parameters;

[0008] Reconfigure the URL parameters according to a preset configuration file, and generate one or more new URLs accordingly;

[0009] Reorganize the new URL into a new processing chain;

[0010] Replay the operations of the new processing chain to obtain data returned after the replay.

[0011] In an embodiment of the present specification, the step of identifying one or more target URLs satisfying a preset screening condition from the URL set includes:

[0012] According to the preset first keyword screening condition, the URLs in the URL set are subjected to keyword screening to identify each valid URL from the URL set.

[0013] In an embodiment of the present specification, before reconfiguring the URL parameters according to the preset configuration file, the method further includes:

[0014] According to the preset second keyword screening condition, the URL parameters are subjected to keyword screening to determine the URLs with actual business significance in the target URLs.

[0015] In an embodiment of this specification, the reconfiguring of the URL parameters according to a preset configuration file includes:

[0016] According to the preset configuration file, the URL parameters of the URL with actual business meaning are reconfigured.

[0017] In an embodiment of this specification, the reorganizing the new URL into a new processing chain includes:

[0018] The new URL and the URLs in the target URL that do not have actual business meanings are reorganized into a new processing chain.

[0019] In an embodiment of this specification, the operation of replaying the new processing chain includes:

[0020] The URLs in the new processing chain are called and accessed sequentially.

[0021] On the other hand, the embodiment of this specification also provides a page operation playback device, including:

[0022] The url acquisition module is used to obtain the url of the target page and form a url set;

[0023] A URL identification module is used to identify one or more target URLs that meet preset screening conditions from the URL set;

[0024] The url parsing module is used to parse the target url and obtain the corresponding url parameters;

[0025] The URL regeneration module is used to reconfigure the URL parameters according to a preset configuration file and generate one or more new URLs accordingly;

[0026] A processing chain regeneration module, used for reorganizing the new URL into a new processing chain;

[0027] The operation replay module is used to replay the operation of the new processing chain to obtain data returned after the replay.

[0028] On the other hand, the embodiments of the present specification further provide a browser client, wherein the browser client is configured with the above-mentioned page operation replay device.

[0029] On the other hand, an embodiment of the present specification further provides a computer device, including a memory, a processor, and a computer program stored in the memory, wherein when the computer program is executed by the processor, the instructions of the above method are executed.

[0030] On the other hand, an embodiment of the present specification further provides a computer storage medium on which a computer program is stored. When the computer program is executed by a processor of a computer device, the instructions of the above method are executed.

[0031] It can be seen from the technical solution provided by the above embodiments of this specification that in the embodiments of this specification, after identifying one or more target URLs that meet the preset screening conditions from the URL of the target page, its URL parameters are reconfigured according to the preset configuration file, and one or more new URLs are generated accordingly, the new URLs are reorganized into a new processing chain, and the operation of the new processing chain is replayed to obtain the data returned after the replay, thereby providing a method for automatically obtaining root cause analysis preparation data. Compared with the traditional manual acquisition method, the embodiments of this specification greatly shorten the time spent on obtaining root cause analysis preparation data, improve the efficiency of obtaining root cause analysis preparation data, save labor costs, and also provide a favorable basis for quickly entering the root cause analysis stage and locating system problems as early as possible. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the technical solutions in the embodiments of this specification or the prior art, the following briefly introduces the drawings required for use in the embodiments or the prior art description. Obviously, the drawings described below are only some embodiments recorded in this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative labor. In the drawings:

[0033] Figure 1 A flowchart of a page operation replay method in some embodiments of this specification is shown;

[0034] Figure 2 A structural block diagram of a browser client in some embodiments of this specification is shown;

[0035] Figure 3 It shows a structural block diagram of a page operation playback device in some embodiments of this specification;

[0036] Figure 4 The structure block diagram of the computer device in some embodiments of the present specification is shown.

[0037] [Description of Reference Numerals]

[0038] 31. URL acquisition module;

[0039] 32. URL identification module;

[0040] 33. URL parsing module;

[0041] 34. URL regeneration module;

[0042] 35. Processing chain regeneration module;

[0043] 36. Operation replay module;

[0044] 402. Computer equipment;

[0045] 404, processor;

[0046] 406. Memory;

[0047] 408, driving mechanism;

[0048] 410, input / output module;

[0049] 412. Input devices;

[0050] 414. Output device;

[0051] 416. Presentation equipment;

[0052] 418. Graphical user interface;

[0053] 420, network interface;

[0054] 422. Communication link;

[0055] 424. Communication bus. DETAILED DESCRIPTION

[0056] In order to enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the drawings in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this specification.

[0057] As a means of ensuring software quality, the root cause analysis (i.e., root cause analysis) of business system test problems is an inevitable stage in the development process. After the business system is put into operation, root cause analysis is generally required when program operation errors, data errors, monitoring alarms, and other faults occur. In order to prepare data for root cause analysis, in this case, relevant personnel (such as developers, testers, operation and maintenance personnel, etc.) are usually not allowed to directly access the relevant websites of the test or production environment to obtain information. They usually need to access multiple websites to query and download relevant system logs, database information, etc. Moreover, the same type of problem occurs multiple times, and relevant personnel need to repeat these steps to obtain data before analyzing the problem each time. In addition, since the relevant website pages generally have many levels and scattered menus, data acquisition is slow and the actions are cumbersome (even repetitive), and it often takes a lot of time and effort to obtain these data. In short, the current method of manually obtaining root cause analysis preparation data (i.e., data prepared or provided for root cause analysis) is time-consuming and labor-intensive, and inefficient.

[0058] In view of this, in order to solve the above problems, this specification provides an embodiment of a page operation replay method, which can be applied to a computer device. Figure 1 As shown, in some embodiments of this specification, the page operation replay method may include the following steps:

[0059] S101, obtaining the uniform resource locator (URL) of a target page and forming a URL set.

[0060] S102: Identify one or more target URLs that meet preset screening conditions from the URL set.

[0061] S103, parsing the target URL to obtain corresponding URL parameters.

[0062] S104: reconfigure the URL parameters according to a preset configuration file, and generate one or more new URLs accordingly.

[0063] S105: Reorganize the new URL into a new processing chain.

[0064] S106: Replay the operation of the new processing chain to obtain data returned after the replay.

[0065] In the embodiment of the present specification, after identifying one or more target URLs that meet the preset screening conditions from the URL of the target page, the URL parameters are reconfigured according to the preset configuration file, and one or more new URLs are generated accordingly, the new URLs are reorganized into a new processing chain, and the operation of the new processing chain is replayed to obtain the data returned after the replay, thereby providing a method for automatically obtaining root cause analysis preparation data. Compared with the traditional manual acquisition method, the embodiment of the present specification greatly shortens the time spent on obtaining root cause analysis preparation data, improves the efficiency of obtaining root cause analysis preparation data, saves labor costs, and also provides a favorable basis for quickly entering the root cause analysis stage and locating system problems early.

[0066] The target page is generally a plurality of pages. In some embodiments of this specification, all URLs of the target page can be automatically obtained by using JS (JavaScript) scripts, thereby forming a URL set. Of course, this is only an illustrative example. In other embodiments of this specification, any known method of automatically obtaining page URLs can be used as needed, and this specification does not limit this to a single method.

[0067] In the process of accessing the target website or system, a lot of URLs will be generated. Among them, some of these URLs are valid URLs (i.e., URLs related to the root cause analysis preparation data) and invalid URLs (i.e., URLs unrelated to the root cause analysis preparation data). Among them, invalid URLs may be, for example, URLs corresponding to images, audio, video, etc. loaded in the target page. The root cause analysis preparation data is generally data related to logs, etc. (such as program log files, monitoring files of the monitoring system, data records in the database, etc.), while the images, audio, video, page styles (css), etc. loaded in the target page are generally unrelated to data such as logs. Therefore, in order to help reduce the amount of calculation, these invalid URLs can be removed from the above URL set in advance.

[0068] In one embodiment of the present specification, the identifying of one or more target URLs satisfying preset screening conditions from the URL set may include: performing keyword screening on the URLs of the URL set according to a preset keyword screening first condition, so as to identify each valid URL from the URL set. The keyword screening first condition may be implemented by a preset regular expression or the like. For example, a filtering blacklist may be set by a regular expression, and the filtering blacklist may contain some keywords (e.g., .jpg, .css, etc.), and all URLs containing one or more of these keywords are identified as invalid URLs. In this way, each valid URL may be identified from the URL set.

[0069] For example, in some exemplary embodiments, the following two URLs are provided.

[0070] url1:

[0071] https: / / i.guancha.cn / news / mainland / 2021 / 03 / 12 / 20210312080843676.jpg

[0072] url2:

[0073] https: / / console.cloud.tencent.com / cls / search?region= <region>&logset_id=<logset_id> &topic_id=<topic_id>

[0074] Since url1 contains the keyword ".jpg", url1 can be considered an invalid URL. However, url2 does not contain keywords such as ".jpg" and ".css", so url2 can be considered a valid URL.

[0075] In some embodiments of the present specification, any suitable URL parsing method may be used to parse the target URL. For example, the target URL may be parsed by a URL parsing tool such as httpclient, jetty, tomcat, etc., or by a JavaScript split method or a custom regular expression. By parsing the target URL, the corresponding URL parameters may be obtained, that is, the request header and body in the target URL may be obtained, wherein the parameter information in the body is the obtained URL parameters, so that these URL parameters may be reconfigured as needed later, so that different new URLs may be spliced ​​out according to different operation configurations.

[0076] In some embodiments of the present specification, before the url parameters are reconfigured according to the preset configuration file, the url parameters can also be keyword-filtered according to the preset keyword-filtering second condition to determine the urls with actual business meanings in the target url, and for the urls with actual business meanings (such as urls with log names, urls for step-by-step directory jumps, etc.), their url parameters can be recorded. Among them, the url with actual business meanings can refer to non-universal urls. Correspondingly, the urls that do not have actual business meanings are universal urls (such as login urls with login, and logout urls with logout). In this way, it can be helpful to further improve processing efficiency.

[0077] For example, when obtaining logs from the log file directory of the operation and maintenance system of the business system, you need to log in to the operation and maintenance system first, then jump to the log directory level by level, then download the log according to the log file name, and finally exit the operation and maintenance system. In this process, a login URL, a URL for jumping to the directory level by level, a URL with a log name, and a logout URL will be generated. The login and logout URLs are required for operating any system, so they are URLs without actual business meaning, while the jump directory and log acquisition URLs are the core URLs of this operation, that is, URLs related to actual business. Therefore, the directory and log file name information in these URLs related to actual business can be recorded.

[0078] The specific implementation of the second condition for keyword screening can refer to the implementation of the first condition for keyword screening mentioned above, and this specification will not elaborate on it.

[0079] In some embodiments of the present specification, the reconfiguration of the url parameters according to the preset configuration file may include: reconfiguring the url parameters of the url with actual business meaning according to the preset configuration file. For the same url, its url parameters (such as host, path (including file name, date, etc.), etc.) can be configurable, so that different new urls can be configured and spliced ​​according to different operation needs, that is, the reuse of urls is realized. Among them, configuration strategies such as which parameters in the url parameters need to be replaced by configuration and what values ​​the replaced parameters have can all be specified through the configuration file. During specific configuration, the configuration strategy is obtained by reading the configuration file, and automatic configuration is performed accordingly.

[0080] In most scenarios, pages are multi-level; when searching for target data, you need to jump to the URL level by level. For example, when we browse the rolling news of a portal website, we usually open the portal website homepage first, then open the news center homepage in the portal website homepage, then open the rolling news homepage in the news center homepage, and finally open any interesting rolling news title in the rolling news homepage to browse the specific rolling news content. In this whole process, the multiple URLs generated are obviously in sequence, and these multiple URLs arranged in sequence are the processing chains of the corresponding operations. In order to replay the page operation, on the basis of splicing into new URLs according to the configuration results, the new URLs need to be reorganized into a new processing chain. For example, the new URLs include: url1, url2, url3, url4 and url5, and these new URLs can be reorganized into a new processing chain: url1→url2→url3→url4→url5.

[0081] For the sake of information security, authentication is required to enter the business system or its corresponding operation and maintenance system, log system, etc. In the scenario of obtaining root cause analysis preparation data, in order to enable operations such as logging in and out to be automatically implemented without manual input, in some embodiments of this specification, the new URL is reorganized into a new processing chain, which may include: the new URL and the URLs in the target URL that do not have actual business meaning are reorganized into a new processing chain. This is conducive to further improving the efficiency of obtaining root cause analysis preparation data and further saving labor costs.

[0082] For example, with the above-mentioned url1, url2, url3, url4 and url5, assuming that the login and logout urls are url0 and url6 respectively, the new url and the urls in the target url that do not have actual business meanings can be reorganized into a new processing chain: url0→url1→url2→url3→url4→url5→url6.

[0083] The URL sequence in the new processing chain is called for access, that is, according to the URL sequence in the new processing chain, an access request is automatically initiated to the host, and the data returned by the host for each access request is automatically cached (such as the program log file of the log system, the monitoring file of the monitoring system, the data records in the database, etc.). When the access of the entire new processing chain is completed, the data returned by each access request can also be packaged for users to download, view and analyze. The data returned by each access request is the data (or part thereof) prepared for the above-mentioned root cause analysis.

[0084] Although the process flows described above include multiple operations that occur in a particular order, it should be clearly understood that the processes may include more or fewer operations, which may be performed sequentially or in parallel (eg, using parallel processors or a multi-threaded environment).

[0085] Corresponding to the above-mentioned page operation replay method, this specification also provides an embodiment of a page operation replay device, referring to Figure 3 As shown, in some embodiments of this specification, the page operation playback device may include:

[0086] The URL acquisition module 31 can be used to acquire the URL of the target page and form a URL set;

[0087] The URL identification module 32 can be used to identify one or more target URLs that meet the preset screening conditions from the URL set;

[0088] The URL parsing module 33 can be used to parse the target URL and obtain corresponding URL parameters;

[0089] The URL regeneration module 34 can be used to reconfigure the URL parameters according to a preset configuration file and generate one or more new URLs accordingly;

[0090] The processing chain regeneration module 35 can be used to reorganize the new URL into a new processing chain;

[0091] The operation replay module 36 may be used to replay the operation of the new processing chain to obtain data returned after the replay.

[0092] In some device embodiments of the present specification, identifying one or more target URLs satisfying a preset screening condition from the URL set may include:

[0093] According to the preset first keyword screening condition, the URLs in the URL set are subjected to keyword screening to identify each valid URL from the URL set.

[0094] In some device embodiments of this specification, the URL regeneration module 34 can also be used to:

[0095] According to the preset second keyword screening condition, the URL parameters are subjected to keyword screening to determine the URLs with actual business significance in the target URLs.

[0096] In some device embodiments of this specification, reconfiguring the URL parameters according to a preset configuration file may include:

[0097] According to the preset configuration file, the URL parameters of the URL with actual business meaning are reconfigured.

[0098] In some device embodiments of this specification, the reorganizing the new URL into a new processing chain may include:

[0099] The new URL and the URLs in the target URL that do not have actual business meanings are reorganized into a new processing chain.

[0100] In some device embodiments of this specification, the operation of replaying the new processing chain may include:

[0101] The URLs in the new processing chain are called and accessed sequentially.

[0102] Based on the page operation replay device of the embodiment of this specification, the root cause analysis preparation data can be automatically obtained. Compared with the traditional manual acquisition method, the page operation replay device of the embodiment of this specification greatly shortens the time for obtaining the root cause analysis preparation data, improves the efficiency of obtaining the root cause analysis preparation data, saves labor costs, and also provides a favorable basis for quickly entering the root cause analysis stage and locating system problems as early as possible.

[0103] This specification also provides an embodiment of a browser client, refer to Figure 2 As shown, the browser client can be configured (or installed) with the above-mentioned page operation replay device. For example, the above-mentioned page operation replay device can be installed in the browser client as a plug-in of the browser client, and on this basis, interact with the host through a network (such as a local area network, a wide area network or the Internet) to achieve automatic replay of page operations.

[0104] Based on the browser client of the embodiment of this specification, the root cause analysis preparation data can be automatically obtained. Compared with the traditional manual acquisition method, the browser client of the embodiment of this specification greatly shortens the time consumption of obtaining the root cause analysis preparation data, improves the efficiency of obtaining the root cause analysis preparation data, saves labor costs, and also provides a favorable basis for quickly entering the root cause analysis stage and locating system problems as soon as possible. Since the above-mentioned page operation replay device is configured (or installed) on the browser client in a plug-in manner, it is not only unnecessary to develop a related client separately for the above-mentioned page operation replay device, but also realizes the reuse of the existing browser client, which can be conducive to further reducing the implementation cost.

[0105] For the convenience of description, the above device is described in various units according to their functions. Of course, when implementing this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0106] The embodiments of this specification also provide a computer device. Figure 4 As shown, in some embodiments of the present specification, the computer device 402 may include one or more processors 404, such as one or more central processing units (CPUs) or graphics processing units (GPUs), and each processing unit may implement one or more hardware threads. The computer device 402 may also include any memory 406, which is used to store any kind of information such as code, settings, data, etc. In a specific implementation, a computer program on the memory 406 and that can be run on the processor 404, when the computer program is run by the processor 404, can execute instructions according to the above method. Non-limiting, for example, the memory 406 may include any one or more combinations of the following: any type of RAM, any type of ROM, flash memory device, hard disk, optical disk, etc. More generally, any memory can use any technology to store information. Further, any memory can provide volatile or non-volatile retention of information. Further, any memory can represent a fixed or removable component of the computer device 402. In one case, when the processor 404 executes an associated instruction stored in any memory or a combination of memories, the computer device 402 can perform any operation of the associated instruction. The computer device 402 also includes one or more drive mechanisms 408 for interacting with any storage, such as a hard disk drive mechanism, an optical disk drive mechanism, etc.

[0107] The computer device 402 may also include an input / output module 410 (I / O) for receiving various inputs (via input device 412) and for providing various outputs (via output device 414). A specific output mechanism may include a presentation device 416 and an associated graphical user interface 418 (GUI). In other embodiments, the input / output module 410 (I / O), input device 412, and output device 414 may not be included, and the computer device 402 may be used as a computer device in a network. The computer device 402 may also include one or more network interfaces 420 for exchanging data with other devices via one or more communication links 422. One or more communication buses 424 couple the components described above together.

[0108] The communication link 422 may be implemented in any manner, for example, through a local area network, a wide area network (e.g., the Internet), a point-to-point connection, etc., or any combination thereof. The communication link 422 may include any combination of hardwired links, wireless links, routers, gateway functions, name servers, etc., governed by any protocol or combination of protocols.

[0109] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products of some embodiments of the present specification. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processor to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processor generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0110] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processor to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0111] These computer program instructions can also be loaded onto a computer or other programmable data processor so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0112] In a typical configuration, a computer device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0113] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0114] Computer readable media include permanent and non-permanent, removable and non-removable media that can be used to store information by any method or technology. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computer device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0115] Those skilled in the art will appreciate that the embodiments of this specification may be provided as methods, systems or computer program products. Therefore, the embodiments of this specification may take the form of complete hardware embodiments, complete software embodiments or embodiments combining software and hardware. Moreover, the embodiments of this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

[0116] The present specification embodiments may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present specification embodiments may also be practiced in distributed computing environments where tasks are performed by remote processors connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0117] Each embodiment in this specification is described in a progressive manner, and the same and similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment. In the description of this specification, the description of the reference term "one embodiment", "some embodiments", "example", "specific example", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the embodiment of this specification. In this specification, the schematic representation of the above terms does not necessarily target the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any one or more embodiments or examples in a suitable manner. In addition, in the absence of mutual contradiction, a person skilled in the art can combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples.

[0118] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.< / region>

Claims

1. A page operation replay method, characterized in that: include: Get the uniform resource locator URL of the target page and form a URL set; According to a preset first keyword screening condition, keyword screening is performed on the URLs in the URL set to identify each valid URL from the URL set; Parse the valid URL to obtain the corresponding URL parameters; According to the preset keyword screening second condition, the URL parameters are subjected to keyword screening to determine the URLs with actual business meanings among the valid URLs; Reconfigure the URL parameters of the URL with actual business meaning according to a preset configuration file, and generate one or more new URLs accordingly; the configuration file contains the parameters to be replaced in the URL parameters and the parameter values ​​after replacement; Reorganize the new URL into a new processing chain; Replay the operations of the new processing chain to obtain data returned after the replay.

2. The page operation replay method according to claim 1, characterized in that: The reorganizing the new URL into a new processing chain includes: The new URL and the URLs without actual business meanings among the valid URLs are reorganized into a new processing chain.

3. The page operation replay method according to claim 1, characterized in that: The operation of replaying the new processing chain includes: The URLs in the new processing chain are called and accessed sequentially.

4. A page operation playback device, characterized in that: include: The url acquisition module is used to obtain the url of the target page and form a url set; A URL identification module, configured to perform keyword screening on the URLs of the URL set according to a preset keyword screening first condition, so as to identify each valid URL from the URL set; The url parsing module is used to parse the valid url and obtain the corresponding url parameters; The url regeneration module is used to perform keyword screening on the url parameters according to the preset keyword screening second condition to determine the urls with actual business meanings in the valid urls, reconfigure the url parameters of the urls with actual business meanings according to the preset configuration file, and generate one or more new urls accordingly; the configuration file contains the parameters to be replaced in the url parameters and the parameter values ​​after replacement; A processing chain regeneration module, used for reorganizing the new URL into a new processing chain; The operation replay module is used to replay the operation of the new processing chain to obtain data returned after the replay.

5. A browser client, characterized in that: The browser client is configured with the page operation replay device according to claim 4.

6. A computer device comprising a memory, a processor, and a computer program stored in the memory, characterized in that: When the computer program is executed by the processor, the computer program executes the instructions of the method according to any one of claims 1 to 3.

7. A computer storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor of a computer device, the computer program executes the instructions of the method according to any one of claims 1 to 3.