CN112000541A - Buried point data reporting method and device, computer equipment and storage medium - Google Patents
Buried point data reporting method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN112000541A CN112000541A CN202010714052.0A CN202010714052A CN112000541A CN 112000541 A CN112000541 A CN 112000541A CN 202010714052 A CN202010714052 A CN 202010714052A CN 112000541 A CN112000541 A CN 112000541A
- Authority
- CN
- China
- Prior art keywords
- buried point
- point data
- reporting
- target
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 40
- 238000012545 processing Methods 0.000 claims description 36
- 238000004590 computer program Methods 0.000 claims description 29
- 230000006870 function Effects 0.000 claims description 22
- 238000009933 burial Methods 0.000 claims 1
- 230000007246 mechanism Effects 0.000 abstract description 7
- 230000008569 process Effects 0.000 description 6
- 238000004891 communication Methods 0.000 description 5
- 238000010586 diagram Methods 0.000 description 5
- 230000006399 behavior Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 238000003491 array Methods 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 230000009191 jumping Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 238000012216 screening Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
- G06F11/3072—Monitoring arrangements determined by the means or processing involved in reporting the monitored data where the reporting involves data filtering, e.g. pattern matching, time or event triggered, adaptive or policy-based reporting
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3089—Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents
- G06F11/3093—Configuration details thereof, e.g. installation, enabling, spatial arrangement of the probes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3438—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment monitoring of user actions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3476—Data logging
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
- G06F2201/865—Monitoring of software
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Computer Hardware Design (AREA)
- Mathematical Physics (AREA)
- Computer Vision & Pattern Recognition (AREA)
- Geophysics And Detection Of Objects (AREA)
Abstract
The application relates to a buried point data reporting method, a buried point data reporting device, computer equipment and a storage medium, wherein the method comprises the following steps: receiving buried point event information uploaded by a preset buried point, acquiring buried point data to be reported from the buried point event information, and generating a corresponding reporting identifier according to the buried point event information; combining the data of the buried points to be reported with the reporting identifier to obtain target buried point data carrying the reporting identifier, and storing the target buried point data to a preset local storage file; reporting the target buried point data stored in the local storage file, and updating the reporting times recorded in the reporting identification; and if the target buried point data is detected to be failed to report and the reporting frequency of the target buried point data is less than the preset threshold value, reporting the target buried point data again. The data is not easy to lose along with the page due to the preset local storage file; the retransmission mechanism improves the probability of successful uploading of the buried point data and reduces the loss rate of uploading the buried point data.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for reporting buried point data, a computer device, and a storage medium.
Background
With the high-speed development of the internet, a large number of application programs and operable pages emerge, the amount of data required to be collected by developers is more and more, and the data processing task is heavier; usually, a developer sets a buried point in a corresponding interface operated by a user, collects user behaviors and obtains buried point data, and then uploads the buried point data to a server for further analysis.
For the consideration of transmission bandwidth and server receiving performance, the buried point data usually adopts a reporting mode of accumulating a plurality of buried point data together in time slices, but when events such as page refreshing, page jumping, page closing and the like occur, the buried point data which is not reported yet can be lost, so that the buried point data received by the server is incomplete; therefore, the data loss rate of the buried point in the conventional buried point data reporting mode is higher.
Disclosure of Invention
In view of the foregoing, it is desirable to provide a buried point data reporting method, device, computer device and storage medium capable of reducing a buried point data loss rate.
A buried point data reporting method comprises the following steps:
receiving buried point event information uploaded by a preset buried point, acquiring buried point data to be reported from the buried point event information, and generating a corresponding reporting identifier according to the buried point event information;
combining the buried point data to be reported with the reporting identifier to obtain target buried point data carrying the reporting identifier, and storing the target buried point data to a preset local storage file;
reporting the target buried point data stored in the local storage file, and updating the reporting times recorded in the reporting identification;
and if the target buried point data is detected to be failed to report and the reporting frequency of the target buried point data is less than a preset threshold value, reporting the target buried point data again.
In one embodiment, the storing the target buried point data to a preset local storage file includes:
acquiring a buried point data group from the preset local storage file;
adding the target buried point data to the buried point data set to obtain a new buried point data set;
and updating the buried point data set stored in the local storage file into the new buried point data set.
In one embodiment, before reporting the target buried point data stored in the local storage file, the method further includes:
detecting an event type corresponding to the target buried point data in the buried point data set;
and determining a data reporting mode of the target buried point data according to the event type.
In one embodiment, the data reporting mode includes an immediate reporting mode and a non-immediate reporting mode;
the determining the data reporting mode of the target buried point data according to the event type comprises the following steps:
if the event type is a preset event type, determining that the data reporting mode of the target buried point data is an instant reporting mode; the immediate reporting mode is that the target buried point data is directly reported after being added to the buried point data group;
if the event type is not the preset event type, determining that the reporting mode of the buried point data is a non-instant reporting mode; and the non-instant reporting mode is to report the target buried point data after adding the target buried point data to the buried point data group and waiting for a preset time.
In one embodiment, the report identifier further includes a data identifier of the target buried point data;
the updating the reporting times of the target buried point data comprises the following steps:
acquiring a data identifier of the currently reported target buried point data;
sending the data identification to a preset number increasing processing function; the number increasing processing function is used for updating the reporting times of the corresponding target buried point data according to the data identification;
if the reporting times of the updated target buried point data are equal to the preset threshold value, deleting the target buried point data with the updated reporting times;
and if the reporting times of the updated target buried point data are smaller than the preset threshold value, confirming that the updating of the reporting times of the target buried point data is completed.
In one embodiment, after reporting the target buried point data stored in the local storage file, the method further includes:
and if the target buried point data is successfully reported, deleting the target buried point data stored in the local storage file.
In one embodiment, after it is detected that the target buried point data fails to be reported and the reporting frequency of the target buried point data is less than a preset threshold, the method further includes:
if the target buried point data is detected to be failed to report again and the reporting times of the target buried point data are equal to the preset threshold value, generating corresponding log information according to the target buried point data, and storing the log information into a preset buried point data processing log file;
and deleting the target buried point data stored in the local storage file.
A buried point data reporting device, the device comprising:
the information receiving module is used for receiving buried point event information uploaded by a preset buried point, acquiring buried point data to be reported from the buried point event information, and generating a corresponding reporting identifier according to the buried point event information;
the data combination module is used for combining the buried point data to be reported with the reporting identifier to obtain target buried point data carrying the reporting identifier, and storing the target buried point data to a preset local storage file;
a data reporting module, configured to report the target buried point data stored in the local storage file, and update the reporting times recorded in the reporting identifier;
and the repeated reporting module is used for reporting the target buried point data again if the reporting failure of the target buried point data is detected and the reporting times of the target buried point data are less than a preset threshold value.
A computer device comprising a memory and a processor, the memory storing a computer program, the processor implementing the following steps when executing the computer program:
receiving buried point event information uploaded by a preset buried point, acquiring buried point data to be reported from the buried point event information, and generating a corresponding reporting identifier according to the buried point event information;
combining the buried point data to be reported with the reporting identifier to obtain target buried point data carrying the reporting identifier, and storing the target buried point data to a preset local storage file;
reporting the target buried point data stored in the local storage file, and updating the reporting times recorded in the reporting identification;
and if the target buried point data is detected to be failed to report and the reporting frequency of the target buried point data is less than a preset threshold value, reporting the target buried point data again.
A computer-readable storage medium, on which a computer program is stored which, when executed by a processor, carries out the steps of:
receiving buried point event information uploaded by a preset buried point, acquiring buried point data to be reported from the buried point event information, and generating a corresponding reporting identifier according to the buried point event information;
combining the buried point data to be reported with the reporting identifier to obtain target buried point data carrying the reporting identifier, and storing the target buried point data to a preset local storage file;
reporting the target buried point data stored in the local storage file, and updating the reporting times recorded in the reporting identification;
and if the target buried point data is detected to be failed to report and the reporting frequency of the target buried point data is less than a preset threshold value, reporting the target buried point data again.
The buried point data reporting method, the buried point data reporting device, the computer equipment and the storage medium comprise the following steps: receiving buried point event information uploaded by a preset buried point, acquiring buried point data to be reported from the buried point event information, and generating a corresponding reporting identifier according to the buried point event information; combining the data of the buried points to be reported with the reporting identifier to obtain target buried point data carrying the reporting identifier, and storing the target buried point data to a preset local storage file; reporting the target buried point data stored in the local storage file, and updating the reporting times recorded in the reporting identification; and if the target buried point data is detected to be failed to report and the reporting frequency of the target buried point data is less than the preset threshold value, reporting the target buried point data again. By storing the target buried point data in a preset local storage file, the data is not easy to lose along with a page, and the storage stability of the target buried point data is improved; meanwhile, by updating the reporting times recorded in the reporting identification of the target buried point data, a retransmission mechanism is provided for the reporting of the target buried point data, the probability of successful uploading of the buried point data is improved, and the loss rate of uploading the buried point data is reduced.
Drawings
FIG. 1 is a diagram of an application environment of a buried point data reporting method according to an embodiment;
fig. 2 is a schematic flow chart of a buried point data reporting method in one embodiment;
FIG. 3 is a flowchart illustrating a step of storing target buried point data in a predetermined local storage file according to an embodiment;
FIG. 4 is a flowchart illustrating a data reporting method for determining target buried point data according to an event type in one embodiment;
FIG. 5 is a flowchart illustrating the reporting procedure of updating target buried point data according to an embodiment;
FIG. 6 is a block diagram illustrating an exemplary embodiment of a device for reporting buried point data;
FIG. 7 is a diagram illustrating an internal structure of a computer device according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The buried point data reporting method provided by the application can be applied to the application environment shown in fig. 1. Wherein the terminal 11 communicates with the server 12 via a network. The terminal 11 receives buried point event information uploaded by a preset buried point, and the terminal 11 acquires buried point data to be reported from the buried point event information and generates a corresponding reporting identifier according to the buried point event information; the terminal 11 combines the buried point data to be reported with the reporting identifier to obtain target buried point data carrying the reporting identifier, and stores the target buried point data to a preset local storage file; the terminal 11 reports the target buried point data stored in the local storage file to the server 12, and meanwhile, the terminal 11 updates the reporting times recorded in the reporting identification; if the terminal 11 detects that the reporting of the target buried point data fails and the reporting frequency of the target buried point data is less than the preset threshold, the terminal 11 reports the target buried point data to the server 12 again.
The terminal 11 may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices, and the server 12 may be implemented by an independent server or a server cluster formed by a plurality of servers.
In an embodiment, as shown in fig. 2, a method for reporting buried point data is provided, which is described by taking the method applied to the terminal in fig. 1 as an example, and includes the following steps:
and 21, receiving buried point event information uploaded by a preset buried point, acquiring buried point data to be reported from the buried point event information, and generating a corresponding reporting identifier according to the buried point event information.
The embedded point is an application running on a terminal or other equipment or a specific process in an interface thereof to collect some information, is used for tracking the use condition of the application, and refers to a relevant technology for collecting and processing user behavior events and an implementation process thereof, such as the number of times that a user clicks a certain button in a page, the duration of watching a certain video and the like; the embedded point data can be used for optimizing the application or providing data support for subsequent operation of the application, and the embedded point information can include access numbers (Visits), Visitor numbers (Visitor), dwell Time (Time On Site), Page browsing numbers (Page Views), and jump Rate (Bounce Rate). The collection of buried point information can be roughly divided into two categories: the page statistics (track this virtual page view) and the operation behavior statistics (track this button by an event) embedded point event information are information that a user executes a corresponding operation in a page or a program and triggers a corresponding embedded point to generate and send a specific operation event. The buried point data is data which can be identified and operated by the server after screening, processing and integrating the buried point event information. The reporting identifier is defined by the server and can identify the embedded point event information and the identifier information of the uploading state of the corresponding embedded point data.
Specifically, a preset embedded point on the terminal is triggered, and corresponding embedded point event information is generated according to the triggering operation and uploaded to the terminal; and the terminal obtains the buried point event information, extracts buried point data from the buried point event information and generates a corresponding reporting identifier according to the buried point event information. The reporting identifier may include a data identifier generated according to the buried point event information and/or the buried point data, and an identifier indicating the number of times of uploading the buried point data. For example, the data Identifier generated according to the buried point event information and/or the buried point data may be uuid (universal Unique Identifier), which is a standard for software construction and is a part of the field of distributed computing environments organized by the open software foundation. uuid is calculated and generated based on data such as current time, counter (counter) and hardware identifier (which may be MAC address of wireless network card of terminal device), and the purpose is to make all elements have unique identification information.
In the step, the terminal obtains the buried point data to be reported and the corresponding reporting identification through the buried point event information uploaded by the preset buried point, and provides data support for subsequent reporting work; the reporting identification enables the terminal to better update and identify the reporting state of the buried point data to be reported, thereby improving the successful uploading probability of the buried point data and reducing the loss rate of the uploaded buried point data.
And step 22, combining the data of the buried points to be reported with the reporting identifier to obtain the data of the target buried points carrying the reporting identifier, and storing the data of the target buried points to a preset local storage file.
The preset local storage file can be used for storing the target buried point data. The preset local storage file can adopt localStorage which is a part of web storage and is used for persistent local storage, and data cannot be expired unless the data is deleted actively.
Specifically, the terminal combines the data identifier uuid, the reporting time and the like to be used as a reporting identifier, recombines the reporting identifier with the buried point data to be reported, attaches the reporting identifier to the buried point data, and obtains the report in a { uuid: uuid, data: payload, time: 0} format after processing to be used as the target buried point data with the reporting identifier. And then the terminal stores the target embedded point data into a localStorage to realize the stable storage of the target embedded point data. It should be noted that the reporting identifier not only includes the above-mentioned contents, but also can add various identifiers that can be recognized and processed according to actual needs, such as an event type identifier, a data processing time identifier, and the like, and meanwhile, the preset local storage file may also adopt other data storage forms.
The terminal in the step combines the buried point data to be reported with the reporting identifier to obtain the target buried point data with the reporting identifier, and the reporting condition of the target buried point data can be mastered through the reporting identifier; meanwhile, the terminal stores the target buried point data to a preset local storage file, so that the target buried point data is stably stored and is not easily influenced by page closing, unloading and the like, the data is not easily lost along with the page, and the storage stability of the target buried point data is improved.
And step 23, reporting the target buried point data stored in the local storage file, and updating the reporting times recorded in the reporting identification.
Specifically, the terminal takes out target buried point data stored in a local storage file and reports the target buried point data to the server; while the reporting process is executed, the reporting times recorded in the reporting identifier are updated, which is usually a single increment. When the terminal reports the target buried point data, different reporting modes can be determined according to the type of the target buried point data, for example, a data identification array and a buried point data array can be respectively generated according to a plurality of target buried point data to be reported, and the data identification arrays and the buried point data arrays are pushed to a preset data sending module to execute a reporting process.
The terminal updates the reporting times recorded in the reporting identification while reporting the target buried point data, so that the reporting condition of the target buried point data is updated, the reporting condition of the target buried point data can be obtained even when the page is closed and unloaded, the successful uploading probability of the buried point data is improved, and the loss rate of the uploaded buried point data is reduced.
And 24, if the failure of reporting the target buried point data is detected and the reporting frequency of the target buried point data is less than a preset threshold value, reporting the target buried point data again.
Specifically, the terminal may detect a report result of the target buried point data, and determine whether the target buried point data is successfully reported from the report result. The reporting result may be a result returned by the server according to the reporting operation, or may be a result obtained by the terminal device after detection, for example, it may be determined that the target buried point data fails to be reported after information returned by the server is not received within a preset time.
A threshold may be set for the reporting times of the target buried point data, for example, the preset threshold of the reporting times is 5 times or 10 times, the target buried point data may be reported again within the preset threshold, and the target buried point data is not reported again after the reporting times reach or exceed the preset threshold, so as to avoid unlimited reporting or single invalid reporting of the target buried point data.
In the step, a preset threshold value is set for the reporting times of the target buried point data, and the target buried point data can be reported again for many times after the reporting fails, so that the target buried point data is ensured not to be reported failed due to network and other reasons; the preset threshold value can also avoid unlimited repeated reporting of target buried point data, occupy network bandwidth and increase data processing pressure of the terminal and the server. The step provides a retransmission mechanism for the report of the target buried point data, improves the successful uploading probability of the buried point data, and reduces the loss rate of uploading the buried point data.
The buried point data reporting method comprises the following steps: receiving buried point event information uploaded by a preset buried point, acquiring buried point data to be reported from the buried point event information, and generating a corresponding reporting identifier according to the buried point event information; combining the data of the buried points to be reported with the reporting identifier to obtain target buried point data carrying the reporting identifier, and storing the target buried point data to a preset local storage file; reporting the target buried point data stored in the local storage file, and updating the reporting times recorded in the reporting identification; and if the target buried point data is detected to be failed to report and the reporting frequency of the target buried point data is less than the preset threshold value, reporting the target buried point data again. By storing the target buried point data in a preset local storage file, the data is not easy to lose along with a page, and the storage stability of the target buried point data is improved; meanwhile, by updating the reporting times recorded in the reporting identification of the target buried point data, a retransmission mechanism is provided for the reporting of the target buried point data, the probability of successful uploading of the buried point data is improved, and the loss rate of uploading the buried point data is reduced.
In an embodiment, as shown in fig. 3, the step 22 of storing the target buried point data into a preset local storage file includes:
and step 33, updating the buried point data set stored in the local storage file into a new buried point data set.
Specifically, the buried point data group is a data list capable of storing a plurality of target buried point data in a preset local storage file at the same time. The terminal can obtain the buried point data group from the preset local storage file, add the newly obtained target buried point data to the buried point data group, then restore the buried point data group into the preset local storage file, and realize the updating of the buried point data group in a mode that the new buried point data group covers the original buried point data group.
In the embodiment, the multiple target buried point data are stored in the local storage file through the buried point data group, the target buried point data are stored in sequence through the buried point data group, and meanwhile, single report or multiple reports can be selected according to the type of the target buried point data, so that the storage stability and the reporting efficiency of the target buried point data are improved.
In an embodiment, as shown in fig. 4, step 23, before reporting the target buried point data stored in the local storage file, further includes:
and step 42, determining a data reporting mode of the target buried point data according to the event type.
Specifically, the event type corresponding to the target buried point data can be set according to the actual data processing requirement, for example, a page opening event, a click event, a custom event, and the like can be set to be reported immediately, and other types of events can be taken out and reported after reaching the time slice.
According to the method and the device, the reporting mode suitable for each target buried point data can be determined by detecting the event type, and the reporting efficiency of the target buried point data and the data processing efficiency of the server are improved.
In an embodiment, the step 42 of determining a data reporting manner of the target buried point data according to the event type includes:
if the event type is a preset event type, determining that the data reporting mode of the target buried point data is an instant reporting mode; the immediate reporting mode is that the target buried point data is directly reported after being added to the buried point data group;
if the event type is not the preset event type, determining that the reporting mode of the buried point data is a non-instant reporting mode; the non-immediate reporting mode is to report the target buried point data after adding the target buried point data to the buried point data group and waiting for a preset time.
Specifically, the preset event types are multiple preset types that need to adopt an instant reporting mode, for example, when only a page open event, a click event, and a custom event are determined as the preset event types, the page dwell time event does not belong to the preset event types, and a non-instant reporting mode should be adopted when reporting. The corresponding relation between the preset event type and the immediate/non-immediate reporting mode is not fixed, and the preset event type can be set to correspond to the non-immediate reporting mode.
In the embodiment, the event type is detected and matched with the preset event type, the specific data reporting mode of the target buried point data is further determined, and the reporting is performed according to the target buried point data or the mode that the server receives the target buried point data, so that the efficiency of reporting the target buried point data and the efficiency of receiving and processing the target buried point data by the server are improved.
In one embodiment, as shown in fig. 5, the step 23 of updating the reporting times of the target buried point data includes:
Specifically, the data identifier uuid or the data identifier array uuidList of the target buried point data reported this time may be transferred into a preset number increasing processing function addTimes function. In the addcopies function, the buried data group dataList in the local storage file localStorage is fetched. An array bearoninList can be defined to realize traversal operation, and through traversal of a data array dataList, if the data identification uuid of the reported target buried point data is matched, the reporting time is increased by one; if the reporting time is less than a preset threshold value, the updated data can be put into the beacon list; after traversing, covering the buried point data group dataList in the local storage file localStorage with data in the beaconiList array to update the reporting times, and deleting the target buried point data of which the reporting times reach a preset threshold. It should be noted that the operation of updating the reporting times of the target buried point data may also be implemented in other manners.
In the embodiment, the update of the reporting times of the target buried point data is realized through a number increasing processing function, the updated reporting times are detected, and the target buried point data reaching a preset threshold value is deleted; and a retransmission mechanism is provided for the report of the target buried point data, the successful uploading probability of the buried point data is improved, and the loss rate of the uploaded buried point data is reduced.
In an embodiment, the step 23, after reporting the target buried point data stored in the local storage file, further includes: and if the target buried point data is successfully reported, deleting the target buried point data stored in the local storage file.
Specifically, the terminal determines the report result of the target buried point data through the information returned by the server, and if the report is detected to be successful, the target buried point data stored in the local storage file can be deleted. The terminal actively deletes the target buried point data stored in the local storage file after detecting that the target buried point data is successfully reported, so that the utilization efficiency of the space in the local storage file is improved, a data guarantee is provided for a retransmission mechanism of the target buried point data, and the loss rate of uploading the buried point data is reduced.
In an embodiment, in step 24, after it is detected that the reporting of the target buried point data fails and the reporting frequency of the target buried point data is smaller than the preset threshold, the method further includes: if the target buried point data is detected to be failed to report again and the reporting times of the target buried point data are equal to a preset threshold value, generating corresponding log information according to the target buried point data, and storing the log information into a preset buried point data processing log file; and deleting the target buried point data stored in the local storage file.
Specifically, when the reporting frequency of the target buried point data is less than the preset threshold and the reporting fails, the terminal may repeatedly report the target buried point data until the reporting frequency reaches or exceeds the preset threshold. Before the target buried point data which fails to be reported is deleted, corresponding log information can be generated according to the target buried point data and stored in a preset buried point data processing log file for later verification or additional recording, so that the buried point data is prevented from being lost and being searched everywhere; the retransmission mechanism improves the probability of successful uploading of the buried point data and reduces the loss rate of uploading the buried point data.
It should be understood that although the various steps in the flow charts of fig. 2-5 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 2-5 may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed in turn or alternately with other steps or at least some of the other steps.
In one embodiment, as shown in fig. 6, there is provided a buried point data reporting apparatus, including: the system comprises an information receiving module 61, a data combination module 62, a data reporting module 63 and a repeated reporting module 64, wherein:
the information receiving module 61 is configured to receive buried point event information uploaded by a preset buried point, obtain buried point data to be reported from the buried point event information, and generate a corresponding reporting identifier according to the buried point event information;
the data combination module 62 is configured to combine the data of the buried points to be reported with the reporting identifier to obtain target data of the buried points with the reporting identifier, and store the target data of the buried points to a preset local storage file;
a data reporting module 63, configured to report the target buried point data stored in the local storage file, and update the reporting times recorded in the reporting identifier;
and a repeated reporting module 64, configured to report the target buried point data again if it is detected that the reporting of the target buried point data fails and the reporting frequency of the target buried point data is smaller than a preset threshold.
In one embodiment, the information receiving module 61 is further configured to obtain the buried point data set from a preset local storage file; adding the target buried point data to the buried point data set to obtain a new buried point data set; and updating the buried point data set stored in the local storage file into a new buried point data set.
In one embodiment, the data reporting module 63 is further configured to detect an event type corresponding to target buried point data in the buried point data set; and determining a data reporting mode of the target buried point data according to the event type.
In one embodiment, the data reporting module 63 is further configured to determine that the data reporting mode of the target buried point data is an instant reporting mode if the event type is a preset event type; the immediate reporting mode is that the target buried point data is directly reported after being added to the buried point data group;
in one embodiment, the data reporting module 63 is further configured to determine that the reporting mode of the buried point data is a non-immediate reporting mode if the event type is not the preset event type; the non-immediate reporting mode is to report the target buried point data after adding the target buried point data to the buried point data group and waiting for a preset time.
In one embodiment, the data reporting module 63 is further configured to obtain a data identifier of the currently reported target buried point data; sending the data identification to a preset number increasing processing function; the number increasing processing function is used for updating the reporting times of the corresponding target buried point data according to the data identification; and if the reporting times of the updated target buried point data are equal to a preset threshold value, deleting the target buried point data with the updated reporting times.
In one embodiment, the data reporting module 63 is further configured to obtain a data identifier of the currently reported target buried point data; sending the data identification to a preset number increasing processing function; the number increasing processing function is used for updating the reporting times of the corresponding target buried point data according to the data identification; and if the reporting times of the updated target buried point data are smaller than a preset threshold value, confirming that the updating of the reporting times of the target buried point data is completed.
In an embodiment, the repeated reporting module 64 is further configured to delete the target buried point data stored in the local storage file if it is detected that the target buried point data is successfully reported.
In one embodiment, the repeated reporting module 64 is further configured to generate corresponding log information according to the target buried point data and store the log information into a preset buried point data processing log file if it is detected that the target buried point data fails to be reported again and the reporting frequency of the target buried point data is equal to a preset threshold; and deleting the target buried point data stored in the local storage file.
For the specific limitation of the buried point data reporting device, reference may be made to the above limitation on the buried point data reporting method, which is not described herein again. All or part of each module in the buried point data reporting device can be realized by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as shown in fig. 7. The computer device includes a processor, a memory, a communication interface, a display screen, and an input device connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless communication can be realized through WIFI, an operator network, NFC (near field communication) or other technologies. The computer program is executed by a processor to realize a buried point data reporting method. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on the shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.
Those skilled in the art will appreciate that the architecture shown in fig. 7 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided, comprising a memory and a processor, the memory having a computer program stored therein, the processor implementing the following steps when executing the computer program:
receiving buried point event information uploaded by a preset buried point, acquiring buried point data to be reported from the buried point event information, and generating a corresponding reporting identifier according to the buried point event information;
combining the data of the buried points to be reported with the reporting identifier to obtain target buried point data carrying the reporting identifier, and storing the target buried point data to a preset local storage file;
reporting the target buried point data stored in the local storage file, and updating the reporting times recorded in the reporting identification;
and if the target buried point data is detected to be failed to report and the reporting frequency of the target buried point data is less than the preset threshold value, reporting the target buried point data again.
In one embodiment, the processor, when executing the computer program, further performs the steps of: acquiring a buried point data group from a preset local storage file; adding the target buried point data to the buried point data set to obtain a new buried point data set; and updating the buried point data set stored in the local storage file into a new buried point data set.
In one embodiment, the processor, when executing the computer program, further performs the steps of: detecting an event type corresponding to target buried point data in the buried point data set; and determining a data reporting mode of the target buried point data according to the event type.
In one embodiment, the processor, when executing the computer program, further performs the steps of: if the event type is a preset event type, determining that the data reporting mode of the target buried point data is an instant reporting mode; the immediate reporting mode is that the target buried point data is added to the buried point data group and then is directly reported.
In one embodiment, the processor, when executing the computer program, further performs the steps of: if the event type is not the preset event type, determining that the reporting mode of the buried point data is a non-instant reporting mode; the non-immediate reporting mode is to report the target buried point data after adding the target buried point data to the buried point data group and waiting for a preset time.
In one embodiment, the processor, when executing the computer program, further performs the steps of: acquiring a data identifier of currently reported target buried point data; sending the data identification to a preset number increasing processing function; the number increasing processing function is used for updating the reporting times of the corresponding target buried point data according to the data identification; and if the reporting times of the updated target buried point data are equal to a preset threshold value, deleting the target buried point data with the updated reporting times.
In one embodiment, the processor, when executing the computer program, further performs the steps of: acquiring a data identifier of currently reported target buried point data; sending the data identification to a preset number increasing processing function; the number increasing processing function is used for updating the reporting times of the corresponding target buried point data according to the data identification; and if the reporting times of the updated target buried point data are smaller than a preset threshold value, confirming that the updating of the reporting times of the target buried point data is completed.
In one embodiment, the processor, when executing the computer program, further performs the steps of: and if the target buried point data is successfully reported, deleting the target buried point data stored in the local storage file.
In one embodiment, the processor, when executing the computer program, further performs the steps of: if the target buried point data is detected to be failed to report again and the reporting times of the target buried point data are equal to a preset threshold value, generating corresponding log information according to the target buried point data, and storing the log information into a preset buried point data processing log file; and deleting the target buried point data stored in the local storage file.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of:
receiving buried point event information uploaded by a preset buried point, acquiring buried point data to be reported from the buried point event information, and generating a corresponding reporting identifier according to the buried point event information;
combining the data of the buried points to be reported with the reporting identifier to obtain target buried point data carrying the reporting identifier, and storing the target buried point data to a preset local storage file;
reporting the target buried point data stored in the local storage file, and updating the reporting times recorded in the reporting identification;
and if the target buried point data is detected to be failed to report and the reporting frequency of the target buried point data is less than the preset threshold value, reporting the target buried point data again.
In one embodiment, the computer program when executed by the processor further performs the steps of: acquiring a buried point data group from a preset local storage file; adding the target buried point data to the buried point data set to obtain a new buried point data set; and updating the buried point data set stored in the local storage file into a new buried point data set.
In one embodiment, the computer program when executed by the processor further performs the steps of: detecting an event type corresponding to target buried point data in the buried point data set; and determining a data reporting mode of the target buried point data according to the event type.
In one embodiment, the computer program when executed by the processor further performs the steps of: if the event type is a preset event type, determining that the data reporting mode of the target buried point data is an instant reporting mode; the immediate reporting mode is that the target buried point data is added to the buried point data group and then is directly reported.
In one embodiment, the computer program when executed by the processor further performs the steps of: if the event type is not the preset event type, determining that the reporting mode of the buried point data is a non-instant reporting mode; the non-immediate reporting mode is to report the target buried point data after adding the target buried point data to the buried point data group and waiting for a preset time.
In one embodiment, the computer program when executed by the processor further performs the steps of: acquiring a data identifier of currently reported target buried point data; sending the data identification to a preset number increasing processing function; the number increasing processing function is used for updating the reporting times of the corresponding target buried point data according to the data identification; and if the reporting times of the updated target buried point data are equal to a preset threshold value, deleting the target buried point data with the updated reporting times.
In one embodiment, the computer program when executed by the processor further performs the steps of: acquiring a data identifier of currently reported target buried point data; sending the data identification to a preset number increasing processing function; the number increasing processing function is used for updating the reporting times of the corresponding target buried point data according to the data identification; and if the reporting times of the updated target buried point data are smaller than a preset threshold value, confirming that the updating of the reporting times of the target buried point data is completed.
In one embodiment, the computer program when executed by the processor further performs the steps of: and if the target buried point data is successfully reported, deleting the target buried point data stored in the local storage file.
In one embodiment, the computer program when executed by the processor further performs the steps of: if the target buried point data is detected to be failed to report again and the reporting times of the target buried point data are equal to a preset threshold value, generating corresponding log information according to the target buried point data, and storing the log information into a preset buried point data processing log file; and deleting the target buried point data stored in the local storage file.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database or other medium used in the embodiments provided herein can include at least one of non-volatile and volatile memory. Non-volatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical storage, or the like. Volatile Memory can include Random Access Memory (RAM) or external cache Memory. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others.
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above examples only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A buried point data reporting method is characterized by comprising the following steps:
receiving buried point event information uploaded by a preset buried point, acquiring buried point data to be reported from the buried point event information, and generating a corresponding reporting identifier according to the buried point event information;
combining the buried point data to be reported with the reporting identifier to obtain target buried point data carrying the reporting identifier, and storing the target buried point data to a preset local storage file;
reporting the target buried point data stored in the local storage file, and updating the reporting times recorded in the reporting identification;
and if the target buried point data is detected to be failed to report and the reporting frequency of the target buried point data is less than a preset threshold value, reporting the target buried point data again.
2. The method of claim 1, wherein storing the target burial point data to a preset local storage file comprises:
acquiring a buried point data group from the preset local storage file;
adding the target buried point data to the buried point data set to obtain a new buried point data set;
and updating the buried point data set stored in the local storage file into the new buried point data set.
3. The method of claim 2, further comprising, prior to reporting the target buried point data stored in the local storage file:
detecting an event type corresponding to the target buried point data in the buried point data set;
and determining a data reporting mode of the target buried point data according to the event type.
4. The method of claim 3, wherein the data reporting modes include an immediate reporting mode and a non-immediate reporting mode;
the determining the data reporting mode of the target buried point data according to the event type comprises the following steps:
if the event type is a preset event type, determining that the data reporting mode of the target buried point data is an instant reporting mode; the immediate reporting mode is that the target buried point data is directly reported after being added to the buried point data group;
if the event type is not the preset event type, determining that the reporting mode of the buried point data is a non-instant reporting mode; and the non-instant reporting mode is to report the target buried point data after adding the target buried point data to the buried point data group and waiting for a preset time.
5. The method according to claim 1, wherein the reporting identifier further includes a data identifier of the target buried point data;
the updating the reporting times of the target buried point data comprises the following steps:
acquiring a data identifier of the currently reported target buried point data;
sending the data identification to a preset number increasing processing function; the number increasing processing function is used for updating the reporting times of the corresponding target buried point data according to the data identification;
if the reporting times of the updated target buried point data are equal to the preset threshold value, deleting the target buried point data with the updated reporting times;
and if the reporting times of the updated target buried point data are smaller than the preset threshold value, confirming that the updating of the reporting times of the target buried point data is completed.
6. The method of claim 1, further comprising, after reporting the target buried point data stored in the local storage file:
and if the target buried point data is successfully reported, deleting the target buried point data stored in the local storage file.
7. The method of claim 1, wherein after detecting that the target buried point data fails to be reported and the reporting frequency of the target buried point data is less than a preset threshold, reporting the target buried point data again, further comprising:
if the target buried point data is detected to be failed to report again and the reporting times of the target buried point data are equal to the preset threshold value, generating corresponding log information according to the target buried point data, and storing the log information into a preset buried point data processing log file;
and deleting the target buried point data stored in the local storage file.
8. A buried point data reporting device, comprising:
the information receiving module is used for receiving buried point event information uploaded by a preset buried point, acquiring buried point data to be reported from the buried point event information, and generating a corresponding reporting identifier according to the buried point event information;
the data combination module is used for combining the buried point data to be reported with the reporting identifier to obtain target buried point data carrying the reporting identifier, and storing the target buried point data to a preset local storage file;
a data reporting module, configured to report the target buried point data stored in the local storage file, and update the reporting times recorded in the reporting identifier;
and the repeated reporting module is used for reporting the target buried point data again if the reporting failure of the target buried point data is detected and the reporting times of the target buried point data are less than a preset threshold value.
9. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor, when executing the computer program, implements the steps of the method of any of claims 1 to 7.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010714052.0A CN112000541A (en) | 2020-07-23 | 2020-07-23 | Buried point data reporting method and device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010714052.0A CN112000541A (en) | 2020-07-23 | 2020-07-23 | Buried point data reporting method and device, computer equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112000541A true CN112000541A (en) | 2020-11-27 |
Family
ID=73467640
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010714052.0A Pending CN112000541A (en) | 2020-07-23 | 2020-07-23 | Buried point data reporting method and device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112000541A (en) |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112699021A (en) * | 2020-12-08 | 2021-04-23 | 网易（杭州）网络有限公司 | Information processing method and device, terminal equipment and server |
| CN112732546A (en) * | 2021-01-28 | 2021-04-30 | 腾讯科技（深圳）有限公司 | Application-based use duration processing method, device, equipment and storage medium |
| CN113010481A (en) * | 2021-03-18 | 2021-06-22 | 成都欧珀通信科技有限公司 | File capture method, device, terminal and storage medium |
| CN113014623A (en) * | 2021-02-05 | 2021-06-22 | 招联消费金融有限公司 | Method and device for processing real-time streaming data of embedded point, computer equipment and storage medium |
| CN113162982A (en) * | 2021-03-19 | 2021-07-23 | 维沃移动通信有限公司 | Buried point information reporting method and device and electronic equipment |
| CN113472858A (en) * | 2021-06-10 | 2021-10-01 | 北京达佳互联信息技术有限公司 | Buried point data processing method and device and electronic equipment |
| CN113760177A (en) * | 2021-01-04 | 2021-12-07 | 北京沃东天骏信息技术有限公司 | Data reporting method and device |
| CN113836464A (en) * | 2021-09-16 | 2021-12-24 | 平安养老保险股份有限公司 | Page data processing method and device, computer equipment and storage medium |
| CN114629818A (en) * | 2022-04-07 | 2022-06-14 | 康键信息技术（深圳）有限公司 | Method and system for reporting and detecting front-end buried point data and computer readable storage medium |
| CN114968413A (en) * | 2022-06-21 | 2022-08-30 | 四三九九网络股份有限公司 | Method for collecting Android application starting event |
| CN115442225A (en) * | 2022-08-01 | 2022-12-06 | 上海数禾信息科技有限公司 | Method and device for reporting buried point log and method and device for monitoring buried point quality |
| CN112732546B (en) * | 2021-01-28 | 2024-06-04 | 腾讯科技（深圳）有限公司 | Method, device, equipment and storage medium for long-term processing based on application use time |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017167042A1 (en) * | 2016-04-01 | 2017-10-05 | 阿里巴巴集团控股有限公司 | Statistical method and apparatus for behaviors of front-end users |
| CN107562598A (en) * | 2017-08-03 | 2018-01-09 | 合肥美的智能科技有限公司 | Processing method, device, computer installation, server and readable storage medium storing program for executing |
| CN110489699A (en) * | 2019-08-16 | 2019-11-22 | 南京云帐房网络科技有限公司 | A kind of asynchronous data collection method and system |
| CN110851339A (en) * | 2019-10-12 | 2020-02-28 | 平安普惠企业管理有限公司 | Method and device for reporting buried point data, storage medium and terminal equipment |
| CN110908879A (en) * | 2019-10-16 | 2020-03-24 | 平安普惠企业管理有限公司 | Method, device, terminal and storage medium for reporting buried point data |
| CN111427741A (en) * | 2020-02-26 | 2020-07-17 | 中国平安人寿保险股份有限公司 | Buried point reporting method and related product |
| CN111435298A (en) * | 2019-01-11 | 2020-07-21 | 北京京东尚科信息技术有限公司 | Point burying method and device, electronic equipment and storage medium |
-
2020
- 2020-07-23 CN CN202010714052.0A patent/CN112000541A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017167042A1 (en) * | 2016-04-01 | 2017-10-05 | 阿里巴巴集团控股有限公司 | Statistical method and apparatus for behaviors of front-end users |
| CN107562598A (en) * | 2017-08-03 | 2018-01-09 | 合肥美的智能科技有限公司 | Processing method, device, computer installation, server and readable storage medium storing program for executing |
| CN111435298A (en) * | 2019-01-11 | 2020-07-21 | 北京京东尚科信息技术有限公司 | Point burying method and device, electronic equipment and storage medium |
| CN110489699A (en) * | 2019-08-16 | 2019-11-22 | 南京云帐房网络科技有限公司 | A kind of asynchronous data collection method and system |
| CN110851339A (en) * | 2019-10-12 | 2020-02-28 | 平安普惠企业管理有限公司 | Method and device for reporting buried point data, storage medium and terminal equipment |
| CN110908879A (en) * | 2019-10-16 | 2020-03-24 | 平安普惠企业管理有限公司 | Method, device, terminal and storage medium for reporting buried point data |
| CN111427741A (en) * | 2020-02-26 | 2020-07-17 | 中国平安人寿保险股份有限公司 | Buried point reporting method and related product |
Cited By (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112699021A (en) * | 2020-12-08 | 2021-04-23 | 网易（杭州）网络有限公司 | Information processing method and device, terminal equipment and server |
| CN113760177A (en) * | 2021-01-04 | 2021-12-07 | 北京沃东天骏信息技术有限公司 | Data reporting method and device |
| CN112732546A (en) * | 2021-01-28 | 2021-04-30 | 腾讯科技（深圳）有限公司 | Application-based use duration processing method, device, equipment and storage medium |
| CN112732546B (en) * | 2021-01-28 | 2024-06-04 | 腾讯科技（深圳）有限公司 | Method, device, equipment and storage medium for long-term processing based on application use time |
| CN113014623A (en) * | 2021-02-05 | 2021-06-22 | 招联消费金融有限公司 | Method and device for processing real-time streaming data of embedded point, computer equipment and storage medium |
| CN113014623B (en) * | 2021-02-05 | 2022-05-10 | 招联消费金融有限公司 | Method and device for processing real-time streaming data of embedded point, computer equipment and storage medium |
| CN113010481B (en) * | 2021-03-18 | 2023-06-09 | 成都欧珀通信科技有限公司 | File capturing method, device, terminal and storage medium |
| CN113010481A (en) * | 2021-03-18 | 2021-06-22 | 成都欧珀通信科技有限公司 | File capture method, device, terminal and storage medium |
| CN113162982A (en) * | 2021-03-19 | 2021-07-23 | 维沃移动通信有限公司 | Buried point information reporting method and device and electronic equipment |
| CN113162982B (en) * | 2021-03-19 | 2023-12-29 | 维沃移动通信有限公司 | Buried point information reporting method and device and electronic equipment |
| CN113472858A (en) * | 2021-06-10 | 2021-10-01 | 北京达佳互联信息技术有限公司 | Buried point data processing method and device and electronic equipment |
| CN113472858B (en) * | 2021-06-10 | 2023-09-29 | 北京达佳互联信息技术有限公司 | Buried point data processing method and device and electronic equipment |
| CN113836464A (en) * | 2021-09-16 | 2021-12-24 | 平安养老保险股份有限公司 | Page data processing method and device, computer equipment and storage medium |
| CN114629818A (en) * | 2022-04-07 | 2022-06-14 | 康键信息技术（深圳）有限公司 | Method and system for reporting and detecting front-end buried point data and computer readable storage medium |
| CN114968413A (en) * | 2022-06-21 | 2022-08-30 | 四三九九网络股份有限公司 | Method for collecting Android application starting event |
| CN115442225A (en) * | 2022-08-01 | 2022-12-06 | 上海数禾信息科技有限公司 | Method and device for reporting buried point log and method and device for monitoring buried point quality |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112000541A (en) | Buried point data reporting method and device, computer equipment and storage medium | |
| WO2019120037A1 (en) | Model construction method, network resource preloading method and apparatus, medium, and terminal | |
| CN110008118B (en) | Page data testing method and device, computer equipment and storage medium | |
| US9836346B2 (en) | Error troubleshooting using a correlated knowledge base | |
| CN113687974B (en) | Client log processing method and device and computer equipment | |
| CN107872523B (en) | Network data loading method and device, storage medium and mobile terminal | |
| CN108319662A (en) | Page processing method, device, electronic equipment and readable storage medium storing program for executing | |
| CN112115167B (en) | Cache system hot spot data access method, device, equipment and storage medium | |
| CN105376335A (en) | Method and device for collection data uploading | |
| CN111866158B (en) | Routing method, routing device, computer equipment and storage medium | |
| CN112506755B (en) | Log acquisition method, device, computer equipment and storage medium | |
| CN113014623B (en) | Method and device for processing real-time streaming data of embedded point, computer equipment and storage medium | |
| CN108984339B (en) | Data recovery method and related product | |
| CN113254320A (en) | Method and device for recording user webpage operation behaviors | |
| CN110659435A (en) | Page data acquisition processing method and device, computer equipment and storage medium | |
| CN113988225A (en) | Method and device for establishing representation extraction model, representation extraction and type identification | |
| CN112052015A (en) | Version release method and device, computer equipment and storage medium | |
| CN111966701A (en) | Metadata updating method, device, equipment and storage medium | |
| CN115828256A (en) | Unauthorized and unauthorized logic vulnerability detection method | |
| CN113840313B (en) | Network mode control method and device of mobile terminal and computer equipment | |
| CN111767111B (en) | Page data processing method and device, electronic equipment and storage medium | |
| CN112541106A (en) | Network data acquisition method and device, computer equipment and storage medium | |
| CN111708651A (en) | Log acquisition, portrait generation and fault positioning method, device and related equipment | |
| CN112214697A (en) | Webpage processing method and device, computer equipment and storage medium | |
| CN108681594A (en) | Document handling method and relevant apparatus |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20201127 |