Tracking data reporting method and apparatus, storage medium, and electronic device

Abstract

A tracking data reporting method, comprising: enabling an initial tracking point among a plurality of tracking points corresponding to a tracking point directed graph; enabling a subsequently triggered tracking point on the basis of tracking data triggered by the initial tracking point and the tracking point directed graph; calculating a reporting throughput upper limit value on the basis of a weight of each tracking point level corresponding to the initial tracking point and the subsequently triggered tracking point; and reporting target tracking data on the basis of a comparison result between the reporting throughput upper limit value and a predetermined throughput threshold. In this way, the possibility of server crash caused by tracking data reporting can be reduced. Also provided are a tracking data reporting apparatus, a storage medium, and an electronic device.

Description

Method, device, storage medium and electronic device for reporting buried point data

[0001] The present application claims priority to the Chinese patent application No. 202410686161.4, filed on May 29, 2024, and entitled "Method, device, storage medium and electronic device for reporting buried point data", the whole content of which is incorporated herein by reference. TECHNICAL FIELD

[0002] The present application relates to the technical field of data transmission, in particular to a method, device, storage medium and electronic device for reporting buried point data. BACKGROUND

[0003] Currently, in order to improve the user experience of electronic devices or solve the abnormality of electronic devices in use, more and more buried points are usually added in the specific process of system / application in electronic devices, abnormal handling process and other processes. The data in the process (i.e. buried point data) is collected through the buried points. The collected data (i.e. buried point data) is used as data support for improving user experience or solving abnormal problems. The buried point data usually needs to be reported to the server. TECHNICAL PROBLEM

[0004] The current buried point data reporting scheme usually reports the buried point data to the server when the code logic is executed to the position of the buried point or the data volume reaches the threshold value, etc. triggering condition. The situation of multiple buried points reporting buried point data at the same time often occurs, which can easily cause the server to crash. TECHNICAL SOLUTION

[0005] The present application provides a buried point data reporting scheme, which can effectively improve the reliability of buried point data reporting in electronic devices and reduce the problem of server crash caused by buried point data reporting.

[0006] The present application provides the following technical solutions:

[0007] According to an embodiment of the present application, a method for reporting buried point data comprises: starting an initialization buried point in a plurality of buried points corresponding to a buried point directed graph, wherein the buried point directed graph is used to indicate the hierarchical relationship and the association relationship between the plurality of buried points, and the plurality of buried points correspond to at least two buried point levels; starting a subsequent trigger buried point in the plurality of buried points according to the buried point data triggered by the initialization buried point and the buried point directed graph; calculating an upper limit value of reporting throughput according to the weight of each buried point level corresponding to the initialization buried point and the subsequent trigger buried point; and reporting target buried point data to a server according to the comparison result of the upper limit value of reporting throughput and a predetermined throughput threshold value.

[0008] In some embodiments of the present application, the starting the initialization event in the plurality of events corresponding to the event directed graph comprises: determining events in a first event level in the event directed graph from the plurality of events; and obtaining the initialization event in the plurality of events according to the events in the first event level.

[0009] In some embodiments of the present application, the obtaining the initialization event in the plurality of events according to the events in the first event level comprises: taking the events in the first event level as the initialization event in the plurality of events; or obtaining a device monitoring scenario, and taking an event in the first event level matching the device monitoring scenario as the initialization event in the plurality of events.

[0010] In some embodiments of the present application, the starting the subsequent triggered event in the plurality of events according to the event data triggered by the initialization event and the event directed graph comprises: triggering and starting each event in an event level associated with the initialization event according to the event data triggered by the initialization event and the event directed graph in order of the event levels, to start the subsequent triggered event in the plurality of events.

[0011] In some embodiments of the present application, the calculating the upper limit of the reporting throughput according to the weight of each event level corresponding to the initialization event and the subsequent triggered event comprises: obtaining the number of events in each event level corresponding to the initialization event and the subsequent triggered event; obtaining the total number of the initialization event and the subsequent triggered event; and calculating the upper limit of the reporting throughput according to the number of events in each event level corresponding to the initialization event and the subsequent triggered event, the total number of the initialization event and the subsequent triggered event, and the weight of each event level corresponding to the initialization event and the subsequent triggered event.

[0012] In some embodiments of the present application, the reporting the target event data to the server according to the comparison result of the upper limit of the reporting throughput and the predetermined throughput threshold comprises: if the upper limit of the reporting throughput is less than or equal to the predetermined throughput threshold, reporting the target event data to the server, the target event data being all the currently triggered event data; and if the upper limit of the reporting throughput is greater than the predetermined throughput threshold, reporting the target event data to the server, the target event data being part of the currently triggered event data.

[0013] In some embodiments of the present application, after the target buried point data is reported to the server, if the upper limit of the reporting throughput is greater than the predetermined throughput threshold, the method further comprises: caching the remaining buried point data in the current triggered all buried point data except the target buried point data, and the remaining buried point data is used for reporting when a predetermined reporting condition is met.

[0014] In some embodiments of the present application, before the upper limit of the reporting throughput is calculated according to the weight of each buried point level corresponding to the initial buried point and the subsequent triggered buried point, the method further comprises: obtaining server load data of the server; and determining the weight of each buried point level in the at least two buried point levels in the buried point directed graph according to the server load data.

[0015] In some embodiments of the present application, the server load data comprises a server throughput upper limit value and a user concurrency upper limit value, and the weight of each buried point level in the at least two buried point levels in the buried point directed graph is determined according to the server load data, comprising: calculating according to the formula ΣT=M*(N1*w1+N2*w2+N3*w3+...+Ni*wi+...+Nn*wn) to obtain the weight of each buried point level in the buried point directed graph, wherein ΣT refers to the server throughput upper limit value, M refers to the user concurrency upper limit value, n is the total number of buried point levels included in the buried point directed graph, i refers to the i-th buried point level, Ni refers to the number of buried points in the i-th buried point level, and wi refers to the weight of the i-th buried point level.

[0016] In some embodiments of the present application, before the server load data of the server is obtained, the method further comprises: obtaining an updated buried point reporting management and control configuration from the cloud; and obtaining the server load data and the buried point directed graph from the updated buried point reporting management and control configuration.

[0017] According to an embodiment of the present application, a device for reporting buried point data comprises: a buried point switch control module configured to open an initial buried point in a plurality of buried points corresponding to a buried point directed graph, wherein the buried point directed graph is configured to indicate a hierarchical relationship and an association relationship between the plurality of buried points, and the plurality of buried points correspond to at least two buried point hierarchies; the buried point switch control module is further configured to open a subsequent triggered buried point in the plurality of buried points according to buried point data triggered by the initial buried point and the buried point directed graph after opening the initial buried point; a throughput calculation module configured to calculate an upper limit value of a reporting throughput according to a weight of each buried point hierarchy corresponding to the initial buried point and the subsequent triggered buried point opened by the buried point switch control module; and a reporting processing module configured to report target buried point data to a server according to a comparison result of the upper limit value of the reporting throughput calculated by the throughput calculation module and a predetermined throughput threshold.

