CN115391147A - Application data dynamic acquisition method and device - Google Patents

Abstract

The application provides a dynamic acquisition method and device for application data, and belongs to the technical field of software. The method comprises the following steps: downloading a first script file corresponding to a target application program on an SDK application management platform, wherein the first script file is an automatic integrated script file; putting the first script file under a code directory of the target application program, and running the first script file to complete SDK integration; under the condition that the SDK is in a running state, acquiring event data of the target application program in real time; and marking the target event and configuring a collection configuration file according to the event data. The method and the device can solve the problems that the SDK integration process is complex, mistakes are easy to occur and much time is consumed in the prior art, and can improve the current situation that the specific service statistics of different application programs can be completed only by the intervention of developers and code modification.

Description

Application data dynamic acquisition method and device

Technical Field

The application belongs to the technical field of software, and particularly relates to a method and a device for dynamically acquiring application data.

Background

In the prior art, to realize data collection of mobile applications, a monitoring SDK (Software Development Kit) is usually installed on an electronic device. The SDK integration needs to depend on an integrated document, codes are added in the project step by step according to the document flow, and under the condition that the number of SDK access steps is large, a certain link is easily missed, or the whole SDK integration fails due to modification errors. Due to the numerous steps, problem location is difficult to achieve when problems arise.

In addition, currently, a common SDK monitors a specific scenario, such as login, registration, and the like, and developers need to actively call a method in the SDK to perform statistical reporting in the specific service scenario, so that customized statistical reporting of some service scenarios becomes more complicated, and developers in non-corresponding fields cannot use the SDK. Therefore, the application scenarios to be reported by the conventional SDK monitoring technology through customized statistics of service scenarios are limited.

Disclosure of Invention

The embodiment of the application aims to provide a method and a device for dynamically acquiring application data, which can solve the problems that an SDK integration process is complex, mistakes are easy to occur, and time consumption is high in the prior art, and improve the current situation that specific service statistics of different application programs can be completed only by intervention of developers and code modification.

In order to solve the technical problem, the present application is implemented as follows:

in a first aspect, the present application provides a method for dynamically acquiring application data, where the method is applied to an electronic device, and the method includes:

downloading a first script file corresponding to a target application program on an SDK application management platform, wherein the first script file is an automatic integrated script file;

putting the first script file under a code directory of the target application program, and running the first script file to complete SDK integration;

under the condition that the SDK is in a running state, acquiring event data of the target application program in real time;

and marking the target event and configuring a collection configuration file according to the event data.

Further, the running the first script file to complete the SDK integration specifically includes:

determining a master directory in a code directory of the target application;

determining a list file of the main directory, and adding an authority request code in the list file;

determining an entry class file in the manifest file, adding an SDK initialization code in the entry class file, and adding an SDK dependency in the manifest file;

and compiling and packaging the program to complete the SDK integration.

Further, before the SDK application management platform downloads the first script file of the corresponding target application, the method further includes:

registering an account number in the SDK application management platform;

and acquiring an application identifier of the target application program, and replacing the code parameters added during the initialization of the target application program according to the application identifier.

Further, the acquiring, in real time, event data of the target application program when the SDK is in a running state includes:

when the SDK is in a running state, initializing the SDK through an application identifier of the target application program;

loading an acquisition configuration file of the target application program, and judging whether the current detected event needs to be reported to a server or not through the acquisition configuration file;

and acquiring event data of the target application program in real time.

Further, the marking the target event and configuring an acquisition configuration file according to the event data includes:

under the condition that the acquisition configuration file determines that the currently detected event needs to be reported to a server, marking the event;

and configuring the configuration acquisition configuration file according to the mark.

In a second aspect, the present application provides a dynamic application data acquisition apparatus, which is applied to an electronic device, and the apparatus includes:

the script downloading module is used for downloading a first script file corresponding to a target application program in the SDK application management platform, wherein the first script file is an automatic integrated script file;

the integrated operation module is used for placing the first script file in a code directory of the target application program and operating the first script file to complete SDK integration;

the event acquisition module is used for acquiring the event data of the target application program in real time under the condition that the SDK is in the running state;

