Method, device and equipment for data presentation, medium and product

Abstract

The embodiment of the invention provides a data presentation method, device and equipment, a medium and a product. The method comprises the following steps: acquiring operation data corresponding to an application running on the terminal equipment, wherein the operation data comprises operation data acquired from a plurality of acquisition points inserted in the application in the running process of the application; and in response to a presentation request for the operation data of the application, visual presentation of the operation data is provided in a user interface of the application, and the visual presentation comprises presentation of at least one of names, categories, parameter information and collection time of the multiple collection points.

Description

TECHNICAL FIELD

[0001] Example embodiments of the present disclosure generally relate to the field of computers, and in particular, to a method, an apparatus, a device and a computer readable storage medium for data presentation. BACKGROUND

[0002] With the popularity of intelligent terminal devices and the continuous expansion of the scale of mobile applications, applications present diversified development trends in terms of functional complexity, interaction path and running state. In order to continuously improve user experience, developers and testers need to deeply understand the state changes and operation logic of applications in the actual running process. In this process, how to more effectively obtain, present and understand the data generated in the running process becomes an important direction to promote product quality optimization and research and development efficiency improvement. SUMMARY

[0003] In a first aspect of the present disclosure, a method for data presentation is provided. The method comprises: obtaining operation data corresponding to an application running on a terminal device, the operation data comprising operation data collected by a plurality of collection points inserted from the application in the running process of the application; and in response to a presentation request for the operation data of the application, providing visual presentation of the operation data in a user interface of the application, wherein the visual presentation comprises presenting at least one of a name, a category, parameter information and collection time of each of the plurality of collection points.

[0004] In a second aspect of the present disclosure, an apparatus for data presentation is provided. The apparatus comprises: a data acquisition module configured to obtain operation data corresponding to an application running on a terminal device, the operation data comprising operation data collected by a plurality of collection points inserted from the application in the running process of the application; and a data presentation module configured to, in response to a presentation request for the operation data of the application, provide visual presentation of the operation data in a user interface of the application, wherein the visual presentation comprises presenting at least one of a name, a category, parameter information and collection time of each of the plurality of collection points.

[0005] In a third aspect of the present disclosure, an electronic device is provided. The device comprises at least one processor; and at least one memory coupled to the at least one processor and storing instructions for execution by the at least one processor. The instructions, when executed by the at least one processor, cause the device to perform the method of the first aspect.

[0006] In a fourth aspect of the present disclosure, a computer readable storage medium is provided. The computer readable storage medium has stored thereon computer executable instructions executable by a processor to implement the method of the first aspect.

[0007] In a fifth aspect of the present disclosure, there is provided a computer program product comprising computer executable instructions, wherein the computer executable instructions, when executed by a processor, implement the method according to the first aspect of the present disclosure.

[0008] It is to be understood that the details set forth herein do not limit the key or critical features of the present disclosure, and are intended to be illustrative only. Other features of the present disclosure will become apparent from the following description, which is to be read in conjunction with the drawings. BRIEF DESCRIPTION OF DRAWINGS

[0009] The above and other features, aspects and advantages of embodiments of the present disclosure will become more apparent from the following detailed description, taken in conjunction with the accompanying drawings, in which like reference numerals denote like elements, and wherein:

[0010] Figure 1 a schematic diagram illustrating an example environment in which embodiments of the present disclosure can be implemented;

[0011] Figure 2 a flow diagram illustrating a process for data presentation according to some embodiments of the present disclosure;

[0012] Figure 3 a schematic diagram illustrating an example interface for data presentation according to some embodiments of the present disclosure;

[0013] Figure 4 a schematic diagram illustrating an example interface for visual presentation of operational data according to some embodiments of the present disclosure;

[0014] Figure 5 a schematic block diagram illustrating an apparatus for data presentation according to certain embodiments of the present disclosure; and

[0015] Figure 6 a block diagram of an electronic device in which one or more embodiments of the present disclosure can be implemented. DETAILED DESCRIPTION

[0016] Embodiments of the present disclosure will be described below in greater detail with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it is to be understood that the present disclosure can be embodied in various forms and should not be construed as being limited to the embodiments set forth herein, but rather should be construed to encompass all alternatives and modifications falling within the scope of the present disclosure. It is to be understood that the drawings and embodiments of the present disclosure are only for illustrative purposes and should not be construed as limiting the scope of protection of the present disclosure.

[0017] In the description of embodiments of the disclosure, the term "comprising" and similar terms thereof are understood to encompass open-ended inclusion, i.e., "comprising but not limited to". The term "based on" is understood to mean "based at least in part on". The term "one embodiment" or "the embodiment" is understood to mean "at least one embodiment". The term "some embodiments" is understood to mean "at least some embodiments". The following can also include other explicit and implicit definitions.

[0018] In this article, unless specifically stated, performing a step "in response to A" does not mean performing the step immediately after "A", but can include one or more intermediate steps.

[0019] It can be understood that the data involved in the technical solutions of the present application (including but not limited to the data itself, the obtaining or use of the data) should comply with the requirements of the relevant laws and regulations and relevant provisions.

[0020] It can be understood that before using the technical solutions disclosed in the embodiments of the present disclosure, the type of personal information involved in the present disclosure, the scope of use, the use scenario, etc. should be informed to the user and the authorization of the user should be obtained through appropriate means according to relevant laws and regulations.

