Data reporting method, device, storage medium and electronic device

Abstract

The present application discloses a data reporting method, device, storage medium and electronic device, which relate to the field of computer technology. The method includes: obtaining target buried point data, the target buried point data includes a target label; according to a preset correspondence, determining the reporting configuration information corresponding to the target label, wherein the preset correspondence includes the correspondence between the label information and the reporting configuration information, the label information is used to indicate the functional module, the reporting configuration information corresponding to each functional module indicates the data processing strategy, and the target label belongs to one or more label information; the target buried point data is processed according to the data processing strategy indicated by the reporting configuration information corresponding to the target label and then reported. The present application realizes that different performance modules are used to process the buried point data with different processing strategies and then report it, thereby realizing the separation of buried points and the unification of data management, effectively improving the controllability of buried point data reporting, and improving the effect of performance analysis based on buried point data.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a data reporting method, device, storage medium, and electronic device. Background Art

[0002] Taking the Android system as an example, there's a need across various industries to capture system data for performance analysis. This typically involves setting up tracking points in different performance modules to collect and report tracking data, generating data useful for performance analysis. Currently, each performance module typically reports data separately, resulting in completely different processing of tracking data for each module. This can lead to reporting confusion and poor controllability, hindering performance analysis based on tracking data. Summary of the Invention

[0003] The embodiments of the present application provide a solution that can effectively improve the reporting controllability of buried data and improve the effect of performance analysis based on buried data.

[0004] The embodiments of this application provide the following technical solutions:

[0005] According to an embodiment of the present application, a data reporting method includes: obtaining target buried point data, wherein the target buried point data includes a target tag; determining reporting configuration information corresponding to the target tag based on a preset correspondence, wherein the preset correspondence includes a correspondence between one or more tag information and one or more reporting configuration information, and the one or more tag information are respectively used to indicate one or more functional modules, each functional module corresponds to a reporting configuration information, and the reporting configuration information corresponding to each functional module is used to indicate a data processing strategy for buried point data corresponding to one or more buried points belonging to the functional module, and the target tag belongs to the one or more tag information; processing the target buried point data according to the data processing strategy indicated by the reporting configuration information corresponding to the target tag, so as to report the processed target buried point data.

[0006] In some embodiments of the present application, the label information includes a first-level label, a second-level label and a third-level label, wherein the first-level label is used to indicate a functional module, which is obtained by modular division based on different functions in the device; the second-level label is used to indicate a sub-module of the functional module, which is divided based on a target strategy; and the third-level label is used to indicate the burial point identification information of the sub-module belonging to the functional module.

[0007] In some embodiments of the present application, the tag information includes a first-level tag, wherein the first-level tag is used to indicate a functional module, and the functional module is obtained by modular division based on different functional performances in the device.

[0008] In some embodiments of the present application, the data processing strategy includes not reporting, processing the buried data based on the data processing strategy, and reporting.

[0009] In some embodiments of the present application, the data processing strategy includes a reporting field processing strategy and / or a reporting indicator processing strategy, the reporting field processing strategy refers to a processing strategy for data fields, and the reporting indicator processing strategy refers to a generation strategy for data reporting indicators corresponding to buried data.

[0010] In some embodiments of the present application, the target tracking data is processed according to the data processing strategy indicated by the reporting configuration information corresponding to the target tag, including: if the data processing strategy is to process the tracking data and report based on the data processing strategy, generate indicator data of the corresponding data reporting indicator according to the generation strategy, and process the data field in the indicator data according to the processing strategy.

[0011] In some embodiments of the present application, a cache area and a first interface are established in the log saving process, the first interface is used for calling by the first performance module in the user program space, and the log saving process includes a target thread; a target kernel thread, a communication thread and a second interface are established in the kernel space, the target kernel thread communicates with the target thread across threads through the communication thread, and the second interface is used for calling by the second performance module in the kernel space; the first performance module and the second performance module are sub-modules of a specific functional module; before obtaining the target buried point data, the method also includes: when the data collection buried point in the first performance module collects the first buried point data, the first performance module calls the first interface to save the first buried point data to the cache area; when the data collection buried point in the second performance module collects the second buried point data, the second performance module calls the second interface to save the second buried point data to the cache area through the cross-thread communication; obtaining the target buried point data includes: obtaining the target buried point data from the cache area.

[0012] According to another embodiment of the present application, a storage medium stores a computer program thereon, and when the computer program is executed by a processor of a computer, the computer is caused to execute the method described in the embodiment of the present application.

[0013] According to another embodiment of the present application, an electronic device may include: a memory storing a computer program; and a processor reading the computer program stored in the memory to execute the method described in the embodiment of the present application.

[0014] In an embodiment of the present application, target buried point data is obtained, and the target buried point data includes a target tag; according to a preset corresponding relationship, the reporting configuration information corresponding to the target tag is determined, wherein the preset corresponding relationship includes a correspondence between one or more tag information and one or more reporting configuration information, and the one or more tag information are respectively used to indicate one or more performance modules, each performance module corresponds to a type of reporting configuration information, and the reporting configuration information corresponding to each performance module is used to indicate a data processing strategy for the buried point data corresponding to one or more buried points belonging to the performance module, and the target tag belongs to the one or more tag information; the target buried point data is processed according to the data processing strategy indicated by the reporting configuration information corresponding to the target tag, so as to report the processed target buried point data.

[0015] In this way, the data collected by data collection points is not reported directly separately. Instead, under the preset correspondence and target label settings, different processing strategies are implemented based on different performance modules to process the data before reporting, thereby realizing the separation of points and the unification of data management, effectively improving the controllability of reporting of data, and effectively guaranteeing the data performance of successfully reported data, thereby improving the effect of performance analysis based on data. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

[0017] Figure 1 A schematic diagram of a system to which embodiments of the present application can be applied is shown.

[0018] Figure 2 A flowchart of a method for reporting burial point data according to an embodiment of the present application is shown.

[0019] Figure 3 A block diagram of a device for reporting buried point data according to an embodiment of the present application is shown.

[0020] Figure 4 A block diagram of an electronic device according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0021] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without making creative efforts are within the scope of protection of this application.

[0022] In the following description, the specific embodiments of the present application will be described with reference to steps and symbols performed by one or more computers, unless otherwise stated. Therefore, these steps and operations will be referred to as being performed by a computer several times, and computer execution referred to herein includes the operation of a computer processing unit by electronic signals representing data in a structured form. This operation converts the data or maintains it at a location in the memory system of the computer, which can be reconfigured or otherwise change the operation of the computer in a manner familiar to those skilled in the art. The data structure in which the data is maintained is a physical location in the memory, which has specific characteristics defined by the data format. However, the principles of the present application are described in the above text, which does not represent a limitation, and those skilled in the art will understand that the various steps and operations described below can also be implemented in hardware.

[0023] Figure 1 Schematic diagram of a system 100 to which embodiments of the present application can be applied is shown. Figure 1 As shown, the system 100 may include a server 101 and a terminal 102. The terminal 102 may be any computer device, such as a computer, a mobile phone, a smart watch, or a home appliance. The server 101 may be a server cluster or a cloud service.

[0024] In one implementation of this example, the terminal 102 can: obtain target buried point data, the target buried point data includes a target tag; determine the reporting configuration information corresponding to the target tag according to a preset corresponding relationship, wherein the preset corresponding relationship includes a correspondence between one or more tag information and one or more reporting configuration information, the one or more tag information are respectively used to indicate one or more performance modules, each performance module corresponds to a reporting configuration information, and the reporting configuration information corresponding to each performance module is used to indicate the data processing strategy of the buried point data corresponding to one or more buried points belonging to the performance module, and the target tag belongs to the one or more tag information; process the target buried point data according to the data processing strategy indicated by the reporting configuration information corresponding to the target tag, so as to report the processed target buried point data. In one example, the processed target buried point data can be reported to the server 101.

[0025] In the embodiment of the present application, the terminal divides the device performance into at least one performance module by modularization, such as a kernel module, an application (app) module, a boot animation (bootanim), and a multimedia framework (media) module.

[0026] One or more tracking points can be set in each performance module. Each tracking point can collect target tracking data, and the target tracking data collected by the tracking point contains the target label.

[0027] In an embodiment of the present application, a preset correspondence is also set, and the preset correspondence includes a correspondence between one or more tag information and one or more reporting configuration information. The one or more tag information are respectively used to indicate one or more performance modules, and each performance module corresponds to a type of reporting configuration information. The reporting configuration information corresponding to each performance module is used to indicate the data processing strategy of the burial point data corresponding to one or more burial points belonging to the performance module.