[0018] In some embodiments of the present application, the buried point switch control module is configured to determine a buried point at a first buried point hierarchy in the buried point directed graph from the plurality of buried points, obtain an initial buried point in the plurality of buried points according to the buried point at the first buried point hierarchy, and open the initial buried point.

[0019] In some embodiments of the present application, the buried point switch control module is configured to take the buried points at the first buried point hierarchy as the initial buried points in the plurality of buried points, or obtain a device monitoring scenario and take a buried point matching the device monitoring scenario among the buried points at the first buried point hierarchy as the initial buried point in the plurality of buried points.

[0020] In some embodiments of the present application, the buried point switch control module is configured to trigger and open, according to the buried point data triggered by the initial buried point and the buried point directed graph, each buried point hierarchy buried point associated with the initial buried point in sequence of the buried point hierarchies, to open the subsequent triggered buried point in the plurality of buried points.

[0021] In some embodiments of the present application, the throughput calculation module is configured to obtain a number of hierarchical buried points of each buried point hierarchy corresponding to the initial buried point and the subsequent triggered buried point, obtain a total number of the initial buried point and the subsequent triggered buried point, and calculate the upper limit value of the reporting throughput according to the number of hierarchical buried points of each buried point hierarchy corresponding to the initial buried point and the subsequent triggered buried point, the total number of the initial buried point and the subsequent triggered buried point, and the weight corresponding to each buried point hierarchy corresponding to the initial buried point and the subsequent triggered buried point.

[0022] In some embodiments of the present application, the reporting processing module is configured to: if the upper limit of the reporting throughput is less than or equal to the predetermined throughput threshold, report the target tracking data to the server, the target tracking data being all tracking data triggered currently; and if the upper limit of the reporting throughput is greater than the predetermined throughput threshold, report target tracking data to the server, the target tracking data being part of the tracking data triggered currently.

[0023] In some embodiments of the present application, after the reporting of the target tracking data to the server, the reporting processing module is configured to: cache the remaining tracking data other than the target tracking data in the tracking data triggered currently, the remaining tracking data being used for reporting when a predetermined reporting condition is met.

[0024] In some embodiments of the present application, before the weight of each tracking level corresponding to the initial tracking and the subsequent triggered tracking is determined, the device further comprises a configuration management module configured to: obtain server load data of the server; and determine the weight of each tracking level in the at least two tracking levels in the tracking directed graph according to the server load data.

[0025] In some embodiments of the present application, the server load data comprises an upper limit of server throughput and an upper limit of user concurrency, and the configuration management module is configured to: calculate the weight of each tracking level in the tracking directed graph according to the formula ΣT=M*(N1*w1+N2*w2+N3*w3+...+Ni*wi+...+Nn*wn), wherein ΣT represents the upper limit of server throughput, M represents the upper limit of user concurrency, n represents the total number of tracking levels included in the tracking directed graph, i represents the i-th tracking level, Ni represents the number of tracking in the i-th tracking level, and wi represents the weight of the i-th tracking level.

[0026] In some embodiments of the present application, before the server load data of the server is obtained, the configuration management module is configured to: obtain an updated tracking reporting management configuration from the cloud; and obtain the server load data and the tracking directed graph from the updated tracking reporting management configuration.

[0027] According to another embodiment of the present application, a storage medium having a computer program stored thereon, when the computer program is executed by a processor of a computer, causes the computer to execute the method according to the embodiments of the present application.

[0028] According to another embodiment of the present application, an electronic device can 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 embodiments of the present application.

[0029] According to another embodiment of the present application, a computer program product or computer program includes computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer readable storage medium, and the processor executes the computer instructions to make the computer device execute the method provided in various optional implementations of the embodiments of the present application. Advantages

[0030] In the embodiments of the present application, the initialization trace point in the plurality of trace points corresponding to the trace point directed graph is opened, wherein the trace point directed graph is used to indicate the hierarchical relationship and the association relationship between the plurality of trace points, and the plurality of trace points correspond to at least two trace point hierarchies; the subsequent triggered trace point in the plurality of trace points is opened according to the trace point data triggered by the initialization trace point and the trace point directed graph; the upper limit value of the reporting throughput is calculated according to the weight of each trace point hierarchy corresponding to the initialization trace point and the subsequent triggered trace point; and the target trace point data is reported to the server according to the comparison result of the upper limit value of the reporting throughput and the predetermined throughput threshold.

[0031] In this way, the initialization trace point in the plurality of trace points corresponding to the trace point directed graph is opened, and the subsequent triggered trace point is controlled in a directed manner according to the trace point data triggered by the initialization trace point and the trace point directed graph, so that the trace points in the device can be reasonably opened and triggered on demand, thereby avoiding the redundancy of trace point data and the unnecessary reporting caused by a large number of opened trace points; further, the upper limit value of the reporting throughput is calculated according to the weight of each trace point hierarchy corresponding to the initialization trace point and the subsequent triggered trace point, and the reporting of the trace point data is controlled according to the comparison result of the upper limit value of the reporting throughput and the predetermined throughput threshold, so that each device can further autonomously and reasonably control the reporting to avoid the high load of the server in advance. In turn, the reporting reliability of the trace point data in the electronic device is effectively improved, and the possibility of server crash caused by the reporting of the trace point data is reliably reduced. BRIEF DESCRIPTION OF DRAWINGS

[0032] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed in the embodiment description will be briefly introduced as follows. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creating any creative labor.

[0033] FIG. 1 shows a system flow diagram of the buried point data reporting according to an embodiment of the present application.

[0034] FIG. 2 shows a configuration obtaining flow diagram according to an embodiment of the present application.

[0035] FIG. 3 shows a buried point switch control flow diagram according to an embodiment of the present application.

[0036] FIG. 4 shows a block diagram of the buried point data reporting apparatus according to an embodiment of the present application.

[0037] FIG. 5 shows a block diagram of the buried point data reporting apparatus according to another embodiment of the present application.

[0038] FIG. 6 shows a block diagram of the electronic device according to an embodiment of the present application.

[0039] Embodiments of the present application