[0021] For example, in response to receiving the active request of the user, the prompt information is sent to the user to explicitly prompt the user that the operation requested to be performed will need to obtain and use the personal information of the user, so that the user can voluntarily choose whether to provide the personal information to the electronic device, application, server or storage medium, etc. software or hardware that performs the operation of the technical solutions of the present disclosure according to the prompt information.

[0022] As an optional but not limited implementation manner, in response to receiving the active request of the user, the prompt information is sent to the user, for example, in the form of a pop-up window, and the prompt information can be presented in the form of text in the pop-up window. In addition, the pop-up window can also carry selection controls for the user to select "agree" or "disagree" to provide personal information to the electronic device.

[0023] It can be understood that the above notification and user authorization process is only illustrative, and does not limit the implementation manner of the present disclosure, and other manners meeting the relevant laws and regulations can also be applied to the implementation manner of the present disclosure.

[0024] Figure 1 A schematic diagram of an example environment 100 in which embodiments of the present disclosure can be implemented is shown. In this example environment 100, an application 120 is installed in a terminal device 110. A user 140 can interact with the application 120 via the terminal device 110 and / or an attached device of the terminal device 110. The application 120 can be a content presentation application (e.g., a video playing application), an online shopping application, or any other appropriate application.

[0025] In Figure 1 In the environment 100, if the application 120 is in an active state, the terminal device 110 can present an interface 150 of the application 120. The interface 150 can include various user interfaces that the application 120 can provide, such as a content presentation interface, a content creation interface, a content publishing interface, a message interface, a personal homepage, and the like. The application 120 can provide a content viewing function to view various contents published in the application 120. Via a corresponding page, the application 120 can provide various online contents to the user 140. Embodiments of the present disclosure do not limit the specific functions of the application and the presented contents. Via a suitable triggering manner, such as clicking or selecting an application icon, the running of the application can be activated.

[0026] In some embodiments, the terminal device 110 communicates with the server 130 to implement the provision of services of the application 120. The terminal device 110 can be any type of mobile terminal, fixed terminal, or portable terminal including a mobile phone, a desktop computer, a laptop computer, a notebook computer, a netbook computer, a tablet computer, a media computer, a multimedia tablet, a personal communication system (PCS) device, a personal navigation device, a personal digital assistant (PDA), an audio / video player, a digital camera / camcorder, a positioning device, a television receiver, a radio broadcast receiver, an electronic book device, a game device, or any combination of the foregoing, including accessories and peripherals of these devices or any combination thereof. In some embodiments, the terminal device 110 can also be capable of supporting any type of interface to the user (such as "wearable" circuitry, etc.). The server 130 can be various types of computing systems / servers capable of providing computing capabilities, including but not limited to mainframes, edge computing nodes, computing devices in a cloud environment, and the like.

[0027] It should be understood that the structure and function of the various elements in the environment 100 are described for illustrative purposes only, without implying any limitation on the scope of the present disclosure.

[0028] As briefly mentioned above, with the continuous development of the mobile Internet and the wide popularity of smart terminal devices, various mobile applications have penetrated into multiple scenarios such as work, life, socialization, and entertainment of users. The interaction logic of the application interface is increasingly complex, the system behavior triggering chain is increasingly fine, and the expectations of users for the response speed and use stability of functions are also continuously improved. In order to intuitively and timely understand the key operations and related data change processes of the system under different interaction paths in the actual running context of the application, the point-in-time technology is widely used to collect event data in the running process of the application on the client side to assist in user path analysis, function verification, performance monitoring, and the like.

[0029] Tracking points (or collection points) are data collection locations preset within an application that automatically record specific events or states during operation. These collection points can be used to collect operational data related to application operation, such as performance metrics, data flow information, or information that tracks and records various events in the application. By acquiring and presenting this operational data, a reliable basis can be provided for performance tuning, functional verification, data analysis, and more. However, traditional operational data presentation solutions still have some problems. The following describes several example scenarios.

[0030] One scenario involves device connectivity, timeliness, and stability issues. For example, the presentation of operational data from collection points often relies on a pairing connection between an external platform and the terminal device. This connection process typically involves multiple steps, such as code scanning, manual confirmation, and page jumps. The operation process is cumbersome and prone to interruptions. At the same time, in the case of an unstable network environment or unavailable platform services, pairing connections may frequently fail, affecting the continuity and success rate of verification work. In addition, since data needs to go through multiple stages such as transmission, parsing, and display, it is difficult for users to immediately view the corresponding operational data when an event is triggered. This delay may interfere with the efficiency of debugging and verification, especially in high-frequency interactions or performance-sensitive scenarios.

[0031] Another scenario involves the display of operational data. In complex application environments, users may need to flexibly filter and analyze data from different sources, structures, and attributes based on specific context. However, existing operational data display methods make it difficult to quickly locate target data using precise expressions and other conditions, limiting their usability and efficiency in actual debugging.

[0032] Furthermore, traditional data presentation tools typically don't support integration with code debugging tools, making it difficult to directly locate the source code where the collection point triggers, making it difficult for users to promptly identify the source of the problem. Furthermore, their filtering configurations are often not persistent, requiring reconfiguration each time a user accesses the page.