[0028] The target tag contained in the target tracking data belongs to the one or more tag information. The tag information corresponding to the target tag can be determined from the threshold correspondence relationship, and the reporting configuration information corresponding to the tag information corresponding to the target tag is the reporting configuration information corresponding to the target tag.

[0029] Figure 2 The flowchart of the data reporting method according to an embodiment of the present application is schematically shown. The execution subject of the data reporting method can be any device, such as Figure 1 Terminal 102 is shown.

[0030] like Figure 2 As shown, the data reporting method may include steps S210 to S230.

[0031] Step S210: acquiring target buried point data, wherein the target buried point data includes a target label;

[0032] Step S220: Determine the reporting configuration information corresponding to the target tag based on a preset correspondence relationship, wherein the preset correspondence relationship includes a correspondence between one or more tag information and one or more reporting configuration information, the one or more tag information are respectively used to indicate one or more performance modules, each performance module corresponds to a type of reporting configuration information, and the reporting configuration information corresponding to each performance module is used to indicate a data processing strategy for the tracking data corresponding to one or more tracking points belonging to the performance module, and the target tag belongs to the one or more tag information;

[0033] Step S230: Process the target buried data according to the data processing strategy indicated by the reporting configuration information corresponding to the target tag, so as to report the processed target buried data.

[0034] Obtaining the target buried point data collected by the local data collection buried point can be done before the corresponding module of the data collection buried point reports the collected target buried point data. In one example, all modules are uniformly set to cache the collected buried point data in the local cache area, and the target buried point data can be taken from the cache area for unified processing.

[0035] After obtaining the target buried point data, the target label contained in the target buried point data can be obtained by extracting information from the target buried point data.

[0036] Then, the preset correspondence relationship includes the correspondence between one or more tag information and one or more reporting configuration information, and the one or more tag information are respectively used to indicate one or more performance modules, each performance module corresponds to a reporting configuration information, and the reporting configuration information corresponding to each performance module is used to indicate the data processing strategy of the burial point data corresponding to one or more burial points belonging to the performance module.

[0037] The target tag contained in the target tracking data belongs to the one or more tag information. The tag information corresponding to the target tag can be determined from the threshold correspondence relationship, and the reporting configuration information corresponding to the tag information corresponding to the target tag is the reporting configuration information corresponding to the target tag.

[0038] The target tracking data is processed according to the data processing strategy indicated by the reporting configuration information corresponding to the target tag, and the processed target tracking data is reported. The tracking data can be processed with different processing strategies based on different performance modules and then reported.

[0039] In this way, based on steps S210 to S230, the data collection points do not directly report the collected point data separately. Instead, under the preset correspondence and target label settings, different processing strategies are implemented based on different performance modules to process the point data and then report it, thereby realizing the separation of points and the unification of data management, effectively improving the controllability of reporting point data, and effectively guaranteeing the data performance of successfully reported point data, thereby improving the effect of performance analysis based on point data.

[0040] The following describes the specific process of each step when reporting tracking data.

[0041] In step S210, target buried point data is obtained, where the target buried point data includes a target label.

[0042] In the implementation of this example, the target buried point data collected by the local data collection buried point can be obtained before the corresponding module of the data collection buried point reports the collected target buried point data. In one example, all modules are uniformly set to cache the collected buried point data to the local cache area, and the target buried point data can be taken from the cache area for unified processing.

[0043] After obtaining the target buried point data, in one example, the target buried point data is extracted and the data summary information in the buried point data is used as the target label. The data summary information includes the collection location information (such as which module it comes from) and the buried point mark information (such as which buried point is collected). In one example, the buried point can be set so that the buried point data collected by the buried point has its own target label.

[0044] In one embodiment, a cache area and a first interface are established in a log saving process, the first interface is used for being called by a first performance module in a user program space, and the log saving process includes a target thread; a target kernel thread, a communication thread and a second interface are established in a kernel space, the target kernel thread communicates with the target thread across threads through the communication thread, and the second interface is used for being called by a second performance module in the kernel space; in step S210, before obtaining the buried point data collected by the local data acquisition buried point, the method further includes: when the data acquisition buried point in the first performance module collects the first buried point data, the first performance module calls the first interface to save the first buried point data to the cache area; when the data acquisition buried point in the second performance module collects the second buried point data, the second performance module calls the second interface to save the second buried point data to the cache area through the cross-thread communication; in step S210, obtaining the target buried point data includes: obtaining the target buried point data from the cache area.

