Link tracking method and device, equipment and storage medium

Abstract

The invention discloses a link tracking method and device, equipment and a storage medium, and relates to the field of distributed technologies. The method comprises the following steps: determining a candidate service label of at least one candidate service scene according to service data of the at least one candidate service scene in a target distributed system; determining a target service label from the candidate service labels according to a target service scene corresponding to the target service request under the condition that the target service request of the user is identified; determining a target dyeing label of the target service request according to the target service label; and dyeing the link track of the target service request according to the target dyeing label so as to track the target service request. According to the technical scheme, the dyeing labels are self-defined in the link tracking of the distributed system, so that the problems of difficulty in link carding, difficulty in quickly judging the fault influence range and the like caused by multiple nodes and long links of the distributed system are solved, and the reliability and the accuracy of distributed link tracking can be improved.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of computer technology, in particular to the field of distributed technology, and specifically to a link tracking method, apparatus, device and storage medium. Background Art

[0002] With the rapid development of computer technology, the performance of a single system cannot meet the needs of large-scale data calculations. Complex software logic also greatly increases maintenance costs. The reliability of a single node in the face of various disasters and risks is gradually difficult to guarantee, prompting computers to enter the era of distributed systems and microservices. As the proportion of distributed services in systems in various fields increases, the logical relationship between abnormal phenomena and root causes becomes vague and difficult to find, and the difficulty of problem diagnosis increases. At the same time, distribution decomposes a complex service into multiple simple microservices, making each microservice more maintainable and more efficient, but there are more nodes to complete a complex service, and the status of each node and between nodes is difficult to guarantee, which is prone to data inconsistency.

[0003] In order to deal with problems such as root cause ambiguity and data inconsistency in a distributed environment, distributed link tracking technology was born, aiming to determine the association relationship between nodes through request-level trajectory tracking and data transparent transmission. However, distributed link tracking analyzes problems from the perspective of a single request, similar to querying the logistics track of a certain express order, but a single request cannot directly reflect the overall service status of the application or interface, and there will often be occasional, uncontrollable random outliers, which cannot accurately evaluate the actual situation of the link. Summary of the invention

[0004] The present application provides a link tracking method, apparatus, device and storage medium to improve the reliability and accuracy of distributed link tracking.

[0005] According to one aspect of the present application, a link tracking method is provided, the method comprising:

[0006] Determining a candidate business tag of the at least one candidate business scenario according to business data of the at least one candidate business scenario in the target distributed system;

[0007] When a target service request of a user is identified, determining a target service tag from the candidate service tags according to a target service scenario corresponding to the target service request;

[0008] Determining a target coloring label for the target service request according to the target service label;

[0009] The link trace of the target service request is colored according to the target coloring label to achieve tracking of the target service request.

[0010] According to another aspect of the present application, a link tracking device is provided, the device comprising:

[0011] A first label determination module, configured to determine a candidate service label of at least one candidate service scenario according to service data of at least one candidate service scenario in a target distributed system;

[0012] A tag screening module, configured to, when a target service request of a user is identified, determine a target service tag from the candidate service tags according to a target service scenario corresponding to the target service request;

[0013] A second label determination module, used to determine a target coloring label of the target service request according to the target service label;

[0014] The link tracking module is used to color the link track of the target business request according to the target coloring label to achieve tracking of the target business request.

[0015] According to another aspect of the present application, an electronic device is provided, the electronic device comprising:

[0016] one or more processors;

[0017] A memory for storing one or more programs;

[0018] When the one or more programs are executed by the one or more processors, the one or more processors implement any one of the link tracking methods provided in the embodiments of the present application.

[0019] According to another aspect of the present application, a computer-readable storage medium is provided, on which a computer program is stored. When the program is executed by a processor, any link tracking method provided in the embodiments of the present application is implemented.

[0020] According to another aspect of the present application, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, the computer program implements any one of the link tracking methods provided in the embodiments of the present application.

[0021] The present application determines the candidate business tag of at least one candidate business scenario based on the business data of at least one candidate business scenario in the target distributed system; when the target business request of the user is identified, the target business tag is determined from the candidate business tags according to the target business scenario corresponding to the target business request; the target coloring tag of the target business request is determined according to the target business tag; the link track of the target business request is colored according to the target coloring tag to track the target business request. The above technical scheme solves the problems of link combing difficulties caused by many nodes and long links in the distributed system and difficulty in quickly determining the impact scope of the fault by customizing the coloring tags in the link tracking of the distributed system, and can improve the reliability and accuracy of distributed link tracking. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 is a flow chart of a link tracking method provided according to Embodiment 1 of the present application;

[0023] Figure 2 is a flow chart of a link tracking method provided according to Embodiment 2 of the present application;

[0024] Figure 3 It is a structural diagram of a link tracking device provided according to Embodiment 3 of the present application;

[0025] Figure 4 It is a structural diagram of an electronic device that implements the link tracking method of an embodiment of the present application. DETAILED DESCRIPTION

[0026] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0027] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0028] In addition, it should be noted that the collection, storage, use, processing, transmission, provision and disclosure of candidate business scenarios, business data and other related data involved in the technical solution of this application comply with the relevant laws and regulations and do not violate public order and good morals.

[0029] Embodiment 1

[0030] Figure 1 This is a flowchart of a link tracking method provided according to the first embodiment of the present application. This embodiment is applicable to the case of full-link tracking of service requests in a distributed system, and can be executed by a link tracking device. The link tracking device can be implemented in the form of hardware and / or software. The link tracking device can be configured in a computer device, such as a server. Figure 1 As shown, the method includes:

[0031] S110. Determine a candidate business tag of at least one candidate business scenario according to business data of at least one candidate business scenario in the target distributed system.

[0032] In this embodiment, the target distributed system refers to a system based on a distributed computing architecture, in which multiple computing nodes work together through a network to achieve common business goals. Candidate business scenarios refer to a collection of specific business processes or operations in the system; for example, the "order process" or "payment process" in an e-commerce platform can be regarded as different business scenarios. Business data refers to the original data related to the candidate business scenarios; business data is the basis for supporting the analysis, identification and generation of target business tags of candidate business scenarios; among them, business data may include the entry application when the business request occurs, the business logic processing application, the business involved field, the business customer group, etc. Candidate business tags refer to tags generated based on the business data analysis results in the candidate business scenarios. These tags are used to identify specific business attributes, characteristics or behavior patterns; for example, different candidate tags can be generated based on data such as user request frequency and business operation type; these tags represent different business scenarios.

[0033] Optionally, the target distributed system may be a bank distributed system; accordingly, in combination with the business architecture under the bank distributed system, a unique business tag corresponding to the business scenario is generated according to information such as the entry application, business logic processing application, business areas, and business customer groups when the transaction occurs.

[0034] For example, taking the common bank personal transfer and remittance transactions as an example, personal transfer and remittance transactions can be initiated through three channels (counter, personal mobile banking, and ATM). Due to the different entry points for the transactions, three business tags need to be established. Each business tag will generate a dynamic transaction link under the subsequent link tracking technology.

[0035] S120: When a target service request of a user is identified, a target service tag is determined from candidate service tags according to a target service scenario corresponding to the target service request.

[0036] In this embodiment, the target business request refers to a business request initiated by a user or system that hopes to be processed; in a distributed system, the target business request usually contains information such as user operations, input parameters, and business goals; the system will match the corresponding business scenarios and tags based on the target business request. The target business scenario refers to the business process or business use case that is most relevant to the current target business request; the target business scenario is the most matching scenario selected from the candidate business scenarios after receiving the target business request. The target business tag refers to a tag screened from the candidate business tags based on the target business scenario; it identifies the characteristics or classification information of the target business request to help the system understand the nature of the request and decide how to process the request; the target business tag is usually a tag that is closely related to the target business scenario after analysis and matching.

[0037] Specifically, when the target business request of the user is identified, the target business scenario corresponding to the target business request is determined according to the entry application generated by the target business request; the target business tag is screened out from the candidate business tags using the target business scenario as an index.