[0033] In light of this, according to an embodiment of the present disclosure, an improved solution for data presentation is proposed. This solution includes, first, obtaining operational data corresponding to an application running on a terminal device, where the operational data includes operational data collected from multiple collection points inserted into the application during its operation. Furthermore, in response to a request to present the operational data of the application, a visual presentation of the operational data is provided in the user interface of the application, where the visual presentation includes presenting at least one of the names, categories, parameter information, and collection time of each of the multiple collection points.

[0034] Thus, without relying on external platforms, web services or remote connections, the terminal device can directly obtain and present the collected operation data, thereby simplifying the data viewing and verification process and improving the convenience of user use. In this way, the user can immediately view the real-time collected operation data after triggering the visual presentation, avoiding the waiting and failure problems caused by network delay or platform instability, and effectively improving the efficiency and stability of debugging and verification. In summary, the embodiments of the present disclosure provide an efficient, stable and instant data presentation scheme in a lightweight, localized and visual manner, which is especially suitable for scenarios that require frequent verification, multiple rounds of debugging and rapid data positioning.

[0035] Some example embodiments of the present disclosure will be described below with reference to the accompanying drawings. In addition, in the following, the example embodiments will be mainly described with respect to the terminal device 110. It should be understood that the actions described with respect to the terminal device 110 can be performed by the application 120 on the terminal device 110, or can be performed by the application 120 in cooperation with its server (e.g., the server 130).

[0036] Figure 2 A flowchart of a process 200 of data presentation according to some embodiments of the present disclosure is shown. The process 200 can be implemented at the terminal device 110. The process 200 will be described below with reference to Figure 1 The process 200 is described.

[0037] At block 210, the terminal device 110 obtains operation data corresponding to an application running on the terminal device. The operation data includes operation data collected from a plurality of collection points inserted in the application during the running of the application. The terminal device 110 can obtain operation data generated by one or more applications 120 running on the terminal device during the running of the application. The operation data is derived from a plurality of collection points pre-inserted in the application, which can be embedded in key logic nodes of the application for automatically recording corresponding event trigger information and related parameters at runtime.

[0038] The collection point can also be referred to as a burying point, a tracking point or a plug-in point, which refers to a trigger point pre-inserted in different logic positions (e.g., in the code of the application) of the application for performing data collection at runtime. Each collection point can be automatically triggered when a specific condition or operation occurs, and the corresponding operation data is obtained. The terminal device 110 can configure a plurality of collection points in the source code of the application 120 by means of a preset interface call, an annotation mark or code plug-in, etc., thereby specifying the key operation nodes or business logic positions that need to be recorded during the running of the application. The setting of the collection point can cover a plurality of types of event or state trigger points, such as page entry or exit, button click, video playback, advertisement exposure, resource loading, interface request, etc.

[0039] Operational data, also known as tracking data, refers to data recorded by multiple pre-defined collection points during the application's runtime when an application interacts with the user or when specific events occur within the application. Operational data can be used to reflect the application's operations and status at specific times and within specific logical paths.

[0040] In some examples, to enable local real-time collection, analysis, and display of application operational data, the terminal device 110 may integrate data monitoring and acquisition modules or components, such as a tracking software development kit (SDK), into the application. The terminal device 110 may utilize the data monitoring and acquisition modules or components integrated into the application to automatically capture operational data corresponding to key acquisition points without interrupting the application's original functional processes.

[0041] In some examples, when a collection point in an application is triggered, the terminal device 110 can use the tracking SDK to obtain the operation data corresponding to the collection point and process the data. For example, the operation data obtained by the terminal device 110 can be organized into structured data objects and stored in the local storage space. In this way, real-time, low-latency data support can be provided for subsequent functions such as visualization. User 140 can view the operation data obtained at multiple collection points in real time and perform debugging or verification accordingly.

[0042] Return Reference Figure 2 In block 220, terminal device 110 may provide a visual presentation of the operation data in the user interface of the application in response to the request to present the operation data of the application. The visual presentation includes presenting at least one of the names, categories, parameter information, and collection time of each of the multiple collection points. For example, terminal device 110 may present a list of operation data in the user interface, where each record in the list may correspond to an operation data item triggered and acquired by a collection point.

[0043] As an example, Figure 3 Schematic diagram of an example interface 300A for data presentation according to some embodiments of the present disclosure is shown. Figure 3 In the illustrated user interface 300A, the terminal device 110 may present the name 301 of the collection point in the user interface 300A, identifying the event type or operation behavior corresponding to the current operation data. The terminal device 110 may also present the category of the collection point in the user interface 300A, for example, a category label 302, indicating the category to which the collection point belongs. The terminal device 110 may also present the time when the collection point was triggered (or understood as the time when the event occurred or the time when the data was collected) in the form of a time label 303.

[0044] Alternatively or additionally, the terminal device 110 can also present the parameter information 304 of the collection point in the user interface 300A, for example, in the form of key-value pairs to display the context parameter fields when the collection point is triggered. The user interface 300A can further support folding or unfolding of the parameter information 304, for example, by clicking on the name 301 of the collection point, the corresponding parameter information 304 of the collection point can be folded or unfolded.

[0045] In some embodiments, the terminal device 110 can present an entry of the application user interface. In response to the triggering of the entry, the terminal device 110 can determine a presentation request for the operation data of the application. For example, the user 140 can directly open the user interface for visualizing the presentation of the operation data in the application by clicking on a specific entry button or triggering a specific gesture, without relying on external web pages or platform loading. In addition, the user interface supports real-time updating of the acquired operation data, and the user 140 can view the latest acquired operation data each time the visualization presentation interface is entered.

[0046] In some examples, the module for visualizing the presentation of the operation data can be integrated in the application of the terminal device 110. For example, the terminal device 110 can integrate the module into the application internally during the application building or compiling stage, so as to realize the local visualization presentation of the operation data during the running process without relying on external platforms or network environments. Alternatively or additionally, the visualization presentation module integrated directly in the application can be bound to a specific application instance. For example, when multiple applications are installed in the terminal device at the same time, the respective visualization presentation modules can be integrated in the respective application packages independently of each other. Each visualization presentation module is only used to present the operation data collected from the application bound thereto, avoiding cross-application interference or data confusion.

[0047] In some embodiments, the terminal device 110 not only can present the operation data collected during the running process of the application locally and visually, but also provides further data operation capabilities, for example, supports filtering operation on the data based on the user interface.

[0048] In some embodiments, the terminal device 110 can provide a filtering control for the operation data in the user interface. In response to a triggering of the filtering control, the terminal device 110 can provide a visualized presentation of filtered operation data in the user interface based on at least one filtering condition determined via the filtering control. For example, the terminal device 110 can perform a corresponding filtering operation on the locally cached set of operation data after receiving an operation of the filtering control by the user 140 (i.e., the user 140 sets one or more filtering conditions). Subsequently, the terminal device 110 can update the presented operation data based on the original user interface, so as to present only operation data items that satisfy the filtering conditions. The setting of the filtering control can help the developer or tester to quickly locate a piece of data of interest in a large amount of data, so as to more efficiently analyze a specific interaction path, behavior triggering logic, or running status of a particular function.

[0049] In some embodiments, the filtering control can include an input control for receiving a filtering condition. For example, the terminal device 110 can present the input control 310 in the interface 300A. The user 140 can provide a keyword, event name, field value, parameter content, or the like via the input control 310. The terminal device 110 can receive the information provided via the input control 310 as a filtering condition, and filter out matching data items from the operation data.

[0050] In some embodiments, the filtering control can include at least one filtering label. For example, the terminal device 110 can present at least one filtering label (collectively or individually referred to as the filtering labels 320) in the interface 300A. Each filtering label 320 can respectively indicate a filtering condition. The selection of each filtering label 320 indicates a triggering of the corresponding filtering condition. For example, the user 140 clicks (or unclicks) a certain filtering label 320, which indicates the selection (or revocation) of the filtering condition. After one or more filtering labels 320 are selected, the terminal device 110 can filter out matching data items from the operation data based on one or more filtering conditions corresponding to the one or more filtering labels 320, and present in the interface.

[0051] In some embodiments, the terminal device 110 can present one or more predetermined filtering labels 320 in the user interface. For example, the terminal device 110 can present a set of preset filtering labels 320 (e.g., a default set of filtering labels 320) in the user interface after triggering the visualized presentation of the operation data. These filtering labels 320 can correspond to common event types, operation behaviors, important data, or filtering operations determined based on user history.

[0052] In some embodiments, the terminal device 110 can present at least one filter label 320 corresponding to the received at least one filter condition in the user interface in response to the received at least one filter condition via the input control 310. For example, the terminal device 110 can parse the filter condition received via the input control 310 and present a filter label 320 corresponding to the filter condition in the user interface after receiving the user-provided filter condition via the input control 310. The user 140 can enable or disable the corresponding filter condition by clicking the filter label 320. This way allows the user to define filter conditions of arbitrary dimensions flexibly according to specific needs and provides filter labels that can be responded to in real time, thereby improving the efficiency of data screening and debugging.

[0053] In some embodiments, the at least one filter label 320 corresponding to different filter conditions can have different visual styles. For example, the filter labels 320 corresponding to different filter conditions can have different colors, shapes, shadows, light effects, etc. The filter label 320 is a visual identification unit that can intuitively display the filtering state, condition type, and data that the user focuses on. By setting different visual styles for filter labels corresponding to different filter conditions, the operation efficiency and interface readability can be improved.

[0054] In some embodiments, in order to meet the user's diverse data operation needs, the terminal device can support setting and triggering multiple types of filter conditions through the input control 310 or the filter label 320, respectively. These filtering methods can cover from simple keyword matching to regular expressions, field expressions, etc. advanced rules, thereby flexibly adapting to different data screening scenarios.

[0055] In some embodiments, the terminal device 110 can provide a visual presentation of the operation data corresponding to at least one collection point matching a first keyword in the user interface in response to a first filter condition in the at least one filter condition indicating filtering based on the first keyword.

[0056] For example, the terminal device 110 can perform data filtering based on a keyword received in the user interface. The terminal device 110 can process the received keyword as a normal text string and search for content containing the keyword in the name (or parameter field) of all collection points. If there is operation data matching the keyword, the terminal device 110 can provide a visual presentation of the operation data matching the keyword in the user interface. Alternatively or additionally, the terminal device 110 can add the filter condition to the user interface in the form of a general filter label. The user 140 can control whether to enable or cancel the keyword matching-based filtering logic by clicking the label.

[0057] As an example, Figure 4A schematic diagram of an example interface 400A showing a visualized presentation of operation data according to some embodiments of the present disclosure is shown. If the terminal device 110 receives the keyword "realtime_click", operation data matching the keyword string can be presented in the interface 400A, and a filter label 401 corresponding to the filter condition can be added in the interface. The filter label 401 can have a visual style corresponding to the filter mode of "keyword matching", for example, the color of the filter label 401 is white. When the filter label 401 is in an active state, the terminal device 110 can present in the interface 400A only operation data of the collection points matching the keyword.

[0058] In some embodiments, the terminal device 110 can provide in the user interface a visualized presentation of operation data corresponding to collection points other than a collection point matching a second keyword for filtering in response to a second filter condition of the at least one filter condition indicating a cutoff filtering and the second keyword for filtering.

[0059] For example, the terminal device 110 can trigger a cutoff filtering operation for a filter label in the interface (which can be a filter label corresponding to any filter mode) in response to an interaction operation (such as clicking the label five times) on the filter label. In the cutoff filtering mode, operation data of the collection points related to the filter label will be excluded from the data presentation result. This filter mode can be suitable for operation data that has low debugging value but frequently appears and affects the overall data presentation effect.

[0060] For example, if operation data of the collection points corresponding to the filter label 405 with the name "track_url" is frequently reported and affects data readability, the user 140 can activate the cutoff filtering state of the filter label 405 by clicking the filter label 405 continuously multiple times. The terminal device 110 can present in the user interface operation data of collection points other than the collection point with the name including "track_url", thereby improving the focus and readability of the data. The filter label 405 can have a visual style corresponding to the filter mode of "cutoff filtering", for example, the color of the filter label 405 is black and includes an exclusion mark.

[0061] In some embodiments, the terminal device 110 can provide in the user interface a visualized presentation of operation data corresponding to at least one collection point matching a regular expression of a plurality of collection points in response to a third filter condition of the at least one filter condition indicating a regular expression based filtering.

[0062] For example, the user 140 can input a filter condition including a regular expression (e.g., containing wildcards, logical OR, prefix / suffix, etc.) via the input control. The terminal device 110 can parse the input in a regular matching manner and present the operation data of the collection points that meet the filter condition in the user interface. In addition, the terminal device 110 can also add a filter tab corresponding to the filter condition in the user interface, which can be used to quickly trigger the filtering manner of the regular expression. For example, the user inputs the regular expression "video.*play". The terminal device 110 can filter the operation data of the collection points with names such as "videoplay", "video_autoplay", "video_manual_play", etc., and present the matching results in the user interface. Further, the terminal device 110 can add a filter tab 402 at the top of the interface 400A. The visual style of the filter tab 402 can be yellow, indicating that the filter condition based on the regular expression is in an activated state.

[0063] In some embodiments, the terminal device 110 can present, in the user interface, a visual presentation of the operation data corresponding to at least one collection point of the plurality of collection points including a field indicated by the field expression in response to a fourth filter condition of the at least one filter condition indicating filtering based on the field expression.

[0064] For example, the terminal device 110 can perform refined data filtering based on a structured expression (e.g., "field name = field value") received in the user interface. This filtering manner is suitable for refined filtering in scenarios where there are a large number of different parameter values under the same event name. For example, the user 140 wants to view only the data of the collection points related to advertisements. At this time, the user 140 can input the field expression "is_ad_event = 1" via the input control to filter out the collection points with the value of the field is_ad_event being 1 and present the filtered operation data in the user interface. The terminal device 110 can add a filter tab 403 in the top tab bar. The visual style of the filter tab 403 can be pink, indicating that the filter condition based on the field expression is in an activated state.

[0065] In some examples, each filter tag supports a toggle interaction behavior. For example, after the user 140 clicks a filter tag, the filter condition corresponding to the filter tag takes effect immediately, and the terminal device 110 can refresh the user interface according to the condition and present the operation data that matches the condition. The filter tag in the activated state is usually displayed in a highlighted color, for example, a label in yellow, white, pink, or the like, corresponding to different filter conditions. When the user 140 clicks the activated filter tag again, the terminal device 110 can temporarily cancel the filter condition and restore the display of unfiltered operation data. At this time, the filter tag (for example, the filter tag 404) can be displayed in a gray state, indicating that the filter condition corresponding to the tag is not activated. If the user 140 clicks the filter tag in the gray state again, the terminal device 110 can re-enable the corresponding filter condition, restore the visual style of the filter tag to the style in the activated state, and restore the display of the data filtered according to the condition in the user interface.

[0066] In some embodiments, the parameter information of the collection point can include a field of a nested dictionary (object) type. In this case, the terminal device 110 can present a detail control (for example, the control 413) in the user interface. In response to the triggering of the control 413 by the user 140, the terminal device 110 can expand and present the content of the subfield included in the field, for example, a nested key-value pair, an array, or a deeper structure.

[0067] In some embodiments, the terminal device 110 can support the operation of performing focused presentation on a certain collection point and operation data. For example, in response to the user double-clicking the name of a target collection point presented in the interface, the terminal device 110 can display the operation data of the target collection point in the interface in focus and can selectively hide the operation data of other non-target collection points.

[0068] In some embodiments, the terminal device 110 can set a code breakpoint for a target collection point in response to the breakpoint setting operation on the target collection point that meets the filter condition among a plurality of collection points. The code breakpoint is used to trigger a pause when the application runs to the position of the target collection point. Further, the terminal device 110 can provide the setting information of the code breakpoint to the code debugging environment of the application.

[0069] During the running of the application, when the execution flow runs to the position of the collection point where the code breakpoint is set, a debugging pause can be triggered to allow the developer or tester to view the current context state, variable value, call stack, and the like, thereby assisting in problem positioning and function verification. After the code breakpoint is triggered, the terminal device 110 can synchronize the setting information of the breakpoint to the currently connected code debugging environment, to realize the linkage at the level of the debugging tool, so that the debugging operation can be directly jumped to the source code position when the breakpoint is hit.

[0070] In some embodiments, the breakpoint setting operation is triggered by a first operation on a filter control indicating a filter condition. For example, in the filter tab area at the top of interface 400A, each filter tab can correspond to a filter condition. When user 140 long-presses filter tab 406, terminal device 110 can interpret the user operation as a breakpoint setting request, and in turn set a code breakpoint on one or more collection points whose names include “splash_ad”. In response to the collection point corresponding to filter tab 406 being set with a breakpoint, terminal device 110 can present filter tab 406 as a tab with a corresponding visual style. For example, filter tab 406 is colored blue, and filter tab 406 is shaped as the shape of a filter tab with a set code breakpoint.

[0071] In some embodiments, in response to a second trigger on a filter control indicating a filter condition, terminal device 110 can cancel the setting of a code breakpoint on a target collection point. For example, when user 140 clicks on filter tab 406 again, terminal device 110 can undo the code breakpoint previously set on the collection point corresponding to filter tab 406, and restore the visual style of filter tab 406 to that of a general filter tab. In this way, dynamic management of breakpoint states and flexible control of debugging processes can be achieved.

[0072] In some embodiments, terminal device 110 can persistently store and manage one or more filter conditions set by user 140 based on the user interface. For example, when user sets a keyword, regular expression, field expression, or other filter condition based on a filter control in the interface, terminal device 110 can write these filter conditions and their states (e.g., whether enabled, whether set with a breakpoint) as configuration items to a local storage area. When the application is launched again and enters the visualized user interface, terminal device 110 can automatically read the locally saved filter configuration content and restore it to the user interface, e.g., reactivating filter tabs that are enabled, restoring data presentation results under filter states, etc., thereby achieving seamless continuation of user debugging logic.

[0073] In some embodiments, terminal device 110 can provide data interaction functions including copying and exporting on operation data of collection points. For example, in response to a long-press operation on name 411 of a collection point presented in interface 400A, terminal device 110 can copy all operation data of the collection point. For another example, in response to a long-press operation on a certain field 412 in parameter information of a collection point presented in interface 400A, terminal device 110 can copy the parameter value corresponding to field 412.

[0074] Continuing to refer to Figure 4In response to triggering of the export control 414, the terminal device 110 can export all operation data presented in the current interface in unification. For example, the terminal device 110 can format all operation data under the current filtering result and package as a standard data file. The exported data file can adopt a standard data format, contain the name, parameter information, category, timestamp, and the like of each collection point, and have good readability and compatibility.

[0075] In summary, according to various embodiments of the present disclosure, by performing operation data acquisition and visualized presentation locally at the terminal device, real-time capture and visualized presentation of data collected by multiple collection points in the application running process are achieved, and the real-time performance and stability of data verification and testing are effectively improved. In addition, by supporting multiple filtering modes based on keywords, regular expressions, and field expressions, and providing interactive filtering control and breakpoint debugging settings through different filtering controls, flexible analysis requirements in complex debugging scenarios can be met. In this way, a better operation experience can be provided for users.

[0076] Embodiments of the present disclosure also provide a corresponding apparatus for implementing the above method or process. Figure 5 A schematic structural block diagram of an apparatus 500 for data presentation is shown according to some embodiments of the present disclosure. The apparatus 500 can be implemented as or included in the terminal device 110. Various modules / components in the apparatus 500 can be implemented by hardware, software, firmware, or any combination thereof.

[0077] Reference is made to Figure 5 As shown, the apparatus 500 includes a data acquisition module 510 configured to acquire operation data corresponding to an application running on a terminal device, the operation data including operation data collected from multiple collection points inserted in the application during running of the application; and a data presentation module 520 configured to, in response to a presentation request for the operation data of the application, provide visualized presentation of the operation data in a user interface of the application, wherein the visualized presentation includes presenting at least one of the name, category, parameter information, and collection time of each of the multiple collection points.

[0078] In some embodiments, the apparatus 500 further includes a filtering module configured to provide a filtering control for the operation data in the user interface; and in response to triggering of the filtering control, provide visualized presentation of filtered operation data in the user interface based on at least one filtering condition determined via the filtering control.

[0079] In some embodiments, the filtering control includes at least one of: an input control for receiving a filtering condition, or at least one filter tag indicative of a respective filtering condition, wherein selection of the at least one filter tag is indicative of triggering of the respective filtering condition.

[0080] In some embodiments, the at least one filter tag is determined by at least one of: presenting one or more predetermined filter tags at the user interface; or presenting at least one filter tag corresponding to the received at least one filtering condition respectively at the user interface in response to the received at least one filtering condition via the input control.

[0081] In some embodiments, at least one filter tag corresponding to different filtering conditions has different visual styles.

[0082] In some embodiments, the data presentation module 520 is further configured to, in response to a first filtering condition in the at least one filtering condition being indicative of filtering based on a first keyword, provide in the user interface a visual presentation of operational data corresponding to at least one of the plurality of collection points matching the first keyword; or in response to a second filtering condition in the at least one filtering condition being indicative of a cut-off filtering and a second keyword for filtering, provide in the user interface a visual presentation of operational data corresponding to the plurality of collection points except for the collection points matching the second keyword.

[0083] In some embodiments, the data presentation module 520 is further configured to, in response to a third filtering condition in the at least one filtering condition being indicative of filtering based on a regular expression, provide in the user interface a visual presentation of operational data corresponding to at least one of the plurality of collection points matching the regular expression; or in response to a fourth filtering condition in the at least one filtering condition being indicative of filtering based on a field expression, present in the user interface a visual presentation of operational data corresponding to at least one of the plurality of collection points including a field indicated by the field expression based on the filtering condition determined via the filtering control.

[0084] In some embodiments, the apparatus 500 further comprises a breakpoint setting module configured to, in response to a breakpoint setting operation on a target collection point of the plurality of collection points that meets a filtering condition, set a code breakpoint at the target collection point, the code breakpoint being used to trigger a pause when the application runs to the target collection point; and provide setting information of the code breakpoint to a code debugging environment of the application.

[0085] In some embodiments, the breakpoint setting operation is triggered by a first operation on a filter control indicative of the filter condition, and the breakpoint setting module is further configured to, in response to a second operation on the filter control indicative of the filter condition, cancel the setting of the code breakpoint at the target collection point.

[0086] In some embodiments, the presentation request for operational data of an application is determined by: presenting an entry of the user interface by the application; and in response to a triggering of the entry, determining the presentation request for the operational data of the application.

[0087] Figure 6 A block diagram of an electronic device 600 in which one or more embodiments of the disclosure can be implemented is shown. The electronic device 600 may, for example, be used to implement a terminal device 110 as shown in Figure 1 It should be understood that the electronic device 600 shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments described herein. Figure 6

[0088] Referring to Figure 6 , the electronic device 600 is in the form of a general electronic device. Components of the electronic device 600 can include, but are not limited to, one or more processing units or processors 610, memory 620, storage 630, one or more communication units 640, one or more input devices 650, and one or more output devices 660. The processor 610 can be a real or virtual processor and is capable of performing various processing according to programs stored in the memory 620. In a multi-processor system, multiple processors perform computer-executable instructions in parallel to improve the parallel processing capability of the electronic device 600.

