CA3141329A1 - Request link tracking method and service request processing method - Google Patents

Abstract

The present application relates to the request link tracing field, and more particularly to a request link tracing method and a business request processing method. The request link tracing method comprises: storing received link tracing data after receiving the link tracing data uploaded by any service node, obtaining a link tracing identification of a request link associated with a request link tracing command when the request link tracing command is received, obtaining link tracing data related to the request link from all pre-stored link tracing data according to the link tracing identification of the request link, and displaying request link information according to the obtained link tracing data related to the request link. Embodiments of the present invention enable realization of tracing the entire link of a business request based on business transparent unique identification (ID).

Description

REQUEST LINK TRACKING METHOD AND SERVICE REQUEST PROCESSING
METHOD
BACKGROUND OF THE INVENTION
Technical Field [0001] The present application relates to the field of request link tracing technology, and more particularly to a request link tracing method, a business request processing method, a data tracing equipment, a service node, a computer equipment and a storage medium.
Description of Related Art

[0002] With the increasing complexity of businesses, systems are also variously divided, in particular with the vigorous rise in micro-service architectures and container technologies, a seemingly simple application might be supported by tens or even hundreds of services at the background, under the environment of clustered deployment, each service likewise possesses tens or even hundreds of deployed nodes. In a complicated service architecture system, almost every frontend business request forms a complicated distributed service invoking link, in such a scenario, when the request becomes slow or unusable, it is impossible to quickly ascertain as to which background service has caused the circumstance, so it is required to trace the invoking link of the business request, so that the failure location can be more quickly located once failure occurs.

[0003] ELK is the mainstream open-source technical method currently employed by the profession to address all-link log collection monitoring, and ELK is an acronym of Elasticsearch, Logstash, and Kibana.

[0004] Elasticsearch is a real-time full text searching and analyzing engine, and provides three essential functions, namely collecting, analyzing and storing data. It is an extensible Date recue / Date received 2021-12-08 distributed system providing highly effective searching functions for such structures as open REST and JAVA API, etc.

[0005] Logstash is a tool used to collect, analyze and filter logs. It supports logs of almost any random types, including system logs, error logs and self-defined application program logs.
Logstash can receive logs from a variety of sources that include syslog, MQ
and JMX, and it can output data in many modes, including e-mails, websockets and Elasticsearch.

[0006] Kibana is a Web-based graphic interface used to search, analyze and visually store log data in Elasticsearch indices. Kibana makes use of the REST interface of Elasticsearch to retrieve data, not only allows users to create dashboard views customized with their own data, but also allows the users to enquire and filter data in special modes.

[0007] However, ELK mainly solves problems concerning collecting and monitoring logs, and it cannot realize tracing of the entire link of a business request (namely the entire request link to which the business request corresponds) based on business transparent unique identification (or unique ID).
SUMMARY OF THE INVENTION

[0008] In view of the deficiencies prevailing in the state of the art, the present invention provides a request link tracing method, a business request processing method, a data tracing equipment, a service node, a computer equipment and a storage medium, and embodiments of the present invention enable realization of tracing the entire link of a business request based on business transparent unique identification (ID).

[0009] According to the first aspect, the present invention provides a request link tracing method, in one embodiment, the method is applied to a data tracing equipment in a service Date recue / Date received 2021-12-08 system that includes a plurality of user equipment, a distributed system consisting of a plurality of service nodes, and a data tracing equipment, and the method comprises:

[0010] storing received link tracing data after receiving the link tracing data uploaded by anyone of the service nodes, wherein the link tracing data is data generated in relation to a business request and a business operation after the service node has executed the business operation corresponding to the business request in response to the business request coming from anyone of the user equipment or anyone of the other service nodes;

[0011] obtaining a link tracing identification of a request link associated with a request link tracing command when the request link tracing command is received, obtaining link tracing data related to the request link from all pre-stored link tracing data according to the link tracing identification of the request link, and displaying request link information according to the obtained link tracing data related to the request link.

[0012] In one embodiment, the step of storing received link tracing data includes:

[0013] obtaining a link tracing identification to which the received link tracing data corresponds;

[0014] creating association information between the link tracing identification and the received link tracing data when the received link tracing data is stored;

[0015] the step of obtaining link tracing data related to the request link from all pre-stored link tracing data according to the link tracing identification of the request link includes:

[0016] obtaining pre-created association information corresponding to the link tracing identification of the request link; and

[0017] obtaining all link tracing data corresponding to the link tracing identification of the request link from all pre-stored link tracing data according to the association information.

[0018] In one embodiment, the step of displaying request link information according to the obtained link tracing data related to the request link includes:

[0019] generating a request link map according to the obtained link tracing data related to the request link; and

[0020] displaying the request link map.

Date recue / Date received 2021-12-08

[0021] According to the second aspect, the present invention provides a business request processing method, in one embodiment, the method is applied to any service node in a service system that includes a plurality of user equipment, a distributed system consisting of a plurality of service nodes, and a data tracing equipment, and the method comprises:

[0022] receiving a business request coming from anyone of the user equipment or anyone of the other service nodes;

[0023] executing a business operation corresponding to the business request;

[0024] generating link tracing data related to the business request and the business operation after executing the business operation; and

[0025] uploading the generated link tracing data to the data tracing equipment.