[0040] The present disclosure will be further described by embodiments in conjunction with the accompanying drawings. It is to be understood that the embodiments provided herein are only used to explain the present disclosure and not used to limit the present disclosure. In addition, the embodiments provided below are used to implement part of the present disclosure, and the technical solutions described in the embodiments of the present disclosure can be implemented in any combination manner without conflict.

[0041] It should be noted that in the embodiments of the present disclosure, the terms "comprise", "contain" or any other variants thereof are intended to cover the non-exclusive inclusion, so that the method or device comprising a series of elements not only includes the elements explicitly described, but also includes other elements not explicitly listed, or includes the elements inherent in the implementation of the method or device. Without more limitations, the element defined by the statement "comprises a" does not exclude the presence of other related elements (such as steps in the method or units in the device, for example, the unit can be part of the circuit, part of the processor, part of the program or software, etc.) in the method or device comprising the element.

[0042] For example, the buried point data reporting method provided by the embodiments of the present disclosure comprises a series of steps, but the buried point data reporting method provided by the embodiments of the present disclosure is not limited to the steps described, and similarly, the buried point data reporting apparatus provided by the embodiments of the present disclosure comprises a series of units, but the apparatus provided by the embodiments of the present disclosure is not limited to comprising the units explicitly described, and can also comprise units required to be set when obtaining related information or processing based on information.

[0043] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. The terminology used in the specification is for describing particular embodiments only and is not intended to be limiting of the disclosure.

[0044] It can be understood that in the specific embodiments of the present application, data related to buried point data is involved, and when the embodiments in the present application are applied to specific products or technologies, the user's permission or consent needs to be obtained, and the collection, use and processing of related data need to comply with relevant laws, regulations and standards of countries and regions.

[0045] FIG. 1 schematically shows a flowchart of a buried point data reporting method according to an embodiment of the present application.

[0046] Referring to FIG. 1, the electronic device can execute the buried point data reporting method shown in steps S110 to S140, and the execution subject of the buried point data reporting method can be any electronic device with processing capability, such as a television, a computer, a mobile phone, a smart watch, and a household appliance.

[0047] Step S110, starting an initialization buried point in a plurality of buried points corresponding to a buried point directed graph, wherein the buried point directed graph is used to indicate the hierarchical relationship and the association relationship between the plurality of buried points, and the plurality of buried points correspond to at least two buried point levels;

[0048] Step S120, starting a subsequent trigger buried point in the plurality of buried points according to the buried point data triggered by the initialization buried point and the buried point directed graph;

[0049] Step S130, calculating a reporting throughput upper limit value according to the weight of each buried point level corresponding to the initialization buried point and the subsequent trigger buried point;

[0050] Step S140, reporting target buried point data to a server according to the comparison result of the reporting throughput upper limit value and a predetermined throughput threshold.

[0051] The electronic device can preset a plurality of buried points in a specific flow of a system / application, an exception handling flow, and the like, and the electronic device can obtain a buried point directed graph of the plurality of buried points. The buried point directed graph is a directed graph formed by connecting buried points according to the association relationship between the buried points. The buried point directed graph can be used to indicate the hierarchical relationship and the association relationship between the plurality of buried points. The buried point directed graph can include at least two buried point levels, and each buried point level can include one or more buried points.

[0052] Taking a music playing flow in a music playing software as an example, the flow can include nodes such as starting an application, entering a music selection interface, a browsing interface, selecting music, searching music, playing music, and the like. A corresponding association relationship between the nodes can be preset in each node, such as presetting a node A1 in the node of starting the application, presetting a node A2 in the node of entering the main interface, and presetting a node A3 in the node of the browsing interface. Usually, the application is started and the music selection interface is entered according to a user operation, so that the node A1 and the node A2 can have an association relationship A1-2. Similarly, a specific flow of a system / application, an exception handling flow, and the like can be preset with multiple nodes, and a directed graph formed by the nodes through a corresponding association relationship can be used as a node directed graph. It should be noted that which nodes in each flow need to be preset can be selected according to actual needs.

[0053] The electronic device can obtain the server load data of the server and the node directed graph of the multiple nodes from the cloud or locally. The electronic device can further start an initial node in the multiple nodes, and start a subsequent triggered node in the multiple nodes according to the node data triggered by the initial node (i.e., the data collected when the initial node is triggered) and the node directed graph. The node directed graph is a directed switch control, i.e., a node start control and a node close control in a direction, so that the multiple nodes can be started or closed according to actual needs in the electronic device.

[0054] The electronic device can further calculate a reporting throughput upper limit value according to the weight of each node level corresponding to the initial node and the subsequent triggered node. The reporting throughput upper limit value is the maximum throughput of the reporting data in the electronic device. For example, at some time, the node levels of the started nodes (i.e., the initial node and the subsequent triggered node in the starting state) in the device are the first, second, and third node levels, respectively. At another time, the node levels of the started nodes in the device are the first and second node levels, respectively. Accordingly, the reporting throughput upper limit value calculated accordingly is different with the different started nodes in the device.

[0055] The electronic device can further compare the reported throughput upper limit value with a predetermined throughput threshold value (i.e., a preset throughput threshold value of the electronic device for reporting the buried point data), and report the to-be-reported buried point data triggered by the plurality of buried points to the server according to a comparison result, the to-be-reported buried point data triggered by the plurality of buried points being buried point data collected by the triggered buried points in the plurality of buried points at the time of reporting the buried points but not reported. For example, referring to FIG. 4, the electronic device can include a buried point data reporting apparatus 410, and the to-be-reported buried point data triggered by the plurality of buried points can be reported to the server 430 by a reporting processing module 414 in the buried point data reporting apparatus 410.

[0056] In this way, based on steps S110 to S140, the initialization buried point in the plurality of buried points corresponding to the buried point directed graph is opened, and the directed opening control of the subsequent triggered buried point is performed according to the buried point data triggered by the initialization buried point and the buried point directed graph, so that the buried points in the device are reasonably opened and the buried point data is triggered as needed, thereby avoiding the redundancy of the buried point data and the unnecessary reporting caused by a large number of opened buried points. Further, the reporting throughput upper limit value is calculated according to the weight of each buried point level corresponding to the initialization buried point and the subsequent triggered buried point, and the reporting of the buried point data is controlled according to the comparison result of the reporting throughput upper limit value and the predetermined throughput threshold value, so that each device can further autonomously and reasonably control the reporting to avoid high server load in advance. Further, the reliability of the buried point data reporting in the electronic device is effectively improved as a whole, and the possibility of server crash caused by the buried point data reporting is reliably reduced.

[0057] The following describes further optional specific embodiments of each step performed when reporting the buried point data in the embodiment of FIG. 1.