and the marking configuration module is used for marking the target event and configuring a collection configuration file according to the event data.

Further, the integrated operation module includes:

a master catalog determining submodule for determining a master catalog in the code catalog of the target application program;

the list file determining submodule is used for determining the list file of the main directory and adding an authority request code in the list file;

the initialization adding submodule is used for determining an entry class file in the manifest file, adding an SDK initialization code in the entry class file, and adding an SDK dependency in the manifest file;

and the compiling and packaging submodule is used for compiling and packaging the program to complete the SDK integration.

Further, the apparatus further comprises:

the account registration module is used for registering an account in the SDK application management platform;

and the application identifier acquisition module is used for acquiring the application identifier of the target application program and replacing the code parameters added during the initialization of the target application program according to the application identifier.

Further, the event collection module includes:

the initialization operation sub-module is used for initializing the SDK through the application identifier of the target application program when the SDK is in an operation state;

the acquisition configuration file loading submodule is used for loading the acquisition configuration file of the target application program and judging whether the currently detected event needs to be reported to the server or not through the acquisition configuration file;

and the event data acquisition submodule is used for acquiring the event data of the target application program in real time.

Further, the tag configuration module includes:

the event marking submodule is used for marking the event under the condition that the acquisition configuration file determines that the currently detected event needs to be reported to the server;

and the file configuration submodule is used for configuring the configuration acquisition configuration file according to the mark.

According to the application data dynamic acquisition method provided by the embodiment of the application data dynamic acquisition method, a first script file corresponding to a target application program is downloaded on an SDK application management platform, and the first script file is an automatic integrated script file; putting the first script file under a code directory of the target application program, and running the first script file to complete SDK integration; under the condition that the SDK is in a running state, acquiring event data of the target application program in real time; and marking the target event and configuring a collection configuration file according to the event data. The method and the device can realize automatic integration of the SDK and dynamic acquisition of the mobile application data, solve the problems that the SDK integration process is complex and easy to make mistakes and consumes more time in the prior art, and improve the current situation that the statistics of specific services of different application programs can be completed only by intervention of developers and code modification. The scheme provided by the application can achieve one-click SDK integration, and the statistical reporting function of the APP for specific service events such as login, registration, approval and collection can be realized through simple configuration operation of an operator in the application program management background.

Drawings

Fig. 1 is a flowchart of a method for dynamically acquiring application data according to an embodiment of the present application;

fig. 2 is a schematic diagram of an application data dynamic acquisition apparatus according to an embodiment of the present application.

The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings in combination with embodiments.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

A flowchart of a dynamic application data acquisition method provided in the embodiments of the present application is described in detail below with reference to the accompanying drawings.

Example one

Referring to fig. 1, a method for dynamically acquiring application data is shown. The method is applied to the electronic equipment and comprises the following steps:

s101: downloading a first script file corresponding to a target application program on an SDK application management platform, wherein the first script file is an automatic integrated script file;

in this step, the target application is an application that needs to be monitored, and in order to implement real-time data acquisition of the target application, an SDK automation integration script file of the application, that is, a first script file, needs to be downloaded on a software development kit application management platform.

The SDK software development kit is generally a collection of development tools used by some software engineers to build application software for a particular software package, software framework, hardware platform, operating system, and the like. A software development tool broadly refers to a collection of related documents, paradigms, and tools that assist in developing a certain class of software. A software development kit is a collection of development tools used by software engineers to create application software for a particular software package, software framework, hardware platform, operating system, etc., and in general, an SDK is an SDK used to develop applications on a Windows platform. It facilitates the creation of applications through compilers, debuggers, software frameworks, and the like. It may simply be a file that provides an application program interface API for a certain programming language, but may also include complex hardware that can communicate with a certain embedded system. Typical tools include utility tools for debugging and other purposes. SDKs also often include example code, supporting technical notes, or other supporting documentation to clarify suspicions for basic reference.

Before the first script file corresponding to the target application program is downloaded by the SDK application management platform, the method further comprises the steps of registering an account number in the SDK application management platform; and acquiring an application identifier of the target application program, and replacing the code parameters added during initialization of the target application program according to the application identifier.

Specifically, before downloading the automated integrated script file, an account is registered on the SDK application management platform; acquiring application identifications such as a public key of a target application program; and selecting a mobile end system such as Android, ios and the like and a computer end system such as Mac, windows, linux and the like where the source code is located, wherein the computer end can replace parameters of codes added during application initialization in the template script according to information such as a public key, an application identifier and the like generated during file creation, and then a developer can download the automatic integrated script file corresponding to the application created by the developer.

S102: putting the first script file under a code directory of the target application program, and running the first script file to complete SDK integration;

in the step, the first script file is placed in an application project code directory without the integrated SDK according to rules, and then the script is executed and run to complete the integration of the SDK.

Optionally, a master directory in the code directory of the target application program is determined; determining a list file of the main directory, and adding an authority request code in the list file; determining an entry class file in the manifest file, adding an SDK initialization code in the entry class file, and adding an SDK dependency in the manifest file; and compiling and packaging the program to complete the SDK integration.

Specifically, android development in a Windows environment is taken as an example. According to the first script file, a source code directory of a project is found in a script program, and which directory is positioned as a main directory; finding a list file under a main directory and adding related codes of the permission request; if the program entry class does not exist in the list file found in the previous step, an entry class file with an SDK initialization statement is generated and set as an entry class in the list file, if the entry class exists, the entry class file is found, and an SDK initialization code is added at a specified position. Finding the built.gradle file of the file in the same directory according to the entry class file determined in the last step, and then adding the SDK dependency at the specified position. After the steps are completed, the program is compiled and packaged.

And writing an automatic integration script file suitable for the project structure aiming at the mobile application project codes, and attaching parameter information such as keys required by integration. For example: aiming at the Android project, the automatic script puts the SDK file into a project compiling designated path, adds a dependence statement in a corresponding position in a configuration file, and adds an SDK initialization statement carrying initialization parameters in a corresponding function of a program entry class.

After placing the SDK file into the project compilation specified path and initializing, the mobile application project code of the data acquisition SDK needs to be integrated. Then, the automatic integration script file is put under the appointed path of the mobile application project, the script is executed, and automatic integration is carried out. For example: aiming at the Android project, a folder containing an automatic integration script file (Shell script), an SDK file and a program entry class (unspecified in original application) is placed in a directory with the same level as that of a main module in the project, the script is executed under a Linux or Windows platform, and a file and a code statement required by SDK integration are inserted into the project file to complete integration.

After the automatic integration script is successfully executed, the source code is subjected to program packaging to generate a mobile application project file which is integrated.

S103: under the condition that the SDK is in a running state, acquiring event data of the target application program in real time;

specifically, when the SDK is in a running state, initializing the SDK by using an application identifier of the target application program; loading an acquisition configuration file of the target application program, and judging whether the current detected event needs to be reported to a server or not through the acquisition configuration file; and acquiring event data of the target application program in real time.

It can be understood that after the SDK code is added to the running script of the application program, the factual event data collection can be performed on the application program when the SDK code runs.

When the SDK code is run for the first time, since no special event (such as specific service event like login, registration, approval, collection) of the application program is marked yet, the electronic device collects all event data and reports the event data to the server side, so as to realize real-time collection and recording of the data.

S104: and marking the target event and configuring a collection configuration file according to the event data.

Specifically, under the condition that the acquisition configuration file determines that the currently detected event needs to be reported to a server, marking the event; and configuring the configuration acquisition configuration file according to the mark.

It can be understood that after the application integration SDK is successful, the application integration SDK interacts with the server during the start operation process to initialize the SDK through parameters such as a key generated during application registration, and the server verifies whether the application is a trusted authorized application.

And after the application authorization verification is passed, loading a collection configuration file of the current application, judging whether the current detected event needs to be reported to the server side through the configuration file, and reporting the whole amount of the default event when the collection configuration file is not set for the application.

The server can see the collected event total data in the application management background, and then adds a mark to a certain event to be configured in a collection configuration file; and then, the application can only collect the marked events according to the configuration in the next starting process, so that the operation work of operators is facilitated, and the operators can modify the configuration automatically according to the requirements in the period without modifying the application source codes.