[0045] The first performance module and the second performance module are both terminal performance modules in the terminal. The terminal can be divided into multiple functional modules, each functional module can correspond to multiple sub-modules, and each sub-module is a performance module. The first performance module is located in the user program space (i.e., userspace), and examples of the first performance modules include the AMS module, Looper module, Native module, Recents module, Contact module, and Mms module. The second performance module is located in the kernel space (i.e., kernelspace), and examples of the second performance modules include the Mem module, CPU module, and I0 module.

[0046] The log storage process, namely the logd process, establishes a cache area and a first interface in the log storage process. The first interface is used for calling by a first performance module in the user program space. The log storage process includes a target thread. A target kernel thread, a communication thread, and a second interface are established in the kernel space. The target kernel thread communicates with the target thread through the communication thread. The second interface is used for calling by a second performance module in the kernel space.

[0047] In this way, a unified management framework for performance modules in user program space and kernel space can be realized. Based on this framework, the coupling between data collection points can be reduced and data caching can be convenient and reliable. For the buried point data collected by data collection points in different performance modules, unified cache processing can be realized conveniently and reliably. That is, when the data collection point in the first performance module collects the first buried point data, the first performance module calls the first interface and saves the first buried point data to the cache area; when the data collection point in the second performance module collects the second buried point data, the second performance module calls the second interface and saves the second buried point data to the cache area through cross-thread communication. After the data is saved in the cache area, the target buried point data can be pulled locally from the cache area without the need for each module to report separately. The reliable caching method further improves the controllability of reporting buried point data.

[0048] In step S220, the reporting configuration information corresponding to the target tag is determined based on the preset corresponding relationship, wherein the preset corresponding relationship includes the corresponding relationship between one or more tag information and one or more reporting configuration information, and the one or more tag information are respectively used to indicate one or more functional modules, each functional module corresponds to a type of reporting configuration information, and the reporting configuration information corresponding to each functional module is used to indicate the data processing strategy of the burial point data corresponding to one or more burial points belonging to the functional module, and the target tag belongs to the one or more tag information.

[0049] Functional modules include kernel modules, application modules, boot animation modules (bootanim), and multimedia framework modules (media).

[0050] The preset correspondence relationship can be a function of a threshold or a configuration table. The preset correspondence relationship includes a correspondence between one or more tag information and one or more reporting configuration information, for example, A tag information corresponds to A1 reporting configuration information. The one or more tag information is used to indicate one or more functional modules, for example, A tag information indicates K functional module.

[0051] The target tag belongs to one or more tag information, for example, the target tag belongs to A tag information. Then, the reporting configuration information corresponding to the target tag is A1 reporting configuration information corresponding to the A tag information, and the A1 reporting configuration information corresponds to the K function module.

[0052] In one embodiment, the tag information includes a first-level tag, wherein the first-level tag is used to indicate a functional module, and the functional module is obtained by modular division based on different functions in the device.

[0053] Functional modules include kernel modules, application modules, boot animation modules, and multimedia framework modules.

[0054] In this embodiment, each tag information only includes a first-level tag that can indicate a functional module. Furthermore, the target tag included in the tracking data can belong to a first-level tag, for example, the target tag is a first-level tag.

[0055] In one embodiment, the label information includes a first-level label, a second-level label, and a third-level label, wherein the first-level label is used to indicate a functional module, which is obtained by modular division based on different functions in the device; the second-level label is used to indicate a sub-module of the functional module, which is divided based on a target strategy; and the third-level label is used to indicate the burial point identification information of the sub-module belonging to the functional module.

[0056] Functional modules include kernel modules, application modules, boot animation modules, and multimedia framework modules. Each functional module can be divided into multiple submodules based on target strategies, which can be designed based on actual conditions. Submodules can be divided into performance modules based on the performance of the functional modules.

[0057] Furthermore, the first-level label corresponds to the functional module, the second-level module corresponds to the sub-module, and the third-level label corresponds to the tracking point in the functional module.

[0058] In this way, the definition of corresponding labels for different modules (functional modules and their sub-modules) further characterizes the multiple performance tracking scenarios in the device. Based on this, the tracking data is processed and reported, and the performance of the reported data is statistically analyzed in many aspects. Different modules are identified by unique labels, which further refines the separation of tracking points and the unification of information processing. This can more accurately reflect the performance status of the device and has a great guiding role in the performance optimization of the device.

[0059] In some embodiments, the data processing strategy includes not reporting, processing the buried data based on the data processing strategy, and reporting.