[0058] In an embodiment, before calculating the reporting throughput upper limit value according to the weight of each buried point level corresponding to the initialization buried point and the subsequent triggered buried point, the server load data of the server can be obtained, and the weight of each buried point level in the at least two buried point levels in the buried point directed graph can be determined according to the server load data.

[0059] The server load data is the load data of the server, and can include a server throughput upper limit value (i.e., the maximum throughput of the server) and a user concurrency upper limit value (i.e., the maximum user concurrency of the server). The electronic device can determine the weight of each buried point level in the buried point directed graph according to the server load data, and the weights corresponding to different buried point levels can be different, for example, the weight of the first buried point level is w1, and the weight of the second buried point level is w2.

[0060] Specifically, in an embodiment, the server load data includes a server throughput upper limit value and a user concurrency upper limit value, and determining the weight of each of the at least two levels of the buried point directed graph according to the server load data can include:

[0061] The weight of each level of the buried point directed graph is calculated according to the formula ΣT=M*(N1*w1+N2*w2+N3*w3+...+Ni*wi+...+Nn*wn), where ΣT refers to the server throughput upper limit value, M refers to the user concurrency upper limit value, n is the total number of levels of the buried point directed graph, i refers to the i-th level of the buried point level, Ni refers to the number of buried points in the i-th level of the buried point level, and wi refers to the weight of the i-th level of the buried point level.

[0062] The server throughput upper limit value and the user concurrency upper limit value can effectively reflect the maximum load of the server side. According to the server throughput upper limit value, the user concurrency upper limit value, and the buried point levels included in the buried point directed graph, the weight w1 to wn of each level of the buried point directed graph is calculated according to the formula ΣT=M*(N1*w1+N2*w2+N3*w3+...+Ni*wi+...+Nn*wn). The weight can be effectively used for autonomous decision-making of the electronic device side for reporting buried point data, to reliably avoid server crashes caused by reporting of buried point data.

[0063] Further, in an embodiment, referring to FIG. 2, before obtaining the server load data of the server, the method can further include: obtaining, from the cloud, an updated buried point reporting management configuration (step S210); and obtaining, from the updated buried point reporting management configuration, the server load data and the buried point directed graph (step S220).

[0064] Referring to FIG. 4, the electronic device can include a buried point data reporting apparatus 410. The configuration management module 411 in the buried point data reporting apparatus 410 can obtain an updated buried point reporting management configuration from the cloud configuration manager of the cloud 420.

[0065] If the electronic device obtains the updated buried point reporting management configuration from the cloud, the electronic device can obtain updated server load data and a buried point directed graph from the updated buried point reporting management configuration, and can update the preset or default server load data and buried point directed graph in the local buried point reporting management configuration using the updated server load data and buried point directed graph. That is, at this time, the electronic device can obtain the latest server load data and buried point directed graph from the cloud.

[0066] In contrast, if the electronic device fails to obtain the updated burying point reporting control configuration, the server load data and the burying point directed graph are obtained from the local burying point reporting control configuration, that is, the preset or default server load data and burying point directed graph in the local burying point reporting control configuration are taken as the server load data and burying point directed graph obtained this time.

[0067] In the related art, burying point control information (that is, burying point reporting control configuration) is directly preset in the electronic device, and the software version is fixed in the electronic device after being released, and cannot be conveniently adjusted. In this way, compared with the related art, the electronic device can be dynamically updated by the cloud (including server load data and burying point directed graph), improve the convenience of burying point adjustment setting, and at the same time, can realize adjustment setting according to project requirements, thereby improving the effectiveness of burying point data.

[0068] In an embodiment, the initialization burying point in the plurality of burying points corresponding to the opened burying point directed graph includes: determining, from the plurality of burying points, a burying point at a first burying point level in the burying point directed graph; obtaining, according to the burying point at the first burying point level, an initialization burying point in the plurality of burying points; and opening the initialization burying point.

[0069] The burying point directed graph is a directed graph formed by connecting burying points according to the association relationship between the burying points. The burying point directed graph can include a plurality of burying point levels, and each burying point level can include one or more burying points. The burying points in a later burying point level and the burying points in an earlier burying point level can be associated through an association relationship.

[0070] For example, in one example, the first burying point level includes burying point A and burying point B, the second burying point level includes burying point C, burying point D and burying point E, A and C are connected through association relationship A1, A and D are connected through association relationship A2, and B and E are connected through association relationship B1.

[0071] From the plurality of burying points, a burying point at a first burying point level in the burying point directed graph is determined; according to the burying point at the first burying point level, an initialization burying point in the plurality of burying points is obtained; and then, the initialization burying point is opened. Further, the device only opens the initialization burying point in the first burying point level at the beginning, and the burying points in the later burying point levels can be opened on demand according to the burying point data triggered by the initialization burying point and the burying point directed graph, so that the device can reasonably open the burying points on demand and trigger the burying point data.

[0072] In an embodiment, the obtaining the initialization burypoint from the burypoints of the first burypoint level comprises: taking the burypoints of the first burypoint level as the initialization burypoints in the plurality of burypoints; or obtaining a device monitoring scenario, and taking the burypoint of the first burypoint level that matches the device monitoring scenario as the initialization burypoint in the plurality of burypoints.

[0073] In the first mode, the burypoints of the first burypoint level are taken as the initialization burypoints in the plurality of burypoints. For example, the first burypoint level includes burypoint A and burypoint B. In this mode, burypoint A and burypoint B are taken as the initialization burypoints by default, that is, all the burypoints in the first burypoint level are started at the first time.

[0074] In the second mode, the device monitoring scenario can be a scenario in which the device needs to be monitored, such as a scenario monitored by an app, a scenario monitored by a system, and the like. The device monitoring scenario is obtained, and the burypoint of the first burypoint level that matches the device monitoring scenario is taken as the initialization burypoint in the plurality of burypoints. For example, the first burypoint level includes burypoint A and burypoint B. In this mode, if the device monitoring scenario 1 matches burypoint A, burypoint A is taken as the initialization burypoint, that is, part or all of the burypoints in the first burypoint level are started at the first time.

[0075] In an embodiment, the starting the subsequent triggered burypoint in the plurality of burypoints according to the burypoint data triggered by the initialization burypoint and the burypoint directed graph can comprise: starting the burypoints of each burypoint level associated with the initialization burypoint in the order of the burypoint levels according to the burypoint data triggered by the initialization burypoint and the burypoint directed graph, to start the subsequent triggered burypoint in the plurality of burypoints.