[0089] The electronic device 600 typically includes a number of computer storage media. Such media can be any available media that is accessible by the electronic device 600 and includes both volatile and non-volatile media, removable and non-removable media. The memory 620 can be a volatile memory (e.g., registers, cache, random access memory (RAM)), a non-volatile memory (e.g., read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof. The storage 630 can be a removable or non-removable media and can include machine-readable media, such as a flash drive, a magnetic disk drive, or any other media that can be used to store information and / or data and that can be accessed by the electronic device 600.

[0090] The electronic device 600 can further include additional removable / non-removable, volatile / non-volatile storage media. Although not shown, the electronic device 600 can further include a data store 670 that can be employed to store data and / or information as described herein. Additionally, the electronic device 600 can include a graphics processing unit (GPU) 680 that can be employed to render graphics and / or other data as described herein. Figure 6 ​As shown in FIG. 12, a disk drive 621 or CD drive 622 can be provided that enable reading from or writing to a removable, non- volatile disk, such as a "floppy drive" or a "click-together" CD or DVD drive. In these instances, each drive can be connected to the system bus 620 by one or more data media interfaces. The memory 620 can include a computer program product 625 having one or more program modules configured to carry out the various methods or actions of the various embodiments of the present disclosure.

[0091] The communication unit 640 enables communication with other electronic devices over a communication medium. Additionally, the functionality of the components of the electronic device 600 can be implemented in a single computing cluster or a plurality of computer machines that are capable of communicating with one another over a communication connection. As such, the electronic device 600 can operate in a networked environment using logical connections to one or more other servers, network personal computers (PCs), or another network nodes in the networking environment.

[0092] The input device 650 can be one or more input devices, such as a mouse, a keyboard, a trackball, etc. The output device 660 can be one or more output devices, such as a display, a speaker, a printer, etc. The electronic device 600 can also communicate with one or more external devices (not shown), such as a storage device, a display device, etc., through the communication unit 640, as needed, with one or more devices that enable a user to interact with the electronic device 600, or with any devices (e.g., a network card, a modem, etc.) that enable the electronic device 600 to communicate with one or more other electronic devices. Such communication can be carried out via an input / output (I / O) interface (not shown).

[0093] According to an example implementation of the present disclosure, a computer readable storage medium is provided having computer executable instructions stored thereon, where the computer executable instructions are executed by a processor to implement the method described above. According to an example implementation of the present disclosure, a computer program product is also provided that is tangibly stored on a non-transitory computer readable medium and includes computer executable instructions, where the computer executable instructions are executed by a processor to implement the method described above.

[0094] Various aspects of the disclosure are now described with reference to the drawings. In general, the drawings described below are diagrammatic and schematic representations of actual or conceptual structures and processes, and as such, they are not drawn to scale. Certain aspects of the disclosure are described in the context of methods, apparatus, devices, and computer program products implemented in accordance with the present disclosure. It should be appreciated that computer-readable program instructions can be loaded onto a computer, other programmable data processing apparatus, or other processing machines to produce a machine, such that the computer-readable program instructions which execute on the computer or other programmable data processing apparatus create a means for implementing the functions specified in the flow diagrams and / or block diagrams.

[0095] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine such that when these instructions are executed by the processor of the computer or other programmable data processing device, a device is generated that implements the functions / actions specified in one or more blocks in the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium, where these instructions cause the computer, programmable data processing device, and / or other device to operate in a specific manner. Thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing various aspects of the functions / actions specified in one or more blocks in the flowchart and / or block diagram.

[0096] Computer-readable program instructions can be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operational steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to implement the functions / actions specified in one or more boxes in the flowchart and / or block diagram.

[0097] The flow charts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the systems, methods and computer program products according to multiple implementations of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a part for a module, program segment or instruction, and a part for a module, program segment or instruction comprises one or more executable instructions for realizing the logical function of the specification. In some alternative implementations, the functions marked in the box can also occur in a sequence different from that marked in the accompanying drawings. For example, two continuous boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flow chart, and the combination of the boxes in the block diagram and / or flow chart can be realized by a special hardware-based system that performs the function or action of the specification, or can be realized by a combination of special hardware and computer instructions.

[0098] While various implementations of the present disclosure have been described above, the foregoing description is intended to be illustrative, non-exhaustive, and not limited to the disclosed implementations. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described implementations. The terminology used herein is intended to best explain the principles of the implementations, their practical applications, or improvements to existing technologies, or to enable others skilled in the art to understand the various implementations disclosed herein.

Claims

1. A method for data presentation, comprising: Acquiring operation data corresponding to an application running on a terminal device, the operation data including operation data collected from a plurality of collection points inserted into the application during the running of the application; and In response to a request to present the operation data of the application, a visual presentation of the operation data is provided in a user interface of the application, wherein the visual presentation includes presenting at least one of the names, categories, parameter information, and collection times of each of the plurality of collection points.

2. The method according to claim 1, further comprising: providing a filter control for the operation data in the user interface; as well as In response to triggering of the filter control, a visual presentation of filtered operational data is provided in the user interface based on at least one filter condition determined via the filter control.

3. The method according to claim 2, wherein the filter control comprises at least one of the following: An input control to receive the filter criteria, or At least one filter tag indicating a corresponding filter condition, wherein selection of the at least one filter tag indicates triggering of the corresponding filter condition.

4. The method of claim 3, wherein the at least one filter tag is determined by at least one of: Presenting one or more predetermined filter tags on the user interface; or In response to at least one filter condition received via the input control, at least one filter tag corresponding to the at least one filter condition is presented on the user interface. The method according to claim 3 , wherein at least one filter label corresponding to different filter conditions has a different visual style.

6. The method of claim 2, wherein providing a visual presentation of the filtered operational data in the user interface comprises: In response to a first filtering condition among the at least one filtering condition indicating filtering based on a first keyword, providing, in the user interface, a visual presentation corresponding to the operation data of at least one collection point among the plurality of collection points that matches the first keyword; or In response to a second filtering condition in the at least one filtering condition indicating a cutoff filtering and a second keyword for filtering, providing in the user interface a visual presentation of operation data corresponding to other collection points among the plurality of collection points except the collection point matching the second keyword.

7. The method according to claim 2, wherein providing a visual presentation of filtered operational data in the user interface based on the filtering condition determined via the filtering control further comprises: In response to a third filtering condition among the at least one filtering condition indicating filtering based on a regular expression, providing, in the user interface, a visual presentation corresponding to the operation data of at least one collection point among the plurality of collection points that matches the regular expression; or In response to a fourth filter condition in the at least one filter condition indicating filtering based on a field expression, a visual presentation of operation data corresponding to at least one collection point in the plurality of collection points including the field indicated by the field expression is presented in the user interface.

8. The method according to claim 1, further comprising: In response to a breakpoint setting operation on a target collection point that meets the filtering conditions among the multiple collection points, setting a code breakpoint for the target collection point, the code breakpoint being used to trigger a pause when the application runs to the target collection point; as well as The setting information of the code breakpoint is provided to a code debugging environment of the application.

9. The method according to claim 8, wherein the breakpoint setting operation is triggered by a first operation on a filter control indicating the filter condition, and the method further comprises: In response to a second triggering of the filter control indicating the filter condition, the setting of the code breakpoint at the target acquisition point is canceled.

10. The method of claim 1 , wherein the request for presentation of operational data for an application is determined by: Presenting an entry to the user interface in the application; and In response to triggering the portal, a presentation request for the operational data of the application is determined.

11. A device for data presentation, comprising: a data acquisition module configured to acquire operation data corresponding to an application running on a terminal device, wherein the operation data includes operation data collected from a plurality of collection points inserted into the application during the running of the application; as well as a data presentation module configured to, in response to a presentation request for the operation data of the application, provide a visual presentation of the operation data in a user interface of the application, wherein the visual presentation includes presenting at least one of the names, categories, parameter information, and collection times of each of the plurality of collection points.

12. An electronic device comprising: at least one processor; as well as At least one memory coupled to the at least one processor and storing instructions for execution by the at least one processor, the instructions causing the electronic device to perform the method according to any one of claims 1 to 10 when executed by the at least one processor.

13. A computer-readable storage medium having computer-executable instructions stored thereon, wherein the computer-executable instructions can be executed by a processor to implement the method according to any one of claims 1 to 10.

14. A computer program product comprising computer executable instructions, wherein the computer executable instructions, when executed by a processor, implement the method according to any one of claims 1 to 10.

Images