[0026] In one embodiment, the step of executing a business operation corresponding to the business request includes:

[0027] in the case the business request comes from anyone of the user equipment, generating a link tracing identification for tracing a request link to which the business request corresponds and a location tracing identification for characterizing a location of the business request in the request link to which the business request corresponds, determining all the other service nodes required to be invoked to complete the business operation and invoking orders of the other service nodes, generating new location tracing identifications dependent upon the location tracing identification and corresponding to the other service nodes according to the invoking orders of the other service nodes, and sending to the other service nodes a new business request generated according to the link tracing identification and the new location tracing identifications corresponding to the other service nodes; and

[0028] in the case the business request comes from anyone of the other service nodes, obtaining a link tracing identification associated with the business request and location tracing identifications generated by the other service nodes, determining invoking orders of the other service nodes required to be invoked when it is determined that other service nodes are required to be invoked to complete the business operation, generating new location tracing Date recue / Date received 2021-12-08 identifications dependent upon the location tracing identification and corresponding to the other service nodes according to the invoking orders of the other service nodes, and sending to the other service nodes a new business request generated according to the link tracing identification and the new location tracing identifications corresponding to the other service nodes.

[0029] In one embodiment, the step of generating link tracing data related to the business request and the business operation after executing the business operation includes:

[0030] in the case the business request comes from anyone of the user equipment, generating link tracing data related to the business operation according to operation execution information related to the business operation, the link tracing identification and the location tracing identification after executing the business operation; and

[0031] in the case the business request comes from anyone of the other service nodes, generating link tracing data related to the business operation according to operation execution information related to the business operation, the link tracing identification and the location tracing identification after executing the business operation.

[0032] According to the third aspect, the present invention provides a data tracing equipment, in one embodiment, the data tracing equipment comprises:

[0033] a data storing module, for storing received link tracing data after receiving the link tracing data uploaded by anyone of service nodes, wherein the link tracing data is data generated in relation to a business request and a business operation after the service node has executed the business operation corresponding to the business request in response to the business request coming from anyone of user equipment or anyone of the other service nodes;
and

[0034] a request link tracing module, for obtaining a link tracing identification of a request link associated with a request link tracing command when the request link tracing command is received, obtaining link tracing data related to the request link from all pre-stored link tracing Date recue / Date received 2021-12-08 data according to the link tracing identification of the request link, and displaying request link information according to the obtained link tracing data related to the request link.

[0035] According to the fourth aspect, the present invention provides a service node, in one embodiment, the service node comprises:

[0036] a business request receiving module, for receiving a business request coming from anyone of user equipment or anyone of other service nodes;

[0037] a business operation executing module, for executing a business operation corresponding to the business request;

[0038] a link tracing data generating module, for generating link tracing data related to the business request and the business operation after the business operation has been executed;
and

[0039] a data uploading module, for uploading the generated link tracing data to a data tracing equipment.

[0040] According to the fifth aspect, the present invention provides a computer equipment that comprises a memory, a processor and a computer program stored on the memory and operable on the processor, and the steps according to anyone of the aforementioned methods are realized when the processor executes the computer program.

[0041] According to the sixth aspect, the present invention provides a computer-readable storage medium storing a computer program thereon, and the steps according to anyone of the aforementioned methods are realized when the computer program is executed by a processor.

[0042] In the embodiments of the present invention, the data tracing equipment stores received link tracing data after receiving the link tracing data uploaded by anyone of the service nodes in a service system, wherein the link tracing data is data generated in relation to a business request and a business operation after the service node has executed the business operation Date recue / Date received 2021-12-08 corresponding to the business request in response to the business request coming from anyone of the user equipment or anyone of the other service nodes, obtains a link tracing identification of a request link associated with a request link tracing command when the request link tracing command is received, obtains link tracing data related to the request link from all pre-stored link tracing data according to the link tracing identification of the request link, and displays request link information according to the obtained link tracing data related to the request link, whereby is made possible to realize to trace the entire link of a business request based on business transparent unique identification (ID).
BRIEF DESCRIPTION OF THE DRAWINGS

[0043] Fig. 1 is a view illustrating the application environment of a request link tracing method in an embodiment;

[0044] Fig. 2 is a flowchart schematically illustrating a request link tracing method in an embodiment;

[0045] Fig. 3 is a flowchart schematically illustrating a business request processing method in an embodiment;

[0046] Fig. 4 is a block diagram illustrating the structure of a data tracing equipment in an embodiment;

[0047] Fig. 5 is a block diagram illustrating the structure of a service node in an embodiment;
and

[0048] Fig. 6 is a view illustrating the internal structure of a computer equipment in an embodiment.
DETAILED DESCRIPTION OF THE INVENTION

Date recue / Date received 2021-12-08

[0049] To make more lucid and clear the objectives, technical solutions and advantages of the present application, the present application is described in greater detail below with reference to the accompanying drawings and embodiments. As should be understood, the specific embodiments as described here are merely meant to explain the present application, rather than to restrict the present application.
Embodiment 1

[0050] The present invention provides a request link tracing method. In one embodiment, the request link tracing method comprises the steps as shown in Fig. 1.