[0076] Referring to FIG. 3, the directed switching control of the remaining burypoints in the plurality of burypoints can be performed according to the burypoint data triggered by the initialization burypoint and the burypoint directed graph. Specifically, in step S310, the burypoints of each burypoint level associated with the initialization burypoint are started in the order of the burypoint levels according to the burypoint data triggered by the initialization burypoint and the burypoint directed graph, until the burypoint of the last burypoint level in the burypoint directed graph is started, thereby starting the subsequent triggered burypoint in the plurality of burypoints. In step S320, the started burypoints are controlled to be closed layer by layer in the reverse order of the burypoint levels from the burypoint of the last burypoint level, and the initialization burypoint is kept started.

[0077] According to the initialization of the triggered buried point data and the association relationship between the buried points in the buried point directed graph, each buried point level of the buried point associated with the initialization of the buried point can be triggered and opened in sequence, until the last buried point level in the buried point directed graph is opened, so that the subsequent triggered buried points are opened layer by layer during the system running.

[0078] For example, during the system running, if the initialization of the buried point triggers the buried point data 1, the association relationship 1 corresponding to the buried point data 1 in the buried point directed graph can be determined, so that the next buried point level connected with the initialization of the buried point through the association relationship 1 (which can be referred to as the lower layer subsequent triggered buried point) can be further opened. Then, after the lower layer associated buried point triggers the buried point data 2, the association relationship 2 corresponding to the buried point data 2 in the buried point directed graph can be determined, so that the next next buried point level connected with the lower layer subsequent triggered buried point through the association relationship 2 (which can be referred to as the lower next layer subsequent triggered buried point) can be further opened. In this way, the layer-by-layer opening control can be performed until the last buried point level in the buried point directed graph is opened.

[0079] Then, starting from the opened buried point in the last buried point level, the opened buried points are closed layer by layer in reverse order of the buried point level, and the initialization of the buried point is kept open. Therefore, after reaching the last buried point level, the closing of the buried points is completed layer by layer in reverse order, but the initialization of the buried point is kept open, so that the next round of buried point triggering can start from the initialization of the buried point.

[0080] For example, if it is detected that the last buried point level in the buried point directed graph is opened, the last buried point level is self-closed after triggering the buried point data. Then, the previous layer (i.e., the second last buried point level) is set as a new last buried point level, and when it is detected that the child layer buried point (i.e., the buried point in the last buried point level) of the new last buried point level is closed, the opened buried point in the new last buried point level is closed. In this way, the buried points are closed layer by layer, but the initialization of the buried point is kept open (for example, when the buried points are closed layer by layer to the first buried point level, the closing is stopped and the initialization of the buried point in the first buried point level is kept open), so that the next round of buried point triggering can start from the initialization of the buried point.

[0081] The layer-by-layer opening and closing of the buried points are performed through a loop, and each loop includes "layer-by-layer opening control starting from the initialization of the buried point, and then layer-by-layer closing control, and keeping the initialization of the buried point open". In this way, the rationality of the opening and control of the buried points in the device can be further effectively guaranteed, and the reliability of the buried point data reporting in the electronic device can be improved.

[0082] In an embodiment, the calculation of the upper limit value of the reporting throughput according to the weight of each buried point level corresponding to the initialization of the buried point and the subsequent triggered buried point can include:

[0083] obtaining the number of hierarchical points of each point level corresponding to the initialization point and the subsequent triggered point; obtaining the total number of the initialization point and the subsequent triggered point; calculating the upper limit value of the reporting throughput according to the number of hierarchical points of each point level corresponding to the initialization point and the subsequent triggered point, the total number of the initialization point and the subsequent triggered point, and the weight corresponding to each point level corresponding to the initialization point and the subsequent triggered point.

[0084] Specifically, the upper limit value of the reporting throughput can be calculated according to the formula ST=U*(K1*w1+K2*w2+K3*w3+…+Ki*wi+…+Kn*wn), wherein ST refers to the upper limit value of the reporting throughput, U refers to the total number of points opened in the device (i.e., the total number of initialization points and subsequent triggered points), n is the total number of hierarchical levels included in the point directed graph, i refers to the i-th point level, Ki refers to the number of hierarchical points corresponding to the i-th point level, and wi refers to the weight corresponding to the i-th point level.

[0085] The upper limit value of the reporting throughput is calculated according to the formula ST=U*(K1*w1+K2*w2+K3*w3+…+Ki*wi+…+Kn*wn), so that the electronic device can effectively make autonomous decisions to avoid server crashes when reporting point data.

[0086] Further, in an embodiment, the reporting of target point data to the server according to the comparison result of the upper limit value of the reporting throughput and the predetermined throughput threshold can include: if the upper limit value of the reporting throughput is less than or equal to the predetermined throughput threshold, reporting the target point data to the server, the target point data being all point data currently triggered; if the upper limit value of the reporting throughput is greater than the predetermined throughput threshold, reporting target point data to the server, the target point data being part of the all point data currently triggered.

[0087] The electronic device can determine whether to compare the upper limit value of the reporting throughput at the moment with the predetermined throughput threshold at regular intervals or at the moment when point data is triggered, and decide how to report all point data currently triggered by multiple points in the device to the server according to the comparison result. The all point data currently triggered by multiple points in the device is the point data collected by the point triggered at the moment of reporting point data but not reported.

[0088] If the upper limit of the reporting throughput is less than or equal to the predetermined throughput threshold, the terminal reports target tracking data to the server, and at this time, the target tracking data is all tracking data triggered at present. In contrast, if the upper limit of the reporting throughput is greater than the predetermined throughput threshold, the target tracking data reported by the terminal to the server is part of the all tracking data triggered at present. Thus, data reporting can be more reliably achieved.

[0089] Further, after the reporting of the target tracking data to the server when the upper limit of the reporting throughput is greater than the predetermined throughput threshold, the method can further include: caching remaining tracking data in the all tracking data triggered at present except the target tracking data, and the remaining tracking data is used for reporting when a predetermined reporting condition is met.

[0090] Specifically, if the comparison result is that the upper limit of the reporting throughput is greater than the predetermined throughput threshold, part of the all tracking data triggered at present (i.e., target tracking data) is reported to the server, and the remaining tracking data in the all tracking data triggered at present except the target tracking data is cached. The part of the remaining tracking data can be tracking data of a data amount corresponding to a difference between the upper limit of the reporting throughput and the predetermined throughput threshold. The cached remaining tracking data can be used for reporting when a predetermined reporting condition is met. In one way, the predetermined reporting condition can be that the cached remaining tracking data does not exceed a reporting data margin when tracking data reporting is performed next time, and the reporting data margin can refer to a remaining reporting data amount when tracking data reporting is performed next time.

[0091] To facilitate better implementation of the tracking data reporting method provided in the embodiments of the present application, the embodiments of the present application further provide a tracking data reporting device based on the above tracking data reporting method. The meanings of the terms are the same as those in the above tracking data reporting method, and specific implementation details can be referred to the description in the method embodiments.

