Method and device for displaying buried point information, server and storage medium

Abstract

The application provides a method and device for displaying buried point information, a server and a storage medium. The method comprises the following steps: in response to receiving a display request of buried point information, the display request carrying a user identifier of a target user and a display scene requirement; based on the display scene requirement and the user identifier, target buried point information of the target user is obtained from a buried point information database; the target buried point information is subjected to Mock virtual processing to obtain buried point display information adapted to a virtual machine; and the buried point display information is pushed to the virtual machine, and the buried point display information is displayed through the virtual machine. The embodiment of the application can display the buried point information in the form of a page, and compared with only displaying link information, the visual effect of the buried point information is improved.

Description

Technical Field

[0001] This invention relates to the field of Internet technology, and in particular to a method, device, server, and storage medium for displaying embedded information. Background Technology

[0002] With the development of internet technology, the number of applications providing services to users is increasing. These applications can record user actions and generate event tracking information for that user. When it's necessary to analyze user behavior, the event tracking information can be retrieved and displayed first, and then the user can be analyzed based on the displayed results.

[0003] In existing technologies, user tracking information is stored in a columnar database, with one tracking information corresponding to one user. When it is necessary to retrieve the tracking information of a target user, the tracking information corresponding to multiple operations of that target user within the application can be retrieved from the database and displayed.

[0004] The inventors found that the existing technology has at least the following technical problems: when the target user has a lot of operations, the number of tracking points corresponding to the target user is also large. However, the tracking points are backend data, which requires staff to analyze each tracking point one by one, which is time-consuming and laborious, resulting in low efficiency in analyzing user behavior. Summary of the Invention

[0005] This invention provides a method, device, server, and storage medium for displaying embedded information, which can improve the efficiency of analyzing user operation behavior.

[0006] In a first aspect, the present invention provides a method for displaying embedded information, comprising:

[0007] In response to receiving a display request for the embedded information, the display request carries the user identifier of the target user and the display scenario requirements;

[0008] Based on the display scenario requirements and the user identifier, the target tracking information of the target user is obtained from the tracking information database;

[0009] The target tracking information is subjected to Mock virtual processing to obtain tracking display information adapted to the virtual machine;

[0010] The event tracking information is pushed to a virtual machine, and the event tracking information is displayed through the virtual machine.

[0011] In one possible design, obtaining the target tracking information of the target user from the database based on the display scenario requirements and the user identifier includes:

[0012] Based on the requirements of the aforementioned display scenario, the target time period for acquiring the data tracking information is determined.

[0013] Using the user identifier and the target time period as search criteria, the target user's target tracking information within the target time period is retrieved from the database.

[0014] In one possible design, determining the target time period for acquiring the tracking information based on the display scenario requirements includes:

[0015] If the display scenario requires the display of the target user's operational behavior within a preset time period, then the preset time period shall be used as the target time period.

[0016] If the display scenario requirement is to display an operation scenario involving an abnormal operation request, then the processing time period for handling the abnormal operation request is determined, and the processing time period is taken as the target time period.

[0017] In one possible design, each operation request requires processing by multiple service nodes; determining the processing time period for handling the abnormal operation request includes:

[0018] Obtain the operation type identifier corresponding to the abnormal operation request;

[0019] Based on the operation type identifier, determine multiple service nodes corresponding to the abnormal operation request and the processing order of the multiple service nodes;

[0020] According to the processing order of the plurality of service nodes, the target service node and the upstream service node of the target service node are selected from the plurality of service nodes, wherein the upstream service node is the service node preceding the target service node;

[0021] The processing time period of the target service node and the processing time period of the upstream service node are combined to obtain the processing time period for processing the abnormal operation request.

[0022] In one possible design, each operation request requires processing by multiple service nodes; the event tracking information includes node logs of multiple service nodes corresponding to multiple operation requests of the target user within a target time period.

[0023] The step of pushing the event tracking information to a virtual machine and displaying the event tracking information through the virtual machine includes: determining the operation order of multiple operation requests from a target user within a target time period; pushing the node logs of multiple service nodes corresponding to the multiple operation requests to the virtual machine according to the operation order; the virtual machine receiving the node logs of the multiple service nodes and dynamically displaying the event tracking information according to the receiving order of the node logs of the multiple service nodes.

[0024] In one possible design, the embedded information includes the node logs of the target service node and the node logs of the upstream service node.

[0025] The step of pushing the event tracking information to a virtual machine and displaying the event tracking information through the virtual machine includes:

[0026] The node logs of the target service node and the node logs of the upstream service node are pushed to the virtual machine, and the embedded point display information is statically displayed through the virtual machine.

[0027] One possible design also includes:

[0028] In response to receiving an operation request from any user, the user identifier of the user and multiple service nodes corresponding to the operation request are obtained;

[0029] Generate node logs for the processing of the operation requests by the multiple service nodes;

[0030] The user identifier is associated with and stored in the node logs corresponding to the multiple service nodes to obtain the data entry information database.

[0031] Secondly, the present invention provides a device for displaying embedded information, comprising:

[0032] The receiving module is used to respond to a display request for received embedded information, wherein the display request carries the user identifier of the target user and the target time period;

[0033] The acquisition module is used to acquire target tracking information from the tracking information database based on the user identifier and the target time period;

[0034] The information processing module is used to perform Mock virtual processing on the target embedding information to obtain embedding display information adapted to the virtual machine;

[0035] The display module is used to push the event tracking information to a virtual machine and display the event tracking information through the virtual machine.

[0036] Thirdly, the present invention provides a server, comprising: at least one processor and a memory;

[0037] The memory stores computer-executed instructions;

[0038] The at least one processor executes the computer execution instructions stored in the memory, causing the at least one processor to perform the method for displaying embedded information as described in the first aspect and various possible designs of the first aspect.

[0039] Fourthly, the present invention provides a computer storage medium storing computer execution instructions, wherein when a processor executes the computer execution instructions, the method for displaying embedded information as described in the first aspect and various possible designs of the first aspect is implemented.

[0040] Fifthly, this application also provides a computer program product, which includes a computer program stored in a computer-readable storage medium. At least one processor can read the computer program from the computer-readable storage medium. When the at least one processor executes the computer program, it implements the method for displaying embedded information as described in the first aspect and various possible designs of the first aspect.

[0041] The present invention provides a method, apparatus, server, and storage medium for displaying event tracking information. Upon receiving a request to display event tracking information, the system first obtains the user's event tracking information based on the display scenario requirements and search conditions corresponding to the user identifier. Then, it performs mock processing on the event tracking information and displays it through a virtual machine. Therefore, the present invention can display the user's event tracking information in a page format, improving the visualization effect of the event tracking information compared to simply displaying backend event tracking data, thereby increasing the efficiency of analyzing user behavior. Attached Figure Description

[0042] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0043] Figure 1 This is a schematic diagram illustrating an application scenario of the method for displaying embedded information provided in an embodiment of the present invention;

[0044] Figure 2 A flowchart illustrating the method for displaying embedded information provided in this embodiment of the invention. Figure 1 ;

[0045] Figure 3 A flowchart illustrating the method for displaying embedded information provided in this embodiment of the invention. Figure 2 ;

[0046] Figure 4 A flowchart illustrating the method for displaying embedded information provided in this embodiment of the invention. Figure 3 ;

[0047] Figure 5 This is a schematic diagram of the structure of the device for displaying embedded information provided in an embodiment of the present invention;

[0048] Figure 6 This is a schematic diagram of the hardware structure of a server provided in an embodiment of the present invention. Detailed Implementation

[0049] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0050] The collection, storage, use, processing, transmission, provision, and disclosure of information such as embedded point information, image data, or user data involved in the technical solution of this application all comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0051] With the development of internet technology, the number of applications providing services to users is increasing. These applications can record user actions and generate event tracking information for that user. When it's necessary to analyze user behavior, the event tracking information can be retrieved and displayed first, and then the user can be analyzed based on the displayed results.

[0052] User event tracking information can be stored within a microservice architecture. Microservice architecture refers to an architecture and organizational method for software development that uses services as the basic functional units, achieved through container technology. While it addresses the high coupling, high maintenance costs, and high iteration costs of monolithic architectures, it also introduces other problems. Due to the finer granularity of functional units, the service call chain inevitably lengthens. This not only increases the difficulty of troubleshooting service issues but can also lead to a service avalanche effect (i.e., a problem at one service node in the chain can spread to other upstream and downstream service nodes). Therefore, establishing a logging chain for the entire service chain and monitoring each service node in the chain is particularly important, as it allows us to have a holistic understanding of the service chain.

[0053] As business volume increases, a single service instance or cluster becomes insufficient to handle service tasks. Therefore, distributed clusters are used to improve service capabilities and enhance the disaster recovery and fault tolerance of service instances or clusters. In related technologies, user event tracking information is stored in a columnar database, where the service nodes within the tracking information are distributed. Each user corresponds to one event tracking record in the columnar database. When retrieving the event tracking information of a target user, the database can be used to retrieve event tracking information corresponding to multiple operations performed by that target user within the application, and this information can be displayed. However, when a target user performs many operations, the number of event tracking records corresponding to that user also increases. Since this event tracking information is backend data, staff must analyze each record individually, which is time-consuming and labor-intensive, resulting in low efficiency in analyzing user behavior.

[0054] To address the aforementioned technical problems, this invention proposes the following technical concept: When a request to display event tracking information is received, the invention first obtains the user's event tracking information based on the display scenario requirements and the search conditions corresponding to the user identifier. Then, the event tracking information undergoes mock processing, and the information is displayed through a virtual machine. Therefore, this invention can display the user's event tracking information in a page format, improving the visualization effect of the event tracking information compared to simply displaying backend event tracking data, thereby increasing the efficiency of analyzing user behavior. Detailed embodiments are described below.

[0055] Figure 1 This is a schematic diagram illustrating an application scenario of the method for displaying embedded information provided in an embodiment of the present invention. For example... Figure 1 As shown, when it's necessary to obtain the target user's operational habits within the application, the user can trigger a request to display the event tracking information. Alternatively, when a user's operation is abnormal and it's necessary to obtain the event tracking information corresponding to the abnormal operation for analysis, the user can trigger a request to display the event tracking information.

[0056] Display terminal 101 receives a user's request to display event tracking information triggered by an application, and transmits the request to server 102 via a wireless network. Server 102 receives the request and determines the event tracking information adapted to the virtual machine (e.g., display terminal 101). Server 102 returns the event tracking information to display terminal 101, and the event tracking information is displayed on display terminal 101.

[0057] Figure 2 A flowchart illustrating the method for displaying embedded information provided in this embodiment of the invention. Figure 1 The execution entity in this embodiment can be Figure 1 The server in the illustrated embodiment is not specifically limited in this embodiment. Figure 2As shown, the method includes:

[0058] S201. In response to receiving a request to display the embedded information, the display request carries the user identifier of the target user and the display scenario requirements.

[0059] In this embodiment of the invention, the target user is either a user whose operation is abnormal, or a user whose operational habits are intended to be obtained. The user identifier can be a symbol that can distinguish different users, such as a username, user phone number, or user ID.

[0060] Among these, event tracking information is used to record user action logs. For example, event tracking information includes actions such as opening a webpage or clicking a button.

[0061] S202. Based on the display scenario requirements and user identifiers, obtain the target user's target tracking information from the tracking information database.

[0062] In this embodiment of the invention, user event tracking information can be stored in an event tracking information database via a Kafka queue. Each user operation request requires processing by multiple service nodes, and the event tracking information can include node logs from these service nodes recording the processing of the operation request. Each service node has different functionalities; the node logs can include the process of processing or transforming the data in the operation request, as well as the timestamps corresponding to each step of processing or transformation. In this step, the target event tracking information obtained from the event tracking information database can meet the needs of different display scenarios. For example, the display scenario requirement can be the display of user operation behavior or the display of abnormal user operations.

[0063] S203. Perform Mock virtual processing on the target tracking information to obtain tracking display information adapted to the virtual machine.

[0064] In this embodiment of the invention, Mock processing enables the reproduction of production service operations and troubleshooting in a test environment. When operation reproduction is required, the user view layer Mock is combined with the cloud infrastructure's tracking information to obtain tracking display information adapted to the virtual machine. When troubleshooting is required, service troubleshooting Mock is used to virtually process the node data of upstream service nodes in the tracking information to obtain tracking display information adapted to the virtual machine. It should be noted that the node data before virtual processing is encrypted data. The node data after virtual processing is unencrypted data in JSON format.

[0065] S204. Push the event tracking information to the virtual machine and display the event tracking information through the virtual machine.

[0066] In this embodiment of the invention, the combined tracking information can be pushed to a virtual machine using WebRTC (Web Real-Time Communications) technology. The tracking information can then be displayed in real time on the virtual machine, enabling the dynamic reproduction of real-time scenarios in the user's production environment or the reproduction of abnormal issues in the test environment.

[0067] The present invention provides a method for displaying event tracking information. When a request to display event tracking information is received, the method first obtains the user's event tracking information based on the display scenario requirements and the search conditions corresponding to the user identifier. Then, the event tracking information is processed using a mock virtual machine, and the event tracking information is displayed through a virtual machine. Therefore, the present invention can display the user's event tracking information in a page format, which improves the visualization effect of event tracking information compared to only displaying backend event tracking data, thereby improving the efficiency of analyzing user behavior.

[0068] Figure 3 A flowchart illustrating the method for displaying embedded information provided in this embodiment of the invention. Figure 2 In this embodiment of the invention, in Figure 2 Based on the provided embodiments, section S202 details the specific implementation method for obtaining target user tracking information from the database based on display scenario requirements and user identifiers. For example... Figure 3 As shown, the method includes:

[0069] S301. Based on the requirements of the display scenario, determine the target time period for the data tracking information that needs to be acquired.

[0070] In this embodiment of the invention, the display scenario requirements include displaying user operation behavior and displaying abnormal operation. Accordingly, this step is as follows: if the display scenario requirement is to display the target user's operation behavior within a preset time period, then the preset time period is taken as the target time period; if the display scenario requirement is to display the operation scenario of an abnormal operation request, then the processing time period for handling the abnormal operation request is determined, and the processing time period is taken as the target time period.

[0071] In this embodiment of the application, the duration of the preset time period is not specifically limited; it can be 5 minutes, 10 minutes, 30 minutes, etc. For example, the preset time period is from 8:00 PM to 8:10 PM.

[0072] It should be noted that each operation request requires processing by multiple service nodes; the processing time period corresponding to the abnormal service node can be obtained. Accordingly, determining the processing time period for handling abnormal operation requests includes: obtaining the operation type identifier corresponding to the abnormal operation request; based on the operation type identifier, determining the multiple service nodes corresponding to the abnormal operation request and their processing order; according to the processing order of the multiple service nodes, selecting the last target service node and its upstream service node from among the multiple service nodes, where the upstream service node is the service node preceding the target service node; and combining the processing time period of the target service node and the processing time period of the upstream service node to obtain the processing time period for handling the abnormal operation request.

[0073] It should be noted that, from the perspective of the service node, the output of the target service node depends only on the upstream service node directly called by that target service node. If, during the investigation, it is found that the problem lies with the upstream service node directly called by the target service node, this abnormal upstream service node can be used as the new target service node. The processing time period of the new target service node can then be combined with the processing time period of the upstream service node to obtain the processing time period for handling abnormal operation requests, until the abnormal service node is identified.

[0074] In this embodiment of the application, since only the tracking information within the processing time period corresponding to the abnormal service node is obtained, the amount of data of the acquired tracking information is reduced, which facilitates the analysis of abnormal problems.

[0075] S302. Using user identifier and target time period as search criteria, retrieve target tracking information of target user within the target time period from the database.

[0076] In this embodiment of the invention, different display scenarios require different time periods for acquiring event tracking information. Optionally, the event tracking information database stores the relationships between time periods, user identifiers, and event tracking information. Accordingly, this step involves using the user identifier and the target time period as search criteria to obtain the target event tracking information of the target user within the target time period from the stored relationships between time periods, user identifiers, and event tracking information.

[0077] Since the target tracking information obtained from the tracking information database can meet the needs of different display scenarios, it not only improves the flexibility of obtaining tracking information, but also reduces the amount of tracking information obtained, thereby further improving the efficiency of analyzing user behavior.

[0078] Figure 4 A flowchart illustrating the method for displaying embedded information provided in this embodiment of the invention. Figure 3In this embodiment of the invention, each operation request requires processing by multiple service nodes; the event tracking information includes node logs of multiple service nodes corresponding to multiple operation requests from the target user within a target time period. Figure 2 Based on the provided embodiments, step S204 details the process of pushing the event tracking information to a virtual machine and displaying the event tracking information through the virtual machine. For example... Figure 4 As shown, the method includes:

[0079] S401. Determine the order of operations for multiple operation requests from the target user within the target time period.

[0080] In this embodiment of the invention, the order of multiple operation requests of a target user within a target time period can be determined based on the time sequence of multiple operation requests.

[0081] S402. In accordance with the operation sequence, push the node logs of multiple service nodes corresponding to multiple operation requests to the virtual machine.

[0082] Optionally, in the order of operations, WebRTC technology can be used to push the node logs of multiple service nodes corresponding to multiple operation requests to the virtual machine.

[0083] S403. The virtual machine receives node logs from multiple service nodes and dynamically displays the event tracking information according to the order in which the node logs from multiple service nodes are received.

[0084] In this embodiment of the invention, the receiving order of node logs from multiple service nodes is consistent with the operation order. That is, the event tracking information is dynamically displayed according to the user's operation order, thereby improving the visualization effect of the event tracking information.

[0085] In other embodiments, the event tracking information includes node logs of the target service node and node logs of the upstream service node. Correspondingly, pushing the event tracking information to a virtual machine and displaying it through the virtual machine includes: pushing the node logs of the target service node and the upstream service node to the virtual machine, and statically displaying the event tracking information through the virtual machine. Optionally, the event tracking information can be unencrypted data in JSON format.

[0086] It should be noted that the event tracking information database includes event tracking information for multiple users. Accordingly, the process of obtaining the event tracking information database includes: in response to receiving an operation request from any user, obtaining the user identifier of that user and the multiple service nodes corresponding to the operation request; generating node logs for the multiple service nodes processing the operation request; and associating and storing the user identifier with the node logs corresponding to the multiple service nodes to obtain the event tracking information database.

[0087] Optionally, the user identifier is associated with the node logs corresponding to multiple service nodes to obtain the user's event tracking information. This user's event tracking information can be stored in an event tracking information database via a Kafka queue. Each service node has different functionalities; the node logs can include the process of processing or transforming data for operation requests, as well as the timestamps corresponding to each step of processing or transformation. In other words, the event tracking information database stores the association between the user identifier, time period, and event tracking information.

[0088] Figure 5 This is a schematic diagram of the structure of the device for displaying embedded point information provided in an embodiment of the present invention. Figure 5 As shown, the device for displaying embedded information includes: a receiving module 501, an acquisition module 502, an information processing module 503, and a display module 504.

[0089] The receiving module 501 is used to respond to the received display request for the embedded information, wherein the display request carries the user identifier of the target user and the target time period;

[0090] The acquisition module 502 is used to obtain target tracking information from the tracking information database based on user identifier and target time period;

[0091] The information processing module 503 is used to perform Mock virtual processing on the target tracking information to obtain tracking display information adapted to the virtual machine;

[0092] The display module 504 is used to push the event tracking information to the virtual machine and display the event tracking information through the virtual machine.

[0093] In one possible design, the acquisition module 502 retrieves the target tracking information of the target user from the database based on the display scenario requirements and the user identifier. Specifically, this includes: determining the target time period for the tracking information to be acquired based on the display scenario requirements; and retrieving the target tracking information of the target user within the target time period from the database using the user identifier and the target time period as search criteria.

[0094] In one possible design, the acquisition module 502 determines the target time period for the tracking information to be acquired based on the display scenario requirements. Specifically, if the display scenario requirement is to display the target user's operation behavior within a preset time period, then the preset time period is used as the target time period; if the display scenario requirement is to display the operation scenario of abnormal operation requests, then the processing time period for handling abnormal operation requests is determined, and the processing time period is used as the target time period.

[0095] In one possible design, each operation request requires processing by multiple service nodes. The acquisition module 502 determines the processing time period for handling abnormal operation requests, specifically including: acquiring the operation type identifier corresponding to the abnormal operation request; based on the operation type identifier, determining the multiple service nodes corresponding to the abnormal operation request and the processing order of the multiple service nodes; according to the processing order of the multiple service nodes, selecting the last target service node and the upstream service node of the target service node from the multiple service nodes, where the upstream service node is the service node preceding the target service node; and combining the processing time period of the target service node and the processing time period of the upstream service node to obtain the processing time period for handling abnormal operation requests.

[0096] In one possible design, each operation request requires processing by multiple service nodes; the event tracking information includes node logs of multiple service nodes corresponding to multiple operation requests of the target user within a target time period; the display module 504 pushes the event tracking information to the virtual machine and displays the event tracking information through the virtual machine, specifically including: determining the operation order of multiple operation requests of the target user within the target time period; pushing the node logs of multiple service nodes corresponding to multiple operation requests to the virtual machine according to the operation order; the virtual machine receives the node logs of multiple service nodes and dynamically displays the event tracking information according to the receiving order of the node logs of multiple service nodes.

[0097] In one possible design, the event tracking information includes the node logs of the target service node and the node logs of the upstream service node; the display module 504 pushes the event tracking information to the virtual machine and displays the event tracking information through the virtual machine, specifically including: pushing the node logs of the target service node and the node logs of the upstream service node to the virtual machine, and statically displaying the event tracking information through the virtual machine.

[0098] In one possible design, a storage module is also included. This storage module, in response to receiving an operation request from any user, retrieves the user's identifier and multiple service nodes corresponding to the operation request; generates node logs for the multiple service nodes processing the operation request; and associates and stores the user identifier with the node logs corresponding to the multiple service nodes to obtain a data tracking information database.

[0099] The apparatus provided in this embodiment can be used to execute the technical solutions of the above method embodiments. Its implementation principle and technical effects are similar, and will not be described again here.

[0100] Figure 6 This is a schematic diagram of the hardware structure of a server provided in an embodiment of the present invention. Figure 6 As shown, the server in this embodiment includes: a processor 601 and a memory 602; wherein

[0101] Memory 602 is used to store instructions executed by the computer;

[0102] The processor 601 is used to execute computer execution instructions stored in the memory to implement the various steps performed by the server in the above embodiments. For details, please refer to the relevant descriptions in the foregoing method embodiments.

[0103] Alternatively, the memory 602 can be either standalone or integrated with the processor 601.

[0104] When the memory 602 is configured independently, the server also includes a bus 603 for connecting the memory 602 and the processor 601.

[0105] This invention also provides a computer storage medium storing computer execution instructions. When the processor executes the computer execution instructions, it implements the method for displaying embedded information as described in any of the above possible implementations.

[0106] This invention also provides a computer program product, including a computer program, which, when executed by a processor, implements the method for displaying embedded information as described in any of the above possible implementations.

[0107] In the several embodiments provided by this invention, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or modules, and may be electrical, mechanical, or other forms.

[0108] Furthermore, the functional modules in the various embodiments of the present invention can be integrated into one processing unit, or each module can exist physically separately, or two or more modules can be integrated into one unit. The unit composed of the above modules can be implemented in hardware or in the form of hardware plus software functional units.

[0109] The integrated modules described above, implemented as software functional modules, can be stored in a computer-readable storage medium. These software functional modules, stored in a storage medium, include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute some steps of the methods of the various embodiments of this application.

[0110] It should be understood that the aforementioned processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. A general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly manifested as being executed by a hardware processor, or executed by a combination of hardware and software modules within the processor.

[0111] The memory may include high-speed RAM, and may also include non-volatile storage (NVM), such as at least one disk storage device, and may also be a USB flash drive, external hard drive, read-only memory, disk or optical disc, etc.

[0112] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0113] The aforementioned storage medium can be implemented from any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The storage medium can be any available medium accessible to general-purpose or special-purpose computers.

[0114] An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Alternatively, the storage medium can be an integral part of the processor. Both the processor and the storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and storage medium can exist as discrete components in an electronic device or host device.