[0060] In some embodiments, the data processing strategy includes a reporting field processing strategy and / or a reporting indicator processing strategy, the reporting field processing strategy refers to a processing strategy for data fields, and the reporting indicator processing strategy refers to a generation strategy for data reporting indicators corresponding to buried data.

[0061] Further, referring to Table (1) and Table (2), in one embodiment, the preset correspondence includes a reporting information table and a reporting indicator table; the reporting information table includes at least one label information, and the label information includes a first-level label, a second-level label and a third-level label; the reporting indicator table includes at least one label information, and the label information includes a first-level label, a second-level label and a third-level label; wherein, the first-level label is used to indicate a functional module, and the functional module is obtained by modular division based on different functions in the device; the second-level label is used to indicate a sub-module of the functional module, and the sub-module of the functional module is divided based on a target strategy; the third-level label is used to indicate the burial point identification information of the burial point of the sub-module belonging to the functional module.

[0062] For example, referring to Table (1) and Table (2), a functional module is Kernel (kernel module), the first-level label corresponding to Kernel is 01, Kernel includes a submodule (that is, Kernel itself is the submodule), the second-level label corresponding to the submodule is 1, the submodule includes multiple tracking points, and the third-level label corresponding to one of the tracking points is io_basic_info. At this time, a label information can be 01-1-io_basic_info. On the basis of pointing to the functional module Kernel, the label information further points to the submodule and tracking point in the functional module Kernel.

[0063] The reporting information table and the reporting indicator table can realize the independent configuration of the reported field information and the reported indicator information, but both are managed through a unique tracking module label. According to the tracking module label, the reported field information and the reported indicator information can be accurately obtained to ensure accurate reporting.

[0064] Furthermore, determining the reporting configuration information corresponding to the target tag according to the preset corresponding relationship may include: determining the reporting configuration information corresponding to the tag information corresponding to the target tag from the reporting information table and the reporting indicator table.

[0065] Furthermore, the reporting configuration information may include not reporting, processing the buried data based on the data processing strategy, and reporting. For example, referring to Table (1), if the tag information corresponding to the target tag is 01-1-io_basic_info, the "enablement status" corresponding to 01-1-io_basic_info can be further queried from Table (1) to be "enabled", and then, the reporting configuration information can indicate processing the buried data based on the data processing strategy and reporting. On the contrary, if the tag information corresponding to the target tag is 02-1-boot, the "enablement status" corresponding to 02-1-boot can be further queried from Table (1) to be "not enabled", and then, at this time, the reporting configuration information can indicate not reporting.

[0066] Furthermore, when the reporting configuration information is to process the buried data and report it based on the data processing strategy, the data processing strategy may include a reporting field processing strategy and / or a reporting indicator processing strategy. The reporting field processing strategy refers to the processing strategy of the data field, and the reporting indicator processing strategy refers to the generation strategy of the data reporting indicator corresponding to the buried data.

[0067] Refer to Table (1) and Table (2). For example, if the tag information corresponding to the target tag is 01-1-io_basic_info, you can further query from Table (1) that the "enablement status" corresponding to 01-1-io_basic_info is "enabled". Then, the reporting configuration information can indicate the processing of the embedded data and reporting based on the data processing strategy.

[0068] Furthermore, the reporting field processing strategy corresponding to 01-1-io_basic_info can be queried from the "reporting field information" column in Table (1) (it should be noted that the reporting field processing strategy in the reporting field information in Table (1) can be set according to actual needs. In some examples, each tag information corresponds to a reporting field processing strategy, and in some examples, multiple tag information corresponds to one reporting field processing strategy).

[0069] The corresponding reporting indicator processing strategy can be further queried from the "reporting indicator information (such as Type, UserID, ProjectID and other configuration information)" column in Table (2).

[0070]

[0071]

[0072]

[0073] Table (1)

[0074]

[0075]

[0076] Table (2)

[0077] In step S230, the target buried data is processed according to the data processing strategy indicated by the reporting configuration information corresponding to the target tag, so as to report the processed target buried data.

[0078] The target buried data is processed based on the data processing strategy indicated by the reported configuration information. If the reported configuration information indicates differentiated processing information (such as the format that needs to be converted, the fields that need to be extracted, etc.), the buried data can be differentially processed to obtain the processed buried data, and then the processed buried data can be reported.

[0079] In one embodiment, processing the target tracking data according to the data processing strategy indicated by the reporting configuration information corresponding to the target tag includes:

[0080] If the data processing strategy is to process the buried data and report it based on the data processing strategy, the indicator data of the corresponding data reporting indicator is generated according to the generation strategy, and the data fields in the indicator data are processed according to the processing strategy.

[0081] The data processing strategy may include a reporting field processing strategy and / or a reporting indicator processing strategy. The reporting field processing strategy refers to the processing strategy of the data field, and the reporting indicator processing strategy refers to the generation strategy of the data reporting indicator corresponding to the buried data.

[0082] For example, data reporting indicators include Type, UserID, ProjectID and other configuration information. According to the generation strategy of each data reporting indicator in the reporting indicator processing strategy, the target tracking data can be processed accordingly to generate indicator data corresponding to Type, UserID, ProjectID and other configuration information. Then, the indicator data is processed according to the reporting field processing strategy, which refers to the processing strategy of the data field, to obtain the processed tracking data, which is then reported.

[0083] To facilitate better implementation of the method for reporting buried data provided in the embodiment of the present application, the embodiment of the present application also provides a device for reporting buried data based on the aforementioned method for reporting buried data. The meanings of the terms herein are the same as those in the aforementioned method for reporting buried data. For specific implementation details, please refer to the description in the method embodiment. Figure 3 A block diagram of a device for reporting buried point data according to an embodiment of the present application is shown.

[0084] like Figure 3 As shown, the reporting device 300 for buried point data may include a data acquisition unit 310, a configuration acquisition unit 320, and a reporting processing unit 330.

[0085] The data acquisition unit 310 can be used to acquire target buried point data, and the target buried point data includes a target tag; the configuration acquisition unit 320 can be used to determine the reporting configuration information corresponding to the target tag based on a preset corresponding relationship, wherein the preset corresponding relationship includes a correspondence between one or more tag information and one or more reporting configuration information, and the one or more tag information are respectively used to indicate one or more performance modules, each performance module corresponds to a reporting configuration information, and the reporting configuration information corresponding to each performance module is used to indicate the data processing strategy of the buried point data corresponding to one or more buried points belonging to the performance module, and the target tag belongs to the one or more tag information; the reporting processing unit 330 can be used to process the target buried point data according to the data processing strategy indicated by the reporting configuration information corresponding to the target tag, so as to report the processed target buried point data.

[0086] In some embodiments of the present application, the label information includes a first-level label, a second-level label and a third-level label, wherein the first-level label is used to indicate a functional module, which is obtained by modular division based on different functions in the device; the second-level label is used to indicate a sub-module of the functional module, which is divided based on a target strategy; and the third-level label is used to indicate the burial point identification information of the sub-module belonging to the functional module.

[0087] In some embodiments of the present application, the tag information includes a first-level tag, wherein the first-level tag is used to indicate a functional module, and the functional module is obtained by modular division based on different functional performances in the device.

[0088] In some embodiments of the present application, the data processing strategy includes not reporting, processing the buried data based on the data processing strategy, and reporting.

[0089] In some embodiments of the present application, the data processing strategy includes a reporting field processing strategy and / or a reporting indicator processing strategy, the reporting field processing strategy refers to a processing strategy for data fields, and the reporting indicator processing strategy refers to a generation strategy for data reporting indicators corresponding to buried data.

[0090] In some embodiments of the present application, the target tracking data is processed according to the data processing strategy indicated by the reporting configuration information corresponding to the target tag, including: if the data processing strategy is to process the tracking data and report based on the data processing strategy, generate indicator data of the corresponding data reporting indicator according to the generation strategy, and process the data field in the indicator data according to the processing strategy.

[0091] In some embodiments of the present application, a cache area and a first interface are established in the log saving process, the first interface is used for being called by the first performance module in the user program space, and the log saving process includes a target thread; a target kernel thread, a communication thread and a second interface are established in the kernel space, the target kernel thread communicates with the target thread across threads through the communication thread, and the second interface is used for being called by the second performance module in the kernel space; the first performance module and the second performance module are sub-modules of a specific functional module; the device also includes: a first cache unit, for when the data collection point in the first performance module collects the first point data, the first performance module calls the first interface and saves the first point data to the cache area; a second cache unit, for when the data collection point in the second performance module collects the second point data, the second performance module calls the second interface and saves the second point data to the cache area through the cross-thread communication; the data acquisition unit is used to: obtain the target point data from the cache area.