[0092] FIG. 4 shows a block diagram of a tracking data reporting device according to one embodiment of the present application. The tracking data reporting device 410 shown in FIG. 4 can be applied to an electronic device, and the tracking data reporting device 410 can include:

[0093] The burying point switch control module 412 can be used to open an initial burying point in a plurality of burying points corresponding to a burying point directed graph, wherein the burying point directed graph is used to indicate a hierarchical relationship and an association relationship between the plurality of burying points, and the plurality of burying points correspond to at least two burying point hierarchies; the burying point switch control module 412 can also be used to open a subsequent trigger burying point in the plurality of burying points according to burying point data triggered by the initial burying point and the burying point directed graph; the throughput calculation module 413 can be used to calculate a reporting throughput upper limit value according to a weight of each burying point hierarchy corresponding to the initial burying point and the subsequent trigger burying point opened by the burying point switch control module; the reporting processing module 414 can be used to report target burying point data to a server according to a comparison result of the reporting throughput upper limit value calculated by the throughput calculation module and a predetermined throughput threshold.

[0094] In some embodiments of the present application, the burying point switch control module is configured to: determine, from the plurality of burying points, a burying point at a first burying point hierarchy in the burying point directed graph; obtain an initial burying point in the plurality of burying points according to the burying point at the first burying point hierarchy; and open the initial burying point.

[0095] In some embodiments of the present application, the burying point switch control module is configured to: take the burying point at the first burying point hierarchy as the initial burying point in the plurality of burying points; or obtain a device monitoring scene and take a burying point matching the device monitoring scene in the burying point at the first burying point hierarchy as the initial burying point in the plurality of burying points.

[0096] In some embodiments of the present application, the burying point switch control module is configured to: according to burying point data triggered by an initial burying point and the burying point directed graph, trigger and open, layer by layer in order of burying point hierarchies, each burying point at a burying point hierarchy associated with the initial burying point, to open a subsequent trigger burying point in the plurality of burying points.

[0097] In some embodiments of the present application, the throughput calculation module is configured to: obtain a number of hierarchical burying points of each burying point hierarchy corresponding to the initial burying point and the subsequent trigger burying point; obtain a total number of the initial burying point and the subsequent trigger burying point; and calculate the reporting throughput upper limit value according to the number of hierarchical burying points of each burying point hierarchy corresponding to the initial burying point and the subsequent trigger burying point, the total number of the initial burying point and the subsequent trigger burying point, and a weight corresponding to each burying point hierarchy corresponding to the initial burying point and the subsequent trigger burying point.

[0098] In some embodiments of the present application, the reporting processing module is configured to: if the upper limit of the reporting throughput is less than or equal to the predetermined throughput threshold, report the target tracking data to the server, the target tracking data being all tracking data triggered currently; and if the upper limit of the reporting throughput is greater than the predetermined throughput threshold, report target tracking data to the server, the target tracking data being part of the tracking data triggered currently.

[0099] In some embodiments of the present application, after the reporting of the target tracking data to the server, the reporting processing module is configured to: cache the remaining tracking data other than the target tracking data in the tracking data triggered currently, the remaining tracking data being used for reporting when a predetermined reporting condition is met.

[0100] In some embodiments of the present application, before the determination of the weight of each tracking level corresponding to the initial tracking and the subsequent triggered tracking, the device further comprises a configuration management module 411 configured to: obtain server load data of the server; and determine the weight of each tracking level in the at least two tracking levels in the tracking directed graph according to the server load data.

[0101] In some embodiments of the present application, the server load data comprises an upper limit of server throughput and an upper limit of user concurrency, and the configuration management module is configured to: calculate the weight of each tracking level in the tracking directed graph according to the formula ΣT=M*(N1*w1+N2*w2+N3*w3+...+Ni*wi+...+Nn*wn), wherein ΣT represents the upper limit of the server throughput, M represents the upper limit of the user concurrency, n represents the total number of tracking levels included in the tracking directed graph, i represents the i-th tracking level, Ni represents the number of tracking points in the i-th tracking level, and wi represents the weight of the i-th tracking level.

[0102] In some embodiments of the present application, before the obtaining of the server load data of the server, the configuration management module is configured to: obtain an updated tracking reporting management configuration from the cloud; and obtain the server load data and the tracking directed graph from the updated tracking reporting management configuration.

[0103] It should be noted that although several modules or units of the device for action execution are mentioned in the foregoing detailed description, such a division is not mandatory. Indeed, according to an embodiment of the application, the features and functionalities of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functionalities of one module or unit described above can be further divided into several modules or units embodied by several modules or units.

[0104] FIG. 5 shows a block diagram of a device for uploading and reporting of buried point data according to another embodiment of the application. The device for uploading and reporting of buried point data 500 shown in FIG. 5 can be applied to a server, and the device for uploading and reporting of buried point data 500 can include the following modules:

[0105] The transmission module 510 can be configured to transmit the buried point directed graph to the electronic device, and the receiving module 520 can be configured to receive target buried point data triggered by a plurality of buried points reported by the electronic device, the target buried point data being reported by the electronic device according to a comparison result of a reporting throughput upper limit value and a predetermined throughput threshold value, the reporting throughput upper limit value being calculated by the electronic device according to weights of each buried point level corresponding to an initial buried point and a subsequent triggered buried point.

[0106] In addition, an embodiment of the application further provides an electronic device, as shown in FIG. 6, which shows a block diagram of an electronic device according to an embodiment of the application, in particular:

[0107] The electronic device can include a processor 601 with one or more processing cores, a memory 602 with one or more computer readable storage media, a power supply 603, an input unit 604, and the like. Those skilled in the art can understand that the structure of the electronic device shown in FIG. 6 does not constitute a limitation on the electronic device, and can include more or fewer components than shown, or combine certain components, or different component arrangements. Among them:

[0108] The processor 601 is the control center of the electronic device, which connects various parts of the computer device through various interfaces and lines, and performs various functions and processes data of the computer device by running or executing software programs and / or modules stored in the memory 602 and calling data stored in the memory 602, thereby overall monitoring the electronic device. Optionally, the processor 601 can include one or more processing cores; preferably, the processor 601 can integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user pages and application programs, etc., and the modem processor mainly processes wireless communication. It can be understood that the above-mentioned modem processor can also not be integrated into the processor 601.

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

[0110] The electronic device further includes a power supply 603 for powering various components, and preferably, the power supply 603 can be logically connected to the processor 601 through a power management system, so as to realize functions such as management of charging, discharging, and power consumption management through the power management system. The power supply 603 can also include one or more direct current or alternating current power supplies, a recharging system, a power supply fault detection circuit, a power supply converter or inverter, a power supply status indicator, and the like.

