Data acquisition method and device, equipment, storage medium and computer program product
By dynamically determining the target business indicator items and data acquisition logic during data acquisition requests, the problem of insufficient data acquisition flexibility caused by the single index label type in the prior art is solved, and a flexible data acquisition process is realized.
Patent Information
- Application Number
- CN202411072459.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-06
- Publication Date
- 2024-11-08
AI Technical Summary
In the fixed index data acquisition method in the prior art, the index tag type is single and does not support type expansion, resulting in low flexibility in data acquisition.
When receiving the data acquisition request, the target service indicator item corresponding to the data to be collected is determined based on the data acquisition request, and the target data acquisition item is found from the preset tag tree based on the target service indicator item, and the target data acquisition logic is determined based on the target data. Acquisition logic collects data for the acquisition.
By dynamically querying target business indicator items and data acquisition logic, the flexibility of data acquisition is improved, and the problem of insufficient flexibility caused by a single indicator label type is solved.
Smart Images

Figure CN118916237A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of data acquisition technology, and in particular to a data acquisition method, device, equipment, storage medium and computer program product. Background Art
[0002] As the system matures, the number of indicators monitored by the system is increasing. At this time, it is becoming more and more important to collect and maintain indicator data in the system. At present, when the number of indicators is small and the source of collected data is single, a fixed indicator data collection method is usually used. However, the indicator label type in the existing fixed indicator data collection method is single and does not support type expansion, resulting in low flexibility in data collection.
[0003] The above contents are only used to assist in understanding the technical solution of the present invention and do not constitute an admission that the above contents are prior art. Summary of the invention
[0004] The main purpose of this application is to provide a data collection method, device, equipment, storage medium and computer program product, aiming to solve the technical problem that the fixed indicator data collection method in the prior art has a single indicator label type and does not support type expansion, resulting in low flexibility in data collection.
[0005] To achieve the above purpose, the present application proposes a data collection method, which comprises:
[0006] When receiving a data collection request, determining a target business indicator item corresponding to the data to be collected based on the data collection request;
[0007] Searching for a target data collection item corresponding to the data to be collected from a preset tag tree according to the target business indicator item;
[0008] Determine the target data collection logic corresponding to the target data collection item;
[0009] The data to be collected is collected based on the target data collection logic.
[0010] In one embodiment, before the step of determining the target business indicator item corresponding to the to-be-collected data based on the data collection request when the data collection request is received, the step further includes:
[0011] Obtain several business risk points in the process of the business to be collected;
[0012] Forming business risk items according to the business risk points, and generating business indicator items corresponding to the business risk items;
[0013] Determine the data collection items corresponding to the business indicator items;
[0014] A preset label tree is generated based on the business risk item, the business indicator item and the data collection item.
[0015] In one embodiment, before the step of generating a preset label tree based on the business risk item, the business indicator item and the data collection item, the step further includes:
[0016] Classifying the business risk points according to the business tag system, and determining the business tag items corresponding to the business risk points;
[0017] The step of generating a preset label tree based on the business risk item, the business indicator item and the data collection item includes:
[0018] Constructing a first mapping relationship between the business risk item and the business indicator item, and a second mapping relationship between the business risk item and the business tag item;
[0019] A preset tag tree is generated based on the first mapping relationship, the second mapping relationship and the data collection item.
[0020] In one embodiment, the step of determining the data collection item corresponding to the business indicator item includes:
[0021] Obtaining the data collection type, data collection logic and data collection engine corresponding to the business to be collected;
[0022] Determine the data collection rule corresponding to the service to be collected based on the data collection type and the data collection logic;
[0023] The data collection item corresponding to the business indicator item is generated based on the data collection rule and the data collection engine.
[0024] In one embodiment, the step of generating the data collection item corresponding to the business indicator item based on the data collection rule and the data collection engine includes:
[0025] Determining the business data risk in the business to be collected based on the data collection logic;
[0026] Determine the frequency of data collection based on the business data risk;
[0027] A data collection item corresponding to the business indicator item is generated based on the data collection rule, the data collection engine and the data collection frequency.
[0028] In one embodiment, after the step of collecting the data to be collected based on the target data collection logic, the method further includes:
[0029] When data collection is completed, determining data collection time information and data statistical type corresponding to the data to be collected according to the target data collection logic;
[0030] The data collection time information and the data to be collected are summarized into corresponding tags in the preset tag tree through the data statistics type.
[0031] In addition, to achieve the above purpose, the present application also proposes a data acquisition device, the device comprising:
[0032] A collection item determination module, configured to determine, upon receiving a data collection request, a target business indicator item corresponding to the data to be collected based on the data collection request;
[0033] An indicator item determination module, used to search for a target data collection item corresponding to the data to be collected from a preset tag tree according to the target business indicator item;
[0034] A collection logic determination module, used to determine the target data collection logic corresponding to the target data collection item;
[0035] A data acquisition module is used to acquire the data to be acquired based on the target data acquisition logic.
[0036] In addition, to achieve the above objectives, the present application also proposes a data acquisition device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the data acquisition method described above.
[0037] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the data acquisition method described above are implemented.
[0038] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps of the data acquisition method described above are implemented.
[0039] The present application provides a data collection method, which discloses that when a data collection request is received, a target data collection item corresponding to the data to be collected is determined based on the data collection request; a target business indicator item corresponding to the data to be collected is searched from a preset label tree according to the target data collection item; a target data collection logic corresponding to the target data collection item is determined; and data collection is performed on the data to be collected based on the target business indicator item and the target data collection logic; because the present invention queries the target business indicator item from the preset label tree according to the target data collection item corresponding to the data to be collected, and performs data collection based on the target business indicator item and the target data collection logic, the technical problem that the indicator label type in the fixed indicator data collection method in the prior art is single and does not support type expansion, resulting in low flexibility in data collection is solved. BRIEF DESCRIPTION OF THE DRAWINGS
[0040] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.
[0041] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.
[0042] Figure 1 A flowchart of the first embodiment of the data collection method of the present application is provided;
[0043] Figure 2 A flow chart of the second embodiment of the data collection method of the present application;
[0044] Figure 3 This is a flowchart for constructing a tree-like labeling system in the data collection method of this application;
[0045] Figure 4 A flowchart of the third embodiment of the data collection method of the present application is provided;
[0046] Figure 5 The data collection logic diagram of the data collection method of this application;
[0047] Figure 6 This is a schematic diagram of the module structure of the data acquisition device according to an embodiment of the present application;
[0048] Figure 7 Schematic diagram of the device structure of the hardware operating environment involved in the data acquisition method in the embodiment of the present application.
[0049] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION
[0050] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.
[0051] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.
[0052] The main solution of the embodiment of the present application is: when a data collection request is received, the target business indicator item corresponding to the data to be collected is determined based on the data collection request; according to the target business indicator item, the target data collection item corresponding to the data to be collected is searched from a preset tag tree; the target data collection logic corresponding to the target data collection item is determined; and data collection is performed on the data to be collected based on the target data collection logic.
[0053] In the prior art, when the number of indicators is small and the source of collected data is single, a fixed indicator data collection method is usually adopted. However, the indicator label type in the existing fixed indicator data collection method is single and does not support type expansion, resulting in low flexibility in data collection.
[0054] The present application provides a solution, which can query the target business indicator items from the preset label tree according to the target data collection items corresponding to the data to be collected, and perform data collection based on the target business indicator items and the target data collection logic, thereby solving the technical problem that the indicator label type in the fixed indicator data collection method in the prior art is single and does not support type expansion, resulting in low flexibility in data collection.
[0055] It should be noted that the execution subject of this embodiment can be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device capable of realizing the above functions, a data acquisition device, etc. The following takes a data acquisition device as an example (hereinafter referred to as a device) to illustrate this embodiment and the following embodiments.
[0056] Based on this, the present application embodiment provides a data collection method, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the data collection method of the present application.
[0057] In this embodiment, the data collection method includes steps S10 to S40:
[0058] Step S10: upon receiving a data collection request, determining a target business indicator item corresponding to the data to be collected based on the data collection request.
[0059] It should be understood that the data collection request may be a request for instructing the device to collect indicator data. Accordingly, the data to be collected is the tag data that needs to be collected in this instruction.
[0060] It should be noted that the above-mentioned target business indicator items may be options for describing the specific data acquisition logic of each risk point in multiple process links of the business.
[0061] Step S20: searching the preset tag tree for the target data collection item corresponding to the data to be collected according to the target business indicator item.
[0062] It should be noted that the above-mentioned preset label tree can be a multi-classification and multi-level label system structure. In this embodiment, the preset label tree stores the mapping relationship between indicator items and data collection items. Therefore, after determining the target business indicator items corresponding to the data to be collected, you can search in the preset label tree according to the target business indicator items, and then determine the target data collection items corresponding to the data to be collected.
[0063] It should be understood that the above-mentioned target data collection item can be an option for collecting the data to be collected. In this embodiment, the target data collection item can be configured with data collection logic for grabbing the data to be collected, and the user can freely configure the data logic parameters of the collection logic in the target data collection item on the front end (such as date, organization, personnel, etc., which are not limited in this embodiment).
[0064] Step S30: Determine the target data collection logic corresponding to the target data collection item.
[0065] It can be understood that the above target data collection logic may be a logic configured in the target data collection item for collecting the data to be collected.
[0066] In this embodiment, the collection item configuration is relatively flexible, and you can freely add parameters in the data logic, such as date, organization, personnel, etc., and configure the collection logic. For example, if the parameter is a date, you can use a date placeholder in the collection logic to replace it. This embodiment does not limit this. In addition, for different indicator items, users can maintain collection items in the foreground.
[0067] Step S40: collecting the data to be collected based on the target data collection logic.
[0068] In this embodiment, after the device determines the target data collection item corresponding to the data to be collected, the data to be collected can be collected by using the target data collection logic configured in the target data collection item.
[0069] Furthermore, after step S40, the method further includes: when data collection is completed, determining the data collection time information and data statistical type corresponding to the data to be collected according to the target data collection logic; and aggregating the data collection time information and the data to be collected to the corresponding label in the preset label tree through the data statistical type.
[0070] It should be understood that the above-mentioned data collection time information can be the date, time and other information of the data to be collected; correspondingly, the above-mentioned data statistical type can be the dimension used to count the data to be collected. For example, in this embodiment, the collected result data can be summarized according to different dimensions such as different institutions, dates, business indicators, etc., and the quantity can be summarized to each label through risk item-indicator item-label item (multi-type and multi-level tree structure) to facilitate the discovery of the risk amount of each link.
[0071] The present embodiment provides a data collection method, which discloses that when a data collection request is received, a target data collection item corresponding to the data to be collected is determined based on the data collection request; a target business indicator item corresponding to the data to be collected is searched from a preset label tree according to the target data collection item; a target data collection logic corresponding to the target data collection item is determined; and data collection is performed on the data to be collected based on the target business indicator item and the target data collection logic. Since the present invention queries the target business indicator item from the preset label tree according to the target data collection item corresponding to the data to be collected, and performs data collection based on the target business indicator item and the target data collection logic, the technical problem that the indicator label type in the fixed indicator data collection method in the prior art is single and does not support type expansion, resulting in low flexibility in data collection is solved.
[0072] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can be referred to the above introduction, and will not be repeated in the following. Figure 2 , Figure 2 A flow chart of the second embodiment of the data collection method of the present application is provided.
[0073] In this embodiment, before step S10, the data collection method further includes steps S01 to S04:
[0074] Step S01: Acquire several business risk points in the process link of the business to be collected.
[0075] It should be understood that the above-mentioned business to be collected can be any business that requires the collection of indicator data. Correspondingly, the above-mentioned business risk points can be various risk points in the process links of the business to be collected.
[0076] Step S02: forming business risk items according to the business risk points, and generating business indicator items corresponding to the business risk items.
[0077] It can be understood that the above-mentioned business risk items can be the business-related risk point knowledge provided by the business; the above-mentioned business indicator items can be the specific data acquisition logic described by the development. In this embodiment, the business indicator items can record information such as the validity, update and description of the indicators. In this embodiment, the business risk items and the business indicator items are in a one-to-one relationship, wherein the business risk items focus on the business side, and the business indicator items focus on the data field dictionary mapping and other contents on the development side. In this embodiment, a multi-classification and multi-level label system can be established according to each key environment of the business process in the business to be collected, and a mapping relationship can be established between each risk point (i.e., risk item) and multiple labels to obtain a preset label tree.
[0078] Step S03: Determine the data collection item corresponding to the business indicator item.
[0079] It should be noted that the above-mentioned data collection item may be a structure used for collecting data in a business indicator item.
[0080] Step S04: Generate a preset label tree based on the business risk item, the business indicator item and the data collection item.
[0081] In the specific implementation, refer to Figure 3 , Figure 3 This is a flowchart for constructing a tree-like labeling system in the data collection method of this application. Figure 3 As shown, in this embodiment, risk items can be formed for each risk point in multiple process links in the business to be collected, wherein the risk items record risk numbers and risk points (including: risk points, risk scenario descriptions, etc.). In addition, indicator items corresponding to the risk items can be formed, wherein the indicator items can record indicator item numbers and indicator item information (including: validity, update time, etc.). Then, a multi-classification and multi-level label system can be established according to each key link in the business process of the business to be collected, and a mapping relationship can be established between each risk point (i.e., risk item) and multiple labels. Among them, in this embodiment, the label item can record information such as label number, label classification, label level, and parent label.
[0082] Furthermore, before the step S04, the method further includes: classifying the business risk points according to a business label system, and determining business label items corresponding to the business risk points.
[0083] It should be noted that the above-mentioned business label system can be a label system provided by business users for classifying risk points in each link of the business to be collected. In this embodiment, the categories of risk points in each link of the business to be collected may include: process category, customer category, asset category, and personnel management category, among which the process category can be specific to each link such as product establishment, liquidation, accounting, post-event monitoring, etc. In addition, in this embodiment, risk items can be divided into high, medium, and low risks according to the different impacts of risks, and labels for whether re-inspection is required can be added according to whether it needs to be handled, and it can be divided into those that need re-inspection and those that do not need re-inspection.
[0084] Correspondingly, the step S04 includes: constructing a first mapping relationship between the business risk item and the business indicator item, and a second mapping relationship between the business risk item and the business label item; generating a preset label tree based on the first mapping relationship, the second mapping relationship and the data collection item.
[0085] It should be understood that if Figure 3 As shown, the above-mentioned first mapping relationship can be a mapping relationship between risk items and indicator items of the business to be collected. In this embodiment, the mapping relationship between risk items and indicator items can be established through risk item numbers and indicator item numbers; the above-mentioned second mapping relationship can be a mapping relationship between risk items and label items of the business to be collected. In this embodiment, the mapping relationship between risk items and label items can be established through risk item numbers and label item numbers. In this embodiment, risk items, indicator items and label items all support real-time addition and update through front-end maintenance, wherein labels support multiple levels and multiple categories; risk items can be labeled in real time through the front-end, such as risk item: product invalid account has not been cancelled, the maintainable label is: product establishment-account management, high risk, no need for rechecking, and invalid risks can be eliminated in real time according to the risk item status during statistics, and the number of label risks can be updated in real time according to the current label of the risk item.
[0086] It should be noted that the risk items, indicator items and label items of the business to be collected in this solution all support real-time addition and update through front-end maintenance. In addition, labels support multiple levels and multiple categories; risk items can be labeled in real time through the front-end, and when statistics are achieved, invalid risks can be eliminated in real time according to the status of the risk items and the number of label risks can be updated in real time according to the current labels of the risk items.
[0087] In actual applications, after establishing the first mapping relationship between the risk items and indicator items of the business to be collected, and the second mapping relationship between the risk items and the label items, the risk items, label items, indicator items and data collection items can be mapped one by one according to the mapping relationship between the indicator items and the data collection items to construct the final preset label tree for labeling the indicators, thereby facilitating the subsequent classification and display of the indicators in multiple dimensions, reducing labor costs and improving R&D efficiency.
[0088] In this embodiment, several business risk points in the process of obtaining the business to be collected are disclosed; business risk items are formed according to the business risk points, and business indicator items corresponding to the business risk items are generated; data collection items corresponding to the business indicator items are determined; and a preset label tree is generated based on the business risk items, business indicator items and data collection items, so as to facilitate the subsequent classification and display of indicators in multiple dimensions, reduce labor costs and improve R&D efficiency.
[0089] Based on the first embodiment and / or the second embodiment of the present application, in the third embodiment of the present application, the same or similar contents as those in the above embodiments can be referred to the above introduction, and will not be described in detail later. Figure 4 , Figure 4 A flowchart of the third embodiment of the data collection method of the present application is provided.
[0090] In this embodiment, step S03 includes steps S031 to S033:
[0091] Step S031: Obtain the data collection type, data collection logic and data collection engine corresponding to the service to be collected.
[0092] It should be understood that the above data collection type may be the data type corresponding to the data to be collected in the service to be collected this time, for example, character type, numeric type, etc., and this embodiment does not impose any limitation on this.
[0093] It can be understood that the above data collection logic is the logic used to capture the data in the business to be collected. The above data collection engine can be an engine used to collect data in the business to be collected. The data collection engine in this embodiment can be for data stored in different databases, where the database can include but is not limited to: hive, mysql, etc. Correspondingly, the above data collection engine can be an engine for collecting data in the hive database, and an engine for collecting data in the mysql database, and this embodiment does not limit this.
[0094] Step S032: Determine the data collection rule corresponding to the service to be collected based on the data collection type and the data collection logic.
[0095] It should be noted that the data collection rules in this embodiment may include data collection logic and configuration of related parameters, wherein the configurable parameters include data collection type, data source, collection item description, etc. In this embodiment, the device may predetermine information such as the type of data collected, the data source used, and the data collection logic when collecting data for the service to be collected, and then generate data collection rules corresponding to the service to be collected based on this information.
[0096] Step S033: Generate data collection items corresponding to the business indicator items based on the data collection rules and the data collection engine.
[0097] In this embodiment, refer to Figure 5 , Figure 5 This is the data collection logic diagram of the data collection method of this application. Figure 5 As shown, each indicator item of the business to be collected will be associated with the corresponding collection item (associated through the indicator item number and the collection item number). The user can freely configure the collection logic and related parameters in the collection item on the front end, including: data collection rules, data collection engine, data collection frequency, data statistics type, etc., and after adjusting the logic, click the data acquisition operation on the front end to perform real-time data acquisition after the logic change, and record the results in the collection result table.
[0098] Furthermore, the step S033 includes: determining the business data risk in the business to be collected based on the data collection logic; determining the data collection frequency according to the business data risk; and generating the data collection item corresponding to the business indicator item based on the data collection rule, the data collection engine and the data collection frequency.
[0099] It should be noted that if Figure 5 As shown, in this embodiment, for different indicator items, users can maintain collection items in the foreground. Due to the diversity of business data storage methods, the collection items include a collection engine, which can be used for data stored in different databases; at the same time, due to the diversity of risk scenarios, the collection logic is set in the collection rules, which can be used to obtain business data risks discovered under the logic; in addition, the collection frequency and statistical dimensions are set for different characteristics of different risks. Finally, through the scheduled tasks in the system, the risk items-indicator items-collection items are executed to realize real-time data collection of risk scenarios in the business process, and the results are placed in the result table.
[0100] It should be understood that this solution implements the dynamic configuration of the data acquisition logic of the indicator collection items, and can quickly respond to the modification of the data acquisition logic of the indicator items, making the change of the indicator data acquisition logic more flexible, shortening the production cycle of the system indicator logic change, and improving the efficiency of realizing business needs.
[0101] In this embodiment, the data collection type, data collection logic and data collection engine corresponding to the business to be collected are disclosed; the data collection rules corresponding to the business to be collected are determined based on the data collection type and the data collection logic; the data collection items corresponding to the business indicator items are generated based on the data collection rules and the data collection engine, so that the change of the indicator data acquisition logic is more flexible, thereby improving the efficiency of realizing business needs.
[0102] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the data collection method of the present application. More simple transformations based on this technical concept are all within the scope of protection of the present application.
[0103] This application also provides a data acquisition device, please refer to Figure 6 , the data acquisition device comprises:
[0104] A collection item determination module 10 is used to determine the target business indicator item corresponding to the data to be collected based on the data collection request when a data collection request is received;
[0105] An indicator item determination module 20, configured to search a target data collection item corresponding to the data to be collected from a preset tag tree according to the target business indicator item;
[0106] A collection logic determination module 30, used to determine the target data collection logic corresponding to the target data collection item;
[0107] The data collection module 40 is used to collect the data to be collected based on the target data collection logic.
[0108] The data acquisition device provided by the present application adopts the data acquisition method in the above embodiment, which can solve the technical problem that the indicator label type in the fixed indicator data acquisition method in the prior art is single and does not support type expansion, resulting in low flexibility of data acquisition. Compared with the prior art, the beneficial effects of the data acquisition device provided by the present application are the same as the beneficial effects of the data acquisition method provided by the above embodiment, and the other technical features in the data acquisition device are the same as the features disclosed in the above embodiment method, which will not be repeated here.
[0109] The present application provides a data acquisition device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the data acquisition method in the above-mentioned embodiment one.
[0110] Reference below Figure 7, which shows a schematic diagram of the structure of a data acquisition device suitable for implementing the embodiment of the present application. The data acquisition device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 7 The data acquisition device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.
[0111] like Figure 7 As shown, the data acquisition device may include a processing device 1001 (e.g., a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the data acquisition device are also stored. The processing device 1001, ROM1002, and RAM1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems can be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touch pad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the data acquisition device to communicate with other devices wirelessly or wired to exchange data. Although the data acquisition device with various systems is shown in the figure, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or have alternatively.
[0112] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.
[0113] The data acquisition device provided by the present application adopts the data acquisition method in the above embodiment to solve the technical problem of data acquisition. Compared with the prior art, the beneficial effects of the data acquisition device provided by the present application are the same as the beneficial effects of the data acquisition method provided by the above embodiment, and the other technical features in the data acquisition device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.
[0114] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.
[0115] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.
[0116] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, and the computer-readable program instructions are used to execute the data collection method in the above-mentioned embodiment.
[0117] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.
[0118] The computer-readable storage medium may be included in the data acquisition device; or may exist independently without being assembled into the data acquisition device.
[0119] The above-mentioned computer-readable storage medium carries one or more programs. When the above-mentioned one or more programs are executed by the data acquisition device, the data acquisition device: when receiving a data acquisition request, determines the target business indicator item corresponding to the data to be collected based on the data acquisition request; searches for the target data collection item corresponding to the data to be collected from a preset label tree according to the target business indicator item; determines the target data collection logic corresponding to the target data collection item; and collects data for the data to be collected based on the target data collection logic.
[0120] Computer program code for performing the operations of the present application may be written in one or more programming languages or a combination thereof, including object-oriented programming languages such as Java, Smalltalk, C++, and conventional procedural programming languages such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).
[0121] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0122] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.
[0123] The readable storage medium provided by the present application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned data collection method, and can solve the technical problem that the indicator label type in the fixed indicator data collection method in the prior art is single and does not support type expansion, resulting in low flexibility of data collection. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided by the present application are the same as the beneficial effects of the data collection method provided by the above-mentioned embodiment, and will not be repeated here.
[0124] The present application also provides a computer program product, including a computer program, which implements the steps of the above-mentioned data acquisition method when executed by a processor.
[0125] The computer program product provided by the present application can solve the technical problem that the indicator label type in the fixed indicator data collection method in the prior art is single and does not support type expansion, resulting in low flexibility in data collection. Compared with the prior art, the beneficial effects of the computer program product provided by the present application are the same as those of the data collection method provided by the above embodiment, and will not be repeated here.
[0126] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.
Claims
1. A data collection method, characterized in that: The method includes: When receiving a data collection request, determining a target business indicator item corresponding to the data to be collected based on the data collection request; Searching for a target data collection item corresponding to the data to be collected from a preset tag tree according to the target business indicator item; Determine the target data collection logic corresponding to the target data collection item; The data to be collected is collected based on the target data collection logic.
2. The method according to claim 1, characterized in that Before the step of determining the target business indicator item corresponding to the to-be-collected data based on the data collection request when the data collection request is received, the method further includes: Obtain several business risk points in the process of the business to be collected; Forming business risk items according to the business risk points, and generating business indicator items corresponding to the business risk items; Determine the data collection items corresponding to the business indicator items; A preset label tree is generated based on the business risk item, the business indicator item and the data collection item.
3. The method according to claim 2, characterized in that Before the step of generating a preset label tree based on the business risk item, the business indicator item and the data collection item, the step further includes: Classifying the business risk points according to the business tag system, and determining the business tag items corresponding to the business risk points; The step of generating a preset label tree based on the business risk item, the business indicator item and the data collection item includes: Constructing a first mapping relationship between the business risk item and the business indicator item, and a second mapping relationship between the business risk item and the business tag item; A preset tag tree is generated based on the first mapping relationship, the second mapping relationship and the data collection item.
4. The method according to claim 2, characterized in that The step of determining the data collection item corresponding to the business indicator item includes: Obtaining the data collection type, data collection logic and data collection engine corresponding to the business to be collected; Determine the data collection rule corresponding to the service to be collected based on the data collection type and the data collection logic; The data collection item corresponding to the business indicator item is generated based on the data collection rule and the data collection engine.
5. The method according to claim 4, characterized in that The step of generating the data collection item corresponding to the business indicator item based on the data collection rule and the data collection engine includes: Determining the business data risk in the business to be collected based on the data collection logic; Determine the frequency of data collection based on the business data risk; A data collection item corresponding to the business indicator item is generated based on the data collection rule, the data collection engine and the data collection frequency.
6. The method according to any one of claims 1 to 5, characterized in that After the step of collecting the data to be collected based on the target data collection logic, the method further includes: When data collection is completed, determining data collection time information and data statistical type corresponding to the data to be collected according to the target data collection logic; The data collection time information and the data to be collected are summarized into corresponding tags in the preset tag tree through the data statistics type.
7. A data acquisition device, characterized in that: The device comprises: A collection item determination module, configured to determine, upon receiving a data collection request, a target business indicator item corresponding to the data to be collected based on the data collection request; An indicator item determination module, used to search for a target data collection item corresponding to the data to be collected from a preset tag tree according to the target business indicator item; A collection logic determination module, used to determine the target data collection logic corresponding to the target data collection item; A data acquisition module is used to acquire the data to be acquired based on the target data acquisition logic.
8. A data acquisition device, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the data collection method according to any one of claims 1 to 6.
9. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the data acquisition method according to any one of claims 1 to 6 are implemented.
10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the data collection method according to any one of claims 1 to 6 are implemented.