[0115] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0116] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for displaying embedded information, characterized in that, include: In response to receiving a display request for the embedded information, the display request carries the user identifier of the target user and the display scenario requirements, the display scenario requirements being the display of the target user's operation behavior within a preset time period or the display of the operation scenario for abnormal operation requests; Based on the requirements of the display scenario, the target time period for the data tracking information to be acquired is determined; wherein, when the display scenario requirement is an operation scenario display of an abnormal operation request, the target time period is determined based on the processing time period of the target service node and the processing time period of the upstream service node of the target service node, and the target service node is the node with the last processing order among the multiple service nodes corresponding to the abnormal operation request. Using the user identifier and the target time period as search criteria, the target user's target tracking information within the target time period is retrieved from the database. The target tracking information is subjected to Mock virtual processing to obtain tracking display information adapted to the virtual machine; The event tracking information is pushed to a virtual machine, and the event tracking information is displayed through the virtual machine.

2. The method according to claim 1, characterized in that, The determination of the target time period for acquiring the tracking information based on the display scenario requirements includes: If the display scenario requires the display of the target user's operational behavior within a preset time period, then the preset time period shall be used as the target time period. If the display scenario requirement is to display an operation scenario involving an abnormal operation request, then the processing time period for handling the abnormal operation request is determined, and the processing time period is taken as the target time period.

3. The method according to claim 2, characterized in that, Each operation request requires processing by multiple service nodes; The determination of the processing time period for handling the abnormal operation request includes: Obtain the operation type identifier corresponding to the abnormal operation request; Based on the operation type identifier, determine multiple service nodes corresponding to the abnormal operation request and the processing order of the multiple service nodes; According to the processing order of the plurality of service nodes, select the last target service node and the upstream service node of the target service node from the plurality of service nodes, wherein the upstream service node is the service node preceding the target service node; The processing time period of the target service node and the processing time period of the upstream service node are combined to obtain the processing time period for processing the abnormal operation request.

4. The method according to claim 2, characterized in that, Each operation request requires processing by multiple service nodes; the event tracking information includes node logs of multiple service nodes corresponding to multiple operation requests of the target user within the target time period; The step of pushing the event tracking information to a virtual machine and displaying the event tracking information through the virtual machine includes: Determine the order of multiple operation requests from a target user within a target time period; According to the operation sequence, push the node logs of the multiple service nodes corresponding to the multiple operation requests to the virtual machine; The virtual machine receives node logs from the multiple service nodes and dynamically displays the data entry information according to the order in which the node logs from the multiple service nodes are received.

5. The method according to claim 3, characterized in that, The information displayed by the tracking points includes the node logs of the target service node and the node logs of the upstream service node; The step of pushing the event tracking information to a virtual machine and displaying the event tracking information through the virtual machine includes: The node logs of the target service node and the node logs of the upstream service node are pushed to the virtual machine, and the embedded point display information is statically displayed through the virtual machine.

6. The method according to any one of claims 1-5, characterized in that, Also includes: In response to receiving an operation request from any user, the user identifier of the user and multiple service nodes corresponding to the operation request are obtained; Generate node logs for the processing of the operation requests by the multiple service nodes; The user identifier is associated with and stored in the node logs corresponding to the multiple service nodes to obtain the data entry information database.

7. A device for displaying embedded information, characterized in that, include: The receiving module is used to respond to the display request received from the embedded information. The display request carries the user identifier of the target user and the target time period. The display scenario requirement is to display the operation behavior of the target user within a preset time period or the operation scenario of abnormal operation request. The acquisition module is used to determine the target time period for the required event tracking information based on the display scenario requirements. When the display scenario requirement is an operation scenario involving an abnormal operation request, the target time period is determined based on the processing time period of the target service node and the processing time period of the upstream service node of the target service node. The target service node is the node with the last processing order among the multiple service nodes corresponding to the abnormal operation request. The module uses the user identifier and the target time period as search criteria to retrieve the target event tracking information of the target user within the target time period from the database. The information processing module is used to perform Mock virtual processing on the target embedding information to obtain embedding display information adapted to the virtual machine; The display module is used to push the event tracking information to a virtual machine and display the event tracking information through the virtual machine.

8. A server, characterized in that, include: At least one processor and memory; The memory stores computer-executed instructions; The at least one processor executes computer execution instructions stored in the memory, causing the at least one processor to perform the method for displaying embedded information as described in any one of claims 1 to 6.

9. A computer storage medium, characterized in that, The computer storage medium stores computer execution instructions. When the processor executes the computer execution instructions, it implements the method for displaying embedded information as described in any one of claims 1 to 6.

Images