CN112181798A - Data recording method and device - Google Patents
Data recording method and device Download PDFInfo
- Publication number
- CN112181798A CN112181798A CN202011351428.2A CN202011351428A CN112181798A CN 112181798 A CN112181798 A CN 112181798A CN 202011351428 A CN202011351428 A CN 202011351428A CN 112181798 A CN112181798 A CN 112181798A
- Authority
- CN
- China
- Prior art keywords
- data
- page
- application
- access
- link
- 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.)
- Granted
Links
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/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
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
An embodiment of the present specification provides a data recording method and apparatus, wherein the data recording method includes: recording access data generated after an application event of an application page in an application access link is triggered; writing the page identification of the application page into a data container of the application access link, and combining the page identification into corresponding access data; under the condition that the access of the application access link is finished, performing data fusion on the link information in the data container and the page element data of the application page and the merged access data; and storing the access data set obtained after fusion in a log file form.
Description
Technical Field
The present disclosure relates to the field of data processing technologies, and in particular, to a data recording method and apparatus.
Background
With the continuous development and popularization of the internet, the mode of providing online services based on the internet is gradually applied to various service fields, more and more merchants provide online services for users in online platforms of various service fields, and users often have certain concerns in the process of providing online services by merchants using online platforms, wherein the concerns refer to whether online services provided by merchants of online platforms can be effectively provided for a long time and whether better service quality can be maintained.
Specifically, in the prior art, in the process of performing data access recording, screenshot data and access data records corresponding to a target page are acquired based on a buried point program in an application, and meanwhile, before performing access data recording, the buried point program needs to be deployed in the target page, and when the target page is accessed, the deployed buried point program acquires relevant data of the target page, such as the screenshot data and the access record data. However, this implementation requires a developer to deploy a point burying program in a target page in advance, which requires large manpower and material resources and makes practical application difficult.
Disclosure of Invention
One or more embodiments of the present specification provide a data recording method. The data recording method comprises the following steps: and recording access data generated after an application event of the application page in the application access link is triggered. And writing the page identification of the application page into a data container of the application access link, and combining the page identification into corresponding access data. And under the condition that the access of the application access link is finished, performing data fusion on the link information in the data container and the page element data of the application page and the merged access data. And storing the access data set obtained after fusion in a log file form.
One or more embodiments of the present specification provide a data recording apparatus including: and the access data recording module is configured to record access data generated after an application event of the application page in the application access link is triggered. And the data merging module is configured to write the page identifier of the application page into a data container of the application access link and merge the page identifier into corresponding access data. And the data fusion module is configured to perform data fusion on the link information in the data container and the page element data of the application page and the merged access data under the condition that the access of the application access link is finished. And the access data set storage module is configured to store the access data set obtained after fusion in a log file form.
One or more embodiments of the present specification provide a data recording apparatus including: a processor; and a memory configured to store computer-executable instructions that, when executed, cause the processor to: and recording access data generated after an application event of the application page in the application access link is triggered. And writing the page identification of the application page into a data container of the application access link, and combining the page identification into corresponding access data. And under the condition that the access of the application access link is finished, performing data fusion on the link information in the data container and the page element data of the application page and the merged access data. And storing the access data set obtained after fusion in a log file form.
One or more embodiments of the present specification provide a storage medium storing computer-executable instructions that, when executed, implement the following: and recording access data generated after an application event of the application page in the application access link is triggered. And writing the page identification of the application page into a data container of the application access link, and combining the page identification into corresponding access data. And under the condition that the access of the application access link is finished, performing data fusion on the link information in the data container and the page element data of the application page and the merged access data. And storing the access data set obtained after fusion in a log file form.
Drawings
In order to more clearly illustrate one or more embodiments or technical solutions in the prior art in the present specification, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present specification, and for those skilled in the art, other drawings can be obtained according to the drawings without inventive exercise;
FIG. 1 is a process flow diagram of a data recording method provided in one or more embodiments of the present disclosure;
FIG. 2 is a flowchart of a data recording method applied to a security project scenario according to one or more embodiments of the present disclosure;
FIG. 3 is a process flow diagram of a data recording method applied to an asset management business scenario according to one or more embodiments of the present disclosure;
FIG. 4 is a schematic diagram of a data recording device according to one or more embodiments of the present disclosure;
fig. 5 is a schematic structural diagram of a data recording device according to one or more embodiments of the present disclosure.
Detailed Description
In order to make those skilled in the art better understand the technical solutions in one or more embodiments of the present disclosure, the technical solutions in one or more embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in one or more embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all embodiments. All other embodiments that can be derived by a person skilled in the art from one or more of the embodiments described herein without making any inventive step shall fall within the scope of protection of this document.
An embodiment of a data recording method provided in this specification:
referring to fig. 1, which shows a processing flow chart of a data recording method provided by the present embodiment, referring to fig. 2, which shows a processing flow chart of a data recording method applied to a security project scenario provided by the present embodiment, and referring to fig. 3, which shows a processing flow chart of a data recording method applied to an asset management service scenario provided by the present embodiment.
Referring to fig. 1, the data recording method provided in this embodiment specifically includes steps S102 to S108.
Step S102, recording access data generated after an application event of an application page in an application access link is triggered.
According to the data recording method provided by the embodiment, the access data generated when the user accesses each application page is recorded, the link information of the application page link accessed by the user and the page element data of the application page are recorded at the same time, and finally, under the condition that the user finishes accessing the application access link, the recorded access data, the page element data and the link information are combined to obtain the access data set of the application page link accessed by the user, and the access data set is stored in the local database in the form of a log file, so that the access data of the whole link in the process of accessing the application link by the user can be recorded completely and stored persistently, and the completeness of the access data record and the comprehensiveness of the access data management are realized.
The application page described in this embodiment refers to a front-end page of an online application that provides services depending on the internet, such as a front-end web page of a guarantee item (e.g., an insurance item) that provides a guarantee service, a business access page of an asset management business (e.g., a fund business, a financing business) that provides an asset management service, or a front-end service page of an online mutual aid help item that provides a mutual aid help service.
The application access link refers to an access recording link for recording an access process in a process of accessing an application page by a user, and specifically, the application access link is composed of application pages accessed by the user, that is: the application pages accessed by the user constitute the user's application access link. Correspondingly, the link information of the application access link comprises an identification chain consisting of the page identifications of the application pages determined according to the access time sequence.
In a specific implementation, in the process of accessing an application page in the application access link, access data generated after an application event of each application page is triggered is recorded.
For example, in the process that a user accesses a web page of a security project, an event monitoring API (Application Programming Interface) provided by HTML5 is called to monitor an event triggered by the user in the process that the web page is accessed, a data recording API is called after the event is executed to record event execution data generated after the event is executed, and the recorded event execution data is stored in a memory as access data of the user accessing the web page;
or, in the process that a user accesses a service access page of the asset management service realized based on the applet, calling a corresponding event monitoring API to monitor an event triggered by the user in the service access page access process, calling a data recording API after the event execution to record event execution data generated after the event execution, and storing the recorded event execution data in an internal memory as access data of the user access service access page.
And step S104, writing the page identifier of the application page into a data container of the application access link, and combining the page identifier to corresponding access data.
In order to improve the access efficiency of the application page, in an optional implementation manner provided by this embodiment, before writing the page identifier of the application page into the data container and merging the page identifier into corresponding access data, by detecting an access request of a user for the application access link, and in a case that a first access request of the user for the application access link is detected, creating a session of the application access link as the data container; the data container records therein a page identifier, a page URL (Uniform Resource Locator) and/or page element data of an accessed application page.
It should be noted that, the data container is located in the memory, in order to improve the recording efficiency of subsequent access to the data set, under the condition that an access request of a user for accessing an application page of the application access link is monitored, the page element data and/or the page URL of the accessed application page is written into the data container of the application access link, that is, the page element data and/or the page URL of the accessed application page is stored into the memory, or after the accessed application page is entered, the page element data and/or the page URL of the accessed application page is written into the data container of the application access link, so that the data fusion of the page element data and/or the page URL and the access data is performed subsequently.
In a specific implementation, in order to improve data writing efficiency and data writing effectiveness in a process of writing a page identifier of the application page into a data container of the application access link, in an optional implementation manner provided in this embodiment, if a page jump event that jumps from the application page to a next application page is monitored, the page identifier of the application page is written into the data container; the page identification comprises a hash character string obtained after the hash processing is carried out on the page element data of the application page.
On the basis, in the process of merging the page identifier to the corresponding access data, merging the page identifier and the access data by merging the hash character string of the application page and the access data of the application page stored in the memory is realized.
And step S106, performing data fusion on the link information in the data container and the page element data of the application page and the merged access data under the condition that the access of the application access link is finished.
In specific implementation, in the access process of the application access link, detecting whether the access of the application access link is finished or not by detecting a specific application event, specifically, confirming that the access of the application access link is finished under the condition that an application exit event or an application confirmation event is detected; otherwise, if the application quit event or the application confirmation event is not detected, determining that the access of the application access link is not finished.
In this embodiment, when the access of the application access link is not finished, the recording and merging processing of the access data of the application page in the application access link is continued, which is specifically implemented as follows:
if a page jump event for jumping from the application page to a next application page is monitored, recording access data generated after the application event of the next application page is triggered and storing the access data into a memory;
and writing the page identifier of the next application page into the data container, and combining the page identifier of the next application page into the access data of the next application page.
In addition, when the access of the application access link is finished, data fusion is performed on the link information in the data container and the page element data of the application page and the merged access data, and in an optional implementation manner provided in this embodiment, the data fusion is specifically implemented in the following manner:
determining a mapping relation between the combined access data and the application page based on the page identification contained in the combined access data;
and merging the link information, the page element data and the merged access data based on the mapping relation to obtain the access data set.
It should be noted that after the access of the application access link is finished and the link information and the page element data in the data container are merged with the recorded access data, in order to improve the memory utilization, the link information and the page element data in the data container stored in the memory are deleted, or the data container in the memory is destroyed. Similarly, after storing the access data set in the form of a log file, in order to further improve the memory utilization, the access data stored in the memory is deleted.
And step S108, storing the access data set obtained after fusion according to the form of a log file.
On the basis that the access data set is obtained by performing data fusion on the link information, the page element data and the recorded access data in the data container, in this embodiment, in order to improve the storage effectiveness of the access data set and also improve the query convenience of the access data set after storage, in an optional implementation manner provided by this embodiment, the access data set is stored in a log file form, which is specifically implemented as follows:
writing the access data set into a log file according to a preset format;
and storing the log file to a local database.
For example, a session field, an application page identification field and an access behavior field are set in the log file, the session field is used for recording a user ID and/or a link ID of an application access link, the application page identification field is used for recording a page URL, page element data and/or page identification of an application page, and the access behavior field is used for recording access data and/or a hash character string recorded for the access page.
The following further describes the data recording method provided in this embodiment by taking an application of the data recording method provided in this embodiment in a guarantee project scenario as an example, and referring to fig. 2, the data recording method applied in the guarantee project scenario specifically includes steps S202 to S214.
Step S202, calling an event monitoring API to monitor events triggered by access actions submitted by a front-end web page aiming at the guarantee items.
The front-end web page of the guarantee item is a web page constructed based on HTML 5.
Step S204, calling a data recording API to record access data generated after the event is executed.
In step S206, the generated access data is stored in the memory.
Step S208, if a page jump event is monitored, writing a hash character string of the front-end web page in the session of the item access link.
The hash character string of the front-end web page is obtained by carrying out hash processing on page element data of the front-end web page before page skipping.
Step S210, merging the hash string and the access data stored in the memory.
Step S212, under the condition that the access of the item access link is finished, performing data fusion on the link information in the session and the page element data of the front-end web page and the merged access data.
And step S214, storing the access data set obtained after fusion in the form of a log file.
The following further describes the data recording method provided in this embodiment by taking an application of the data recording method provided in this embodiment in an asset management service scenario as an example, and referring to fig. 3, the data recording method applied in the asset management service scenario specifically includes steps S302 to S316.
Step S302, calling an event monitoring API to monitor a business event triggered by an access action submitted by a business access page aiming at the asset management business.
The service access page of the asset management service is a service page realized based on an applet.
Step S304, calling a data recording API to record access data generated after the business event is executed.
Step S306, the generated access data is stored in the memory.
Step S308, if a page jump event is monitored, writing a hash character string of the service access page in the session of the service access link.
The hash character string of the service access page is obtained by performing hash processing on page element data of the service access page before page skipping.
Step S310, merging the hash string and the access data stored in the memory.
Step S312, in the case that the access of the service access link is finished, performing data fusion on the link information in the session and the page element data of the service access page with the merged access data.
Step S314, storing the access data set obtained after fusion according to the form of the log file.
Step S316, delete the access data and session stored in the memory.
In summary, in the data recording method provided in this embodiment, access data generated after an application page is accessed in an application access link is recorded, a page identifier of the accessed application page is written into a corresponding data container, and the page identifier is merged with the recorded access data, and then, under the condition that access to the application access link is finished, data fusion is performed on link information in the data container, page element data of the application page, and the recorded access data, so that access data of a full link in an application access link access process can be completely recorded, and finally, an access data set obtained after merging is persistently stored in a log file form, so that integrity of access data recording and comprehensiveness of access data management are achieved.
The data recording device provided by the specification comprises the following embodiments:
in the above embodiments, a data recording method is provided, and correspondingly, a data recording apparatus is also provided, which is described below with reference to the accompanying drawings.
Referring to fig. 4, a schematic diagram of a data recording apparatus provided in this embodiment is shown.
Since the device embodiments correspond to the method embodiments, the description is relatively simple, and the relevant portions may refer to the corresponding description of the method embodiments provided above. The device embodiments described below are merely illustrative.
The present embodiment provides a data recording apparatus including:
an access data recording module 402 configured to record access data generated after an application event of an application page in an application access link is triggered;
a data merging module 404, configured to write the page identifier of the application page into a data container of the application access link, and merge the page identifier into corresponding access data;
a data fusion module 406, configured to perform data fusion on the link information in the data container and the page element data of the application page and the merged access data when the access of the application access link is finished;
and an access data set storage module 408 configured to store the access data set obtained after the fusion in the form of a log file.
Optionally, the access data recording module 402 is specifically configured to:
calling a monitoring interface to monitor an application event triggered by an access action submitted by the application page;
and calling a data recording interface to record the access data generated after the application event is executed, and storing the generated access data to a memory.
Optionally, the data merging module 404 includes:
the page identifier writing sub-module is configured to write the page identifier of the application page into the data container if a page jump event that the application page jumps to a next application page from the application page is monitored;
the page identification comprises a hash character string obtained after the hash processing is carried out on the page element data of the application page.
Optionally, the data merging module 404 includes:
and the merging submodule is configured to merge the hash character string of the application page with the access data of the application page stored in the memory.
Optionally, the application access link is composed of application pages accessed by a user, and the link information includes an identifier chain composed of page identifiers of the application pages determined according to an access time sequence.
Optionally, the data recording apparatus further includes:
the data container module is configured to create a session of the application access link as the data container if a first access request of a user for the application access link is detected;
and the data container records page identification, page URL and/or page element data of the accessed application page in the application access link.
Optionally, the data fusion module 406 is specifically configured to:
determining a mapping relation between the combined access data and the application page based on the page identification contained in the combined access data;
and merging the link information, the page element data and the merged access data based on the mapping relation to obtain the access data set.
Optionally, the data recording apparatus further includes:
the recording module is configured to record access data generated after the application event of the next application page is triggered and store the access data into a memory if a page jump event of jumping from the application page to the next application page is monitored;
a writing module configured to write the page identifier of the next application page into the data container and merge the page identifier of the next application page into the access data of the next application page;
the recording module and the writing module operate when access of the application access link is not ended.
Optionally, the access data set storage module 408 is specifically configured to:
writing the access data set into a log file according to a preset format;
and storing the log file to a local database.
The data recording device provided by the specification comprises the following embodiments:
corresponding to the above-described data recording method, based on the same technical concept, one or more embodiments of the present specification further provide a data recording apparatus for performing the above-described data recording method, and fig. 5 is a schematic structural diagram of the data recording apparatus provided by one or more embodiments of the present specification.
The present embodiment provides a data recording apparatus, including:
as shown in fig. 5, the data recording device may have a relatively large difference due to different configurations or performances, and may include one or more processors 501 and a memory 502, where the memory 502 may store one or more stored applications or data. Memory 502 may be, among other things, transient or persistent storage. The application program stored in memory 502 may include one or more modules (not shown), each of which may include a series of computer-executable instructions in a data recording device. Still further, the processor 501 may be configured to communicate with the memory 502 to execute a series of computer-executable instructions in the memory 502 on a data recording device. The data recording apparatus may also include one or more power supplies 503, one or more wired or wireless network interfaces 504, one or more input-output interfaces 505, one or more keyboards 506, and the like.
In a particular embodiment, a data recording apparatus includes a memory, and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the data recording apparatus, and configured for execution by one or more processors the one or more programs include computer-executable instructions for:
recording access data generated after an application event of an application page in an application access link is triggered;
writing the page identification of the application page into a data container of the application access link, and combining the page identification into corresponding access data;
under the condition that the access of the application access link is finished, performing data fusion on the link information in the data container and the page element data of the application page and the merged access data;
and storing the access data set obtained after fusion in a log file form.
Optionally, the recording access data generated after an application event of an application page in the application access link is triggered includes:
calling a monitoring interface to monitor an application event triggered by an access action submitted by the application page;
and calling a data recording interface to record the access data generated after the application event is executed, and storing the generated access data to a memory.
Optionally, the writing the page identifier of the application page into the data container of the application access link includes:
if a page jump event of jumping from the application page to a next application page is monitored, writing a page identifier of the application page into the data container;
the page identification comprises a hash character string obtained after the hash processing is carried out on the page element data of the application page.
Optionally, the merging the page identifier into corresponding access data includes:
and merging the hash character string of the application page with the access data of the application page stored in the memory.
Optionally, the writing the page identifier of the application page into the data container of the application access link, and merging the page identifier into the corresponding access data instruction before executing, further includes:
if a first access request of a user for the application access link is detected, establishing a session of the application access link as the data container;
and the data container records page identification, page URL and/or page element data of the accessed application page in the application access link.
Optionally, the performing data fusion on the link information in the data container and the page element data of the application page and the merged access data includes:
determining a mapping relation between the combined access data and the application page based on the page identification contained in the combined access data;
and merging the link information, the page element data and the merged access data based on the mapping relation to obtain the access data set.
Optionally, the storing the access data set obtained after the fusion in the form of a log file includes:
writing the access data set into a log file according to a preset format;
and storing the log file to a local database.
An embodiment of a storage medium provided in this specification is as follows:
in correspondence to the above-described data recording method, based on the same technical idea, one or more embodiments of the present specification further provide a storage medium.
The storage medium provided in this embodiment is used to store computer-executable instructions, and when executed, the computer-executable instructions implement the following processes:
recording access data generated after an application event of an application page in an application access link is triggered;
writing the page identification of the application page into a data container of the application access link, and combining the page identification into corresponding access data;
under the condition that the access of the application access link is finished, performing data fusion on the link information in the data container and the page element data of the application page and the merged access data;
and storing the access data set obtained after fusion in a log file form.
Optionally, the recording access data generated after an application event of an application page in the application access link is triggered includes:
calling a monitoring interface to monitor an application event triggered by an access action submitted by the application page;
and calling a data recording interface to record the access data generated after the application event is executed, and storing the generated access data to a memory.
Optionally, the writing the page identifier of the application page into the data container of the application access link includes:
if a page jump event of jumping from the application page to a next application page is monitored, writing a page identifier of the application page into the data container;
the page identification comprises a hash character string obtained after the hash processing is carried out on the page element data of the application page.
Optionally, the merging the page identifier into corresponding access data includes:
and merging the hash character string of the application page with the access data of the application page stored in the memory.
Optionally, the performing data fusion on the link information in the data container and the page element data of the application page and the merged access data includes:
determining a mapping relation between the combined access data and the application page based on the page identification contained in the combined access data;
and merging the link information, the page element data and the merged access data based on the mapping relation to obtain the access data set.
Optionally, the storing the access data set obtained after the fusion in the form of a log file includes:
writing the access data set into a log file according to a preset format;
and storing the log file to a local database.
It should be noted that the embodiment of the storage medium in this specification and the embodiment of the data recording method in this specification are based on the same inventive concept, and therefore, for specific implementation of this embodiment, reference may be made to implementation of the foregoing corresponding method, and repeated details are not described here.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
In the 30 s of the 20 th century, improvements in a technology could clearly be distinguished between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Hardware Description Language), traffic, pl (core universal Programming Language), HDCal (jhdware Description Language), lang, Lola, HDL, laspam, hardward Description Language (vhr Description Language), vhal (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.
The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functions of the units may be implemented in the same software and/or hardware or in multiple software and/or hardware when implementing the embodiments of the present description.
One skilled in the art will recognize that one or more embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, one or more embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The description has been presented with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the description. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
One or more embodiments of the present description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above description is only an example of this document and is not intended to limit this document. Various modifications and changes may occur to those skilled in the art from this document. Any modifications, equivalents, improvements, etc. which come within the spirit and principle of the disclosure are intended to be included within the scope of the claims of this document.
Claims (12)
1. A data recording method, comprising:
recording access data generated after an application event of an application page in an application access link is triggered;
writing the page identification of the application page into a data container of the application access link, and combining the page identification into corresponding access data;
under the condition that the access of the application access link is finished, performing data fusion on the link information in the data container and the page element data of the application page and the merged access data;
and storing the access data set obtained after fusion in a log file form.
2. The data recording method according to claim 1, wherein the recording of the access data generated after the application event of the application page in the application access link is triggered comprises:
calling a monitoring interface to monitor an application event triggered by an access action submitted by the application page;
and calling a data recording interface to record the access data generated after the application event is executed and storing the access data into a memory.
3. The data recording method of claim 1, wherein writing the page identification of the application page into a data container of the application access link comprises:
if a page jump event of jumping from the application page to a next application page is monitored, writing a page identifier of the application page into the data container;
the page identification comprises a hash character string obtained after the hash processing is carried out on the page element data of the application page.
4. The data recording method of claim 3, said merging the page identification to the corresponding access data, comprising:
and merging the hash character string of the application page with the access data of the application page stored in the memory.
5. The data recording method according to claim 1, wherein the application access link is composed of application pages accessed by a user, and the link information includes an identification chain composed of page identifications of the application pages determined in an access time order.
6. The data recording method according to claim 1, wherein before the steps of writing the page identifier of the application page into the data container of the application access link and merging the page identifier into the corresponding access data are executed, the method further comprises:
if a first access request of a user for the application access link is detected, establishing a session of the application access link as the data container;
and the data container records page identification, page URL and/or page element data of the accessed application page in the application access link.
7. The data recording method according to claim 1, wherein the data fusing the link information in the data container and the page element data of the application page with the merged access data includes:
determining a mapping relation between the merged access data and an application page based on a page identifier contained in the merged access data;
and merging the link information, the page element data and the merged access data based on the mapping relation to obtain the access data set.
8. The data recording method according to claim 1, wherein in a case where the access of the application access link is not ended, the following operation is performed:
if a page jump event for jumping from the application page to a next application page is monitored, recording access data generated after the application event of the next application page is triggered and storing the access data into a memory;
and writing the page identifier of the next application page into the data container, and combining the page identifier of the next application page into the access data of the next application page.
9. The data recording method according to claim 1, wherein storing the merged access data set in a log file comprises:
writing the access data set into the log file according to a preset format;
and storing the log file to a local database.
10. A data recording apparatus comprising:
the access data recording module is configured to record access data generated after an application event of an application page in an application access link is triggered;
the data merging module is configured to write the page identifier of the application page into a data container of the application access link and merge the page identifier into corresponding access data;
the data fusion module is configured to perform data fusion on the link information in the data container and the page element data of the application page and the merged access data under the condition that the access of the application access link is finished;
and the access data set storage module is configured to store the access data set obtained after fusion in a log file form.
11. A data recording apparatus comprising:
a processor; and the number of the first and second groups,
a memory configured to store computer-executable instructions that, when executed, cause the processor to:
recording access data generated after an application event of an application page in an application access link is triggered;
writing the page identification of the application page into a data container of the application access link, and combining the page identification into corresponding access data;
under the condition that the access of the application access link is finished, performing data fusion on the link information in the data container and the page element data of the application page and the merged access data;
and storing the access data set obtained after fusion in a log file form.
12. A storage medium storing computer-executable instructions that when executed implement the following:
recording access data generated after an application event of an application page in an application access link is triggered;
writing the page identification of the application page into a data container of the application access link, and combining the page identification into corresponding access data;
under the condition that the access of the application access link is finished, performing data fusion on the link information in the data container and the page element data of the application page and the merged access data;
and storing the access data set obtained after fusion in a log file form.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011351428.2A CN112181798B (en) | 2020-11-27 | 2020-11-27 | Data recording method and device |
| CN202110490783.6A CN113176988B (en) | 2020-11-27 | 2020-11-27 | Data recording method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011351428.2A CN112181798B (en) | 2020-11-27 | 2020-11-27 | Data recording method and device |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110490783.6A Division CN113176988B (en) | 2020-11-27 | 2020-11-27 | Data recording method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112181798A true CN112181798A (en) | 2021-01-05 |
| CN112181798B CN112181798B (en) | 2021-03-19 |
Family
ID=73918711
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110490783.6A Active CN113176988B (en) | 2020-11-27 | 2020-11-27 | Data recording method and device |
| CN202011351428.2A Active CN112181798B (en) | 2020-11-27 | 2020-11-27 | Data recording method and device |
Family Applications Before (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110490783.6A Active CN113176988B (en) | 2020-11-27 | 2020-11-27 | Data recording method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN113176988B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113176988B (en) * | 2020-11-27 | 2024-05-17 | 蚂蚁胜信(上海)信息技术有限公司 | Data recording method and device |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106446228A (en) * | 2016-10-08 | 2017-02-22 | 中国工商银行股份有限公司 | Collection analysis method and device for WEB page data |
| CN111324675A (en) * | 2020-02-11 | 2020-06-23 | 支付宝实验室(新加坡)有限公司 | Analysis display method and system of application access link and electronic equipment |
| CN111737630A (en) * | 2020-08-25 | 2020-10-02 | 智者四海（北京）技术有限公司 | Method for recording user access path |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110825943B (en) * | 2019-10-23 | 2023-10-10 | 支付宝(杭州)信息技术有限公司 | Method, system and equipment for generating user access path tree data |
| CN111523072B (en) * | 2020-04-20 | 2023-08-15 | 咪咕文化科技有限公司 | Page access data statistics method and device, electronic equipment and storage medium |
| CN113176988B (en) * | 2020-11-27 | 2024-05-17 | 蚂蚁胜信(上海)信息技术有限公司 | Data recording method and device |
-
2020
- 2020-11-27 CN CN202110490783.6A patent/CN113176988B/en active Active
- 2020-11-27 CN CN202011351428.2A patent/CN112181798B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106446228A (en) * | 2016-10-08 | 2017-02-22 | 中国工商银行股份有限公司 | Collection analysis method and device for WEB page data |
| CN111324675A (en) * | 2020-02-11 | 2020-06-23 | 支付宝实验室(新加坡)有限公司 | Analysis display method and system of application access link and electronic equipment |
| CN111737630A (en) * | 2020-08-25 | 2020-10-02 | 智者四海（北京）技术有限公司 | Method for recording user access path |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113176988A (en) | 2021-07-27 |
| CN113176988B (en) | 2024-05-17 |
| CN112181798B (en) | 2021-03-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108173706B (en) | Service marking method, device and equipment under multi-service system | |
| CN110781165B (en) | Method, device and equipment for processing service data | |
| CN107066519B (en) | Task detection method and device | |
| CN111400681B (en) | Data authority processing method, device and equipment | |
| CN110569428A (en) | recommendation model construction method, device and equipment | |
| CN111930810B (en) | Data rule mining method and device | |
| CN107479868B (en) | Interface loading method, device and equipment | |
| CN114547024A (en) | SQL statement risk detection method, device, equipment and medium | |
| CN111768303A (en) | Transaction processing method, device, equipment and system | |
| CN110602163B (en) | File uploading method and device | |
| CN112181798B (en) | Data recording method and device | |
| CN111782328A (en) | Application processing method and device | |
| CN114819958A (en) | Transaction processing method, device and equipment based on block chain | |
| CN111753328B (en) | Private data leakage risk detection method and system | |
| CN112258295A (en) | Recording processing method, device and equipment | |
| CN112256696A (en) | Form data processing method, device, equipment and storage medium | |
| CN109409037B (en) | Method, device and equipment for generating data confusion rule | |
| CN110992039A (en) | Transaction processing method, device and equipment | |
| CN113435950B (en) | Bill processing method and device | |
| CN112199399A (en) | Data processing method and device | |
| CN113254823A (en) | Webpage data processing method and device | |
| CN114594944A (en) | Application construction system and device | |
| CN108628615B (en) | Method, device and equipment for detecting abandoned codes | |
| CN111324778A (en) | Data and service processing method and device and electronic equipment | |
| CN110955653A (en) | Data page processing method, device, equipment and computer system |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |