A method and device for displaying buried point data

Abstract

The present application discloses a method for displaying buried point data, which can be applied to a client. The method includes: in response to an address confirmation operation triggered in a first web page, obtaining a target address corresponding to the address confirmation operation, where the first web page is an access page of a target application, and the target address includes an access address of the first web page and a target parameter, and the target address is obtained by adding the target parameter to the tail of the access address. In response to the target address including the target parameter, displaying a buried point debugging tool running control, and in response to a trigger operation on the buried point debugging tool running control, displaying the buried point data reported by the buried point software development kit of the target application. Thus, it can be seen that with this solution, the user operations required for the user to view the buried point data reported by the buried point software development kit of the target application are relatively simple, and correspondingly, the efficiency of obtaining the buried point data reported by the buried point software development kit of the target application is higher.

Description

Technical Field

[0001] This application relates to the field of computer technologies, and in particular, to a method and device for displaying buried point data. Background Art

[0002] Buried point analysis is a common data collection method for website analysis. For web applications, corresponding buried point SDKs can be deployed in web pages, and buried point data can be collected through the buried point SDKs, so as to analyze the operation data of the web applications.

[0003] Currently, buried point data can be viewed through the console of a browser on a computer or packet capture on a mobile phone, and further analysis can be performed on the buried point data. However, in this way, the efficiency of obtaining buried point data is low. Therefore, there is an urgent need for a solution to solve the above problems. Summary of the Invention

[0004] To solve or at least partially solve the above technical problems, embodiments of this application provide a method and device for displaying buried point data.

[0005] In a first aspect, embodiments of this application provide a method for displaying buried point data, the method including:

[0006] In response to an address confirmation operation triggered in a first web page, obtain a target address corresponding to the address confirmation operation, where the first web page is an access page of a target application, and the target address includes an access address of the first web page and target parameters, and the target address is obtained by adding the target parameters to the tail of the access address;

[0007] In response to the target address including the target parameters, display a running control for a buried point debugging tool, where the target parameters are used to indicate running the buried point debugging tool corresponding to the target application;

[0008] In response to a trigger operation on the running control for the buried point debugging tool, run the buried point debugging tool to display the buried point data reported by the buried point software development kit of the target application.

[0009] Optionally, the running the buried point debugging tool to display the buried point data reported by the buried point software development kit of the target application includes:

[0010] Determine that the buried point debugging tool has been downloaded to the local;

[0011] Run the buried point debugging tool downloaded to the local to display the buried point data.

[0012] Optionally, running the logging debugging tool to display the logging data reported by the logging software development kit of the target application includes:

[0013] Determine that the logging debugging tool has not been downloaded locally;

[0014] Download the logging debugging tool locally;

[0015] Run the logging debugging tool downloaded locally to display the logging data.

[0016] Optionally, running the logging debugging tool downloaded locally to display the logging data includes:

[0017] Display the logging data obtained by the logging debugging tool from the logging software development tool.

[0018] Optionally, the method further includes:

[0019] Display the configuration information of the target application; and / or,

[0020] Display the running information of the logging software development kit.

[0021] Optionally, the running information of the logging software development kit includes:

[0022] The call information of the target application calling the logging software development kit, and / or the network requests sent by the logging software development kit.

[0023] Optionally, displaying the configuration information of the target application includes:

[0024] Display the configuration information obtained by the logging debugging tool from the logging software development tool.

[0025] Optionally, displaying the running information of the logging software development kit includes:

[0026] Display the running information obtained by the logging debugging tool from the logging software development tool.

[0027] Optionally, the target parameters include:

[0028] Logging debugging tool running instructions and the identifier of the target application.

[0029] Optionally, displaying the logging data reported by the logging software development kit of the target application includes:

[0030] Determine the operating environment of the buried point debugging tool, and display the buried point data according to the display mode corresponding to the operating environment.

[0031] Optionally, the programming language used by the buried point debugging tool is JavaScript.

[0032] In a second aspect, an embodiment of the present application provides a buried point data display device, which includes:

[0033] An acquisition unit, configured to acquire a target address corresponding to the address confirmation operation in response to an address confirmation operation triggered in a first web page. The first web page is an access page of a target application, and the target address includes an access address of the first web page and target parameters. The target address is obtained by adding the target parameters to the end of the access address;