[0051] In the present embodiment, the application environment of the request link tracing method can be the service system as shown in Fig. 2. The service system includes a plurality of user equipment (as indicated by 11 in Fig. 2), a distributed system (as indicated by 12 in Fig. 2) consisting of a plurality of service nodes, and a data tracing equipment (as indicated by 13 in Fig. 2), of which the user equipment includes, but is not limited to include, a personal computer, a notebook computer, a smart mobile phone, a panel computer and a table computer.
Each service node in the distributed system can be invoked by the other service nodes to provide thereto one or more services, and each service node can be embodied as an independent server or a server cluster consisting of a plurality of servers.
The data tracing equipment can be embodied as an independent equipment (such as an independent server), and can also be embodied as one data tracing server with a piece or plurality ofclient side equipment, of which the client side equipment can include, but is not limited to include, a personal computer, a notebook computer, a smart mobile phone, a panel computer and a table computer. When the data tracing equipment is not embodied as an independent server, the steps required for the data tracing equipment to execute can be realized by a tracing server, and the tracing server can be a Zipkin server, in which Zipkin is a type of open-source distributed real-time data tracing system, and its main function is to aggregate real-time Date recue / Date received 2021-12-08 monitor data coming from various heterogeneous systems, for instance, it is possible to compile simple configurations and codes to enable an application to report link tracing data to Zipkin. Zipkin mainly consists of four parts, namely collector, data storage, enquiry and Web interface. The collector of Zipkin is responsible for receiving tracing data reported by various systems; data storage makes use of Cassandra by default, and it can also be replaced with My SQL; the enquiry service is employed to provide data enquiring capabilities for other services, while the Web service is a graphical user interface officially provided by default.

[0052] As should be noted, the number of service nodes and their mutual invoking relations in the distributed system in Fig. 2 are merely shown by way of example, while the number of service nodes and their mutual invoking relations in the distributed system are not restricted in the present embodiment.

[0053] The steps illustrated in Fig. 1 are described below in conjunction with Fig. 2

[0054] S110 - storing received link tracing data after receiving the link tracing data uploaded by anyone of the service nodes, wherein the link tracing data is data generated in relation to a business request and a business operation after the service node has executed the business operation corresponding to the business request in response to the business request coming from anyone of the user equipment or anyone of the other service nodes.

[0055] In this embodiment, any user equipment can send a business request to a specific service node or any service node in the distributed system, for instance, the user equipment sends an order information enquiring request to a certain service node to obtain order information of an order required to be enquired thereby. In order to complete this business request, plural rounds of service invoking may be performed inside the distributed system to finally complete the request, for instance, the user equipment sends a business request to service node A of the distributed system, service node A then respectively invokes service node B
and service node C in response to the business request, while it is required for service node Date recue / Date received 2021-12-08 B to further invoke service node D and for service node C to further invoke service node E
before service node A could finally complete the business request.

[0056] With respect to any service node in the distributed system, when it receives a business request coming from the user equipment or another service node, it executes an business operation (that can be such operations as counting data, enquiring data, etc.) corresponding to the business request; after the business operation has been executed to completion, data related to the business request and the business operation (namely link tracing data) is generated and uploaded to the data tracing equipment (if the data tracing equipment is not an independent equipment, for instance, it is formed by a client side equipment and a data tracing server, the service node will specifically upload the link tracing data to the data tracing server).

[0057] The link tracing data can be a log, and can specifically include a link tracing identification, a location tracing identification, and operation execution information related to the business operation. The operation execution information related to the business operation can include such information as execution result of the business operation (e.g., execution succeeded, execution failed, failure, etc.), node identifications of other service nodes as invoked, business type, failure information should failure occur, processing starting and ending times and processing duration of the business request.

[0058] Specifically, in this embodiment the link tracing identification and the location tracing identification are generated by the service node based on the OpenTracing specification.
OpenTracing is an open-distributed tracing specification, it supplies API
definitions irrelevant to platforms and irrelevant to manufacturers to enable developing personnel to conveniently add or replace implementations of specific tracing systems. In OpenTracing, a session (Trace) is represented by a set of operations (Span) having reference relation, the session (Trace) is a logical transaction coordinating completion of processes of various nodes in the distributed system, and operations (Span) are computational logic units whose completion requires consumption of certain time.
Date recue / Date received 2021-12-08

[0059] The aforementioned link tracing identification is Tracing ID used to trace the request link to which the business request corresponds. Tracing ID is an ID
representative of a unique request, this ID is generally generated by a service node that is the first to process the business request in the distributed system, and is forwarded through network to the next requested service node under distributed invoking. Since each business request only has one globally unique ID, it is therefore possible to associate together the entire relevant link tracing data of the request link to which a business request corresponds through this ID, so that a problematic service node can be quickly found when the request becomes slow, is not responsive, or fails, so as to more quickly solve the problem. More specifically, the generating rule of Tracing ID
can be a character string consisting of server IP, generation time of the ID, self increasing sequence and current process number, exemplarily, a generated Tracing ID can be Oad1348f1403169275002100356696.

[0060] The location tracing identification is Span ID used to characterize the location or level of the business request in its corresponding request link. The generating rule of Span ID can be as exemplified by the following example. For instance, service node A
sequentially invokes three service nodes B, C, D during the process of processing a business request, then the Span IDs of the three rounds of invoking are, respectively, "0.1", "0.2"
and "0.3", if service node B continues to invoke two service nodes E and F, then the Span IDs of the two rounds of invoking are, respectively, "0.1.1" and "0.1.2".

[0061] After the data tracing equipment has received the link tracing data uploaded by any service node, the data is stored. In one embodiment, the step of storing received link tracing data includes:

[0062] obtaining a link tracing identification to which the received link tracing data corresponds;

[0063] creating association information betweenthe link tracing identification and the received link tracing data when the received link tracing data is stored.

Date recue / Date received 2021-12-08

[0064] In this embodiment, after the data tracing equipment has received the link tracing data, link tracing identification is obtained therefrom, and association information between the link tracing identification and the received link tracing data is thereafter created when the received link tracing data is stored, so as to facilitate to subsequently find all link tracing data related to the link tracing identification through the link tracing identification and its corresponding association information. The association information can be index information.

[0065] S120 - obtaining a link tracing identification of a request link associated with a request link tracing command when the request link tracing command is received, obtaining link tracing data related to the request link from all pre-stored link tracing data according to the link tracing identification of the request link, and displaying request link information according to the obtained link tracing data related to the request link.

[0066] In this embodiment, the request link tracing command can be triggered by a preset timed task, for example, it is possible to regularly find out a business request whose processing duration has exceeded a preset threshold, and subsequently to automatically trace the request link of this business request. The request link tracing command can further come from an external system, for instance, when it is required for an external system to trace the request link(s) of a certain business request or certain business requests, it is possible to send the request link tracing command to the data tracing equipment. In the case the data tracing equipment is formed by a client side equipment and a tracing server, the request link tracing command can come from the developing personnel, for instance, the developing personnel can send the request link tracing command via the client side equipment to the tracing server.

[0067] Specifically, after the data tracing equipment has received the request link tracing command, a link tracing identification of the request link associated with the request link tracing command is obtained, possibly, the link tracing identification can be carried with the request link tracing command, and thereafter the link tracing data related to the request link is obtained from all pre-stored link tracing data according to the link tracing identification;

Date recue / Date received 2021-12-08 specifically, it is possible to obtain pre-created association information, such as index information, corresponding to the link tracing identification of the request link, and subsequently to obtain all link tracing data corresponding to the link tracing identification of the request link from all pre-stored link tracing data based on the obtained association information.

[0068] Request link information is thereafter displayed according to the obtained link tracing data, and this can specifically be to generate a request link map based on the obtained link tracing data related to the request link

[0069] , and to display the generated request link map, so as to achieve the objective of making network invoking perspective, to solve the link tracing problem in implementing large-scale micro-service architectures, and to apply to such scenarios as quick detection of failures, and service managements, etc.

[0070] As should be understood, although the various steps in the flowchart of Fig. 1 are sequentially displayed as indicated by arrows, these steps are not necessarily executed in the sequences indicated by arrows. Unless otherwise explicitly noted in this paper, execution of these steps is not restricted by any sequence, as these steps can also be executed in other sequences (than those indicated in the drawings). Moreover, at least partial steps in Fig. 1 may include plural sub-steps or multi-phases, these sub-steps or phases are not necessarily completed at the same timing, but can be executed at different timings, and these sub-steps or phases are also not necessarily sequentially performed, but can be performed in turns or alternately with other steps or with at least some of sub-steps or phases of other steps.
Embodiment 2

[0071] Based on the same inventive conception as Embodiment 1, the present invention further provides a business request processing method. In one embodiment, the application environment of the business request processing method can be the service system as shown Date recue / Date received 2021-12-08 in Fig. 2. See the relevant description in Embodiment 1 for the description of the service system, while no repetition is made in this context.

[0072] The business request processing method is explained below with an example of its being applied to any service node (hereinafter referred to as "the current service node") in Fig. 2.
In this embodiment, as shown in Fig. 3, the business request processing method comprises the following steps:

[0073] S210 - receiving a business request coming from anyone of the user equipment or anyone of the other service nodes.

[0074] S220 - executing a business operation corresponding to the business request.

[0075] S230 - generating link tracing data related to the business request and the business operation after executing the business operation.

[0076] S240 - uploading the generated link tracing data to the data tracing equipment.

[0077] In this embodiment, the business request received by the current service node may come from any user equipment, and may also come from any other service node in the distributed system. After receiving the business request, the current service node executes a business operation, which can be enquiry of order information and amendment to order data, etc., corresponding to the business request, and generates corresponding link tracing data after the business operation has been executed to completion.

[0078] Specifically, the generated link tracing data can be a log, and the log can specifically include a link tracing identification, a location tracing identification, and operation execution information related to the business operation. The operation execution information related to the business operation can include such information as execution result of the business operation (e.g., execution succeeded, execution failed, failure, etc.), node identifications of other service nodes as invoked, business type (such as order enquiry, order data amendment, etc.), failure information should failure occur, processing starting and ending times and Date recue / Date received 2021-12-08 processing duration of the business request. The generated link tracing data will be uploaded by the current service node to the data tracing equipment.

[0079] Specifically, the current service node generates the link tracing identification and the location tracing identification based on the OpenTracing specification.
OpenTracing is an open-distributed tracing specification, it supplies API definitions irrelevant to platforms and irrelevant to manufacturers to enable developing personnel to conveniently add or replace implementations of specific tracing systems. In OpenTracing, a session (Trace) is represented by a set of operations (Span) having reference relation, the session (Trace) is a logical transaction coordinating completion of processes of various nodes in the distributed system, and operations (Span) are computational logic units whose completion requires consumption of certain time.

[0080] The aforementioned link tracing identification is Tracing ID used to trace the request link to which the business request corresponds. Tracing ID is an ID
representative of a unique request, this ID is generally generated by a service node that is the first to process the business request in the distributed system, and is forwarded through network to the next requested service node under distributed invoking. Since each business request only has one globally unique ID, it is therefore possible to associate together the entire relevant link tracing data of the request link to which a business request corresponds through this ID, so that a problematic service node can be quickly found when the request becomes slow, is not responsive, or fails, so as to more quickly solve the problem. More specifically, the generating rule of Tracing ID
can be a character string consisting of server IP, generation time of the ID, self increasing sequence and current process number, exemplarily, a generated Tracing ID can be Oad1348f1403169275002100356696.

[0081] The location tracing identification is Span ID used to characterize the location or level of the business request in its corresponding request link. The generating rule of Span ID can be as exemplified by the following example. For instance, service node A
sequentially Date recue / Date received 2021-12-08 invokes three service nodes B, C, D during the process of processing a business request, then the Span IDs of the three rounds of invoking are, respectively, "0.1", "0.2"
and "0.3", if service node B continues to invoke two service nodes E and F, then the Span IDs of the two rounds of invoking are, respectively, "0.1.1" and "0.1.2".

[0082] In a possible embodiment, the service node is integrated with SNTracker (a type of distributed link tracing system based on the OpenTracing specification), in which is integrated MDC (Mapped Diagnostic Contexts) function of SLF4J, making it easy for the user to output the Tracing ID and Span ID of the currently invoked context by merely simply amending log configuration files; specifically, it is possible to realize the capability of asynchronously printing the log to the local disk based on SLF4J (a type of Java log framework) and Logback (a type of open-source log component), when the framework or the component is accessible, the output format of the log file can be self-defined under the precondition of asynchronous log printing. It is possible to realize the log printing type based on requirements, such as summary log and/or statistic log, of which the summary log is a log that is generated and grounded to the magnetic disk each time a service node is invoked, and the statistic log is a log that is counted and output at a certain time interval.

[0083] The service node can remotely report the link tracing data via SNTracker to the data tracing equipment, such as a Zipkin tracing server, to perform distributed link tracing display, so as to achieve the objective of making network invoking perspective, to solve the link tracing problem in implementing large-scale micro-service architectures, and to apply to such scenarios as quick detection of failures, and service managements, etc.

[0084] In one embodiment, the step of executing a business operation corresponding to the business request includes:

[0085] in the case the business request comes from anyone of the user equipment, generating a link tracing identification for tracing a request link to which the business request corresponds and a location tracing identification for characterizing a location of the business request in Date recue / Date received 2021-12-08 the request link to which the business request corresponds, determining all the other service nodes required to be invoked to complete the business operation and invoking orders of the other service nodes, generating new location tracing identifications dependent upon the location tracing identification and corresponding to the other service nodes according to the invoking orders of the other service nodes, and sending to the other service nodes a new business request generated according to the link tracing identification and the new location tracing identifications corresponding to the other service nodes; and

[0086] in the case the business request comes from anyone of the other service nodes, obtaining a link tracing identification associated with the business request and location tracing identifications generated by the other service nodes, determining invoking orders of the other service nodes required to be invoked when it is determined that other service nodes are required to be invoked to complete the business operation, generating new location tracing identifications dependent upon the location tracing identification and corresponding to the other service nodes according to the invoking orders of the other service nodes, and sending to the other service nodes a new business request generated according to the link tracing identification and the new location tracing identifications corresponding to the other service nodes.

[0087] In this embodiment, if the received business request comes from a user equipment, the current service node generates the Tracing ID (namely a link tracing identification) corresponding to the business request based on the aforementioned generating rule of the Tracing ID and generates the Span ID (namely a location tracing identification) corresponding to the business request based on the aforementioned generating rule of the Span ID. Moreover, the generated Tracing ID and Span ID can be cached in the context of a thread corresponding to the business request to facilitate subsequent retrieval. If the received business request comes from any other service node, it is then possible to obtain the Tracing ID and Span ID associated with the business request as generated by the other service node.
Exemplarily, the service node integrated with SNTracker will generate a Span after having been invoked, and will cache it in the context of the SNTracker (such as SnTrackerContext);

Date recue / Date received 2021-12-08 this context is ThreadLocal (a thread variable) of the cache, when it is required to obtain the Tracing ID and Span ID therefrom, it is possible to firstly obtain the context of the current SNTracker, and then obtain the Span via the context instance, whereby the Tracing ID and Span ID can be obtained from the Span.

[0088] If it is determined that the completion of the received business request requires to invoke other service nodes, it is necessary to determine invoking orders of the other service nodes required to be invoked, and to generate new location tracing identifications dependent upon the location tracing identification and corresponding to the other service nodes according to the invoking orders of the other service nodes, for instance, service node A
invokes service node B in the process of processing a business request, and the Span ID of this invoking is "0.1", if service node B further needs to continue to invoke two service nodes E and F, service node B will generate two Span IDs based on the Span ID "0.1", such as "0.1.1"
and "0.1.2", and thereafter send to the other service nodes required to be invoked a new business request generated according to the link tracing identification and the new location tracing identifications corresponding to the other service nodes.

[0089] Correspondingly, in one embodiment, the step of generating link tracing data related to the business request and the business operation after executing the business operation includes: in the case the business request comes from anyone of the user equipment, generating link tracing data according to operation execution information related to the business operation, the link tracing identification and the location tracing identification after executing the business operation; and if it is determined that the business request comes from anyone of the other service nodes, generating link tracing data according to operation execution information related to the business operation, the link tracing identification and the location tracing identification after executing the business operation.

[0090] In this embodiment, since any service node in the distributed system executes a business operation (that can be such an operation as counting data, enquiring data, etc.) related to a Date recue / Date received 2021-12-08 business request upon reception of the business request coming from the user equipment or any other service node, generates data (namely link tracing data) related to the business request and the business operation after the business operation has been executed to completion, and uploads the data to the data tracing device (if the data tracing equipment is not an independent equipment but consists of a client side equipment and a data tracing server, for example, then the service node will specifically upload the link tracing data to the data tracing server), it is therefore possible to realize the tracing of the business request through the link tracing data in the data tracing equipment. Moreover, since the service node is integrated with SNTracker based on the OpenTracing specification, and one business request corresponds to one Tracing ID, it is therefore possible to associate together all link tracing data related to the request link to which a business request corresponds through one Tracing ID, so that the business request can be traced through the all link tracing data, and failed location can hence be quickly located should failure occur.

[0091] As should be understood, although the various steps in the flowchart of Fig. 3 are sequentially displayed as indicated by arrows, these steps are not necessarily executed in the sequences indicated by arrows. Unless otherwise explicitly noted in this paper, execution of these steps is not restricted by any sequence, as these steps can also be executed in other sequences (than those indicated in the drawings). Moreover, at least partial steps in Fig. 3 may include plural sub-steps or multi-phases, these sub-steps or phases are not necessarily completed at the same timing, but can be executed at different timings, and these sub-steps or phases are also not necessarily sequentially performed, but can be performed in turns or alternately with other steps or with at least some of sub-steps or phases of other steps.
Embodiment 3

[0092] Based on the same inventive conception as Embodiment 1, the present invention further provides a data tracing equipment. In one embodiment, as shown in Fig. 4, the data tracing equipment comprises the following modules:

Date recue / Date received 2021-12-08

[0093] a data storing module 110, for storing received link tracing data after receiving the link tracing data uploaded by anyone of service nodes, wherein the link tracing data is data generated in relation to a business request and a business operation after the service node has executed the business operation corresponding to the business request in response to the business request coming from anyone of user equipment or anyone of the other service nodes;
and

[0094] a request link tracing module 120, for obtaining a link tracing identification of a request link associated with a request link tracing command when the request link tracing command is received, obtaining link tracing data related to the request link from all pre-stored link tracing data according to the link tracing identification of the request link, and displaying request link information according to the obtained link tracing data related to the request link.

[0095] In one embodiment, the data storing module includes a link tracing identification obtaining sub-module and an association information creating sub-module.

[0096] The link tracing identification obtaining sub-module is employed for obtaining a link tracing identification to which the received link tracing data corresponds.

[0097] The association information creating sub-module is employed for creating association information between the link tracing identification and the received link tracing data when the received link tracing data is stored.

[0098] Correspondingly, the request link tracing module includes an association information obtaining sub-module and a link tracing data obtaining sub-module.

[0099] The association information obtaining sub-module is employed for obtaining pre-created association information corresponding to the link tracing identification of the request link. The link tracing data obtaining sub-module is employed for obtaining all link tracing Date recue / Date received 2021-12-08 data corresponding to the link tracing identification of the request link from all pre-stored link tracing data according to the association information.

[0100] In one embodiment, the request link tracing module further includes a request link map generating sub-module and a request link map displaying sub-module.

[0101] The request link map generating sub-module is employed for generating a request link map according to the obtained link tracing data related to the request link.
The request link map displaying sub-module is employed for displaying the request link map.

[0102] Specific definitions relevant to the data tracing equipment may be inferred from the aforementioned definitions to the request link tracing method, while no repetition is made in this context. The various modules in the aforementioned data tracing equipment can be wholly or partly realized via software, hardware, and a combination of software with hardware. The various modules can be embedded in the form of hardware in a processor in a computer equipment or independent of any computer equipment, and can also be stored in the form of software in a memory in a computer equipment, so as to facilitate the processor to invoke and perform operations corresponding to the aforementioned various modules.
Embodiment 4

[0103] Based on the same inventive conception as Embodiment 2, the present invention further provides a service node. In one embodiment, as shown in Fig. 5, the service node comprises the following modules:

[0104] a business request receiving module 210, for receiving a business request coming from anyone of user equipment or anyone of other service nodes;

[0105] a business operation executing module 220, for executing a business operation corresponding to the business request;

[0106] a link tracing data generating module 230, for generating link tracing data related to the Date recue / Date received 2021-12-08 business request and the business operation after the business operation has been executed;
and

[0107] a data uploading module 240, for uploading the generated link tracing data to a data tracing equipment.

[0108] In one embodiment, the business operation executing module includes a first executing sub-module and a second executing sub-module.

[0109] The first executing sub-module is employed for, in the case the business request comes from anyone of the user equipment, generating a link tracing identification for tracing a request link to which the business request corresponds and a location tracing identification for characterizing a location of the business request in the request link to which the business request corresponds, determining all the other service nodes required to be invoked to complete the business operation and invoking orders of the other service nodes, generating new location tracing identifications dependent upon the location tracing identification and corresponding to the other service nodes according to the invoking orders of the other service nodes, and sending to the other service nodes a new business request generated according to the link tracing identification and the new location tracing identifications corresponding to the other service nodes.

[0110] The second executing sub-module is employed for, in the case the business request comes from anyone of the other service nodes, obtaining a link tracing identification associated with the business request and location tracing identifications generated by the other service nodes, determining invoking orders of the other service nodes required to be invoked when it is determined that other service nodes are required to be invoked to complete the business operation, generating new location tracing identifications dependent upon the location tracing identification and corresponding to the other service nodes according to the invoking orders of the other service nodes, and sending to the other service nodes a new Date recue / Date received 2021-12-08 business request generated according to the link tracing identification and the new location tracing identifications corresponding to the other service nodes.

[0111] In one embodiment, the link tracing data generating module includes a first data generating sub-module and a second data generating sub-module.

[0112] The first data generating sub-module is employed for, in the case the business request comes from anyone of the user equipment, generating link tracing data according to operation execution information related to the business operation, the link tracing identification and the location tracing identification after executing the business operation.

[0113] The second data generating sub-module is employed for, in the case the business request comes from anyone of the other service nodes, generating link tracing data according to operation execution information related to the business operation, the link tracing identification and the location tracing identification after executing the business operation.

[0114] Specific definitions relevant to the service node may be inferred from the aforementioned definitions to the business request processing method, while no repetition is made in this context. The various modules in the aforementioned service node can be wholly or partly realized via software, hardware, and a combination of software with hardware. The various modules can be embedded in the form of hardware in a processor in a computer equipment or independent of any computer equipment, and can also be stored in the form of software in a memory in a computer equipment, so as to facilitate the processor to invoke and perform operations corresponding to the aforementioned various modules.
Embodiment 5

[0115] In this embodiment is provided a computer equipment, whose internal structure can be as shown in Fig. 6. The computer equipment comprises a processor, a memory, a network Date recue / Date received 2021-12-08 interface and a database connected to each other via a system bus. The processor of the computer equipment is employed to provide computing and controlling capabilities. The memory of the computer equipment includes a nonvolatile storage medium and an internal memory. The nonvolatile storage medium stores therein an operating system, a computer program and a database. The internal memory provides environment for the running of the operating system and the computer program in the nonvolatile storage medium.
The database of the computer equipment is employed to store such data as link tracing identifications, location tracing identifications, and link tracing data, etc. The network interface of the computer equipment is employed to connect to an external terminal via network for communication. The computer program realizes a request link tracing method provided by Embodiment 1 or a business request processing method provided by Embodiment 2 when it is executed by a processor.

[0116] As understandable to persons skilled in the art, the structure illustrated in Fig. 6 is merely a block diagram of partial structure relevant to the solution of the present application, and does not constitute any restriction to the computer equipment on which the solution of the present application is applied, as the specific computer equipment may comprise component parts that are more than or less than those illustrated in Fig. 6, or may combine certain component parts, or may have different layout of component parts.
Embodiment 6

[0117] in this embodiment is provided a computer-readable storage medium storing thereon a computer program, and steps included in the request link tracing method provided by Embodiment 1 or included in the business request processing method provided by Embodiment 2 are realized when the computer program is executed by a processor.

[0118] As comprehensible to persons ordinarily skilled in the art, the entire or partial flows in the methods according to the aforementioned embodiments can be completed via a computer Date recue / Date received 2021-12-08 program instructing relevant hardware, the computer program can be stored in a nonvolatile computer-readable storage medium, and the computer program can include the flows as embodied in the aforementioned various methods when executed. Any reference to the memory, storage, database or other media used in the various embodiments provided by the present application can all include nonvolatile and/or volatile memory/memories. The nonvolatile memory can include a read-only memory (ROM), a programmable ROM
(PROM), an electrically programmable ROM (EPROM), an electrically erasable and programmable ROM (EEPROM) or a flash memory. The volatile memory can include a random access memory (RAM) or an external cache memory. To serve as explanation rather than restriction, the RAM is obtainable in many forms, such as static RAM
(SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct Rambus dynamic RAM (DRDRAM), and Rambus dynamic RAM (RDRAM), etc.

[0119] Technical features of the aforementioned embodiments are randomly combinable, while all possible combinations of the technical features in the aforementioned embodiments are not exhausted for the sake of brevity, but all these should be considered to fall within the scope recorded in the Description as long as such combinations of the technical features are not mutually contradictory.

[0120] The foregoing embodiments are merely directed to several modes of execution of the present application, and their descriptions are relatively specific and detailed, but they should not be hence misunderstood as restrictions to the inventive patent scope. As should be pointed out, persons with ordinary skill in the art may further make various modifications and improvements without departing from the conception of the present application, and all these should pertain to the protection scope of the present application.
Accordingly, the patent protection scope of the present application shall be based on the attached Claims.
Date recue / Date received 2021-12-08

Claims (10)

What is claimed is:

1. A request link tracing method, characterized in that the method is applied to a data tracing equipment in a service system that includes a plurality of user equipment, a distributed system consisting of a plurality of service nodes, and a data tracing equipment, and that the method comprises:
storing received link tracing data after receiving the link tracing data uploaded by anyone of the service nodes, wherein the link tracing data is data generated in relation to a business request and a business operation after the service node has executed the business operation corresponding to the business request in response to the business request coming from anyone of the user equipment or anyone of the other service nodes;
obtaining a link tracing identification of a request link associated with a request link tracing command when the request link tracing command is received, obtaining link tracing data related to the request link from all pre-stored link tracing data according to the link tracing identification of the request link, and displaying request link information according to the obtained link tracing data related to the request link.

2. The request link tracing method according to Claim 1, characterized in that the step of storing received link tracing data includes:
obtaining a link tracing identification to which the received link tracing data corresponds;
creating association information between the link tracing identification and the received link tracing data when the received link tracing data is stored;
and that the step of obtaining link tracing data related to the request link from all pre-stored Date recue / Date received 2021-12-08 link tracing data according to the link tracing identification of the request link includes:
obtaining pre-created association information corresponding to the link tracing identification of the request link; and obtaining all link tracing data corresponding to the link tracing identification of the request link from all pre-stored link tracing data according to the association information.

3. The request link tracing method according to Claim 1, characterized in that the step of displaying request link information according to the obtained link tracing data related to the request link includes:
generating a request link map according to the obtained link tracing data related to the request link; and displaying the request link map.

4. A business request processing method, characterized in that the method is applied to any service node in a service system that includes a plurality of user equipment, a distributed system consisting of a plurality of service nodes, and a data tracing equipment, and that the method comprises:
receiving a business request coming from anyone of the user equipment or anyone of the other service nodes;
executing a business operation corresponding to the business request;
generating link tracing data related to the business request and the business operation after executing the business operation; and Date recue / Date received 2021-12-08 uploading the generated link tracing data to the data tracing equipment.

5. The request link tracing method according to Claim 1, characterized in that the step of executing a business operation corresponding to the business request includes:
in the case the business request comes from anyone of the user equipment, generating a link tracing identification for tracing a request link to which the business request corresponds and a location tracing identification for characterizing a location of the business request in the request link to which the business request corresponds, determining all the other service nodes required to be invoked to complete the business operation and invoking orders of the other service nodes, generating new location tracing identifications dependent upon the location tracing identification and corresponding to the other service nodes according to the invoking orders of the other service nodes, and sending to the other service nodes a new business request generated according to the link tracing identification and the new location tracing identifications corresponding to the other service nodes; and in the case the business request comes from anyone of the other service nodes, obtaining a link tracing identification associated with the business request and location tracing identifications generated by the other service nodes, determining invoking orders of the other service nodes required to be invoked when it is determined that other service nodes are required to be invoked to complete the business operation, generating new location tracing identifications dependent upon the location tracing identification and corresponding to the other service nodes according to the invoking orders of the other service nodes, and sending to the other service nodes a new business request generated according to the link tracing identification and the new location tracing identifications corresponding to the other service nodes.

6. The request link tracing method according to Claim 5, characterized in that the step of Date recue / Date received 2021-12-08 generating link tracing data related to the business request and the business operation after executing the business operation includes:
in the case the business request comes from anyone of the user equipment, generating link tracing data related to the business operation according to operation execution information related to the business operation, the link tracing identification and the location tracing identification after executing the business operation; and in the case the business request comes from anyone of the other service nodes, generating link tracing data related to the business operation according to operation execution information related to the business operation, the link tracing identification and the location tracing identification after executing the business operation.

7. A data tracing equipment, characterized in comprising:
a data storing module, for storing received link tracing data after receiving the link tracing data uploaded by anyone of service nodes, wherein the link tracing data is data generated in relation to a business request and a business operation after the service node has executed the business operation corresponding to the business request in response to the business request coming from anyone of user equipment or anyone of the other service nodes; and a request link tracing module, for obtaining a link tracing identification of a request link associated with a request link tracing command when the request link tracing command is received, obtaining link tracing data related to the request link from all pre-stored link tracing data according to the link tracing identification of the request link, and displaying request link information according to the obtained link tracing data related to the request link.

8. A service node, characterized in comprising:

Date recue / Date received 2021-12-08 a business request receiving module, for receiving a business request coming from anyone of user equipment or anyone of other service nodes;
a business operation executing module, for executing a business operation corresponding to the business request;
a link tracing data generating module, for generating link tracing data related to the business request and the business operation after the business operation has been executed; and a data uploading module, for uploading the generated link tracing data to a data tracing equipment.

9. A computer equipment, comprising a memory, a processor and a computer program stored on the memory and operable on the processor, characterized in that the method steps according to anyone of Claims 1 to 6 are realized when the processor executes the computer program.

10. A computer-readable storage medium, storing a computer program thereon, characterized in that the method steps according to anyone of Claims 1 to 6 are realized when the computer program is executed by a processor.
Date recue / Date received 2021-12-08