[0038] In this embodiment, the entry application refers to the initial application that receives and processes the target business request; it is the direct interaction point between the user and the system, and can be a website, APP (Application), or other types of interface systems; through the entry application, the system can identify the user's request type and determine the subsequent processing flow.

[0039] S130. Determine a target coloring label of the target service request according to the target service label.

[0040] In this embodiment, the target coloring label refers to an identification label assigned to the target business request according to the target business label, which is mainly used to "color" the business request; the coloring label helps the system track the processing process of the target business request and record its path and status changes in the system.

[0041] Optionally, the target service tag is directly used as the target coloring tag of the target service request; or, a unique exclusive tag is generated for the target service request, and the target service tag is combined with the exclusive tag to obtain the target coloring tag of the target service request.

[0042] S140 . Color the link trace of the target service request according to the target coloring label to track the target service request.

[0043] In this embodiment, the link trace refers to the various service nodes, processing links and their sequence that a business request passes through from initiation to completion; the link trace is usually recorded and analyzed to help identify possible problems in the system and perform performance monitoring, troubleshooting and business analysis.

[0044] In an optional implementation, when an application on the link track changes, a version information will be configured in the application. The version information is stored in the metadata of the registration center, and an independent environment of the current version is created for it. Only the changed application needs to be deployed in the independent environment. After the coloring label passes through the changed application, if its downstream application cannot be found in the independent deployment environment, it will be automatically routed to the previous stable environment.

[0045] For example, taking personal transfer and remittance transactions under the personal mobile banking channel as an example, the entry application where the transaction occurs (i.e. the supporting application of personal mobile banking) is used as the root node to add a business tag (bizTag) field in the service method, and the bizTag field value is set to the unique tag number generated in the early stage. The traffic coloring technology is used. When the downstream application calls the service, it will synchronously inherit the bizTag field value. If there is a change in the application version in the link, the traffic coloring technology will route according to the latest changed version, and postpone it downward in sequence until the link is closed through business support application services such as personal settlement and message notification.

[0046] In another optional implementation, after the link trajectory of the target business request is dyed, the link trajectory data of the target business request is obtained; the link trajectory data refers to data collected during the dyeing process of the link trajectory according to a pre-configured fault-tolerant sampling rate; based on the link trajectory data, the target link topology map is determined.

[0047] In this embodiment, link trace data refers to the data generated by tracking the processing flow and path of the target business request during the service call process; these data record the call status, execution order, processing time, dependency and other information of each service node from the initiation to the final completion of the request. Link trace data helps to analyze and monitor the entire business process and identify potential performance bottlenecks or failure points. The fault-tolerant sampling rate refers to a proportional value used by the system when collecting link trace data, which is used to determine which request link traces should be collected; the setting of the fault-tolerant sampling rate can balance the accuracy of data collection and the performance load of the system when the system pressure is high; a lower sampling rate can reduce the system pressure, while a higher sampling rate can obtain more data, thereby improving the accuracy of the analysis. The target link topology diagram refers to a graphical representation of the dependency and call order between services in the entire system architecture; it depicts how different services, application modules, databases and other components interact and work together; in the link topology diagram, the dependency between each service can be clearly seen, helping developers or operation and maintenance personnel understand and troubleshoot the health status, performance bottlenecks and root causes of the system.

[0048] Furthermore, according to the link trajectory data, determining the target link topology map may be to parse the link trajectory data to obtain the dependency relationship and calling sequence between the candidate services; and generating the target link topology map according to the dependency relationship and calling sequence between the candidate services.

[0049] In this embodiment, dependency refers to the fact that in a microservice architecture, the implementation of a service depends on the provision of other services; for example, service A may need to call service B and service C to provide certain data or functions. Through link trajectory data, these dependencies can be identified and a dependency network between services can be constructed. The call order refers to the execution order of each service when processing a business request; through link trajectory data, the system can track the call flow of requests between different services, and then draw the call order of these services; for example, service A calls service B first, and service B calls service C, etc.

