WO2018202171A1 - 埋点验证***及方法 - Google Patents

埋点验证***及方法 Download PDF

Info

Publication number
WO2018202171A1
WO2018202171A1 PCT/CN2018/085722 CN2018085722W WO2018202171A1 WO 2018202171 A1 WO2018202171 A1 WO 2018202171A1 CN 2018085722 W CN2018085722 W CN 2018085722W WO 2018202171 A1 WO2018202171 A1 WO 2018202171A1
Authority
WO
WIPO (PCT)
Prior art keywords
buried point
data
buried
client
verification
Prior art date
Application number
PCT/CN2018/085722
Other languages
English (en)
French (fr)
Inventor
黄华
陈志平
唐洵
张冲
陈灯霞
Original Assignee
平安科技（深圳）有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2018202171A1 publication Critical patent/WO2018202171A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3668—Software testing
    • G06F11/3672—Test management
    • G06F11/3676—Test management for coverage analysis
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3668—Software testing
    • G06F11/3672—Test management
    • G06F11/3688—Test management for test execution, e.g. scheduling of test suites

Definitions

  • the present application relates to a data analysis system and method, and more particularly to a buried point verification system and method.
  • the present application provides a buried point verification system that runs on a server.
  • the system includes:
  • a data receiving module configured to receive, by the network, the buried point data and the buried point data summary information transmitted by the client in real time;
  • a data processing module for performing real-time analysis on buried point data to convert buried point data from unstructured data to structured data
  • the data verification module is configured to compare the structured buried point data with the buried point data summary information to determine whether the buried point data is lost.
  • the present application also provides a buried point verification method that runs on a server.
  • the method includes:
  • Data receiving step receiving, by the network, the buried point data and the buried point data summary information transmitted by the client in real time;
  • Data processing steps real-time analysis of buried point data, converting buried point data from unstructured data to structured data;
  • Data verification step Compare the structured buried point data with the buried point data summary information to determine whether the buried point data is lost.
  • the present application further provides a computer readable storage medium storing a buried point verification system, the buried point verification system being executable by at least one processor to implement the following steps:
  • the structured buried point data is compared with the buried point data summary information to determine whether the buried point data is lost.
  • the buried point verification system, the computer storage medium and the method provided by the application enable the server to analyze and process the buried point data in real time after receiving the buried point data and the buried point data summary information transmitted by the client. After converting the buried data from the unstructured data to the structured data, it is judged whether the client's application software has a buried data loss, and the buried point coverage of the client backhaul can also be calculated.
  • FIG. 1 is an application environment diagram of a preferred embodiment of a buried point verification system of the present application.
  • FIG. 2 is a diagram showing the operating environment of a preferred embodiment of the buried point verification system of the present application.
  • FIG. 3 is a functional block diagram of a preferred embodiment of the buried point verification system of the present application.
  • FIG. 4 is a flow chart of a preferred embodiment of a buried point verification method of the present application.
  • FIG. 1 it is an application environment diagram of a preferred embodiment of the buried point verification system 10 of the present application.
  • This buried point verification system 10 is applied to the server 1.
  • the server 1 connects a plurality of clients 3 through the network 2.
  • the network 2 can be a network of a local area network, a wide area network, a metropolitan area network, a personal area network, etc.; it can be a wired network or a wireless network.
  • the client 3 can be a desktop computer, a notebook, a tablet, a mobile phone, or other terminal device in which application software is installed and can communicate with the server 1 via the network 2.
  • Server 1 includes, but is not limited to, memory 11, processor 12, and display 13.
  • the memory 11 stores program code of the buried point verification system 10, which may include at least one type of storage medium including a flash memory, a hard disk, a multimedia card, a card type memory (eg, SD or DX memory, etc.) , random access memory (RAM), static random access memory (SRAM), read only memory (ROM), electrically erasable programmable read only memory (EEPROM), programmable read only memory (PROM), magnetic memory, disk, CD and so on.
  • RAM random access memory
  • SRAM static random access memory
  • ROM read only memory
  • EEPROM electrically erasable programmable read only memory
  • PROM programmable read only memory
  • magnetic memory disk, CD and so on.
  • the processor 12 reads and executes the program code of the buried point verification system 10 from the memory 11, and provides the following functions of the buried point verification system 10.
  • the display 13 displays the execution result of the buried point verification system 10.
  • FIG 2 shows only server 1 with components 11-13, it being understood that server 1 may include more or fewer components.
  • Each client 3 (only one shown in Figure 2) is equipped with one or more application software 30 (only one is shown in Figure 2).
  • This embodiment is described by taking an application software 30 as an example.
  • the publisher of the application software 30 sets a number of embedding points in the application software 30 for analyzing the operation behavior of the user of the client 3 to the application software 30 and/or testing the functional effects of the application software 30.
  • the client 3 records the buried point data triggered by the user and the buried point data summary information including the complete operation behavior of the user, and the buried point data and the buried point data are transmitted through the network 2.
  • the summary information is transmitted to the server 1.
  • the buried point verification system 10 of the server 1 processes and analyzes the received buried point data and the buried point data summary information, and determines whether or not the embedded software data is lost in the application software 30 of the client 3.
  • the buried point test system 10 can also compare the received buried point data with the buried point data in the complete buried point specification file of the application software 30 stored in the memory 11 of the server 1, and calculate the client 3 back. Buried coverage. Then, the buried point test system 10 can also generate a buried point verification report, and send the buried point coverage rate and the buried point check report to the preset client 3 through the network 2.
  • the client 3 may be a user of the application software 30 or a developer of the application software 30.
  • FIG. 3 it is a functional block diagram of a preferred embodiment of the buried point verification system 10 of the present application.
  • the buried point verification system 10 includes a data receiving module 110, a data processing module 120, and a data verification module 130.
  • the data receiving module 110 is configured to receive the buried point data and the buried point data summary information of the application software 30 transmitted by the client 3 in real time through the network 2.
  • the buried data summary information records the complete behavior of the user operating the application software 30. For example, when the user uses the application software 30, five operations are performed and 30 buried points are triggered, and the information is completely recorded in the buried point data summary information. in. Under the influence of the network 2, or the application software 30 of the client 3 has a missing code, the buried data returned by the client 3 may be missing or lost.
  • the data processing module 120 is configured to perform real-time analysis on the buried point data, and convert the buried point data from the unstructured data into the structured data.
  • the burying point verification system 10 uses a search engine, for example, the open source search engine Elasticsearch, to automatically and in real time obtain the burying point data transmitted back by the client 3, and ensure that the burying point data can be searched once it reaches the server 1. , to avoid the delay in time.
  • a search engine for example, the open source search engine Elasticsearch
  • the buried point data returned by client 3 is unstructured data.
  • the buried data may be a text file including a long string of characters:
  • the data processing module 120 uses the search engine Elasticsearch to convert the unstructured buried data into structured data, organized in a predefined model or in a predefined manner, and stored in a database.
  • Elasticsearch extracts buried point information from unstructured buried point data, such as the identification information of the buried point "process_id: 3", “action_id: 40001", the type of user operation and time corresponding to the buried point, and the write structure. Corresponding array of data.
  • the search engine Elasticsearch also writes other information in the unstructured buried data, such as the client IP address, MAC address, etc., the version of the client application software, etc., to the corresponding array of structured data.
  • the data verification module 130 is configured to compare the structured buried point data with the buried point data summary information to determine whether the application software 30 has lost buried data. For example, the buried point data summary information records that the user has triggered 30 buried points when using the application software 30, and only 26 out of the 30 buried points in the structured buried point data, then there are 4 The buried point data is lost.
  • the buried point verification system 10 includes a data receiving module 110, a data processing module 120, a data verification module 130, and a computing module 140.
  • the data receiving module 110 is configured to receive the buried point data and the buried point data summary information of the application software 30 transmitted by the client 3 in real time through the network 2.
  • the buried data summary information records the complete behavior of the user operating the application software 30. For example, when the user uses the application software 30, five operations are performed and 30 buried points are triggered, and the information is completely recorded in the buried point data summary information. in. Under the influence of the network 2, or the application software 30 of the client 3 has a missing code, the buried data returned by the client 3 may be missing or lost.
  • the data processing module 120 is configured to perform real-time analysis on the buried point data, and convert the buried point data from the unstructured data into the structured data.
  • the burying point verification system 10 uses a search engine, for example, the open source search engine Elasticsearch, to automatically and in real time obtain the burying point data transmitted back by the client 3, and ensure that the burying point data can be searched once it reaches the server 1. , to avoid the delay in time.
  • a search engine for example, the open source search engine Elasticsearch
  • the buried data returned by client 3 is unstructured data.
  • the buried data may be a text file that includes a long string of characters (see the example above).
  • the data processing module 120 uses the search engine Elasticsearch to convert the unstructured buried data into structured data, organized in a predefined model or in a predefined manner, and stored in a database.
  • Elasticsearch extracts buried point information from unstructured buried point data, such as the identification information of the buried point "process_id: 3", "action_id: 40001", the type of user operation and time corresponding to the buried point, and the write structure. Corresponding array of data.
  • the search engine Elasticsearch also writes other information in the unstructured buried data, such as the client IP address, MAC address, etc., the version of the client application software, etc., to the corresponding array of structured data.
  • the data verification module 130 is configured to compare the structured buried point data with the buried point data summary information to determine whether the application software 30 has lost buried data. For example, the buried point data summary information records that the user has triggered 30 buried points when using the application software 30, and only 26 out of the 30 buried points in the structured buried point data, then there are 4 The buried point data is lost.
  • the buried point verification system 10 includes a data receiving module 110, a data processing module 120, a data verification module 130, a calculation module 140, and a report generation module 150.
  • the data receiving module 110 is configured to receive the buried point data and the buried point data summary information of the application software 30 transmitted by the client 3 in real time through the network 2.
  • the buried data summary information records the complete behavior of the user operating the application software 30. For example, when the user uses the application software 30, five operations are performed and 30 buried points are triggered, and the information is completely recorded in the buried point data summary information. in. Under the influence of the network 2, or the application software 30 of the client 3 has a missing code, the buried data returned by the client 3 may be missing or lost.
  • the data processing module 120 is configured to perform real-time analysis on the buried point data, and convert the buried point data from the unstructured data into the structured data.
  • the burying point verification system 10 uses a search engine, for example, the open source search engine Elasticsearch, to automatically and in real time obtain the burying point data transmitted back by the client 3, and ensure that the burying point data can be searched once it reaches the server 1. , to avoid the delay in time.
  • a search engine for example, the open source search engine Elasticsearch
  • the buried data returned by client 3 is unstructured data.
  • the buried data may be a text file that includes a long string of characters (see the example above).
  • the data processing module 120 uses the search engine Elasticsearch to convert the unstructured buried data into structured data, organized in a predefined model or in a predefined manner, and stored in a database.
  • Elasticsearch extracts buried point information from unstructured buried point data, such as the identification information of the buried point "process_id: 3", "action_id: 40001", the type of user operation and time corresponding to the buried point, and the write structure. Corresponding array of data.
  • the search engine Elasticsearch also writes other information in the unstructured buried data, such as the client IP address, MAC address, etc., the version of the client application software, etc., to the corresponding array of structured data.
  • the data verification module 130 is configured to compare the structured buried point data with the buried point data summary information to determine whether the application software 30 has lost buried data. For example, the buried point data summary information records that the user has triggered 30 buried points when using the application software 30, and only 26 out of the 30 buried points in the structured buried point data, then there are 4 The buried point data is lost.
  • the report generation module 150 is configured to generate a buried point verification report.
  • the burying point verification report includes, but is not limited to, related information of the application software 30 corresponding to the burying check, such as application software name, version, and the like, time of verification occurrence, and related information of the server 1, and verification result Data and other information.
  • the report generation module 150 stores the buried point verification report in the memory 11 of the server 1.
  • the buried point verification system 10 includes a data receiving module 110, a data processing module 120, a data verification module 130, a calculation module 140, and a report generation module 150, and a reminder module 160.
  • the functions of the data receiving module 110, the data processing module 120, the data verification module 130, the calculation module 140, and the report generation module 150 are described in the above embodiments.
  • the reminder module 160 is configured to send the buried point coverage and/or the buried point verification report to the preset client 3.
  • the reminding module 160 may send the buried point coverage and the buried point verification report calculated by each of the buried point verifications to the preset client 3, such as a work computer of the buried point engineer.
  • the buried point verification report and the preset format reminder information are sent, for example, “the software identifier is ***, the version number.
  • the buried point coverage rate is ###, the burying point data missing rate is too large, please check and adjust the burying point scheme", to the default buried point engineer's working computer.
  • FIG. 4 a flow chart of a preferred embodiment of the buried point verification method of the present application.
  • the buried point verification system method may include only steps S110, S120, and S130.
  • step S110 the data receiving module 110 receives the buried point data and the buried point data summary information of the application software 30 transmitted by the client 3 in real time through the network 2.
  • the buried data summary information records the complete behavior of the user operating the application software 30. For example, when the user uses the application software 30, five operations are performed and 30 buried points are triggered, and the information is completely recorded in the buried point data summary information. in. Under the influence of the network 2, or the application software 30 of the client 3 has a missing code, the buried data returned by the client 3 may be missing or lost.
  • step S120 the data processing module 120 performs real-time analysis on the buried point data to convert the buried point data from the unstructured data into the structured data.
  • the burying point verification system 10 uses a search engine, for example, an open source search engine, Elasticsearch, to automatically and in real time obtain the burying point data transmitted back by the client 3, and ensure that the burying point data is searched as soon as it reaches the server 1. , to avoid the delay in time.
  • a search engine for example, an open source search engine, Elasticsearch
  • the buried point data returned by client 3 is unstructured data.
  • the buried data may be a text file including a long string of characters:
  • the data processing module 120 uses the search engine Elasticsearch to convert the unstructured buried data into structured data, organized in a predefined model or in a predefined manner, and stored in a database.
  • Elasticsearch extracts buried point information from unstructured buried point data, such as the identification information of the buried point "process_id: 3", “action_id: 40001", the type of user operation and time corresponding to the buried point, and the write structure. Corresponding array of data.
  • the search engine Elasticsearch also writes other information in the unstructured buried data, such as the client IP address, MAC address, etc., the version of the client application software, etc., to the corresponding array of structured data.
  • step S130 the data verification module 130 compares the structured buried point data with the buried point data summary information to determine whether the application software 30 has lost buried data.
  • the buried point data summary information records that the user has triggered 30 buried points when using the application software 30, and only 26 out of the 30 buried points in the structured buried point data, then there are 4 The buried point data is lost.
  • the buried point verification method includes steps S110, S120, S130, and S140.
  • step S110 the data receiving module 110 receives the buried point data and the buried point data summary information of the application software 30 transmitted by the client 3 in real time through the network 2.
  • the buried data summary information records the complete behavior of the user operating the application software 30. For example, when the user uses the application software 30, five operations are performed and 30 buried points are triggered, and the information is completely recorded in the buried point data summary information. in. Under the influence of the network 2, or the application software 30 of the client 3 has a missing code, the buried data returned by the client 3 may be missing or lost.
  • step S120 the data processing module 120 performs real-time analysis on the buried point data to convert the buried point data from the unstructured data into the structured data.
  • the burying point verification system 10 uses a search engine, for example, an open source search engine, Elasticsearch, to automatically and in real time obtain the burying point data transmitted back by the client 3, and ensure that the burying point data is searched as soon as it reaches the server 1. , to avoid the delay in time.
  • a search engine for example, an open source search engine, Elasticsearch
  • the buried data returned by client 3 is unstructured data.
  • the buried data may be a text file that includes a long string of characters (see the example above).
  • the data processing module 120 uses the search engine Elasticsearch to convert the unstructured buried data into structured data, organized in a predefined model or in a predefined manner, and stored in a database.
  • Elasticsearch extracts buried point information from unstructured buried point data, such as the identification information of the buried point "process_id: 3", "action_id: 40001", the type of user operation and time corresponding to the buried point, and the write structure. Corresponding array of data.
  • the search engine Elasticsearch also writes other information in the unstructured buried data, such as the client's IP address, MAC address, etc., the version of the client application, and so on, to the corresponding array of structured data.
  • step S130 the data verification module 130 compares the structured buried point data with the buried point data summary information to determine whether the application software 30 has lost buried data.
  • the buried point data summary information records that the user has triggered 30 buried points when using the application software 30, and only 26 out of the 30 buried points in the structured buried point data, then there are 4 The buried point data is lost.
  • the buried point verification method includes steps S110, S120, S130, S140, and S150.
  • step S110 the data receiving module 110 receives the buried point data and the buried point data summary information of the application software 30 transmitted by the client 3 in real time through the network 2.
  • the buried data summary information records the complete behavior of the user operating the application software 30. For example, when the user uses the application software 30, five operations are performed and 30 buried points are triggered, and the information is completely recorded in the buried point data summary information. in. Under the influence of the network 2, or the application software 30 of the client 3 has a missing code, the buried data returned by the client 3 may be missing or lost.
  • step S120 the data processing module 120 performs real-time analysis on the buried point data to convert the buried point data from the unstructured data into the structured data.
  • the burying point verification system 10 uses a search engine, for example, an open source search engine, Elasticsearch, to automatically and in real time obtain the burying point data transmitted back by the client 3, and ensure that the burying point data is searched as soon as it reaches the server 1. , to avoid the delay in time.
  • a search engine for example, an open source search engine, Elasticsearch
  • the buried data returned by client 3 is unstructured data.
  • the buried data may be a text file that includes a long string of characters (see the example above).
  • the data processing module 120 uses the search engine Elasticsearch to convert the unstructured buried data into structured data, organized in a predefined model or in a predefined manner, and stored in a database.
  • Elasticsearch extracts buried point information from unstructured buried point data, such as the identification information of the buried point "process_id: 3", "action_id: 40001", the type of user operation and time corresponding to the buried point, and the write structure. Corresponding array of data.
  • the search engine Elasticsearch also writes other information in the unstructured buried data, such as the client IP address, MAC address, etc., the version of the client application software, etc., to the corresponding array of structured data.
  • step S130 the data verification module 130 compares the structured buried point data with the buried point data summary information, and determines whether the application software 30 has lost buried data.
  • the buried point data summary information records that the user has triggered 30 buried points when using the application software 30, and only 26 out of the 30 buried points in the structured buried point data, then there are 4 The buried point data is lost.
  • Step S150 The report generation module 150 generates a buried point verification report.
  • the burying point verification report includes, but is not limited to, related information of the application software 30 corresponding to the burying check, such as application software name, version, and the like, time of verification occurrence, and related information of the server 1, and verification result Data and other information.
  • the report generation module 150 stores the buried point verification report in the memory 11 of the server 1.
  • the buried point verification system method may further include step S160 in addition to steps S110, S120, S130, S140, and S150.
  • step S160 the reminding module 16 sends the buried point coverage and/or the buried point verification report to the preset client 3.
  • the reminding module 160 may send the buried point coverage and the buried point verification report calculated by each of the buried point verifications to the preset client 3, such as a work computer of the buried point engineer.
  • the preset client 3 such as a work computer of the buried point engineer.
  • the buried point verification report and the preset format reminder information are sent, for example, “the software identifier is ***, the version number. For the *** software, the buried point coverage rate is ###, the burying point data missing rate is too large, please check and adjust the burying point scheme", to the default buried point engineer's working computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