[0111] The electronic device can further include an input unit 604, which can be used to receive input digital or character information, and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function controls.

[0112] Although not shown, the electronic device can also include a display unit and the like, which will not be described here. Specifically, in the present embodiment, the processor 601 in the electronic device will load one or more executable files corresponding to the processes of the computer programs into the memory 602 according to the following instructions, and run the computer programs stored in the memory 602 by the processor 601, so as to realize various functions in the foregoing embodiments of the present application. For example, the processor 601 can perform the following steps:

[0113] Start an initial point in a plurality of points corresponding to a point graph, wherein the point graph is used to indicate a hierarchical relationship and an association relationship between the plurality of points, and the plurality of points correspond to at least two point levels; start a subsequent trigger point in the plurality of points according to point data triggered by the initial point and the point graph; calculate an upper limit value of a reporting throughput according to a weight of each point level corresponding to the initial point and the subsequent trigger point; and report target point data to a server according to a comparison result of the upper limit value of the reporting throughput and a predetermined throughput threshold.

[0114] In some embodiments of the present application, the starting the initialization event in the plurality of events corresponding to the event directed graph comprises: determining events in a first event level in the event directed graph from the plurality of events; and obtaining the initialization event in the plurality of events according to the events in the first event level.

[0115] In some embodiments of the present application, the obtaining the initialization event in the plurality of events according to the events in the first event level comprises: taking the events in the first event level as the initialization event in the plurality of events; or obtaining a device monitoring scenario, and taking an event in the first event level matching the device monitoring scenario as the initialization event in the plurality of events.

[0116] In some embodiments of the present application, the starting the subsequent triggered event in the plurality of events according to the event data triggered by the initialization event and the event directed graph comprises: triggering and starting each event in an event level associated with the initialization event according to the event data triggered by the initialization event and the event directed graph in order of the event levels, to start the subsequent triggered event in the plurality of events.

[0117] In some embodiments of the present application, the calculating the upper limit of the reporting throughput according to the weight of each event level corresponding to the initialization event and the subsequent triggered event comprises: obtaining the number of events in each event level corresponding to the initialization event and the subsequent triggered event; obtaining the total number of the initialization event and the subsequent triggered event; and calculating the upper limit of the reporting throughput according to the number of events in each event level corresponding to the initialization event and the subsequent triggered event, the total number of the initialization event and the subsequent triggered event, and the weight of each event level corresponding to the initialization event and the subsequent triggered event.

[0118] In some embodiments of the present application, the reporting the target event data to the server according to the comparison result of the upper limit of the reporting throughput and the predetermined throughput threshold comprises: if the upper limit of the reporting throughput is less than or equal to the predetermined throughput threshold, reporting the target event data to the server, the target event data being all the currently triggered event data; and if the upper limit of the reporting throughput is greater than the predetermined throughput threshold, reporting the target event data to the server, the target event data being part of the currently triggered event data.

[0119] In some embodiments of this application, after reporting the target event data to the server if the upper limit of the reported throughput is greater than the predetermined throughput threshold, the method further includes: caching the remaining event data other than the target event data in all currently triggered event data, and the remaining event data is used to report when the predetermined reporting conditions are met.

[0120] In some embodiments of this application, before calculating the upper limit of the reporting throughput based on the weight of each tracking level corresponding to the initial tracking point and the subsequent triggering tracking point, the method further includes: obtaining the server load data of the server; and determining the weight of each tracking level in the at least two tracking levels in the tracking point directed graph based on the server load data.

[0121] In some embodiments of this application, the server load data includes a server throughput upper limit and a user concurrency upper limit. Determining the weight of each of the at least two tracking levels in the directed tracking graph based on the server load data includes: calculating the weight of each tracking level in the directed tracking graph according to the formula ΣT=M*(N1*w1+N2*w2+N3*w3+...+Ni*wi+...+Nn*wn), where ΣT refers to the server throughput upper limit, M refers to the user concurrency upper limit, n is the total number of tracking levels in the directed tracking graph, i refers to the i-th tracking level, Ni refers to the number of tracking points in the i-th tracking level, and wi refers to the weight of the i-th tracking level.

[0122] In some embodiments of this application, before obtaining the server load data of the server, the method further includes: obtaining the update tracking point reporting management configuration from the cloud; and obtaining the server load data and the tracking point directed graph from the update tracking point reporting management configuration.

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

[0124] Therefore, embodiments of this application also provide a storage medium storing a computer program that can be loaded by a processor to execute the steps in any of the methods provided in embodiments of this application.

[0125] The storage medium can be a computer readable storage medium, and can include a read only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0126] The computer program stored in the storage medium can execute the steps in any method provided by the embodiments of the present application, thus achieving the beneficial effects of the methods provided by the embodiments of the present application. Details are described in the foregoing embodiments, and will not be described here.

[0127] Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the embodiments disclosed herein. The specification and examples given herein are not intended to be exhaustive or limiting, and these and any other variations that are deemed to fall within the scope of the present application are intended to be included herein. Accordingly, the application is not limited to the embodiments described herein, but rather the scope of the application is to be accorded the full scope consistent with the claims, modifications and equivalents thereof.

[0128] It should be understood that the application is not limited to the embodiments described above and shown in the drawings, but various modifications and changes can be made without departing from the scope of the application.

Claims

1. A method for reporting embedded data, wherein, include: The initialization point is started among multiple points corresponding to the directed graph of the tracking points. The directed graph of the tracking points is used to indicate the hierarchical relationship and association between the multiple tracking points. The multiple tracking points correspond to at least two tracking point levels. Based on the data triggered by the initialization point and the directed graph of the points, the subsequent trigger points among the multiple points are activated. The upper limit of the reporting throughput is calculated based on the weight of each data point level corresponding to the initial data point and the subsequent trigger data points. The target data points are reported to the server based on the comparison between the reported throughput upper limit and the predetermined throughput threshold.

2. The method according to claim 1, wherein, The initialization points among the multiple points corresponding to the directed graph of the enabled tracking points include: From the plurality of embedded points, determine the embedded point located at the first embedded point level in the embedded point directed graph; Based on the embedding points at the first embedding point level, the initial embedding point among the plurality of embedding points is obtained; Enable the initialization point.

3. The method according to claim 2, wherein, The step of obtaining the initialization point among the plurality of embedding points based on the embedding points of the first embedding point level includes: All the embedding points at the first embedding level are used as initial embedding points among the plurality of embedding points; or Obtain the device monitoring scenario, and use the device monitoring scenario matching the embedding points in the first embedding point level as the initialization embedding point among the multiple embedding points.

4. The method according to claim 1, wherein, The step of activating subsequent trigger points among the multiple event points based on the event point data triggered by the initial event point and the directed event point graph includes: Based on the data triggered by the initialization point and the directed graph of the points, the points associated with each point level of the initialization point are triggered layer by layer in the order of the points, so as to enable the subsequent triggered points among the multiple points.

5. The method according to claim 1, wherein, The step of calculating the upper limit of reporting throughput based on the weight of each data point level corresponding to the initial data point and the subsequent trigger data points includes: Obtain the number of layer-level embeddings corresponding to each embedding level of the initial embedding point and the subsequent trigger embedding point; Obtain the total number of the initialization points and the subsequent trigger points; The upper limit of the reporting throughput is calculated based on the number of layer-level tracking points corresponding to each tracking point level of the initial tracking point and the subsequent trigger tracking point, the total number of initial tracking points and the subsequent trigger tracking points, and the weight corresponding to each tracking point level of the initial tracking point and the subsequent trigger tracking point.

6. The method according to claim 1, wherein, The step of reporting the target data point to the server based on the comparison result between the reported throughput upper limit and the predetermined throughput threshold includes: If the reported throughput upper limit is less than or equal to the predetermined throughput threshold, then the target data point is reported to the server, and the target data point is all data point data triggered at the moment. If the upper limit of the reported throughput is greater than the predetermined throughput threshold, then target data is reported to the server. The target data is a portion of all data triggered at the moment.

7. The method according to claim 6, wherein, After stating that if the upper limit of the reported throughput is greater than the predetermined throughput threshold, the target data point is reported to the server, the method further includes: The remaining data of all currently triggered data points, excluding the target data point, are cached. This remaining data point is used to report data when predetermined reporting conditions are met.

8. The method according to claim 1, wherein, Before calculating the upper limit of reporting throughput based on the weight of each data point level corresponding to the initial data point and the subsequent triggered data points, the method further includes: Obtain the server load data of the server; The weight of each of the at least two tracking levels in the tracking graph is determined based on the server load data.

9. The method according to claim 8, wherein, The server load data includes the upper limit of server throughput and the upper limit of user concurrency. Determining the weight of each of the at least two tracking levels in the directed tracking graph based on the server load data includes: The weights of each tracking level in the directed tracking graph are calculated using the formula ΣT=M*(N1*w1+N2*w2+N3*w3+...+Ni*wi+...+Nn*wn), where ΣT refers to the upper limit of server throughput, M refers to the upper limit of user concurrency, n is the total number of tracking levels in the directed tracking graph, i refers to the i-th tracking level, Ni refers to the number of tracking points in the i-th tracking level, and wi refers to the weight of the i-th tracking level.

10. The method according to claim 8, wherein, Before obtaining the server load data, the process also includes: Retrieve updated monitoring and reporting configurations from the cloud; The server load data and the directed graph of the tracking points are obtained from the update tracking point reporting management configuration.

11. The method according to claim 10, wherein, The method further includes: If the update tracking point reporting control configuration cannot be obtained, the server load data and the tracking point directed graph are obtained from the local tracking point reporting control configuration.

12. The method according to claim 10, wherein, The method further includes: Based on the server load data and directed graph of the updated tracking point reporting management configuration, update the server load data and directed graph of the local tracking point reporting management configuration.

13. The method according to claim 4, wherein, The step of triggering and activating subsequent triggered points among the multiple points by sequentially activating the points associated with the initialization point based on the point data triggered by the initialization point and the directed graph of the points, according to the order of the point hierarchy, includes: Based on the data triggered by the initialization point and the directed graph of the points, the points associated with each point level of the initialization point are triggered layer by layer in the order of the points, until the point located at the last point level in the directed graph of the points is activated, so as to activate the subsequent trigger points among multiple points. In addition, starting from the last level of the tracking points, the enabled tracking points are controlled to be turned off layer by layer in reverse order of the tracking point levels, while keeping the initial tracking points enabled.

14. A device for reporting embedded data, wherein, include: The tracking point switch control module is used to activate the initial tracking point among multiple tracking points corresponding to the tracking point directed graph. The tracking point directed graph is used to indicate the hierarchical relationship and association relationship between the multiple tracking points, and the multiple tracking points correspond to at least two tracking point levels. The tracking point switch control module is also used to, after enabling the initial tracking point, enable subsequent triggering tracking points among the multiple tracking points according to the tracking point data triggered by the initial tracking point and the tracking point directed graph. The throughput calculation module is used to calculate the upper limit of the reported throughput based on the weight of each level of the initialization point and the subsequent triggering point activated by the point switch control module. The reporting processing module is used to report target embedded data to the server based on the comparison result between the upper limit of the reported throughput calculated by the throughput calculation module and the predetermined throughput threshold.

15. The apparatus according to claim 14, wherein, The embedding point switch control module is used to: determine the embedding point located at the first embedding point level in the directed embedding point graph from the plurality of embedding points; obtain the initialization embedding point among the plurality of embedding points based on the embedding point at the first embedding point level; and enable the initialization embedding point.

16. The apparatus according to claim 15, wherein, The embedded point switch control module is used to: use all the embedded points in the first embedded point level as initial embedded points in the plurality of embedded points; or obtain the device monitoring scenario and use the embedded points in the first embedded point level that match the device monitoring scenario as initial embedded points in the plurality of embedded points.

17. The apparatus according to claim 14, wherein, The tracking point switch control module is used to: trigger and activate the tracking points of each tracking point level associated with the initial tracking point layer by layer according to the tracking point data triggered by the initial tracking point and the tracking point directed graph, so as to activate the subsequent triggered tracking points among the multiple tracking points.

18. The apparatus according to claim 14, wherein, The throughput calculation module is used to: obtain the number of layer-level tracking points corresponding to each tracking point level of the initial tracking point and the subsequent trigger tracking point; obtain the total number of initial tracking points and the subsequent trigger tracking points; and calculate the upper limit of the reported throughput based on the number of layer-level tracking points corresponding to each tracking point level of the initial tracking point and the subsequent trigger tracking point, the total number of initial tracking points and the subsequent trigger tracking points, and the weight corresponding to each tracking point level of the initial tracking point and the subsequent trigger tracking point.

19. A storage medium, wherein, It stores a computer program that, when executed by the computer's processor, causes the computer to perform the method described in any one of claims 1 to 13.

20. An electronic device, wherein, include: Memory, which stores computer programs; A processor reads a computer program stored in memory to perform the method described in any one of claims 1 to 13.

Images