[0050] It should be noted that graphical tools or algorithms can be used to visualize the dependencies and calling sequences between candidate services to form a link topology diagram; through the link topology diagram, users can clearly see how the various services collaborate, the path of data flow, and potential risk points in the system.

[0051] It can be understood that, based on the inheritance of the original traditional distributed link tracking technology, this application transforms the original single transaction link tracking into the transaction link tracking of N transactions, increases the sampling rate setting, and makes appropriate fault tolerance for transaction interruptions caused by some transactions being affected by their own factors; it can ensure that the display of the link topology diagram is not affected by individual transaction problems and the overall link display is not affected, and highlight the faulty nodes when the link display is not missing, which is helpful for the rapid diagnosis of faulty services and their upstream and downstream relationships and impact range.

[0052] The embodiment of the present application determines the candidate business tag of at least one candidate business scenario according to the business data of at least one candidate business scenario in the target distributed system; when the target business request of the user is identified, the target business tag is determined from the candidate business tags according to the target business scenario corresponding to the target business request; the target coloring tag of the target business request is determined according to the target business tag; the link track of the target business request is colored according to the target coloring tag to track the target business request. The above technical scheme solves the problems of link combing difficulties caused by many nodes and long links in the distributed system and difficulty in quickly determining the impact scope of the fault by customizing the coloring tags in the link tracking of the distributed system, and can improve the reliability and accuracy of distributed link tracking.

[0053] Embodiment 2

[0054] Figure 2It is a flow chart of a link tracking method provided according to the second embodiment of the present application. Based on the technical solutions of the above embodiments, this embodiment refines "coloring the link track of the target business request according to the target coloring label" into "determining the label processing method of the candidate service when the target business request passes through the candidate service; the label processing method is pre-set according to the interface type of the candidate service; based on the label processing method, the candidate service is colored according to the target coloring label, and the target coloring label is continued to be passed along the link track of the target business request". It should be noted that for the parts not described in detail in the embodiments of the present application, please refer to the relevant statements of other embodiments. Figure 2 As shown, the method includes:

[0055] S210. Determine a candidate business tag of at least one candidate business scenario according to business data of at least one candidate business scenario in the target distributed system.

[0056] S220: When a target service request of a user is identified, a target service tag is determined from candidate service tags according to a target service scenario corresponding to the target service request.

[0057] S230: Determine a target coloring label of the target service request according to the target service label.

[0058] Optionally, the unique identifier of the target business request is timestamped or hashed to obtain a candidate coloring label; the target business label is combined with the candidate coloring label to obtain a target coloring label of the target business request.

[0059] In this embodiment, the unique identifier of the target business request refers to a tag used to identify a specific business request; this identifier is very important in a distributed system because it enables the system to track the life cycle of each request, especially in scenarios involving multiple service interactions; for example, in a microservice architecture, a user's request may trigger multiple service calls, and these service calls can be associated with the same request through a unique identifier. A timestamp is usually a digital tag generated based on the current time, used to record the specific time when an event or request occurs; here, the timestamp is part of the candidate coloring tag generated; the role of the timestamp is to help distinguish different requests by recording the time information of the request, especially in high concurrency scenarios, to ensure that each request can be uniquely identified. A hash function refers to a function that maps input data to a fixed-length output, and the output is usually a "hash value" or "hash code"; in a distributed system, a hash function is often used to process a request identifier to generate a relatively short hash value, which can be used as a simplified version of the identifier to help the system store and process data more efficiently. A candidate coloring tag refers to a coloring tag obtained by processing the unique identifier of the target business request through a timestamp or a hash function.

[0060] S240. When the target service request passes through the candidate service, determine the label processing mode of the candidate service; the label processing mode is pre-set according to the interface type of the candidate service.

[0061] In this embodiment, the candidate service refers to a service that may be called during the flow of the target business request; in a distributed system, a business request may pass through multiple services (such as different services in a microservice architecture), each of which is responsible for different functions; a candidate service is a service that participates in processing the request according to the path or requirements of the request in a specific business process. The label processing method refers to the rules or strategies for processing and applying the coloring labels; these processing methods are usually set based on the service interface type, the characteristics of the request, or other predefined strategies.

[0062] Exemplarily, for the http (HyperTextTransfer Protocol) entry service under spring (Spring Framework) or the dsf (Data Service Framework) entry service, by using annotations, annotate the public (access modifier) ​​method corresponding to the service of the root node of the entry application to transfer the coloring label; for java (Java Programming Language) internal methods, it is necessary to combine the annotation method with the Monitor mechanism, annotate the public methods that need to be marked, and manage the mutual exclusive access and concurrency control between multiple threads through Monitor; due to the complexity of the bank's distributed system, in addition to the common interface calls mentioned above, further research on traffic transparent transmission methods for services of other types or frameworks can be carried out. The tag value can be set using the TagUtil (Tag Utility) method. This method can realize the transparent transmission of tags for different interfaces, but because this method is nested on the business logic, the current nested service will cause it to be unable to be colored, and the transparent transmission will start from the first downstream application called downward.

[0063] It is understandable that the core of dyeing technology needs to realize full-link label transmission to adapt to different business scenarios. Different callers will use different calling interfaces; dyeing label transmission needs to adapt to different interfaces to realize label transparent transmission. By determining the label processing method, the adaptability of dyeing labels can be improved, further ensuring the smooth transmission of labels.

[0064] S250 . Based on the label processing method, the candidate service is colored according to the target coloring label, and the target coloring label is continuously transmitted along the link track of the target service request to realize the tracking of the target service request.

[0065] Optionally, based on the label processing method, the candidate service can be colored according to the target coloring label by performing a label existence check on whether the target coloring label exists in the candidate service; if the label existence check passes, the target coloring label continues to be passed along the link track of the target business request; if the label existence check fails, the label processing method is used to add the target coloring label to the candidate service to color the candidate service.

[0066] In this embodiment, the label existence check is a verification process used to check whether a target coloring label already exists in a service; this is to determine whether the service has been marked with a specific coloring label, so as to be able to identify whether the service has processed a specific request link or business process; if the label exists, it means that the service has received the target request or part of the request; if the label does not exist, it means that the service has not received the request or has not been colored.

[0067] The embodiments of the present application determine a candidate business tag of at least one candidate business scenario based on business data of at least one candidate business scenario in a target distributed system; when a target business request of a user is identified, the target business tag is determined from the candidate business tags according to the target business scenario corresponding to the target business request; the target coloring tag of the target business request is determined according to the target business tag; when the target business request passes through the candidate service, the tag processing method of the candidate service is determined; the tag processing method is pre-set according to the interface type of the candidate service; based on the tag processing method, the candidate service is colored according to the target coloring tag, and the target coloring tag is continued to be transmitted along the link track of the target business request to achieve tracking of the target business request. The above technical solution is based on a customized business label system, combined with traffic coloring and distributed link tracking technology, and displays the transaction link trajectory by obtaining label coloring data within a period of time; from a technical point of view, the data sampling rate is set in combination with the traffic coloring technology to further optimize the traditional distributed link tracking technology, which can better accommodate the link inaccuracy caused by occasional factors, improve the accuracy of link topology display, and save the computing cost of link trajectory tracking and map display; from a functional point of view, it solves the difficulties in sorting out transaction links due to the large number of nodes and long links in the bank's distributed system, and it is difficult to quickly determine the scope of fault impact.

[0068] Embodiment 3

[0069] Figure 3 This is a schematic diagram of the structure of a link tracking device provided in Embodiment 3 of the present application, which can be applied to the case of full-link tracking of service requests in a distributed system. The link tracking device can be implemented in the form of hardware and / or software, and the link tracking device can be configured in a computer device, such as a server. Figure 3 As shown, the device comprises:

[0070] A first label determination module 310, configured to determine a candidate service label of at least one candidate service scenario according to service data of at least one candidate service scenario in a target distributed system;