[0034] A first display unit, configured to display a buried point debugging tool operation control in response to the target address including the target parameters. The target parameters are used to indicate to run the buried point debugging tool corresponding to the target application;

[0035] A second display unit, configured to run the buried point debugging tool to display the buried point data reported by the buried point software development kit of the target application in response to a trigger operation on the buried point debugging tool operation control.

[0036] Optionally, the second display unit is configured to:

[0037] Determine that the buried point debugging tool has been downloaded to the local;

[0038] Run the buried point debugging tool downloaded to the local to display the buried point data.

[0039] Optionally, the second display unit is configured to:

[0040] Determine that the buried point debugging tool has not been downloaded to the local;

[0041] Download the buried point debugging tool to the local;

[0042] Run the buried point debugging tool downloaded to the local to display the buried point data.

[0043] Optionally, running the buried point debugging tool downloaded to the local to display the buried point data includes:

[0044] Display the buried point data obtained by the buried point debugging tool from the buried point software development tool.

[0045] Optionally, the device further includes:

[0046] A third display unit for displaying the configuration information of the target application; and / or,

[0047] A fourth display unit for displaying the running information of the buried point software development kit.

[0048] Optionally, the running information of the buried point software development kit includes:

[0049] The call information of the target application calling the buried point software development kit, and / or, the network requests sent by the buried point software development kit.

[0050] Optionally, the displaying of the configuration information of the target application includes:

[0051] Displaying the configuration information obtained by the buried point debugging tool from the buried point software development tool.

[0052] Optionally, the displaying of the running information of the buried point software development kit includes:

[0053] Displaying the running information obtained by the buried point debugging tool from the buried point software development tool.

[0054] Optionally, the target parameters include:

[0055] Buried point debugging tool running instructions and the identifier of the target application.

[0056] Optionally, the displaying of the buried point data reported by the buried point software development kit of the target application includes:

[0057] Determine the running environment of the buried point debugging tool, and display the buried point data according to the display mode corresponding to the running environment.

[0058] Optionally, the programming language used by the buried point debugging tool is JavaScript.

[0059] In a third aspect, an embodiment of the present application provides a device, the device includes a processor and a memory;

[0060] The processor is used to execute the instructions stored in the memory, so that the device executes the method described in any one of the above first aspects.

[0061] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, including instructions, the instructions instructing the device to execute the method described in any one of the above first aspects.

[0062] Fifth aspect, an embodiment of the present application provides a computer program product. When the computer program product runs on a computer, it causes the computer to execute the method described in any one of the above first aspects.

[0063] Compared with the prior art, the embodiments of the present application have the following advantages:

[0064] The embodiments of the present application provide a method for displaying buried point data. In one example, the method can be applied to a client. The method includes: in response to an address confirmation operation triggered in a first web page, obtaining a target address corresponding to the address confirmation operation. The first web page is an access page of a target application program, and the target address includes the access address of the first web page and a target parameter, and the target address is obtained by adding the target parameter to the tail of the access address. After obtaining the target address, the target address can be parsed. If it is determined that the target address includes a target parameter, a buried point debugging tool running control is displayed. The target parameter is used to indicate running the buried point debugging tool corresponding to the target application program. After displaying the buried point debugging tool running control, the user can perform a trigger operation on the buried point debugging tool running control. Correspondingly, the client can, in response to the trigger operation on the buried point debugging tool running control, display the buried point data reported by the buried point software development kit (SDK) of the target application program. Thus, it can be seen that with this solution, the user can first input a target parameter at the tail of the access address corresponding to the first web page and trigger an address confirmation operation. Further, by performing a trigger operation on the buried point debugging tool running control, the user can view the buried point data reported by the buried point SDK of the target application program. The user operation is simple, and correspondingly, the efficiency of obtaining the buried point data reported by the buried point SDK of the target application program is higher. Description of the Drawings

[0065] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the drawings described below are only some embodiments recorded in the present application. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0066] Figure 1 It is a schematic flowchart of a method for displaying buried point data provided by an embodiment of the present application;

[0067] Figure 2 It is a schematic diagram of the process of a method for displaying buried point data provided by an embodiment of the present application;

[0068] Figure 3A structural schematic diagram of a buried point data display device provided by an embodiment of the present application. Detailed implementation manners

[0069] In order to enable those skilled in the art to better understand the solutions of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0070] The inventors of the present application have found through research that currently, buried point data can be viewed on the computer side through the console of the browser or by packet capturing on the mobile side, and further analysis can be performed on the buried point data. However, using this method requires the user to be familiar with the buried point SDK. In other words, it requires a relatively high technical threshold, resulting in low efficiency in obtaining buried point data using this method.

[0071] The inventors of the present application have also found that a browser plugin can be installed to capture and display buried point data through the browser plugin. However, the use of browser plugins is relatively restricted. It can only be used on specific browsers and cannot be used on the mobile side.

[0072] In view of this, an embodiment of the present application provides a method and device for displaying buried point data.

[0073] The following will describe in detail various non-limiting implementation manners of the present application in conjunction with the accompanying drawings.

[0074] Exemplary method

[0075] See Figure 1 , which is a flowchart of a method for displaying buried point data provided by an embodiment of the present application. In one example, this method can be executed by a client. As an example, the method may include the following steps: S101 - S103.

[0076] S101: In response to an address confirmation operation triggered in a first web page, obtain a target address corresponding to the address confirmation operation. The first web page is an access page of a target application, and the target address includes an access address of the first web page and a target parameter. The target address is obtained by adding the target parameter to the end of the access address.

[0077] In one example, the user can enter a target parameter in the network address input area on the first web page. Before the user enters the target address in the network address input area, the address in the network address input area is the access address of the target application. As an example, the user can enter the target parameter at the end of the access address, so that the address in the address input area is changed to the target address. Further, the user can trigger an address confirmation operation for the target address. For example, after the user enters the target parameter at the end of the access address included in the URL input field on the first web page, the user clicks a control for triggering the confirmation operation or clicks the "enter" key on the keyboard.

[0078] The embodiments of the present application do not specifically limit the target application, and the target application can be any web application.

[0079] In one example, the target address may include a target parameter for instructing to run the buried point debugging tool corresponding to the target application. In this way, after the client obtains the target address, it can run the corresponding buried point debugging tool according to the target parameter.

[0080] In one example, the target parameter can be any parameter that can indicate to run the buried point debugging tool corresponding to the target application. As an example, the target parameter may include a buried point debugging tool running instruction and an identifier of the target application. In this way, according to the identifier of the target application and the buried point debugging tool running instruction in the target parameter, the client can determine that it is necessary to run the buried point debugging tool corresponding to the target application.

[0081] Regarding the buried point debugging tool corresponding to the target application, the embodiments of the present application do not specifically limit the programming language used by the buried point debugging tool. In one example, the programming language used by the buried point debugging tool can be JavaScript. In this case, the buried point debugging tool can run in any browser, so that this solution can be applicable to any browser.

[0082] S102: In response to the target address including the target parameter, display a buried point debugging tool running control, where the target parameter is used to instruct to run the buried point debugging tool corresponding to the target application.

[0083] After obtaining the target address, the target address can be parsed. When it is determined that the target address includes a target parameter, the corresponding buried point debugging tool of the target application can be determined according to the target parameter. For this case, the client can display a running control for the buried point debugging tool. In one example, the client can display the running control for the buried point debugging tool in a first preset area on the first web page. The embodiments of the present application do not specifically limit the first preset area, and the first preset area can be any area on the first web page. For example, the first preset area can be located in the lower right corner of the first web page.

[0084] S103: In response to a trigger operation on the running control for the buried point debugging tool, run the buried point debugging tool to display the buried point data reported by the buried point software development kit of the target application.

[0085] After displaying the running control for the buried point debugging tool, the user can trigger an operation on the running control for the buried point debugging tool. For example, the user can click on the running control for the buried point debugging tool. Correspondingly, the client can, in response to the trigger operation on the running control for the buried point debugging tool, run the buried point debugging tool and display the buried point data reported by the buried point SDK of the target application.

[0086] In one example, when specifically implementing the display of the buried point data, the buried point data can be displayed in a second preset area on the first web page. For example, a floating layer can be displayed on the right side of the first web page, and the buried point data can be displayed on this floating layer.

[0087] In one example, before displaying the buried point data, the running environment of the buried point debugging tool can be determined, and the buried point data can be displayed according to the display mode corresponding to the running environment. The running environment mentioned here can include, for example, running on a computer or running on a mobile phone. It can be seen that in this solution, when displaying the buried point data, the running environment of the buried point debugging tool can be combined for display, so that this solution can be applied to both the computer side and the mobile phone side.

[0088] In one example, when specifically implementing S103, it can be implemented through the following steps A1 - A2.

[0089] Step A1: Determine that the buried point debugging tool has been downloaded to the local.

[0090] In one example, the content stored locally can be scanned to determine whether the buried point debugging tool has been downloaded to the local.

[0091] In yet another example, it is possible to determine whether the buried point debugging tool has been downloaded to the local based on the download identifier of the buried point debugging tool. Herein, the download identifier of the buried point debugging tool is used to indicate whether the buried point debugging tool has been downloaded to the local. In one example, after downloading the buried point debugging tool to the local, the client can set the download identifier to an identifier indicating that the buried point debugging tool has been downloaded to the local.

[0092] Step A2: Run the buried point debugging tool downloaded to the local and display the buried point data.

[0093] After determining that the buried point debugging tool has been downloaded to the local, the client can run the buried point debugging tool downloaded to the local. In one example, the buried point debugging tool has the functions of obtaining the aforementioned buried point data and rendering the buried point data. Therefore, after running the buried point debugging tool, the buried point data can be displayed using this buried point debugging tool.

[0094] In one example, the buried point debugging tool can obtain the buried point data from the buried point SDK. In one example, after the buried point debugging tool runs, it can send a notification message to the buried point SDK, and this notification message is used to indicate that the buried point debugging tool is ready for work. After receiving this notification message, the buried point SDK can send the data it has obtained to the buried point debugging tool, wherein the buried point data obtained by the buried point SDK can be stored in the message dispatching center of the buried point SDK, for example, storing the buried point data in the form of buried point logs.. In one example, the data obtained by the buried point SDK can include the buried point data. After the buried point debugging tool obtains the buried point data from the buried point SDK, it can display the buried point data in the first web page.

[0095] In one example, the buried point SDK can send the buried point data to the buried point debugging tool in the form of buried point logs. In one example, the buried point SDK can send the buried point logs to the buried point debugging tool in the form of full - volume logs. In one example, the buried point SDK can send the buried point logs to the buried point debugging tool in the form of incremental logs. In another example, when the buried point SDK first sends the buried point logs to the buried point debugging tool, it can send the buried point logs to the buried point debugging tool in the form of full - volume logs, and when the buried point SDK subsequently sends the buried point logs to the buried point debugging tool again, it can send the buried point logs to the buried point debugging tool in the form of incremental logs.

[0096] In one example, communication can be carried out between the buried point SDK and the buried point debugging tool through post message.

[0097] In yet another example, when specifically implemented, S103 may be implemented through the following steps B1 - B3.

[0098] Step B1: Determine that the buried - point debugging tool has not been downloaded locally.

[0099] In one example, the content stored locally can be scanned to determine whether the buried - point debugging tool has been downloaded locally.

[0100] In yet another example, it is possible to determine whether the buried - point debugging tool has been downloaded locally based on the download identifier of the buried - point debugging tool. Regarding the download identifier, reference can be made to the relevant description part above, and no repeated description will be given here.

[0101] Step B2: Download the buried - point debugging tool to the local.

[0102] Step B3: Run the buried - point debugging tool downloaded locally to display the buried - point data.

[0103] After determining that the buried - point debugging tool has not been downloaded locally, the buried - point debugging tool can be downloaded to the local, and further, the buried - point debugging tool downloaded locally can be run to display the buried - point data. Regarding the specific implementation of step B3, reference can be made to the specific description part of step A2 above, and no repeated description will be given here.

[0104] Regarding the buried - point data, it should be noted that the buried - point data may be the data collected by the buried - point SDK. In a specific example, after the target application integrates the buried - point SDK, the target application can call the application programming interface (API) for buried - point reporting. The buried - point SDK will perform a preliminary verification on the buried - point name and buried - point attributes passed in by the target application, and then send the buried - point request to the server. In this process, the buried - point SDK can record the results of the foregoing verification and the results of sending the buried - point request to the server (success or failure) in the message dispatching center of the buried - point SDK. The buried - point data mentioned in the embodiments of the present application may include data such as the results of the foregoing verification and the results of sending the buried - point request to the server.

[0105] As can be seen from the above description, by using the solution provided in the embodiments of the present application, a user can first input a target parameter at the end of the access address corresponding to the first web page and trigger an address confirmation operation. Further, for the triggering operation of the control for running the buried point debugging tool, the buried point data reported by the buried point SDK of the target application can be viewed. The user operation is simple, and correspondingly, the efficiency of obtaining the buried point data reported by the buried point SDK of the target application is higher.

[0106] In one example, considering that after the user views the buried point data, the user can analyze the buried point data. In the case of determining that the buried point data is abnormal, the user can analyze the reason for the abnormality of the buried point data. In one example, considering the reason for the abnormality of the buried point data, it may be that the buried point SDK runs abnormally or the target application configuration is abnormal. Therefore, in order to improve the efficiency of locating the reason for the abnormality of the buried point data, in one example of the embodiments of the present application, the client can also display the configuration information of the target application and / or the running information of the buried point SDK.

[0107] In one example, the message dispatching center of the buried point SDK can store the configuration information of the target application and the running information of the buried point SDK. Therefore, the buried point SDK can send the configuration information of the target application and / or the running information of the buried point SDK to the buried point debugging tool, and the buried point debugging tool displays the configuration information of the target application and / or the running information of the buried point SDK.

[0108] Regarding the configuration information of the target application, it should be noted that the configuration information of the target application includes, but is not limited to: the initialization configuration of the target application, the public parameters of the target application, and the enabling status of the additional functions of the target application, etc., which will not be listed one by one here.

[0109] Regarding the running information of the buried point SDK, it can be the information generated during the running process of the buried point SDK. As an example, the running information of the buried point SDK can include the call information of the target application calling the buried point SDK. Specifically, it can be the call information of the target application calling the API of the buried point SDK. As another example, the running information of the buried point SDK can include the network requests sent by the buried point SDK.

[0110] In one example, the running information of the buried point SDK can be reflected as the running log of the buried point SDK. As an example, the running log recorded by the message dispatching center of the buried point SDK can be a log recorded by classifying the running log, for example, a log recorded by classifying according to the three categories of "prompt", "alarm", and "error". Correspondingly, when the buried point debugging tool displays the running information of the buried point SDK, it can also display the running information corresponding to each category according to the category. In one example, the buried point SDK can send the running log to the buried point debugging tool in the form of a full-volume log. In another example, the buried point SDK can send the running log to the buried point debugging tool in the form of an incremental log. In another example, when the buried point SDK first sends the running log to the buried point debugging tool, it can send the running log to the buried point debugging tool in the form of a full-volume log. When the buried point SDK subsequently sends the running log to the buried point debugging tool again, it can send the running log to the buried point debugging tool in the form of an incremental log.

[0111] To facilitate understanding of this solution, next, the solution provided by the embodiments of the present application will be introduced from the perspective of signaling interaction. Refer to Figure 2 , which is a schematic process diagram of a method for displaying buried point data provided by the embodiments of the present application. As Figure 2 shown:

[0112] The web application (target application) integrates the buried point SDK and initializes the buried point SDK.

[0113] The buried point SDK loads the buried point debugging tool. Specifically, the buried point SDK can respond to the address confirmation operation, obtain the target address corresponding to the address confirmation operation, and display the buried point debugging tool running control when it is determined that the target address includes the target parameter. The target parameter is used to indicate the buried point debugging tool corresponding to running the target application. In response to the trigger operation for the buried point debugging tool running control, the buried point debugging tool is run.

[0114] After the buried point debugging tool runs, it can send a notification message to the buried point SDK.

[0115] After the buried point SDK receives the notification message, it can send the buried point data, the configuration information of the target application, and the running information of the buried point SDK to the buried point debugging tool. Correspondingly, the buried point debugging tool can display the sent buried point data, the configuration information of the target application, and the running information of the buried point SDK.

[0116] Exemplary device

[0117] Based on the method provided in the above embodiments, an embodiment of the present application further provides a device, which will be introduced below with reference to the accompanying drawings.

[0118] See Figure 3 , this figure is a schematic structural diagram of a buried point data display device provided by an embodiment of the present application. The device 300 may specifically include, for example: an acquisition unit 301, a first display unit 302, and a second display unit 303.

[0119] The acquisition unit 301 is configured to obtain a target address corresponding to the address confirmation operation in response to the address confirmation operation triggered in the first web page. The first web page is an access page of the target application, and the target address includes the access address of the first web page and target parameters, and the target address is obtained by adding the target parameters to the end of the access address;

[0120] The first display unit 302 is configured to display a buried point debugging tool running control in response to the target address including the target parameters, and the target parameters are used to indicate running the buried point debugging tool corresponding to the target application;

[0121] The second display unit 303 is configured to run the buried point debugging tool to display the buried point data reported by the buried point software development kit of the target application in response to the trigger operation on the buried point debugging tool running control.

[0122] Optionally, the second display unit 303 is configured to:

[0123] Determine that the buried point debugging tool has been downloaded to the local;

[0124] Run the buried point debugging tool downloaded to the local to display the buried point data.

[0125] Optionally, the second display unit 303 is configured to:

[0126] Determine that the buried point debugging tool has not been downloaded to the local;

[0127] Download the buried point debugging tool to the local;

[0128] Run the buried point debugging tool downloaded to the local to display the buried point data.

[0129] Optionally, running the buried point debugging tool downloaded to the local to display the buried point data includes:

[0130] Displaying the buried point data obtained by the buried point debugging tool from the buried point software development tool.

[0131] Optionally, the device further includes:

[0132] A third display unit for displaying the configuration information of the target application; and / or,

[0133] A fourth display unit for displaying the running information of the buried point software development kit.

[0134] Optionally, the running information of the buried point software development kit includes:

[0135] The call information of the target application calling the buried point software development kit, and / or, the network requests sent by the buried point software development kit.

[0136] Optionally, the displaying of the configuration information of the target application includes:

[0137] Displaying the configuration information obtained by the buried point debugging tool from the buried point software development tool.

[0138] Optionally, the displaying of the running information of the buried point software development kit includes:

[0139] Displaying the running information obtained by the buried point debugging tool from the buried point software development tool.

[0140] Optionally, the target parameters include:

[0141] Buried point debugging tool running instructions and the identifier of the target application.

[0142] Optionally, the displaying of the buried point data reported by the buried point software development kit of the target application includes:

[0143] Determine the running environment of the buried point debugging tool, and display the buried point data according to the display mode corresponding to the running environment.

[0144] Optionally, the programming language used by the buried point debugging tool is JavaScript.

[0145] Since the device 300 is the device corresponding to the method provided in the above method embodiment, the specific implementation of each unit of the device 300 is the same concept as that of the above method embodiment. Therefore, for the specific implementation of each unit of the device 300, reference can be made to the description part of the above method embodiment, and details are not described herein again.

[0146] An embodiment of the present application further provides a device, the device includes a processor and a memory;

[0147] The processor is used to execute the instructions stored in the memory, so that the device executes the buried point data display method provided in the above method embodiment.

[0148] An embodiment of the present application provides a computer-readable storage medium, including instructions for instructing a device to execute the method for displaying buried point data provided in the above method embodiment.

[0149] An embodiment of the present application further provides a computer program product, which, when running on a computer, causes the computer to execute the method for displaying buried point data provided in the above method embodiment.

[0150] After considering the specification and practicing the invention disclosed herein, those skilled in the art will readily conceive of other embodiments of the present application. The present application is intended to cover any variations, uses, or adaptations of the present application, which follow the general principles of the present application and include known common general knowledge or conventional technical means in the technical field not disclosed in the present disclosure. The specification and embodiments are only to be considered as exemplary, and the true scope and spirit of the present application are pointed out by the following claims.

[0151] It should be understood that the present application is not limited to the exact structures described above and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of the present application is only limited by the appended claims.

[0152] The above are only the preferred embodiments of the present application and are not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A method for displaying buried point data, characterized in that The method includes: In response to an address confirmation operation triggered in a first web page, obtaining a target address corresponding to the address confirmation operation, where the first web page is an access page of a target application, and the target address includes an access address of the first web page and target parameters, and the target address is obtained by adding the target parameters to the tail of the access address; In response to the target address including the target parameters, displaying a running control of a buried point debugging tool, where the target parameters are used to indicate running the buried point debugging tool corresponding to the target application, and the target parameters include a buried point debugging tool running instruction and an identifier of the target application, and the programming language used by the buried point debugging tool is JavaScript, indicating that the buried point debugging tool can run in any browser; In response to a trigger operation on the running control of the buried point debugging tool, running the buried point debugging tool to display the buried point data reported by the buried point software development kit of the target application. Among them, after the buried point debugging tool runs, a notification message is sent to the buried point software development kit, and the notification message is used to indicate that the buried point debugging tool is ready for work. After receiving the notification message, the buried point software development kit reports the buried point data it has obtained to the buried point debugging tool; The method further includes: Displaying the running information of the buried point software development kit; The displaying the buried point data reported by the buried point software development kit of the target application includes: Determining the running environment of the buried point debugging tool, and displaying the buried point data according to the display mode corresponding to the running environment, where the running environment is any one of a mobile terminal and a computer terminal.

2. The method according to claim 1, characterized in that, The running the buried point debugging tool to display the buried point data reported by the buried point software development kit of the target application includes: Determining that the buried point debugging tool has been downloaded to the local; Running the buried point debugging tool downloaded to the local to display the buried point data.

3. The method according to claim 1, wherein The running the buried point debugging tool to display the buried point data reported by the buried point software development kit of the target application includes: Determining that the buried point debugging tool has not been downloaded to the local; Downloading the buried point debugging tool to the local; Running the buried point debugging tool downloaded to the local to display the buried point data.

4. The method according to claim 2 or 3, characterized in that, The running the buried point debugging tool downloaded to the local to display the buried point data includes: Displaying the buried point data obtained by the buried point debugging tool from the buried point software development kit.

5. The method according to claim 1, characterized in that, The method further includes: Displaying the configuration information of the target application.

6. The method according to claim 5, wherein The running information of the buried point software development kit includes: The calling information of the target application calling the buried point software development kit, and / or, the network requests sent by the buried point software development kit.

7. The method according to claim 5, characterized in that The displaying the configuration information of the target application includes: Displaying the configuration information obtained by the buried point debugging tool from the buried point software development kit.

8. The method according to claim 5, characterized in that, The displaying the running information of the buried point software development kit includes: Display the running information obtained by the logging debugging tool from the logging software development kit.

9. A buried point data display device, characterized in that, The device includes: An acquisition unit, configured to acquire a target address corresponding to the address confirmation operation in response to an address confirmation operation triggered on a first web page, where the first web page is an access page of a target application, and the target address includes an access address of the first web page and target parameters, and the target address is obtained by adding the target parameters to the tail of the access address; A first display unit, configured to display a logging debugging tool running control when it is determined that the target address includes target parameters, where the target parameters are used to indicate running a logging debugging tool corresponding to the target application, the target parameters include a logging debugging tool running instruction and an identifier of the target application, and the programming language used by the logging debugging tool is JavaScript, to indicate that the logging debugging tool can run in any browser; A second display unit, configured to run the logging debugging tool to display the logging data reported by the logging software development kit of the target application in response to a trigger operation on the logging debugging tool running control. After the logging debugging tool runs, a notification message is sent to the logging software development kit, where the notification message is used to indicate that the logging debugging tool is ready for work, and after receiving the notification message, the logging software development kit reports the logging data obtained by itself to the logging debugging tool; A fourth display unit, configured to display the running information of the logging software development kit; The displaying the logging data reported by the logging software development kit of the target application includes: Determine the running environment of the logging debugging tool, and display the logging data according to the display mode corresponding to the running environment, where the running environment is any one of a mobile phone side and a computer side.

10. A buried point data display device, characterized in that, The device includes a processor and a memory; The processor is configured to execute instructions stored in the memory, so that the device executes the method according to any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that, Includes instructions that instruct the device to execute the method according to any one of claims 1 to 8.

Images