Inspection method and device applied to ticket management system, equipment and storage medium
Through the interface element identification and inspection script generation of dialogue sheet management system, the problem of low system inspection efficiency is solved, unified monitoring and inspection of multiple platforms is realized, and operation and maintenance complexity is reduced.
Patent Information
- Application Number
- CN202311617887.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-11-29
- Publication Date
- 2025-05-30
AI Technical Summary
The existing technology is inefficient in system automation inspection, and it is impossible to achieve unified monitoring of multiple platforms. The technical requirements of operation and maintenance personnel are high, and automation operation and maintenance tools rely on specific technology stacks.
Page elements are identified through multiple target interfaces of the dialogue sheet management system, inspection scripts are generated, target inspection data is determined, and inspection reports are generated, so as to achieve unified monitoring and inspection of multiple target interfaces.
It improves the efficiency of system inspection, realizes unified monitoring of multiple platforms, reduces the technical requirements of operation and maintenance personnel, and reduces the dependence of automated operation and maintenance tools on specific technology stacks.
Smart Images

Figure CN120069765A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of computer technology, and in particular, to an inspection method, device, equipment, and storage medium applied to a call record management system. Background Art
[0002] With the continuous development of computer technology, big data, container, and microservice technologies have begun to be applied in various industries, increasing the management difficulty of system operation and maintenance. System automated inspection has become a promising direction.
[0003] In the prior art, to achieve system automated inspection, automated tools and technologies can be used to regularly check and monitor the system or the method of automated operation and maintenance can be adopted to ensure the normal operation of the system and discover potential problems.
[0004] Since the prior art requires in-depth understanding of the configuration and operation of the system and tools, it has high technical requirements for operation and maintenance personnel; the technology development is not yet mature, and the automated operation and maintenance tools and processes rely on specific technology stacks. When facing multiple different components and systems, adaptation and adjustment are required, and unified monitoring of multiple platforms cannot be achieved, resulting in the technical problem of low system inspection efficiency. Summary of the Invention
[0005] This application provides an inspection method, device, equipment, and storage medium applied to a call record management system to solve the technical problem of low system inspection efficiency.
[0006] In a first aspect, this application provides an inspection method applied to a call record management system, including:
[0007] Identifying page elements of multiple target interfaces of the call record management system to determine first page elements, and obtaining at least one operation information of the target interfaces based on the first page elements;
[0008] Generating corresponding inspection scripts based on the operation information;
[0009] Determining target inspection data based on the inspection scripts, and generating an inspection report based on the target inspection data.
[0010] Optionally, obtaining at least one operation information of the target interfaces based on the first page elements includes:
[0011] Monitoring the triggering situation and triggering time of the first page elements of the target interfaces based on a target browser plugin;
[0012] Obtaining the triggering situation and triggering time of the first page elements at a first preset time interval, and determining at least one operation information.
[0013] Optionally, obtain the triggering situation and triggering time of the first page element based on the first preset time interval, and determine at least one operation message, including:
[0014] Obtain the triggering situation and triggering time of the page opening element, system login element, content filling element, button click element, page jump element, and / or menu dropdown element based on the first preset time interval, and determine at least one operation message.
[0015] Optionally, determine target inspection data based on an inspection script, including:
[0016] Judge whether the inspection script meets the first preset condition;
[0017] If so, perform inspection element recognition on multiple target interfaces based on the inspection script to determine the second page element;
[0018] Determine the target inspection data based on the second page element.
[0019] Optionally, generate an inspection report based on the target inspection data, including:
[0020] Obtain the target inspection data based on the second preset time interval;
[0021] Generate an inspection report based on the target inspection data.
[0022] Optionally, after generating an inspection report based on the target inspection data, including:
[0023] Judge whether the target inspection data in the inspection report meets the second preset condition;
[0024] If not, generate a warning message based on the target inspection data.
[0025] Optionally, perform page element recognition on multiple target interfaces of the call list management system to determine the first page element, and further include:
[0026] Perform page element recognition on the data visualization interface, log system interface, and / or resource visualization interface of the call list management system to determine the first page element.
[0027] In a second aspect, the present application provides an inspection device applied to a call list management system, including:
[0028] A first processing module, configured to perform page element recognition on multiple target interfaces of the call list management system to determine the first page element, and obtain at least one operation message of the target interface based on the first page element;
[0029] A second processing module, configured to generate a corresponding inspection script based on the operation message;
[0030] A third processing module, configured to determine target inspection data based on an inspection script and generate an inspection report based on the target inspection data.
[0031] Optionally, the first processing module is further configured to:
[0032] Monitor the triggering situation and triggering time of the first page element of the target interface based on the target browser plug-in;
[0033] Obtain the triggering situation and triggering time of the first page element at a first preset time interval, and determine at least one operation message.
[0034] Optionally, the first processing module is further configured to:
[0035] Obtain the triggering situation and triggering time of a page opening element, a system login element, a content filling element, a button click element, a page jump element, and / or a menu drop-down element at a first preset time interval, and determine at least one operation message.
[0036] Optionally, the first processing module is further configured to:
[0037] Perform page element recognition on the system visualization interface, the log system interface, and / or the resource visualization interface of the call list management system to determine the first page element.
[0038] Optionally, the third processing module is further configured to:
[0039] Determine whether the inspection script meets a first preset condition;
[0040] If so, perform inspection element recognition on multiple target interfaces based on the inspection script to determine a second page element;
[0041] Determine target inspection data based on the second page element.
[0042] Optionally, the third processing module is further configured to:
[0043] Obtain the target inspection data at a second preset time interval;
[0044] Generate an inspection report based on the target inspection data.
[0045] Optionally, the third processing module is further configured to:
[0046] Determine whether the target inspection data in the inspection report meets a second preset condition;
[0047] If not, generate a warning message based on the target inspection data.
[0048] In a third aspect, the present application provides an inspection device applied to a call list management system, including:
[0049] Processor and memory;
[0050] The memory stores computer-executable instructions;
[0051] The processor executes the computer-executable instructions stored in the memory, so that the inspection device applied to the call record management system executes the inspection method applied to the call record management system in any item of the first aspect.
[0052] In a fourth aspect, the present application provides a computer-readable storage medium, in which computer-executable instructions are stored, and when the computer-executable instructions are executed by a processor, they are used to implement the inspection method applied to the call record management system in any item of the first aspect.
[0053] An inspection method, device, equipment and storage medium applied to a call record management system provided by the present application determine a first page element by identifying page elements of multiple target interfaces of the call record management system, and obtain at least one operation information of the target interface based on the first page element; generate a corresponding inspection script based on the operation information; determine target inspection data based on the inspection script, and generate an inspection report based on the target inspection data; thus, based on a target browser plugin, identify elements of multiple target interfaces of the call record management system to determine a first page element, regularly monitor the triggering situation and triggering time of the first page element by setting a first time interval to obtain operation information, generate a corresponding inspection script, identify inspection elements of multiple target interfaces based on the inspection script that meets the first preset condition to determine a second page element, repeatedly obtain target inspection data by setting a second time interval, generate an inspection report, and judge the inspection content of the inspection report based on a second preset condition, and generate a warning information for data that cannot meet the second preset condition, which solves the technical problem of low system inspection efficiency and achieves the technical effect of improving system inspection efficiency. Description of the Drawings
[0054] The drawings here are incorporated into the specification and constitute a part of this specification, showing embodiments consistent with the present application, and are used together with the specification to explain the principles of the present application.
[0055] Figure 1 It is the inspection method flow applied to the call record management system provided by the embodiment of the present application Figure 1 ;
[0056] Figure 2 It is the inspection method flow applied to the call record management system provided by the embodiment of the present application Figure 2 ;
[0057] Figure 3 It is the first exemplary flow of the inspection method applied to the call record management system provided by the embodiment of the present application Figure 3 ;
[0058] Figure 4 This is a schematic structural diagram of an inspection device applied to a call record management system provided by an embodiment of the present application;
[0059] Figure 5 This is a hardware structure diagram of an inspection device applied to a call record management system provided by an embodiment of the present application.
[0060] Through the above-mentioned drawings, specific embodiments of the present application have been shown, and more detailed descriptions will be provided hereinafter. These drawings and textual descriptions are not intended to limit the scope of the concept of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. Detailed Description of the Embodiments
[0061] Here, the exemplary embodiments will be described in detail, and the examples are shown in the drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. On the contrary, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.
[0062] In the prior art, to achieve system automated inspection, automated tools and technologies can be used to regularly check and monitor the system, or the method of automated operation and maintenance can be adopted to ensure the normal operation of the system and discover potential problems.
[0063] Since the prior art requires in-depth understanding of the configuration and operation of the system and tools, it has high technical requirements for operation and maintenance personnel; the technology development is not yet mature, and the automated operation and maintenance tools and processes rely on specific technology stacks. When facing multiple different components and systems, adaptation and adjustment are required, and unified monitoring of multiple platforms cannot be achieved, resulting in the technical problem of low system inspection efficiency.
[0064] A patrol inspection method, device, equipment, and storage medium for a call record management system provided by this application determine first page elements by identifying page elements on multiple target interfaces of the call record management system, and obtain at least one operation information of the target interface based on the first page elements; generate corresponding patrol inspection scripts based on the operation information; determine target patrol inspection data based on the patrol inspection scripts, and generate a patrol inspection report based on the target patrol inspection data; thus, identify elements on multiple target interfaces of the call record management system based on a target browser plugin to determine first page elements, regularly monitor the triggering situation and triggering time of the first page elements by setting a first time interval, obtain operation information, generate corresponding patrol inspection scripts, identify patrol inspection elements on multiple target interfaces based on the patrol inspection scripts that meet the first preset condition to determine second page elements, repeat obtaining target patrol inspection data by setting a second time interval, generate a patrol inspection report, and judge the patrol inspection content of the patrol inspection report based on a second preset condition, and generate a warning message for data that cannot meet the second preset condition, solving the technical problem of low system patrol inspection efficiency and achieving the technical effect of improving system patrol inspection efficiency.
[0065] The following uses specific embodiments to elaborate in detail on the technical solutions of this application and how the technical solutions of this application solve the above technical problems. These several specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of this application will be described below with reference to the accompanying drawings.
[0066] Figure 1 The flow of the patrol inspection method for a call record management system provided by an embodiment of this application Figure 1 As Figure 1 shown, the patrol inspection method for a call record management system provided by an embodiment of this application includes:
[0067] S101. Identify page elements on multiple target interfaces of the call record management system to determine first page elements, and obtain at least one operation information of the target interface based on the first page elements;
[0068] In this embodiment, the target interfaces include a data visualization interface (Grafana visualization interface), a log system interface, and a resource visualization interface; the first page elements include page opening elements, system login elements, content filling elements, button click elements, page jump elements, and menu dropdown elements; the operation information includes page opening information, system login information, content filling information, button click information, page jump information, and menu dropdown information.
[0069] S102. Generate corresponding patrol inspection scripts based on the operation information;
[0070] S103. Determine the target inspection data based on the inspection script, and generate an inspection report based on the target inspection data.
[0071] In this embodiment, the target inspection data includes kafka backlog data and host resource data.
[0072] An inspection method applied to a call record management system provided by this application determines the first page elements by identifying the page elements of multiple target interfaces of the call record management system, and obtains at least one operation information of the target interface based on the first page elements; generates a corresponding inspection script based on the operation information; determines the target inspection data based on the inspection script, and generates an inspection report based on the target inspection data; thus, based on the target browser plugin, it identifies the elements of multiple target interfaces of the call record management system to determine the first page elements, and by setting the first time interval, regularly monitors the triggering situation and triggering time of the first page elements to obtain operation information, generates a corresponding inspection script, identifies the inspection elements of multiple target interfaces based on the inspection script that meets the first preset condition to determine the second page elements, repeats to obtain the target inspection data by setting the second time interval, generates an inspection report, and based on the second preset condition, judges the inspection content of the inspection report, and generates a warning message for the data that cannot meet the second preset condition, solving the technical problem of low system inspection efficiency and achieving the technical effect of improving the system inspection efficiency.
[0073] Figure 2 This is the flow of the inspection method applied to the call record management system provided by the embodiments of this application. Figure 2 As Figure 2 shown, the inspection method applied to the call record management system provided by the embodiments of this application includes:
[0074] S201. Identify the page elements of the data visualization interface, log system interface, and / or resource visualization interface of the call record management system to determine the first page elements;
[0075] S202. Monitor the triggering situation and triggering time of the first page elements of the target interface based on the target browser plugin;
[0076] In this embodiment, the target browser plugin refers to the Selenium IDE browser plugin.
[0077] S203. Obtain the triggering situation and triggering time of the page opening element, system login element, content filling element, button click element, page jump element, and / or menu dropdown element based on the first preset time interval to determine at least one operation information;
[0078] S204. Generate a corresponding inspection script based on the operation information;
[0079] S205. Determine whether the inspection script meets the first preset condition; if so, based on the inspection script, perform inspection element recognition on multiple target interfaces to determine the second page elements;
[0080] In this embodiment, the first preset condition means that the inspection script uses the WebDriver tool to perform the operation of opening the target interface; the second page elements include kafka backlog value, host load, disk usage rate, number of containers, file volume, network packet loss rate, and module alarm number.
[0081] S206. Determine the target inspection data based on the second page elements;
[0082] S207. Obtain the target inspection data based on the second preset time interval; generate an inspection report based on the target inspection data;
[0083] S208. Determine whether the target inspection data in the inspection report meets the second preset condition; if not, generate a warning message based on the target inspection data.
[0084] In this embodiment, the second preset condition means that the value of the target inspection data is less than the corresponding preset threshold.
[0085] Through S201 - S208, install and start the Selenium IDE browser plugin in Google Chrome or Firefox browser, perform page element recognition on multiple target interfaces of the call list management system based on the Selenium IDE browser plugin to determine the first page elements, set the first time interval, regularly monitor the triggering situation and triggering time of the first page elements, obtain operation information based on the recording function of the Selenium IDE browser plugin, generate the corresponding inspection script, based on the first preset condition, the inspection script uses the WebDriver tool to perform inspection element recognition on multiple target interfaces to determine the second page elements, based on setting the second time interval, repeatedly obtain the target inspection data, generate an inspection report, and after the inspection report is generated, generate a warning message based on the data that cannot meet the second preset condition.
[0086] Figure 3 This is the first exemplary process of the inspection method applied to the call list management system provided by the embodiment of the present application Figure 3 . As Figure 3 shown, the inspection method applied to the call list management system provided by the embodiment of the present application includes:
[0087] S301. Determine whether the inspection script can open the inspection page;
[0088] S302. If not, modify the inspection script;
[0089] S303. If so, add a patrol data location method to the patrol script;
[0090] In this embodiment, adding a patrol data location method includes adding call volume, exception logs, call merge volume, exception codes, host load, Mongo connection count, Kafka backlog, disk usage rate, container count, file volume, network packet loss rate, and module warning count.
[0091] S304. Add the patrol script to the scheduled task;
[0092] S305. Populate the patrol data and generate a patrol report.
[0093] A patrol method applied to a call management system provided by this application determines a first page element by identifying page elements on multiple target interfaces of the call management system, and obtains at least one operation information of the target interface based on the first page element; generates a corresponding patrol script based on the operation information; determines target patrol data based on the patrol script, and generates a patrol report based on the target patrol data; thus, based on the target browser plugin, identifies elements on multiple target interfaces of the call management system to determine the first page element, regularly monitors the triggering situation and triggering time of the first page element by setting a first time interval to obtain operation information, generates a corresponding patrol script, identifies patrol elements on multiple target interfaces based on the patrol script that meets the first preset condition to determine the second page element, repeatedly obtains target patrol data by setting a second time interval, generates a patrol report, and based on the second preset condition, judges the patrol content of the patrol report, and generates a warning message for data that cannot meet the second preset condition, solving the technical problem of low system patrol efficiency and achieving the technical effect of improving system patrol efficiency.
[0094] Figure 4 It is a schematic structural diagram of a patrol device applied to a call management system provided by an embodiment of this application. The device in this embodiment can be in the form of software and / or hardware. As Figure 4 shown, the patrol device 400 applied to the call management system provided by the embodiment of this application includes a first processing module 401, a second processing module 402, and a third processing module 403:
[0095] The first processing module 401 is used to identify page elements on multiple target interfaces of the call management system to determine a first page element, and obtain at least one operation information of the target interface based on the first page element;
[0096] The second processing module 402 is used to generate a corresponding patrol script based on the operation information;
[0097] The third processing module 403 is configured to determine target inspection data based on an inspection script and generate an inspection report based on the target inspection data.
[0098] In a possible implementation, the first processing module 401 is further configured to:
[0099] Monitor the triggering situation and triggering time of the first page element of the target interface based on the target browser plugin;
[0100] Obtain the triggering situation and triggering time of the first page element at a first preset time interval, and determine at least one operation message.
[0101] In a possible implementation, the first processing module 401 is further configured to:
[0102] Obtain the triggering situation and triggering time of a page opening element, a system login element, a content filling element, a button click element, a page jump element, and / or a menu dropdown element at a first preset time interval, and determine at least one operation message.
[0103] In a possible implementation, the first processing module 401 is further configured to:
[0104] Perform page element recognition on the system visualization interface, the log system interface, and / or the resource visualization interface of the conversation form management system to determine the first page element.
[0105] In a possible implementation, the third processing module 403 is further configured to:
[0106] Determine whether the inspection script meets a first preset condition;
[0107] If so, perform inspection element recognition on multiple target interfaces based on the inspection script to determine a second page element;
[0108] Determine target inspection data based on the second page element.
[0109] In a possible implementation, the third processing module 403 is further configured to:
[0110] Obtain the target inspection data at a second preset time interval;
[0111] Generate an inspection report based on the target inspection data.
[0112] In a possible implementation, the third processing module 403 is further configured to:
[0113] Determine whether the target inspection data in the inspection report meets a second preset condition;
[0114] If not, generate a warning message based on the target inspection data.
[0115] An inspection device applied to a call record management system provided by this application determines a first page element by identifying page elements on multiple target interfaces of the call record management system, and obtains at least one operation information of the target interface based on the first page element; generates a corresponding inspection script based on the operation information; determines target inspection data based on the inspection script, and generates an inspection report based on the target inspection data; thus, based on a target browser plugin, it identifies elements on multiple target interfaces of the call record management system to determine the first page element, regularly monitors the triggering situation and triggering time of the first page element by setting a first time interval, obtains operation information, generates a corresponding inspection script, performs inspection element identification on multiple target interfaces based on the inspection script that meets the first preset condition to determine a second page element, repeats obtaining target inspection data by setting a second time interval, generates an inspection report, and judges the inspection content of the inspection report based on a second preset condition, and generates a warning message for data that cannot meet the second preset condition, solving the technical problem of low system inspection efficiency and achieving the technical effect of improving system inspection efficiency.
[0116] Figure 5 It is a hardware structure diagram of an inspection device applied to a call record management system provided by an embodiment of this application. As Figure 5 shown, the inspection device 500 applied to the call record management system includes:
[0117] A processor 501 and a memory 502;
[0118] The memory stores computer execution instructions;
[0119] The processor executes the computer execution instructions stored in the memory 502, so that the inspection device applied to the call record management system executes the inspection method applied to the call record management system as described above.
[0120] It should be understood that the above-mentioned processor 501 may be a central processing unit (CPU for short), or other general-purpose processors, digital signal processors (DSP for short), application specific integrated circuits (ASIC for short), etc. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the method disclosed in combination with the invention can be directly embodied as being executed and completed by a hardware processor, or can be executed and completed by a combination of hardware and software modules in the processor. The memory 502 may include a high-speed random access memory (RAM for short), and may also include non-volatile memory (NVM for short), such as at least one disk memory, and may also be a USB flash drive, a mobile hard disk, a read-only memory, a magnetic disk or an optical disc, etc.
[0121] The embodiment of the present application correspondingly further provides a computer-readable storage medium, in which computer-executable instructions are stored, and when the computer-executable instructions are executed by a processor, they are used to implement an inspection method applied to a call record management system.
[0122] It should be noted that for the foregoing method embodiments, for the sake of simple description, they are all expressed as a series of action combinations. However, those skilled in the art should know that the present application is not limited by the described action sequence, because according to the present application, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily essential to the present application.
[0123] Furthermore, it should be noted that although the steps in the flowchart are shown in sequence according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless there is a clear description in this article, the execution of these steps has no strict order limitation, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowchart may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same moment, but can be executed at different moments. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed alternately or alternately with at least a part of other steps or sub-steps or stages of other steps.
[0124] It should be understood that the above-described device embodiments are merely illustrative, and the devices of the present application can also be implemented in other ways. For example, the division of units / modules in the above embodiments is only a logical function division, and there can be other division methods in actual implementation. For example, multiple units, modules or components can be combined, or can be integrated into another system, or some features can be ignored or not executed.
[0125] In addition, without special instructions, in each embodiment of the present application, each functional unit / module can be integrated in one unit / module, or each unit / module can exist physically alone, or two or more units / modules can be integrated together. The above integrated unit / module can be implemented in the form of hardware or in the form of a software program module.
[0126] When the integrated unit / module is implemented in the form of hardware, the hardware can be a digital circuit, an analog circuit, etc. The physical implementation of the hardware structure includes but is not limited to transistors, memristors, etc. Without special instructions, the processor can be any suitable hardware processor, such as CPU, GPU, FPGA, DSP, and ASIC, etc. Without special instructions, the storage unit can be any suitable magnetic storage medium or magneto-optical storage medium, such as resistive random access memory RRAM (Resistive Random Access Memory), dynamic random access memory DRAM (Dynamic Random Access Memory), static random access memory SRAM (Static Random-Access Memory), enhanced dynamic random access memory EDRAM (Enhanced Dynamic Random Access Memory), high-bandwidth memory HBM (High-Bandwidth Memory), hybrid memory cube HMC (Hybrid Memory Cube), etc.
[0127] When the integrated unit / module is implemented in the form of a software program module and sold or used as an independent product, it can be stored in a computer-readable memory. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods in various embodiments of this application. The aforementioned memory includes: various media that can store program codes, such as USB flash drives, read-only memories (ROM, Read-Only Memory), random access memories (RAM, Random Access Memory), mobile hard disks, magnetic disks, or optical discs.
[0128] In the above embodiments, the descriptions of each embodiment have their own emphases. For the parts not detailed in a certain embodiment, reference can be made to the relevant descriptions of other embodiments. The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity of description, not all possible combinations of the technical features in the above embodiments are described. However, as long as the combinations of these technical features do not conflict, they should all be considered as the scope described in this specification.
[0129] After considering the specification and practicing the invention disclosed herein, those skilled in the art will readily think of other implementation schemes of this application. This application aims to cover any variations, uses, or adaptive changes of this application. These variations, uses, or adaptive changes follow the general principles of this application and include the common general knowledge or conventional technical means in the technical field not disclosed in this application. The specification and embodiments are only regarded as exemplary, and the true scope and spirit of this application are pointed out by the following claims.
[0130] It should be understood that this application is not limited to the precise structures already described and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is only limited by the appended claims.
Claims
1. A patrol inspection method applied to a call record management system, characterized in that, it includes: Identifying first page elements for multiple target interfaces of the call record management system, and obtaining at least one operation information of the target interface based on the first page elements; Generating a corresponding patrol inspection script based on the operation information; Determining target patrol inspection data based on the patrol inspection script, and generating a patrol inspection report based on the target patrol inspection data.
2. The method according to claim 1, characterized in that, The obtaining at least one operation information of the target interface based on the first page elements includes: Monitoring the triggering situation and triggering time of the first page elements of the target interface based on a target browser plugin; Obtaining the triggering situation and the triggering time of the first page elements at a first preset time interval, and determining at least one piece of the operation information.
3. The method according to claim 2, characterized in that, The obtaining the triggering situation and the triggering time of the first page elements at a first preset time interval, and determining at least one piece of the operation information includes: Obtaining the triggering situation and the triggering time of page opening elements, system login elements, content filling elements, button click elements, page jump elements and / or menu dropdown elements at the first preset time interval, and determining at least one piece of the operation information.
4. The method according to claim 3, characterized in that, The determining target patrol inspection data based on the patrol inspection script includes: Judging whether the patrol inspection script meets a first preset condition; If so, performing patrol inspection element identification on multiple target interfaces based on the patrol inspection script to determine second page elements; Determining the target patrol inspection data based on the second page elements.
5. The method according to claim 4, characterized in that, The generating a patrol inspection report based on the target patrol inspection data includes: Obtaining the target patrol inspection data at a second preset time interval; Generating the patrol inspection report based on the target patrol inspection data.
6. The method according to claim 5, characterized in that, After the generating a patrol inspection report based on the target patrol inspection data, it includes: Judging whether the target patrol inspection data in the patrol inspection report meets a second preset condition; If not, generating a warning message based on the target patrol inspection data.
7. The method according to claim 1, characterized in that, The identifying first page elements for multiple target interfaces of the call record management system further includes: Performing page element identification on a data visualization interface, a log system interface and / or a resource visualization interface of the call record management system to determine the first page elements.
8. A patrol inspection device applied to a call record management system, characterized in that, it includes: A first processing module, configured to identify first page elements for multiple target interfaces of the call record management system, and obtain at least one operation information of the target interface based on the first page elements; A second processing module, configured to generate a corresponding patrol inspection script based on the operation information; A third processing module, configured to determine target inspection data based on the inspection script and generate an inspection report based on the target inspection data.
9. An inspection device applied to a call record management system, characterized in that, it includes: a processor and a memory; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory, so that the inspection device applied to the call record management system executes the inspection method applied to the call record management system according to any one of claims 1 to 7.
10. A computer-readable storage medium, characterized in that, the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, they are used to implement the inspection method applied to the call record management system according to any one of claims 1 to 7.