[0071] The tag screening module 320 is used to determine the target service tag from the candidate service tags according to the target service scenario corresponding to the target service request when the target service request of the user is identified;

[0072] A second label determination module 330 is used to determine a target coloring label of a target service request according to a target service label;

[0073] The link tracking module 340 is used to color the link track of the target business request according to the target coloring label to achieve tracking of the target business request.

[0074] The embodiment of the present application determines the candidate business tag of at least one candidate business scenario according to the business data of at least one candidate business scenario in the target distributed system; when the target business request of the user is identified, the target business tag is determined from the candidate business tags according to the target business scenario corresponding to the target business request; the target coloring tag of the target business request is determined according to the target business tag; the link track of the target business request is colored according to the target coloring tag to track the target business request. The above technical scheme solves the problems of link combing difficulties caused by many nodes and long links in the distributed system and difficulty in quickly determining the impact scope of the fault by customizing the coloring tags in the link tracking of the distributed system, and can improve the reliability and accuracy of distributed link tracking.

[0075] Optionally, the link tracking module 340 includes:

[0076] A mode determination unit, used for determining a label processing mode of a candidate service when a target service request passes through the candidate service; the label processing mode is pre-set according to an interface type of the candidate service;

[0077] The service coloring unit is used to color the candidate service according to the target coloring label based on the label processing mode, and continue to transmit the target coloring label along the link track of the target service request.

[0078] Optional, service dyeing unit, specifically for:

[0079] Perform label existence check on whether the target coloring label exists in the candidate service;

[0080] If the label existence check passes, the target colored label will continue to be transmitted along the link track of the target service request;

[0081] If the label existence check fails, the label processing method is used to add the target coloring label to the candidate service to color the candidate service.

[0082] Optionally, the second tag determination module 330 is specifically configured to:

[0083] Perform timestamp or hash function processing on the unique identifier of the target business request to obtain a candidate coloring label;

[0084] The target service label is combined with the candidate coloring labels to obtain the target coloring label of the target service request.

[0085] Optionally, the device further includes a topology map generation module; the topology map generation module includes:

[0086] A data acquisition unit, used to acquire link trajectory data requested by a target service; the link trajectory data refers to data collected during the coloring process of the link trajectory according to a pre-configured fault-tolerant sampling rate;

[0087] The topology map generating unit is used to determine the target link topology map according to the link trajectory data.

[0088] Optionally, a topology map generating unit is specifically used to:

[0089] Parse the link trajectory data to obtain the dependency relationship and calling order between candidate services;

[0090] Generate a target link topology diagram based on the dependency relationship and calling sequence between candidate services.

[0091] The link tracking device provided in the embodiments of the present application can execute the link tracking method provided in any embodiment of the present application, and has the corresponding functional modules and beneficial effects for executing each link tracking method.

[0092] According to an embodiment of the present application, the present application also provides an electronic device, a readable storage medium and a computer program product.

[0093] Embodiment 4

[0094] Figure 4 4 is a schematic diagram of the structure of an electronic device 410 that implements the link tracking method of an embodiment of the present application. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workbenches, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present application described and / or required herein.

[0095] like Figure 4As shown, the electronic device 410 includes at least one processor 411, and a memory connected to the at least one processor 411 in communication, such as a read-only memory (ROM) 412, a random access memory (RAM) 413, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 411 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 412 or the computer program loaded from the storage unit 418 to the random access memory (RAM) 413. In RAM413, various programs and data required for the operation of the electronic device 410 can also be stored. The processor 411, ROM412 and RAM413 are connected to each other via a bus 414. An input / output (I / O) interface 415 is also connected to the bus 414.

[0096] Multiple components in the electronic device 410 are connected to the I / O interface 415, including: an input unit 416, such as a keyboard, a mouse, etc.; an output unit 417, such as various types of displays, speakers, etc.; a storage unit 418, such as a disk, an optical disk, etc.; and a communication unit 419, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 419 allows the electronic device 410 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0097] Processor 411 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of processor 411 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. Processor 411 executes the various methods and processes described above, such as a link tracking method.