[0092] It should be noted that, although several modules or units of the device for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiment of the application, the features and functions of two or more modules or units described above can be concretized in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into multiple modules or units to be concretized.

[0093] In addition, an embodiment of the present application further provides an electronic device, which may be a terminal or a server, such as Figure 4 , which shows a schematic structural diagram of an electronic device involved in an embodiment of the present application, specifically:

[0094] The electronic device may include one or more processing core processors 401, one or more computer-readable storage media memories 402, a power supply 403, an input unit 404 and other components. Those skilled in the art will understand that Figure 4 The electronic device structure shown in the figure does not constitute a limitation of the electronic device, and may include more or fewer components than shown in the figure, or combine certain components, or arrange components differently.

[0095] Processor 401 is the control center of the electronic device, connecting the various components of the entire computer device using various interfaces and lines. By running or executing software programs and / or modules stored in memory 402 and accessing data stored in memory 402, it performs various computer device functions and processes data, thereby monitoring the electronic device as a whole. Optionally, processor 401 may include one or more processing cores; preferably, processor 401 may integrate an application processor and a modem processor, wherein the application processor primarily processes the operating system, user interfaces, and application programs, while the modem processor primarily handles wireless communications. It is understood that the modem processor may not be integrated into processor 401.

[0096] The memory 402 can be used to store software programs and modules. The processor 401 executes various functional applications and data processing by running the software programs and modules stored in the memory 402. The memory 402 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc.; the data storage area may store data created according to the use of the computer device, etc. In addition, the memory 402 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage device. Accordingly, the memory 402 may also include a memory controller to provide the processor 401 with access to the memory 402.

[0097] The electronic device also includes a power supply 403 for supplying power to various components. Preferably, the power supply 403 can be logically connected to the processor 401 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The power supply 403 can also include one or more DC or AC power supplies, a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator, and other arbitrary components.

[0098] The electronic device may further include an input unit 404, which may be configured to receive input digital or character information and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control.

[0099] Although not shown, the electronic device may further include a display unit, etc., which will not be described in detail here. Specifically, in this embodiment, the processor 401 in the electronic device will load the executable files corresponding to the processes of one or more computer programs into the memory 402 according to the following instructions, and the processor 401 will run the computer programs stored in the memory 402, thereby realizing the various functions of the aforementioned embodiments of the present application. For example, the processor 401 may perform the following steps:

[0100] Obtain target buried point data, wherein the target buried point data includes a target tag; determine the reporting configuration information corresponding to the target tag based on a preset corresponding relationship, wherein the preset corresponding relationship includes a corresponding relationship between one or more tag information and one or more reporting configuration information, and the one or more tag information are respectively used to indicate one or more functional modules, each functional module corresponds to a reporting configuration information, and the reporting configuration information corresponding to each functional module is used to indicate a data processing strategy for the buried point data corresponding to one or more buried points belonging to the functional module, and the target tag belongs to the one or more tag information; process the target buried point data according to the data processing strategy indicated by the reporting configuration information corresponding to the target tag, so as to report the processed target buried point data.

[0101] Those skilled in the art will appreciate that all or part of the steps in the various methods of the above embodiments may be accomplished by a computer program, or by controlling related hardware through a computer program. The computer program may be stored in a computer-readable storage medium and loaded and executed by a processor.

[0102] To this end, an embodiment of the present application further provides a storage medium storing a computer program, which can be loaded by a processor to execute the steps of any method provided in the embodiment of the present application.

[0103] The storage medium may include a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0104] Since the computer program stored in the storage medium can execute the steps of any method provided in the embodiments of the present application, the beneficial effects that can be achieved by the method provided in the embodiments of the present application can be achieved. Please refer to the previous embodiments for details and will not be repeated here.

[0105] Those skilled in the art will readily conceive of other embodiments of the present application after considering the specification and practicing the embodiments disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present application that follow the general principles of this application and include common knowledge or customary techniques in the art that are not disclosed herein.

[0106] It should be understood that the present application is not limited to the embodiments that have been described above and shown in the accompanying drawings, but various modifications and changes may be made without departing from the scope thereof.

Claims