An application developer fills necessary information such as package names of applications in a data acquisition SDK integration platform, and obtains information such as application identifiers and keys of the SDK after platform verification so as to obtain configuration information for use during initialization of the SDK. And configuring the customization information such as a data acquisition range, a data uploading period and the like on an application management background of the data acquisition SDK integration platform by an operator to which the application belongs so as to achieve the purpose of customizing acquisition of application running data. After the data acquisition SDK is integrated into a project, application identification and key information are transmitted during initialization, and the SDK integration platform verifies the identity of the SDK integration platform and pulls the SDK integration platform to a corresponding customized data acquisition configuration to be transmitted to an application.

And in the application running process, acquiring required program running data according to the customized configuration information, and uploading the data to the server. The server pulls program running data, and the data are stored in the database according to categories. And (4) making a relevant rule by using the operator, taking out the required data from the database for checking, and making an appropriate operation strategy according to the data condition.

Through the steps provided by the embodiment of the application, developers in the field of data acquisition and SDK integration do not need to manually add the SDK file and the SDK dependency configuration and initialization statements to corresponding positions in the project code according to the integration file any more, but only need to place the script file at a specified position in the main directory of the target application program after downloading the SDK script file, and after executing and running the script, the system can automatically acquire event data of the target application program and mark the event, and configure the acquisition configuration file according to the marked event. Therefore, any developer or person skilled in using a computer can operate and complete the SDK integration work; meanwhile, the problem that the SDK does not work as expected due to lack of certain steps is avoided, the problem needs to be checked step by step according to the integrated document, and time is wasted. At the moment, only the automatic integration script needs to be executed once again, and the integration process becomes simple and fast.

In a second aspect, the present application provides a dynamic application data acquisition apparatus 20, which is applied to an electronic device, where the dynamic application data acquisition apparatus 20 includes:

the script downloading module 201 is configured to download a first script file corresponding to a target application program on an SDK application management platform, where the first script file is an automated integrated script file;

an integration operation module 202, configured to put the first script file in the code directory of the target application, and operate the first script file to complete SDK integration;

the integrated operation module 202 includes:

a master catalog determining submodule 2021, configured to determine a master catalog in the code catalog of the target application program;

the manifest file determining sub-module 2022 is configured to determine a manifest file of the main directory, and add an authority request code to the manifest file;

the initialization adding sub-module 2023 is configured to determine an entry class file in the manifest file, add an SDK initialization code to the entry class file, and add an SDK dependency to the manifest file;

and the compiling and packaging submodule 2024 is used for compiling and packaging the program to complete the SDK integration.

The event acquisition module 203 is configured to acquire event data of the target application program in real time when the SDK is in a running state;

wherein, the event collecting module 203 comprises:

an initialization operation sub-module 2031, configured to initialize the SDK through the application identifier of the target application program when the SDK is in an operation state;

an acquisition configuration file loading submodule 2032, configured to load an acquisition configuration file of the target application program, and determine, through the acquisition configuration file, whether a currently detected event needs to be reported to the server;

the event data acquiring sub-module 2033 is configured to acquire event data of the target application program in real time.

And the marking configuration module 204 is configured to mark the event of the target and configure an acquisition configuration file according to the event data.

The mark configuration module 204 includes:

the event marking sub-module 2041 is configured to mark the event when the acquisition configuration file determines that the currently detected event needs to be reported to the server;

the file configuration submodule 2042 is configured to configure the configuration acquisition configuration file according to the flag.

In addition, the dynamic application data acquisition device 20 further includes:

the account registration module is used for registering an account on the SDK application management platform;

and the application identifier acquisition module is used for acquiring the application identifier of the target application program and replacing the code parameters added during the initialization of the target application program according to the application identifier.

The application data dynamic acquisition device 20 provided in the embodiment of the present application can implement each process implemented in the above application data dynamic acquisition method embodiment, and is not described here again to avoid repetition.