[0098] In some embodiments, the link tracking method may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 418. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 410 via the ROM 412 and / or the communication unit 419. When the computer program is loaded into the RAM 413 and executed by the processor 411, one or more steps of the link tracking method described above may be performed. Alternatively, in other embodiments, the processor 411 may be configured as the link tracking method in any other appropriate manner (e.g., by means of firmware).

[0099] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0100] Computer programs for implementing the methods of the present application may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable link tracking device, so that when the computer program is executed by the processor, the functions / operations specified in the flowchart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine as a stand-alone software package and partially on a remote machine, or entirely on a remote machine or server.

[0101] In the context of the present application, a computer readable storage medium may be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, device or equipment. A computer readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, a computer readable storage medium may be a machine readable signal medium. A more specific example of a machine readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0102] To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

[0103] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0104] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.

[0105] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps recorded in this application can be executed in parallel, sequentially or in different orders, as long as the expected results of the technical solution of this application can be achieved, and this document is not limited here.

[0106] The above specific implementations do not constitute a limitation on the protection scope of this application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of this application should be included in the protection scope of this application.

Claims

1. A link tracking method, characterized in that: include: Determining a candidate business tag of the at least one candidate business scenario according to business data of the at least one candidate business scenario in the target distributed system; When a target service request of a user is identified, determining a target service tag from the candidate service tags according to a target service scenario corresponding to the target service request; Determining a target coloring label for the target service request according to the target service label; The link trace of the target service request is colored according to the target coloring label to achieve tracking of the target service request.

2. The method according to claim 1, characterized in that Coloring the link trace of the target service request according to the target coloring label includes: When the target service request passes through the candidate service, determining a label processing mode of the candidate service; the label processing mode is pre-set according to the interface type of the candidate service; Based on the label processing mode, the candidate service is colored according to the target coloring label, and the target coloring label is continuously transmitted along the link track of the target service request.

3. The method according to claim 2, characterized in that Based on the label processing mode, the candidate service is colored according to the target coloring label, including: Performing a label existence check on whether a target dye label exists in the candidate service; If the label existence check passes, the target colored label is continuously transferred along the link track of the target service request; If the label existence check fails, the label processing method is used to add the target coloring label to the candidate service to color the candidate service.

4. The method according to claim 1, characterized in that: The step of determining a target coloring label of the target service request according to the target service label includes: Performing timestamp or hash function processing on the unique identifier of the target service request to obtain a candidate coloring label; The target service label is combined with the candidate coloring labels to obtain a target coloring label for the target service request.

5. The method according to claim 1, characterized in that After coloring the link trace of the target service request, the method further includes: Acquire link trajectory data of the target service request; the link trajectory data refers to data collected from the coloring process of the link trajectory according to a pre-configured fault-tolerant sampling rate; A target link topology map is determined based on the link trajectory data.

6. The method according to claim 5, characterized in that Determining a target link topology map according to the link trajectory data includes: Parsing the link trajectory data to obtain the dependency relationship and calling sequence between the candidate services; Generate a target link topology diagram based on the dependency relationship and calling sequence between candidate services.

7. A link tracking device, characterized in that: include: A first label determination module, configured to determine a candidate service label of at least one candidate service scenario according to service data of at least one candidate service scenario in a target distributed system; A tag screening module, configured to, when a target service request of a user is identified, determine a target service tag from the candidate service tags according to a target service scenario corresponding to the target service request; A second label determination module, used to determine a target coloring label of the target service request according to the target service label; The link tracking module is used to color the link track of the target business request according to the target coloring label to achieve tracking of the target business request.

8. An electronic device, characterized in that: include: one or more processors; A memory for storing one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the link tracking method as described in any one of claims 1-6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the link tracking method as described in any one of claims 1 to 6 is implemented.

10. A computer program product, comprising a computer program, wherein when the computer program is executed by a processor, the computer program implements the link tracking method according to any one of claims 1 to 6.

Images