本申请提供了一种埋点验证***，该***应用于服务器。该***包括一系列功能模块。通过这些功能模块，服务器通过网络接收客户端实时传送的埋点数据及埋点数据概要信息，对埋点数据进行实时分析，将埋点数据从非结构化数据转换为结构化数据，将结构化的埋点数据与埋点数据概要信息进行对比，判断客户端的应用软件是否发生埋点数据丢失的情况，还可以计算客户端回传的埋点覆盖率。

Description

埋点验证***及方法
本申请要求于2017年5月5日提交中国专利局，申请号为2017103128091、发明名称为“埋点验证***及方法”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及一种数据分析***及方法，尤其涉及一种埋点验证***及方法。
背景技术
随着移动互联网的快速发展，移动客户端的各种应用软件层出不穷。为了研究用户行为和应用软件的功能效果，通常会在应用软件中设置许多埋点。用户使用应用软件触发埋点对应的功能时，客户端会将埋点相关的数据传回服务器端。由于网络环境影响或终端应用软件可能存在代码缺失的情况，服务器端收到的埋点数据可能不准确，故需要对埋点数据进行校验。目前埋点校验采用的是人工校验方式。由于埋点数据众多，人工校验效率低，且很容易出错。
发明内容
鉴于以上内容，有必要提供一种埋点验证***及方法，可以对客户端回传的埋点数据进行实时、自动获取及分析，提高埋点数据验证的效率及准确性。
首先，为实现上述目的，本申请提供一种埋点验证***，运行于服务器。该***包括：
数据接收模块，用于通过网络接收客户端实时传送的埋点数据及埋点数据概要信息；
数据处理模块，用于对埋点数据进行实时分析，将埋点数据从非结构化数据转换为结构化数据；及
数据校验模块，用于将结构化的埋点数据与埋点数据概要信息进行对比，判断埋点数据是否丢失。
此外，本申请还提供一种埋点验证方法，运行于服务器。该方法包括：
数据接收步骤：通过网络接收客户端实时传送的埋点数据及埋点数据概要 信息；
数据处理步骤：对埋点数据进行实时分析，将埋点数据从非结构化数据转换为结构化数据；及
数据校验步骤：将结构化的埋点数据与埋点数据概要信息进行对比，判断埋点数据是否丢失。
此外，本申请还提供一种计算机可读存储介质，所述计算机可读存储介质存储有埋点验证***，所述埋点验证***可被至少一处理器执行，以实现如下步骤：
通过网络接收客户端实时传送的埋点数据及埋点数据概要信息；
对埋点数据进行实时分析，将埋点数据从非结构化数据转换为结构化数据；及
将结构化的埋点数据与埋点数据概要信息进行对比，判断埋点数据是否丢失。
相较现有技术，本申请提供的埋点验证***、计算机存储介质及方法可以使服务器在接收客户端传送的埋点数据及埋点数据概要信息后，实时对埋点数据进行分析、处理，将埋点数据从非结构化数据转换为结构化数据后，判断客户端的应用软件是否发生埋点数据丢失的情况，还可以计算客户端回传的埋点覆盖率。
附图说明
图1为本申请埋点验证***较佳实施例的应用环境图。
图2为本申请埋点验证***较佳实施例的运行环境图。
图3为本申请埋点验证***较佳实施例的功能模块图。
图4为本申请埋点验证方法较佳实施例的流程图。
具体实施方式
如图1所示，是本申请埋点验证***10较佳实施例的应用环境图。该埋点验证***10应用于服务器1。服务器1通过网络2连接多个客户端3。网络2可以为局域网，广域网，城域网，个人局域网等等类型的网络；可以为有线网络，也可以为无线网络。客户端3可以为桌上型计算机、笔记本、平板电脑、手机，或其它安装有应用软件，可以通过网络2与服务器1进行通信的终端装 置。
如图2所示，是本申请埋点验证***10较佳实施例的运行环境图。服务器1包括，但不仅限于，存储器11、处理器12及显示器13。
存储器11存储埋点验证***10的程序代码，该存储器11可以包括至少一种类型的存储介质，所述存储介质包括闪存、硬盘、多媒体卡、卡型存储器(例如，SD或DX存储器等等)、随机访问存储器(RAM)、静态随机访问存储器(SRAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、可编程只读存储器(PROM)、磁性存储器、磁盘、光盘等等。
处理器12从存储器11读取并执行埋点验证***10的程序代码，提供埋点验证***10的下述功能。显示器13显示埋点验证***10的执行结果。
图2仅示出了具有组件11-13的服务器1，应当理解的是，服务器1可以包括更多或者更少的组件。每个客户端3(图2仅示出一个)安装有一个或多个应用软件30(图2仅示出一个)。本实施例以一个应用软件30为例说明。该应用软件30的发布方在该应用软件30中设置了许多埋点，用于分析客户端3的用户对该应用软件30的操作行为及/或测试该应用软件30的功能效果。当用户使用该应用软件30时，埋点被触发，客户端3记录被用户触发的埋点数据及包含用户完整操作行为的埋点数据概要信息，并通过网络2将埋点数据及埋点数据概要信息传送至服务器1。服务器1的埋点验证***10对接收到的埋点数据及埋点数据概要信息进行处理、分析，判断客户端3的应用软件30是否发生埋点数据丢失的情况。
进一步地，埋点测试***10还可以将接收到的埋点数据与服务器1的存储器11中存储的有关应用软件30的完整埋点规范文件中的埋点数据进行比对，计算客户端3回传的埋点覆盖率。之后，埋点测试***10还可以生成埋点校验报告，并通过网络2将埋点覆盖率及埋点校验报告发送至预设的客户端3。在本实施例中，客户端3可以是应用软件30的用户，也可以是应用软件30的开发方。
如图3所示，是本申请埋点验证***10较佳实施例的功能模块图。
在一个实施例中，该埋点验证***10包括数据接收模块110、数据处理模块120及数据校验模块130。
数据接收模块110，用于通过网络2接收客户端3实时传送的应用软件30的埋点数据及埋点数据概要信息。埋点数据概要信息记录了用户操作应用软件 30的完整行为，例如用户在使用该应用软件30时执行了5项操作、触发了30个埋点，这些信息都会完整地记录在埋点数据概要信息中。受网络2的影响，或者是客户端3的应用软件30存在代码缺失的情况，客户端3传回的埋点数据可能发生缺失或丢失的情况。
数据处理模块120，用于对埋点数据进行实时分析，将埋点数据从非结构化数据转换为结构化数据。在本实施例中，埋点验证***10利用搜索引擎，例如，开源搜索引擎Elasticsearch，自动、实时获取客户端3回传的埋点数据，确保埋点数据一经到达服务器1，即可被搜索到，避免了时间上的延迟。
客户端3回传的埋点数据为非结构化数据，例如，埋点数据可能是一个包括一长串字符的文本文件：
2017-02-2320:57:21
423|3010026410614|248c382809043ba84a8312ac1ce302085|865199028189698|460013950475581||5.0.0|Android4.4.4|Android|HMNOTE1LTE|61.158.152.208|scmiui.com|00:00:00:00:00:00|20009|3(action_id和process_id，两个组成了这个埋点的唯一标识)|{"ssid":"CMCC-EDU","bssid":"00:26:7a:2b:43:bb","appid":"10013","signal":-60,"openid":"4100026420614","msg":0}|PA1000_WIFI
进一步地，数据处理模块120利用搜索引擎Elasticsearch将非结构化的埋点数据转化为结构化数据，以一个预定义的模型或预先定义好的方式进行组织，存储于数据库。例如，Elasticsearch从非结构化的埋点数据中提取埋点信息，例如埋点的标识信息"process_id：3"、"action_id：40001"，埋点对应的用户操作类型及时间等信息，写入结构化数据的相应数组。搜索引擎Elasticsearch将非结构化的埋点数据中的其他信息，例如客户端IP地址、MAC地址等，客户端应用软件的版本等信息，也写入结构化数据的相应数组。
以下为数据处理模块120处理后的结构化的数据示例：
Figure PCTCN2018085722-appb-000001
Figure PCTCN2018085722-appb-000002
数据校验模块130，用于将结构化的埋点数据与埋点数据概要信息进行对比，判断应用软件30是否发生埋点数据丢失的情况。例如，埋点数据概要信息中记录了用户在使用应用软件30时触发了30个埋点，而结构化的埋点数据中只有该30个埋点中的26个埋点信息，那么就有4个埋点数据丢失了。
在另一个实施例中，该埋点验证***10包括数据接收模块110、数据处理模块120、数据校验模块130及计算模块140。
数据接收模块110，用于通过网络2接收客户端3实时传送的应用软件30的埋点数据及埋点数据概要信息。埋点数据概要信息记录了用户操作应用软件30的完整行为，例如用户在使用该应用软件30时执行了5项操作、触发了30个埋点，这些信息都会完整地记录在埋点数据概要信息中。受网络2的影响，或者是客户端3的应用软件30存在代码缺失的情况，客户端3传回的埋点数据可能发生缺失或丢失的情况。
数据处理模块120，用于对埋点数据进行实时分析，将埋点数据从非结构化数据转换为结构化数据。在本实施例中，埋点验证***10利用搜索引擎，例如，开源搜索引擎Elasticsearch，自动、实时获取客户端3回传的埋点数据，确保埋点数据一经到达服务器1，即可被搜索到，避免了时间上的延迟。
客户端3回传的埋点数据为非结构化数据。例如，埋点数据可能是一个包括一长串字符的文本文件(请参上文中的例子)。数据处理模块120利用搜索引擎Elasticsearch将非结构化的埋点数据转化为结构化数据，以一个预定义的模型 或预先定义好的方式进行组织，存储于数据库。例如，Elasticsearch从非结构化的埋点数据中提取埋点信息，例如埋点的标识信息"process_id：3"、"action_id：40001"，埋点对应的用户操作类型及时间等信息，写入结构化数据的相应数组。搜索引擎Elasticsearch将非结构化的埋点数据中的其他信息，例如客户端IP地址、MAC地址等，客户端应用软件的版本等信息，也写入结构化数据的相应数组。
数据校验模块130，用于将结构化的埋点数据与埋点数据概要信息进行对比，判断应用软件30是否发生埋点数据丢失的情况。例如，埋点数据概要信息中记录了用户在使用应用软件30时触发了30个埋点，而结构化的埋点数据中只有该30个埋点中的26个埋点信息，那么就有4个埋点数据丢失了。
计算模块140，用于将结构化的埋点数据与服务器端1的存储器11中存储的完整埋点规范文件进行比对，计算客户端3回传的埋点覆盖率，例如，26/30＝86.7％。
在另一个实施例中，该埋点验证***10包括数据接收模块110、数据处理模块120、数据校验模块130、计算模块140及报告生成模块150。
数据接收模块110，用于通过网络2接收客户端3实时传送的应用软件30的埋点数据及埋点数据概要信息。埋点数据概要信息记录了用户操作应用软件30的完整行为，例如用户在使用该应用软件30时执行了5项操作、触发了30个埋点，这些信息都会完整地记录在埋点数据概要信息中。受网络2的影响，或者是客户端3的应用软件30存在代码缺失的情况，客户端3传回的埋点数据可能发生缺失或丢失的情况。
数据处理模块120，用于对埋点数据进行实时分析，将埋点数据从非结构化数据转换为结构化数据。在本实施例中，埋点验证***10利用搜索引擎，例如，开源搜索引擎Elasticsearch，自动、实时获取客户端3回传的埋点数据，确保埋点数据一经到达服务器1，即可被搜索到，避免了时间上的延迟。
客户端3回传的埋点数据为非结构化数据。例如，埋点数据可能是一个包括一长串字符的文本文件(请参上文中的例子)。数据处理模块120利用搜索引擎Elasticsearch将非结构化的埋点数据转化为结构化数据，以一个预定义的模型或预先定义好的方式进行组织，存储于数据库。例如，Elasticsearch从非结构化的埋点数据中提取埋点信息，例如埋点的标识信息"process_id：3"、"action_id：40001"，埋点对应的用户操作类型及时间等信息，写入结构 化数据的相应数组。搜索引擎Elasticsearch将非结构化的埋点数据中的其他信息，例如客户端IP地址、MAC地址等，客户端应用软件的版本等信息，也写入结构化数据的相应数组。
数据校验模块130，用于将结构化的埋点数据与埋点数据概要信息进行对比，判断应用软件30是否发生埋点数据丢失的情况。例如，埋点数据概要信息中记录了用户在使用应用软件30时触发了30个埋点，而结构化的埋点数据中只有该30个埋点中的26个埋点信息，那么就有4个埋点数据丢失了。
计算模块140，用于将结构化的埋点数据与服务器端1的存储器11中存储的完整埋点规范文件进行比对，计算客户端3回传的埋点覆盖率，例如，26/30＝86.7％。
报告生成模块150用于生成埋点校验报告。所述埋点校验报告包括，但不限于，埋点校验对应的应用软件30的相关信息，例如应用软件名称、版本等信息，校验发生的时间及服务器1的相关信息，校验结果数据等信息。报告生成模块150将该埋点校验报告存储于服务器1的存储器11。
在另一个实施例中，该埋点验证***10除了包括数据接收模块110、数据处理模块120、数据校验模块130、计算模块140及报告生成模块150，还包括提醒模块160。数据接收模块110、数据处理模块120、数据校验模块130、计算模块140及报告生成模块150的功能请参上文中的实施例所述。提醒模块160，则用于将埋点覆盖率及/或埋点校验报告发送至预设的客户端3。
所述提醒模块160可以是将每次埋点验证计算得到的埋点覆盖率及埋点校验报告发送至预设的客户端3，例如埋点工程师的工作电脑。
也可以是，当计算得到的埋点覆盖率低于预设阀值(例如85％)时，发送埋点校验报告及预设格式的提醒信息，例如“软件标识为***、版本号为***的软件的埋点覆盖率为###，埋点数据缺失率过大，请检查并调整埋点方案”，至预设的埋点工程师的工作电脑。
如图4所示，本申请埋点验证方法较佳实施例的流程图。
在一个实施例中，该埋点验证***方法可以只包括步骤S110、S120及S130。
步骤S110，数据接收模块110通过网络2接收客户端3实时传送的应用软件30的埋点数据及埋点数据概要信息。埋点数据概要信息记录了用户操作应用软件30的完整行为，例如用户在使用该应用软件30时执行了5项操作、触发了30个埋点，这些信息都会完整地记录在埋点数据概要信息中。受网络2的影 响，或者是客户端3的应用软件30存在代码缺失的情况，客户端3传回的埋点数据可能发生缺失或丢失的情况。
步骤S120，数据处理模块120对埋点数据进行实时分析，将埋点数据从非结构化数据转换为结构化数据。在本实施例中，埋点验证***10利用搜索引擎，例如，开源搜索引擎Elasticsearch，自动、实时获取客户端3回传的埋点数据，确保埋点数据一到达服务器1，即可被搜索到，避免了时间上的延迟。
客户端3回传的埋点数据为非结构化数据，例如，埋点数据可能是一个包括一长串字符的文本文件：
2017-02-2320:57:21
423|3010026410614|248c382809043ba84a8312ac1ce302085|865199028189698|460013950475581||5.0.0|Android4.4.4|Android|HMNOTE1LTE|61.158.152.208|scmiui.com|00:00:00:00:00:00|20009|3(action_id和process_id，两个组成了这个埋点的唯一标识)|{"ssid":"CMCC-EDU","bssid":"00:26:7a:2b:43:bb","appid":"10013","signal":-60,"openid":"4100026420614","msg":0}|PA1000_WIFI
数据处理模块120利用搜索引擎Elasticsearch将非结构化的埋点数据转化为结构化数据，以一个预定义的模型或预先定义好的方式进行组织，存储于数据库。例如，Elasticsearch从非结构化的埋点数据中提取埋点信息，例如埋点的标识信息"process_id：3"、"action_id：40001"，埋点对应的用户操作类型及时间等信息，写入结构化数据的相应数组。搜索引擎Elasticsearch将非结构化的埋点数据中的其他信息，例如客户端IP地址、MAC地址等，客户端应用软件的版本等信息，也写入结构化数据的相应数组。
以下为步骤S120中数据处理模块120处理后的结构化的数据示例：
Figure PCTCN2018085722-appb-000003
Figure PCTCN2018085722-appb-000004
步骤S130，数据校验模块130将结构化的埋点数据与埋点数据概要信息进行对比，判断应用软件30是否发生埋点数据丢失的情况。例如，埋点数据概要信息中记录了用户在使用应用软件30时触发了30个埋点，而结构化的埋点数据中只有该30个埋点中的26个埋点信息，那么就有4个埋点数据丢失了。
在另一个实施例中，该埋点验证方法包括步骤S110、S120、S130及S140。
步骤S110，数据接收模块110通过网络2接收客户端3实时传送的应用软件30的埋点数据及埋点数据概要信息。埋点数据概要信息记录了用户操作应用软件30的完整行为，例如用户在使用该应用软件30时执行了5项操作、触发了30个埋点，这些信息都会完整地记录在埋点数据概要信息中。受网络2的影响，或者是客户端3的应用软件30存在代码缺失的情况，客户端3传回的埋点数据可能发生缺失或丢失的情况。
步骤S120，数据处理模块120对埋点数据进行实时分析，将埋点数据从非结构化数据转换为结构化数据。在本实施例中，埋点验证***10利用搜索引擎，例如，开源搜索引擎Elasticsearch，自动、实时获取客户端3回传的埋点数据，确保埋点数据一到达服务器1，即可被搜索到，避免了时间上的延迟。
客户端3回传的埋点数据为非结构化数据。例如，埋点数据可能是一个包括一长串字符的文本文件(请参上文中的例子)。数据处理模块120利用搜索引擎Elasticsearch将非结构化的埋点数据转化为结构化数据，以一个预定义的模型或预先定义好的方式进行组织，存储于数据库。例如，Elasticsearch从非结构化的埋点数据中提取埋点信息，例如埋点的标识信息"process_id：3"、"action_id：40001"，埋点对应的用户操作类型及时间等信息，写入结构化数据的相应数组。搜索引擎Elasticsearch将非结构化的埋点数据中的其他信 息，例如客户端IP地址、MAC地址等，客户端应用软件的版本等信息，也写入结构化数据的相应数组。
步骤S130，数据校验模块130将结构化的埋点数据与埋点数据概要信息进行对比，判断应用软件30是否发生埋点数据丢失的情况。例如，埋点数据概要信息中记录了用户在使用应用软件30时触发了30个埋点，而结构化的埋点数据中只有该30个埋点中的26个埋点信息，那么就有4个埋点数据丢失了。
步骤S140：计算模块140将结构化的埋点数据与服务器端1的存储器11中存储的完整埋点规范文件进行比对，计算客户端3回传的埋点覆盖率，例如，26/30＝86.7％。
在另一个实施例中，该埋点验证方法包括步骤S110、S120、S130、S140及S150。
步骤S110，数据接收模块110通过网络2接收客户端3实时传送的应用软件30的埋点数据及埋点数据概要信息。埋点数据概要信息记录了用户操作应用软件30的完整行为，例如用户在使用该应用软件30时执行了5项操作、触发了30个埋点，这些信息都会完整地记录在埋点数据概要信息中。受网络2的影响，或者是客户端3的应用软件30存在代码缺失的情况，客户端3传回的埋点数据可能发生缺失或丢失的情况。
步骤S120，数据处理模块120对埋点数据进行实时分析，将埋点数据从非结构化数据转换为结构化数据。在本实施例中，埋点验证***10利用搜索引擎，例如，开源搜索引擎Elasticsearch，自动、实时获取客户端3回传的埋点数据，确保埋点数据一到达服务器1，即可被搜索到，避免了时间上的延迟。
客户端3回传的埋点数据为非结构化数据。例如，埋点数据可能是一个包括一长串字符的文本文件(请参上文中的例子)。数据处理模块120利用搜索引擎Elasticsearch将非结构化的埋点数据转化为结构化数据，以一个预定义的模型或预先定义好的方式进行组织，存储于数据库。例如，Elasticsearch从非结构化的埋点数据中提取埋点信息，例如埋点的标识信息"process_id：3"、"action_id：40001"，埋点对应的用户操作类型及时间等信息，写入结构化数据的相应数组。搜索引擎Elasticsearch将非结构化的埋点数据中的其他信息，例如客户端IP地址、MAC地址等，客户端应用软件的版本等信息，也写入结构化数据的相应数组。
步骤S130，数据校验模块130将结构化的埋点数据与埋点数据概要信息进 行对比，判断应用软件30是否发生埋点数据丢失的情况。例如，埋点数据概要信息中记录了用户在使用应用软件30时触发了30个埋点，而结构化的埋点数据中只有该30个埋点中的26个埋点信息，那么就有4个埋点数据丢失了。
步骤S140：计算模块140将结构化的埋点数据与服务器端1的存储器11中存储的完整埋点规范文件进行比对，计算客户端3回传的埋点覆盖率，例如，26/30＝86.7％。
步骤S150：报告生成模块150生成埋点校验报告。所述埋点校验报告包括，但不限于，埋点校验对应的应用软件30的相关信息，例如应用软件名称、版本等信息，校验发生的时间及服务器1的相关信息，校验结果数据等信息。报告生成模块150将该埋点校验报告存储于服务器1的存储器11。
在另一个实施例中，该埋点验证***方法除了包括步骤S110、S120、S130、S140及S150，还可以包括步骤S160。步骤S110、S120、S130、S140及S150执行的操作请参上文中的实施例所述。在步骤S160，提醒模块16将埋点覆盖率及/或埋点校验报告发送至预设的客户端3。
所述提醒模块160可以是将每次埋点验证计算得到的埋点覆盖率及埋点校验报告发送至预设的客户端3，例如埋点工程师的工作电脑。也可以是，当计算得到的埋点覆盖率低于预设阀值(例如85％)时，发送埋点校验报告及预设格式的提醒信息，例如“软件标识为***、版本号为***的软件的埋点覆盖率为###，埋点数据缺失率过大，请检查并调整埋点方案”，至预设的埋点工程师的工作电脑。
最后所应说明的是，以上实施例仅用以说明本申请的技术方案而非限制，尽管参照较佳实施例对本申请进行了详细说明，本领域的普通技术人员应当理解，可以对本申请的技术方案进行修改或等同替换，而不脱离本申请技术方案的精神和范围。

Claims (20)

  1. 一种埋点验证***，运行于服务器，其特征在于，该***包括：
    数据接收模块，用于通过网络接收客户端实时传送的埋点数据及埋点数据概要信息；
    数据处理模块，用于对埋点数据进行实时分析，将埋点数据从非结构化数据转换为结构化数据；及
    数据校验模块，用于将结构化的埋点数据与埋点数据概要信息进行对比，判断埋点数据是否丢失。
  2. 如权利要求1所述的埋点验证***，其特征在于，该***还包括：
    计算模块，用于将结构化的埋点数据与服务器端存储的完整埋点规范文件进行比对，计算客户端回传的埋点覆盖率。
  3. 如权利要求1或2所述的埋点验证***，其特征在于，该***还包括：
    报告生成模块，用于生成埋点校验报告。
  4. 如权利要求1所述的埋点验证***，其特征在于，该***还包括：
    提醒模块，用于将埋点覆盖率及/或埋点校验报告发送至预设的客户端。
  5. 如权利要求2所述的埋点验证***，其特征在于，该***还包括：
    提醒模块，用于将埋点覆盖率及/或埋点校验报告发送至预设的客户端。
  6. 如权利要求1所述的埋点验证***，其特征在于，所述埋点数据概要信息记录了用户操作客户端应用软件的行为。
  7. 如权利要求1所述的埋点验证***，其特征在于，所述结构化数据以一个预定义的模型或预先定义好的方式存储埋点信息。
  8. 一种埋点验证方法，运行于服务器，其特征在于，该方法包括：
    数据接收步骤：通过网络接收客户端实时传送的埋点数据及埋点数据概要信息；
    数据处理步骤：对埋点数据进行实时分析，将埋点数据从非结构化数据转换为结构化数据；及
    数据校验步骤：将结构化的埋点数据与埋点数据概要信息进行对比，判断埋点数据是否丢失。
  9. 如权利要求8所述的埋点验证方法，其特征在于，该方法还包括：
    计算步骤：将结构化的埋点数据与服务器端存储的完整埋点规范文件进行比对，计算客户端回传的埋点覆盖率。
  10. 如权利要求8或9所述的埋点验证方法，其特征在于，该方法还包括：
    生成埋点校验报告。
  11. 如权利要求8所述的埋点验证方法，其特征在于，该方法还包括：
    将埋点覆盖率及/或埋点校验报告发送至预设的客户端。
  12. 如权利要求9所述的埋点验证方法，其特征在于，该方法还包括：
    将埋点覆盖率及/或埋点校验报告发送至预设的客户端。
  13. 如权利要求8所述的埋点验证方法，其特征在于，所述埋点数据概要信息记录了用户操作客户端应用软件的行为。
  14. 如权利要求8所述的埋点验证方法，其特征在于，所述结构化数据以一个预定义的模型或预先定义好的方式存储埋点信息。
  15. 一种计算机可读存储介质，所述计算机可读存储介质存储有埋点验证***，所述埋点验证***可被至少一处理器执行，以实现如下步骤：
    通过网络接收客户端实时传送的埋点数据及埋点数据概要信息；
    对埋点数据进行实时分析，将埋点数据从非结构化数据转换为结构化数据；及
    将结构化的埋点数据与埋点数据概要信息进行对比，判断埋点数据是否丢失。
  16. 如权利要求15所述的计算机可读存储介质，其特征在于，所述埋点验证***可被所述处理器执行时，还实现如下步骤：
    将结构化的埋点数据与服务器端存储的完整埋点规范文件进行比对，计算客户端回传的埋点覆盖率。
  17. 如权利要求15或16所述的计算机可读存储介质，其特征在于，所述埋点验证***可被所述处理器执行时，还实现如下步骤：
    生成埋点校验报告。
  18. 如权利要求15或16所述的计算机可读存储介质，其特征在于，所述埋点验证***可被所述处理器执行时，还实现如下步骤：
    将埋点覆盖率及/或埋点校验报告发送至预设的客户端。
  19. 如权利要求15所述的计算机可读存储介质，其特征在于，所述埋点数据概要信息记录了用户操作客户端应用软件的行为。
  20. 如权利要求15所述的计算机可读存储介质，其特征在于，所述结构化数据以一个预定义的模型或预先定义好的方式存储埋点信息。
PCT/CN2018/085722 2017-05-05 2018-05-04 埋点验证***及方法 WO2018202171A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710312809.1 2017-05-05
CN201710312809.1A CN107870860B (zh) 2017-05-05 2017-05-05 埋点验证***及方法

Publications (1)

Publication Number Publication Date
WO2018202171A1 true WO2018202171A1 (zh) 2018-11-08

Family

ID=61761481

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/085722 WO2018202171A1 (zh) 2017-05-05 2018-05-04 埋点验证***及方法

Country Status (2)

Country Link
CN (1) CN107870860B (zh)
WO (1) WO2018202171A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113642047A (zh) * 2021-08-13 2021-11-12 上海哔哩哔哩科技有限公司 埋点数据验证方法及***

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107870860B (zh) * 2017-05-05 2020-12-15 平安科技（深圳）有限公司 埋点验证***及方法
CN108664401B (zh) * 2018-05-11 2021-10-12 创新先进技术有限公司 埋点合理性的评估方法及装置
CN110554951A (zh) * 2018-05-31 2019-12-10 北京京东尚科信息技术有限公司 一种埋点管理的方法和装置
CN111190807B (zh) * 2018-11-14 2023-08-18 杭州萤石软件有限公司 一种埋点测试方法及设备
CN111506489B (zh) * 2019-01-30 2023-05-30 斑马智行网络(香港)有限公司 测试方法、***、设备、服务器及存储介质
CN112749078B (zh) * 2019-10-31 2024-06-18 北京沃东天骏信息技术有限公司 一种埋点测试方法和装置
CN111338933A (zh) * 2020-02-07 2020-06-26 北京每日优鲜电子商务有限公司 埋点验证方法、装置、设备及存储介质
CN111522900B (zh) * 2020-03-18 2023-09-01 携程计算机技术（上海）有限公司 非结构化数据的自动解析方法、***、设备及存储介质
CN111459811B (zh) * 2020-03-26 2023-07-18 广州虎牙科技有限公司 埋点数据校验方法和装置
CN111611140B (zh) * 2020-04-30 2023-05-16 广州华多网络科技有限公司 埋点数据的上报验证方法、装置、电子设备及存储介质
CN113254335B (zh) * 2021-05-20 2024-04-16 北京达佳互联信息技术有限公司 测试数据的处理方法、装置、服务器及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104915296A (zh) * 2015-06-29 2015-09-16 北京金山安全软件有限公司 埋点测试方法、数据的查询方法及装置
CN105046601A (zh) * 2015-07-09 2015-11-11 传成文化传媒（上海）有限公司 用户数据处理方法和***
CN106469185A (zh) * 2016-08-29 2017-03-01 浪潮电子信息产业股份有限公司 一种网站统计中进行数据收集的方法
CN106571949A (zh) * 2016-09-23 2017-04-19 北京五八信息技术有限公司 埋点处理方法及装置
CN107870860A (zh) * 2017-05-05 2018-04-03 平安科技（深圳）有限公司 埋点验证***及方法

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101561777A (zh) * 2008-04-14 2009-10-21 中兴通讯股份有限公司 一种实现覆盖率测试的***和方法
CN102158890B (zh) * 2011-02-16 2015-06-03 中国联合网络通信集团有限公司 测试数据的发送、接收方法、设备和***
CN106156212A (zh) * 2015-04-22 2016-11-23 阿里巴巴集团控股有限公司 一种数据采集方法和***、及其终端和服务器
CN106294101B (zh) * 2015-05-19 2019-08-23 阿里巴巴集团控股有限公司 页面打点测试方法和装置
CN106528432B (zh) * 2016-12-12 2019-01-25 北京三快在线科技有限公司 测试场景数据的构建方法及装置、埋点测试方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104915296A (zh) * 2015-06-29 2015-09-16 北京金山安全软件有限公司 埋点测试方法、数据的查询方法及装置
CN105046601A (zh) * 2015-07-09 2015-11-11 传成文化传媒（上海）有限公司 用户数据处理方法和***
CN106469185A (zh) * 2016-08-29 2017-03-01 浪潮电子信息产业股份有限公司 一种网站统计中进行数据收集的方法
CN106571949A (zh) * 2016-09-23 2017-04-19 北京五八信息技术有限公司 埋点处理方法及装置
CN107870860A (zh) * 2017-05-05 2018-04-03 平安科技（深圳）有限公司 埋点验证***及方法

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113642047A (zh) * 2021-08-13 2021-11-12 上海哔哩哔哩科技有限公司 埋点数据验证方法及***

Also Published As

Publication number Publication date
CN107870860A (zh) 2018-04-03
CN107870860B (zh) 2020-12-15

Similar Documents

Publication Publication Date Title
WO2018202171A1 (zh) 埋点验证***及方法
US10795964B2 (en) Text address processing method and apparatus
CN109446068B (zh) 接口测试方法、装置、计算机设备和存储介质
CN110221982B (zh) 业务***的性能测试方法、装置、设备及可读存储介质
WO2019071891A1 (zh) 代码覆盖率分析方法及应用服务器
CN109766534B (zh) 报表生成方法、装置、计算机设备及可读存储介质
US20160283348A1 (en) Testing of application service versions on live data
WO2018184420A1 (zh) 软件测试方法、装置、电子设备及介质
TW201737163A (zh) 問題預測方法及預測系統
KR20180082504A (ko) 애플리케이션 정보 위험 관리를 위한 방법 및 장치
CN112491602B (zh) 行为数据的监控方法、装置、计算机设备及介质
US10705946B2 (en) Techniques for real time server testing in a production environment
KR20190022431A (ko) 랜덤 포레스트 모델의 훈련 방법, 전자장치 및 저장매체
CN107957940B (zh) 一种测试日志处理方法、***及终端
WO2016206605A1 (zh) 一种客户端数据的采集方法和装置
WO2019085466A1 (zh) 关联测试方法、***、应用服务器及计算机可读存储介质
US20200050534A1 (en) System error detection
US20160085664A1 (en) Generating a fingerprint representing a response of an application to a simulation of a fault of an external service
CN113938408B (zh) 一种数据流量测试方法、装置、服务器及存储介质
CN112511459A (zh) 一种流量识别方法、装置、电子设备及存储介质
CN105207829B (zh) 一种入侵检测数据处理方法、装置，及***
CN113362173A (zh) 防重机制验证方法、验证***、电子设备及存储介质
CN109088872A (zh) 带使用期限的云平台的使用方法、装置、电子设备及介质
CN110737820A (zh) 用于生成事件信息的方法和装置
US11706120B1 (en) Automated process flow testing system

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18794832

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 18/02/2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18794832

Country of ref document: EP

Kind code of ref document: A1