According to the application data dynamic acquisition device 20 provided by the embodiment of the application data dynamic acquisition method, a script downloading module 201, an integrated operation module 202, an event acquisition module 203 and a mark configuration module 204 are arranged, so that a first script file corresponding to a target application program is downloaded on an SDK application management platform, wherein the first script file is an automatic integrated script file; putting the first script file under a code directory of the target application program, and running the first script file to complete SDK integration; under the condition that the SDK is in a running state, acquiring event data of the target application program in real time; and marking the target event and configuring a collection configuration file according to the event data. The method and the device can realize automatic integration of the SDK and dynamic acquisition of the mobile application data, solve the problems that the SDK integration process is complex, mistakes are easy to occur and time is long in the prior art, and solve the current situation that different APP specific service statistics can be completed only by intervention of developers and code modification. The scheme provided by the application can achieve one-click SDK integration, and the statistical reporting function of the APP for specific service events such as login, registration, approval and collection can be realized through simple configuration operation of an operator in the application program management background.

The virtual device in the embodiment of the present application may be a device, and may also be a component, an integrated circuit, or a chip in a terminal.

The present invention may be methods, apparatus, systems and/or computer program products. The computer program product may include a computer-readable storage medium having computer-readable program instructions embodied therewith for carrying out aspects of the invention.

The computer readable storage medium may be a tangible device that can hold and store the instructions for use by the instruction execution device. The computer readable storage medium may be, for example, an electronic memory device, a magnetic memory device, an optical memory device, an electromagnetic memory device, a semiconductor memory device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a Static Random Access Memory (SRAM), a portable compact disc read-only memory (CD-ROM), a Digital Versatile Disc (DVD), a memory stick, a floppy disk, a mechanical coding device, such as punch cards or in-groove projection structures having instructions stored thereon, and any suitable combination of the foregoing. Computer-readable storage media as used herein is not to be interpreted as a transitory signal per se, such as a radio wave or other freely propagating electromagnetic wave, an electromagnetic wave propagating through a waveguide or other transmission medium (e.g., optical pulses through a fiber optic cable), or an electrical signal transmitted through an electrical wire.

The computer-readable program instructions described herein may be downloaded from a computer-readable storage medium to a respective computing/processing device, or to an external computer or external storage device via a network, such as the internet, a local area network, a wide area network, and/or a wireless network. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. The network adapter card or network interface in each computing/processing device receives computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in a computer-readable storage medium in the respective computing/processing device.

Computer program instructions for carrying out operations of the present invention may be assembler instructions, instruction Set Architecture (ISA) instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source or object code in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The computer-readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the 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 the connection may be made to an external computer (for example, through the Internet using an Internet service provider). In some embodiments, aspects of the present invention are implemented by personalizing an electronic circuit, such as a programmable logic circuit, a Field Programmable Gate Array (FPGA), or a Programmable Logic Array (PLA), with state information of computer-readable program instructions, which can execute the computer-readable program instructions.

Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-readable program instructions.

These computer-readable program instructions may be provided to a processing unit of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processing unit of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer-readable program instructions may also be stored in a computer-readable storage medium that can direct a computer, programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer-readable medium storing the instructions comprises an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer, other programmable apparatus or other devices implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

It is noted that, unless expressly stated otherwise, all features disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose. Thus, unless expressly stated otherwise, each feature disclosed is one example only of a generic series of equivalent or similar features. Where used, further, preferably, still further and more preferably is a brief introduction to the description of the other embodiment based on the foregoing embodiment, the combination of the contents of the further, preferably, still further or more preferably back strap with the foregoing embodiment being a complete construction of the other embodiment. Several further, preferred, still further or more preferred arrangements of the belt after the same embodiment may be combined in any combination to form a further embodiment.

It will be appreciated by persons skilled in the art that the embodiments of the invention described above and shown in the drawings are given by way of example only and are not limiting of the invention. The objects of the invention have been fully and effectively accomplished. The functional and structural principles of the present invention have been shown and described in the examples, and any variations or modifications of the embodiments of the present invention may be made without departing from the principles.

Finally, it should be noted that: the above embodiments are only used for illustrating the technical solutions of the present disclosure, and not for limiting the same; while the present disclosure has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art will understand that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present disclosure.

The above description is only an example of the present invention and is not intended to limit the present invention. Various modifications and alterations to this invention will become apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention should be included in the scope of the claims of the present invention.

Claims (10)

1. A dynamic acquisition method of application data is applied to electronic equipment, and is characterized in that the method comprises the following steps:

downloading a first script file corresponding to a target application program on an SDK application management platform, wherein the first script file is an automatic integrated script file;

putting the first script file under a code directory of the target application program, and running the first script file to complete SDK integration;

under the condition that the SDK is in a running state, acquiring event data of the target application program in real time;

and marking the target event and configuring a collection configuration file according to the event data.

2. The method for dynamically collecting application data according to claim 1, wherein the running the first script file to complete SDK integration specifically comprises:

determining a master directory in a code directory of the target application;

determining a list file of the main directory, and adding an authority request code in the list file;

determining an entry class file in the manifest file, adding an SDK initialization code in the entry class file, and adding an SDK dependency in the manifest file;

and compiling and packaging the program to complete the SDK integration.

3. The method for dynamically collecting application data according to claim 1, wherein before the SDK application management platform downloads the first script file corresponding to the target application program, the method further comprises:

registering an account number in the SDK application management platform;

and acquiring an application identifier of the target application program, and replacing the code parameters added during initialization of the target application program according to the application identifier.

4. The dynamic application data acquisition method according to claim 1, wherein acquiring event data of the target application program in real time with the SDK in a running state comprises:

when the SDK is in a running state, initializing the SDK through an application identifier of the target application program;

loading an acquisition configuration file of the target application program, and judging whether the current detected event needs to be reported to a server or not through the acquisition configuration file;

and acquiring event data of the target application program in real time.

5. The method for dynamically collecting application data according to claim 4, wherein the marking the event of the target and configuring a collection configuration file according to the event data comprises:

under the condition that the acquisition configuration file determines that the currently detected event needs to be reported to a server, marking the event;

and configuring the configuration acquisition configuration file according to the mark.

6. The utility model provides an application data developments collection system, is applied to electronic equipment, its characterized in that, the device includes:

the script downloading module is used for downloading a first script file corresponding to a target application program in the SDK application management platform, wherein the first script file is an automatic integrated script file;

the integrated operation module is used for placing the first script file in a code directory of the target application program and operating the first script file to complete SDK integration;

the event acquisition module is used for acquiring the event data of the target application program in real time under the condition that the SDK is in the running state;

and the marking configuration module is used for marking the target event and configuring a collection configuration file according to the event data.

7. The dynamic application data acquisition device according to claim 6, wherein the integrated operation module comprises:

a master catalog determining submodule for determining a master catalog in the code catalog of the target application program;

the list file determining submodule is used for determining the list file of the main directory and adding an authority request code in the list file;

the initialization adding submodule is used for determining an entry class file in the manifest file, adding an SDK initialization code in the entry class file, and adding an SDK dependency in the manifest file;

and the compiling and packaging submodule is used for compiling and packaging the program to complete the SDK integration.

8. The dynamic acquisition device of application data according to claim 6, characterized in that the device further comprises:

the account registration module is used for registering an account on the SDK application management platform;

and the application identifier acquisition module is used for acquiring the application identifier of the target application program and replacing the code parameters added during the initialization of the target application program according to the application identifier.

9. The dynamic acquisition device of application data according to claim 6, wherein the event acquisition module comprises:

the initialization operation sub-module is used for initializing the SDK through the application identifier of the target application program when the SDK is in an operation state;

the acquisition configuration file loading submodule is used for loading the acquisition configuration file of the target application program and judging whether the currently detected event needs to be reported to the server or not through the acquisition configuration file;

and the event data acquisition submodule is used for acquiring the event data of the target application program in real time.

10. The dynamic acquisition device of application data according to claim 9, wherein the tag configuration module comprises:

the event marking submodule is used for marking the event under the condition that the acquisition configuration file determines that the currently detected event needs to be reported to the server;

and the file configuration submodule is used for configuring the configuration acquisition configuration file according to the mark.

Images