1. A data reporting method, characterized in that: include: Obtain target buried point data, where the target buried point data includes a target label; Determine the reporting configuration information corresponding to the target tag according to the preset corresponding relationship, wherein the preset corresponding relationship includes a correspondence between one or more tag information and one or more reporting configuration information, the one or more tag information are respectively used to indicate one or more functional modules, each functional module corresponds to a type of reporting configuration information, and the reporting configuration information corresponding to each functional module is used to indicate the data processing strategy of the burial point data corresponding to one or more burial points belonging to the functional module, and the target tag belongs to the one or more tag information; The target buried point data is processed according to the data processing strategy indicated by the reporting configuration information corresponding to the target tag to report the processed target buried point data; wherein, a cache area and a first interface are established in the log saving process, and the first interface is used for calling by the first performance module in the user program space, and the log saving process includes a target thread; a target kernel thread, a communication thread and a second interface are established in the kernel space, and the target kernel thread communicates with the target thread across threads through the communication thread, and the second interface is used for calling by the second performance module in the kernel space; the first performance module and the second performance module are sub-modules of a specific functional module; Before acquiring the target buried point data, the method further includes: when the data acquisition buried point in the first performance module collects first buried point data, the first performance module calls the first interface to save the first buried point data to the cache area; when the data acquisition buried point in the second performance module collects second buried point data, the second performance module calls the second interface to save the second buried point data to the cache area through the cross-thread communication; The obtaining of target buried point data includes: obtaining the target buried point data from the cache area.

2. The method according to claim 1, characterized in that The label information includes a first-level label, a second-level label and a third-level label, wherein the first-level label is used to indicate a functional module, which is obtained by modular division based on different functions in the device; the second-level label is used to indicate a sub-module of the functional module, which is divided based on a target strategy; and the third-level label is used to indicate the burial point identification information of the sub-module belonging to the functional module.

3. The method according to claim 1, characterized in that The tag information includes a first-level tag, wherein the first-level tag is used to indicate a functional module, and the functional module is obtained by modular division based on different functional performances in the device.

4. The method according to claim 1, wherein The data processing strategy includes not reporting, processing the buried data based on the data processing strategy, and reporting.

5. The method according to claim 4, characterized in that The data processing strategy includes a reporting field processing strategy and / or a reporting indicator processing strategy. The reporting field processing strategy refers to a processing strategy for data fields, and the reporting indicator processing strategy refers to a generation strategy for data reporting indicators corresponding to buried data.

6. The method according to claim 5, characterized in that The processing of the target tracking data according to the data processing strategy indicated by the reporting configuration information corresponding to the target tag includes: If the data processing strategy is to process the buried data and report it based on the data processing strategy, the indicator data of the corresponding data reporting indicator is generated according to the generation strategy, and the data fields in the indicator data are processed according to the processing strategy.

7. A data reporting device, characterized in that: include: A data acquisition unit is used to: acquire target buried point data from a buffer area, wherein the target buried point data includes a target tag; A configuration acquisition unit, configured to: determine the reporting configuration information corresponding to the target tag according to a preset corresponding relationship, wherein the preset corresponding relationship includes a corresponding relationship between one or more tag information and one or more reporting configuration information, the one or more tag information are respectively used to indicate one or more performance modules, each performance module corresponds to a type of reporting configuration information, and the reporting configuration information corresponding to each performance module is used to indicate a data processing strategy for the buried point data corresponding to one or more buried points belonging to the performance module, and the target tag belongs to the one or more tag information; A reporting processing unit, used for: processing the target buried data according to the data processing strategy indicated by the reporting configuration information corresponding to the target tag, so as to report the processed target buried data; wherein, the cache area and the first interface are established in the log saving process, the first interface is used for being called by the first performance module in the user program space, and the log saving process includes a target thread; a target kernel thread, a communication thread and a second interface are established in the kernel space, the target kernel thread communicates with the target thread across threads through the communication thread, and the second interface is used for being called by the second performance module in the kernel space; the first performance module and the second performance module are submodules of a specific functional module; The first cache unit is used for: before obtaining the target buried point data, when the data acquisition buried point in the first performance module collects the first buried point data, the first performance module calls the first interface to save the first buried point data to the cache area; when the data acquisition buried point in the second performance module collects the second buried point data, the second performance module calls the second interface to save the second buried point data to the cache area through the cross-thread communication.

8. A storage medium, characterized in that: A computer program is stored thereon, and when the computer program is executed by a processor of a computer, the computer is caused to execute the method according to any one of claims 1 to 6.

9. An electronic device, characterized in that: include: a memory storing a computer program; A processor reads a computer program stored in a memory to execute the method according to any one of claims 1 to 6.

Images