CA3235906A1 - Microservice full-link monitoring system and method - Google Patents

Microservice full-link monitoring system and method

Info

Publication number
CA3235906A1
CA3235906A1 CA3235906A CA3235906A CA3235906A1 CA 3235906 A1 CA3235906 A1 CA 3235906A1 CA 3235906 A CA3235906 A CA 3235906A CA 3235906 A CA3235906 A CA 3235906A CA 3235906 A1 CA3235906 A1 CA 3235906A1
Authority
CA
Canada
Prior art keywords
service
invoking
node
spanid
link
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CA3235906A
Other languages
French (fr)
Inventor
Fuping Wang
Xiaoqing ZHAI
Sheng Yang
Jianmei CUI
Qian Sun
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
10353744 Canada Ltd
Original Assignee
10353744 Canada Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 10353744 Canada Ltd filed Critical 10353744 Canada Ltd
Publication of CA3235906A1 publication Critical patent/CA3235906A1/en
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/50—Testing arrangements
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/3006—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/32—Monitoring with visual or acoustical indication of the functioning of the machine
    • G06F11/324—Display of status information
    • G06F11/327—Alarm or error message display
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/805—Real-time
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/865—Monitoring of software
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • Computing Systems (AREA)
  • Physics & Mathematics (AREA)
  • Mathematical Physics (AREA)
  • Quality & Reliability (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Environmental & Geological Engineering (AREA)
  • Debugging And Monitoring (AREA)
  • Telephonic Communication Services (AREA)

Abstract

Pertaining to the field of microservice technology, the present invention discloses a microservice full-link monitoring system and its corresponding method, of which the system comprises: a collection framework module; a message queue module; a computing center module; and a monitoring center module, wherein the message queue module and the computing center module are both deployed in a distributed mode. The microservice full-link monitoring system and its corresponding method provided by the present invention solve the problem concerning link embedded points in invoking services across threads, whereby there is no code intrusion, monitoring conveniency and availability are greatly enhanced, the difficult point of link transmission across threads is solved, and large-scale scenarios are suited.

Description

BACKGROUND OF THE INVENTION
Technical Field [0001] The present invention relates to the field of microservice technology, and more particularly to a microservice full-link monitoring system and its corresponding method.
Description of Related Art
[0002] At present, the microservice design pattern has already been popularized nationwide.
The microservice design pattern encourages service division, and facilitates code decoupling, but it brings about new problems at the same time, such as it increases dependency among services, namely one service usually depends on plural underlying services, and links are invoked relatively deeply, as nested invoking of more than three layers becomes more and more frequent, so there are many problems to be urgently dealt with: it is difficult to locate problems, and it is hard to find performance bottlenecks.
[0003] There are quite a few full-link monitoring systems on the market, and zipkins carried byCAT and Spring cloud of some online platforms are all problematic in terms of the following aspects: 1. codes are strongly intrusive, it is required to display for the writing of codes and to monitor embedded points; 2. real timeliness is inferior, there is a bottleneck in computation, the large-scale microservice system monitoring scenario is not suited. There is a central node both in Cat or Zipkin for the storage of computations (cat being stored to mysql, and zipkin usually to ES), there is a performance bottleneck on the framework, and extensibility is inferior; 3. the link is easily broken, as the invoking across threads makes the link to break.
SUMMARY OF THE INVENTION
[0004] In order to deal with the problems pending in the state of the art, embodiments of the present invention provide a microservice full-link monitoring system and its corresponding method, solve the problem concerning link embedded points in invoking services across threads, whereby Date recue/Date received 2024-04-19 there is no code intrusion, monitoring conveniency and availability are greatly enhanced; the difficult point of link transmission across threads is solved, and no hard coding is required for link transmission across threads; distributed extending capability is provided, and large-scale scenarios are suited. The technical solutions are as follows.
[0005] According to one aspect, there is provided a microservice full-link monitoring system, the system comprises:
[0006] a collection framework module, for collecting service invoking data and performing link series connection;
[0007] a message queue module, for receiving in real time the service invoking data coming from the collection framework module;
[0008] a computing center module, for subscribing the service invoking data from the message queue module, and aggregately storing the same in real time; and
[0009] a monitoring center module, for reading monitor data stored by the computing center module, and providing monitoring functions; wherein
[0010] the message queue module and the computing center module are both deployed in a distributed mode.
[0011] In conjunction with the first aspect, in a first possible mode of realization, the collection framework module is employed for collecting service invoking data that includes link IDs, node IDs, service names, request parameters, server IPs, and response times.
[0012] In conjunction with the first aspect, in a second possible mode of realization, the collection framework module is employed for setting up a link ID and a node ID
or generating a new link ID and a node ID for a current service based on a link ID and a node ID transmitted from an invoker.
[0013] In conjunction with any one of the first and second possible modes of realization of the Date recue/Date received 2024-04-19 first aspect, in the third to the fourth possible modes of realization, the link ID is a TraceID, and the node ID is a SpanID.
[0014] In conjunction with the first aspect, in the fifth possible mode of realization, the message queue module employs a Kafka architecture, and/or the computing center module employs a Druid architecture.
[0015] In conjunction with the first aspect, in the sixth possible mode of realization, the monitoring center module is employed for reading monitor data stored by the computing center module, and providing monitoring functions that include invoking link presentation, searching, monitoring, and alarming.
[0016] According to the second aspect, there is a microservice full-link monitoring method in conjunction with the microservice full-link monitoring system described in the first aspect, the method comprises a data collecting step, and the data collecting step specifically includes the following sub-steps:
[0017] requesting a first service;
[0018] the collection framework module generating a link ID for present invoking, and generating a first node ID for a current request, the first service invoking a second service;
[0019] the collection framework module obtaining a link ID and a node ID of current invoking, generating a second node ID for the second service, and transmitting the link ID and the second node ID to the second service through parameters;
[0020] the second service processing a request, and the collection framework module setting the transmitted link ID and node ID as the current link ID and node ID;
[0021] the second service starting a child thread to invoke a third service, and a parent thread automatically passing the link ID and node ID information to the child thread;
[0022] the collection framework module obtaining a link ID and a node ID of current invoking, Date recue/Date received 2024-04-19 generating a third node ID for the third service, and transmitting the link ID
and the second node ID to the third service through parameters;
[0023] the second service starting the child thread to invoke a fourth service, and the parent thread automatically passing the link ID and node ID information to the child thread; and
[0024] the collection framework module obtaining a link ID and a node ID of current invoking, generating a fourth node ID for the third service, and transmitting the link ID and the third node ID to the third service through parameters.
[0025] In conjunction with the second aspect, in the first to the third possible modes of realization of the second aspect, the data collecting step specifically includes the following sub-steps:
[0026] requesting a first service;
[0027] the collection framework module generating a TraceID for present invoking, and generating a first SpanID for a current request, the first service invoking a second service;
[0028] the collection framework module obtaining a TraceID and a SpanID of current invoking, generating a second SpanID for the second service, and transmitting the TraceID and the second SpanID to the second service through parameters;
[0029] the second service processing a request, and the collection framework module setting the transmitted TraceID and SpanID as the current TraceID and SpanID;
[0030] the second service starting a child thread to invoke a third service, and a parent thread automatically passing the TraceID and SpanID information to the child thread;
[0031] the collection framework module obtaining a TraceID and a SpanID of current invoking, generating a third SpanID for the third service, and transmitting the TraceID
and the second SpanID to the third service through parameters;
[0032] the second service starting the child thread to invoke a fourth service, and the parent Date recue/Date received 2024-04-19 thread automatically passing the TraceID and SpanID information to the child thread; and
[0033] the collection framework module obtaining a TraceID and a SpanID of current invoking, generating a fourth SpanID for the third service, and transmitting the TraceID
-and the third SpanID to the third service through parameters.
[0034] In conjunction with the second aspect, in the fourth to the sixth possible modes of realization of the second aspect, the method further comprises a data analysis processing step, and the data analysis processing step specifically includes the following sub-steps:
[0035] the collection framework module collecting service invoking data, and sending the same to the message queue module;
[0036] the computing center module drawing the service invoking data out of the message queue module, and aggregately storing the same; and
[0037] the monitoring center module reading monitor data from the computing center module, and providing monitoring functions that include invoking link presentation, searching, monitoring, and alarming.
[0038] In conjunction with any one of the fourth to the sixth possible modes of realization of the second aspect, in the seventh to the ninth possible modes of realization, the data analysis processing step specifically includes the following sub-steps:
[0039] the collection framework module collecting service invoking data, and sending the same to the message queue module of a Kafka architecture;
[0040] the computing center module of a Druid architecture drawing the service invoking data out of the message queue module of a Kafka architecture, and aggregately storing the same; and
[0041] the monitoring center module reading monitor data from the computing center module of a Druid architecture, and providing monitoring functions that include invoking link presentation, searching, monitoring, and alarming.
Date recue/Date received 2024-04-19
[0042] The technical solutions provided by the embodiments of the present invention bring about the following advantageous effects.
[0043] 1.By providing such mainstream frameworks as Spring Mvc, Thrift, Dubbo, Hessian, Protobuf-RPC, Okttp, and Rsf, etc., with embedded point plug-ins, and by providing annotation AOP support for Java, the use is convenient, it suffices to perform full-link monitoring only through simple configuration; the problem concerning link embedded points in invoking services across threads is solved, there is no intrusion by codes, and monitoring conveniency and availability are greatly enhanced.
[0044] 2.By selecting monitored contents (link IDs, node IDs, system IDs, invoker system IDs, server IPs, service names, service types, processing start times, processing end times, request parameters, user IDs, and response times, etc.) through the mode of configuration, monitored information is made configurable; the monitored data is sent to kafka in real time, and then aggregately stored at Druid in real time. The monitoring center can read druid data in real time for presenting and monitoring, the real timeliness is high, in addition, with such excellent open-source frameworks as kafka and Druid, throughput is high and computational capability is strong, distributed extending capability is provided, and large-scale scenarios are suited.
[0045] 3.Codes start the child thread to invoke services, wherein it is possible to automatically obtain TraceIDs (link IDs) and spanIDs (node IDs) of the parent thread, whereby integrity of the entire link is guaranteed, the difficult point of link transmission across threads is solved, and no hard coding is required for link transmission across threads.
BRIEF DESCRIPTION OF THE DRAWINGS
[0046] To describe the technical solutions in the embodiments of the present invention more clearly, drawings required to be used in the description of the embodiments will be briefly introduced below. Apparently, the drawings introduced below are merely directed to some embodiments of the present invention, while it is possible for persons ordinarily skilled in the art to acquire other drawings without spending any creative effort in the process based on these Date recue/Date received 2024-04-19 drawings.
[0047] Fig. 1 is a view schematically illustrating the structure of the microservice full-link monitoring system provided by an embodiment of the present invention;
[0048] Fig. 2 is a view illustrating working demonstration of the entire architecture of the microservice full-link monitoring system provided by an embodiment of the present invention, taking Http service that is based on a Spring Mvc framework as example;
[0049] Fig. 3 is a flowchart schematically illustrating the microservice full-link monitoring method of the microservice full-link monitoring system provided by an embodiment of the present invention;
[0050] Fig. 4 is a view demonstrating a link page of the microservice full-link monitoring system performing full-link monitoring provided by an embodiment of the present invention; and
[0051] Fig. 5 is a view demonstrating a link page of the microservice full-link monitoring system performing full-link monitoring provided by an embodiment of the present invention.
DETAILED DESCRIPTION OF THE INVENTION
[0052] To make more lucid and clear the objectives, technical solutions and advantages of the present invention, the technical solutions in the embodiments of the present invention will be clearly and comprehensively described below with reference to the drawings in the embodiments of the present invention. Apparently, the embodiments as described are merely partial, rather than the entire, embodiments of the present invention. All other embodiments obtainable by persons ordinarily skilled in the art on the basis of the embodiments in the present invention and without spending any creative effort shall all be covered by the protection scope of the present invention.
[0053] In the microservice full-link monitoring system and method provided by the embodiments of the present invention, by providing such mainstream frameworks as Spring Mvc, Thrift, Dubbo, Hessian, Protobuf-RPC, Okttp, and Rsf, etc., with embedded point plug-ins, and by providing annotation AOP support for Java, the use is convenient, it suffices to perform full-link Date recue/Date received 2024-04-19 monitoring only through simple configuration, the problem concerning link embedded points in invoking services across threads is solved, there is no intrusion by codes, and monitoring conveniency and availability are greatly enhanced; by selecting monitored contents through the mode of configuration, monitored information is made configurable; the monitored data is sent to kafka in real time, and then aggregately stored at Druid in real time. The monitoring center can read druid data in real time for presenting and monitoring, the real timeliness is high, in addition, with such excellent open-source frameworks as kafka and Druid, throughput is high and computational capability is strong, distributed extending capability is provided, and large-scale scenarios are suited; codes start the child thread to invoke services, it is possible to automatically obtain TraceIDs (link IDs) and spanIDs (node IDs) of the parent thread, whereby integrity of the entire link is guaranteed, the difficult point of link transmission across threads is solved, and no hard coding is required for link transmission across threads. Accordingly, the microservice full-link monitoring system and method provided by the embodiments of the present invention can be broadly applied to full-link monitoring under various microservice scenarios.
[0054] Reference is made to specific embodiments below to describe in greater detail the microservice full-link monitoring system and method provided by the embodiments of the present invention.
[0055] Fig. 1 is a view schematically illustrating the structure of the microservice full-link monitoring system provided by an embodiment of the present invention. As shown in Fig. 1, the microservice full-link monitoring system provided by an embodiment of the present invention comprises a collection framework module 11, a message queue module 12, a computing center module 13, and a monitoring center module 14.
[0056] Collection framework module 11 is employed for collecting service invoking data and performing link series connection. Specifically, collecting service invoking data includes collecting service invoking data including link IDs, node IDs, service names, request parameters, server IPs, and response times. Exemplarily, collection framework module 11 collects such service Date recue/Date received 2024-04-19 invoking data as link IDs, node IDs, system IDs, invoker system IDs, server IPs, service names, service types, processing start times, processing end times, request parameters, user IDs, and response times, etc. As should be noted, monitored contents are selected according to the mode of configuration based on practical requirements, so as to collect plural types of service invoking data, to which no particular restriction is made in the embodiments of the present invention.
[0057] Moreover, the process of link series connection can specifically include setting up a link ID and a node ID or generating a new link ID and a node ID for a current service based on a link ID and a node ID transmitted from an invoker. Here, the link ID is set as a TraceID, and the node ID is set as a SpanID.
[0058] Specifically, message queue module 12 is employed for receiving in real time service invoking data coming from collection framework module 11, computing center module 13 is employed for subscribing service invoking data from message queue module 12 and aggregately storing the same in real time, and monitoring center module 14 is employed for reading monitor data stored by computing center module 13, and providing monitoring functions.
Message queue module 12 and computing center module 13 are both deployed in a distributed mode. Preferably, message queue module 12 employs a Kafka architecture, and computing center module 13 employs a Druid architecture. In addition, preferably, monitoring center module 14 is employed for reading monitor data stored by computing center module 13, and providing monitoring functions that include invoking link presentation, searching, monitoring, and alarming.
[0059] Fig. 2 is a view illustrating working demonstration of the entire architecture of the microservice full-link monitoring system provided by an embodiment of the present invention, taking Http service that is based on a Spring Mvc framework as example. Fig. 3 is a flowchart schematically illustrating the microservice full-link monitoring method of the microservice full-link monitoring system provided by an embodiment of the present invention, likewise taking for example Http service that is based on a Spring Mvc framework. Figs. 4 and 5 are views each demonstrating a link page of the microservice full-link monitoring system performing full-link Date recue/Date received 2024-04-19 monitoring provided by an embodiment of the present invention.
[0060] The microservice full-link monitoring method of the microservice full-link monitoring system provided by an embodiment of the present invention comprises a data collecting step and a data analysis processing step. Examples are taken here with the first service as service A, with the second service as service B, with the third service as service C, with the fourth service as service D; with the first node ID as 0, with the second node ID as 0.1, with the third node ID as 0.1.1, with the fourth node ID as 0.1.2; correspondingly with the first SpanID
as SpanID: 0, with the second SpanID as SpanID: 0.1, with the third SpanID as SpanID: 0.1.1, and with the fourth SpanID as SpanID: 0.1.2.
[0061] The data collecting step specifically includes the following sub-steps:
[0062] requesting a first service (service A) at the page;
[0063] the collection framework module generating a link ID for present invoking, and generating a first node ID (0) for a current request;
[0064] the first service (service A) invoking a second service (service B);
[0065] the collection framework module obtaining a link ID and a node ID of current invoking, generating a second node ID (0.1) for the second service (service B), and transmitting the link ID
and the second node ID to the second service (service B) through parameters;
[0066] the second service (service B) processing a request, and the collection framework module setting the transmitted link ID and node ID as the current link ID and node ID;
[0067] the second service (service B) starting a child thread to invoke a third service (service C), and a parent thread automatically passing the link ID and node ID
information to the child thread;
[0068] the collection framework module obtaining a link ID and a node ID of current invoking, generating a third node ID (0.1.1) for the third service (service C), and transmitting the link ID and Date recue/Date received 2024-04-19 the second node ID (0.1) to the third service (service C) through parameters;
[0069] the second service (service B) starting the child thread to invoke a fourth service (service D), and the parent thread automatically passing the link ID and node ID
information to the child thread; and
[0070] the collection framework module obtaining a link ID and a node ID of current invoking, generating a fourth node ID (0.1.2) for the third service (service C), and transmitting the link ID
and the third node ID (0.1.1) to the third service (service C) through parameters.
[0071] Preferably, the data collecting step is realized by specifically including the following sub-steps:
[0072] requesting a first service (service A) at a page;
[0073] the collection framework module generating a TraceID for present invoking, and generating a first SpanID (SpanID: 0) for a current request;
[0074] the first service (service A) invoking a second service (service B);
[0075] the collection framework module obtaining a TraceID and a SpanID of current invoking, generating a second SpanID (SpanID: 0.1) for the second service (service B), and transmitting the TraceID and the second SpanID to the second service (service B) through parameters;
[0076] the second service (service B) processing a request, and the collection framework module setting the transmitted link ID and node ID as the current TraceID and SpanID;
[0077] the second service (service B) starting a child thread to invoke a third service (service C), and a parent thread automatically passing the TraceID and SpanID
information to the child thread;
[0078] the collection framework module obtaining a TraceID and a SpanID of current invoking, generating a third SpanID (SpanID: 0.1.1) for the third service (service C), and transmitting the TraceID and the second SpanID to the third service (service C) through parameters;

Date recue/Date received 2024-04-19
[0079] the second service (service B) starting the child thread to invoke a fourth service (service D), and the parent thread automatically passing the TraceID and SpanID
information to the child thread; and
[0080] the collection framework module obtaining a TraceID and a SpanID of current invoking, generating a fourth SpanID (SpanID: 0.1.1) for the third service (service C), and transmitting the TraceID and the third SpanID to the third service (service C) through parameters.
[0081] The data analysis processing step specifically includes the following sub-steps:
[0082] the collection framework module collecting service invoking data, and sending the same to the message queue module;
[0083] the computing center module drawing the service invoking data out of the message queue module, and aggregately storing the same; and
[0084] the monitoring center module reading monitor data from the computing center module, and providing monitoring functions that include invoking link presentation, searching, monitoring, and alarming.
[0085] Preferably, the data analysis processing step is realized by specifically including the following sub-steps:
[0086] the collection framework module collecting service invoking data, and sending the same to the message queue module of a Kafka architecture;
[0087] the computing center module of a Druid architecture drawing the service invoking data out of the message queue module of a Kafka architecture, and aggregately storing the same; and
[0088] the monitoring center module reading monitor data from the computing center module of a Druid architecture, and providing monitoring functions that include invoking link presentation, searching, monitoring, and alarming.
[0089] As is notable, besides the aforementioned modes, the processes of the above data Date recue/Date received 2024-04-19 collecting step and data analysis processing step can be further realized via other modes, to which no specific restriction is made in the embodiments of the present invention.
[0090] As should be noted, when the microservice full-link monitoring system provided by the aforementioned embodiment triggers a microservice full-link monitoring business, it is merely exemplarily described by the being devided into the aforementioned various functional modules, while it is possible, in actual application, to assign the functions to different functional modules for completion based on actual requirements, that is to say, to divide the internal structure of the system into different functional modules to complete the entire or partial functions described above.
In addition, the microservice full-link monitoring system provided by the aforementioned embodiment pertains to the same conception as the microservice full-link monitoring method of the method embodiment ¨ see the corresponding method embodiment for its specific realization process, while no repetition will be made in this context.
[0091] All the above optional technical solutions can be randomly combined to form optional embodiments of the present invention, and these are not redundantly described one by one.
[0092] In summary, as compared with prior-art technology, the microservice full-link monitoring system and method provided by the embodiments of the present invention achieve the following advantageous effects.
[0093] 1. By providing such mainstream frameworks as Spring Mvc, Thrift, Dubbo, Hessian, Protobuf-RPC, Okttp, and Rsf, etc., with embedded point plug-ins, and by providing annotation AOP support for Java, the use is made convenient, it suffices to perform full-link monitoring only through simple configuration, the problem concerning link embedded points in invoking services across threads is solved, there is no intrusion by codes, and monitoring conveniency and availability are greatly enhanced.
[0094] 2. By selecting monitored contents (link IDs, node IDs, system IDs, invoker system IDs, server IPs, service names, service types, processing start times, processing end times, request parameters, user IDs, and response times, etc.) through the mode of configuration, monitored Date recue/Date received 2024-04-19 information is made configurable; the monitored data is sent to kafka in real time, and then aggregately stored at Druid in real time. The monitoring center can read druid data in real time for presenting and monitoring, the real timeliness is high, in addition, with such excellent open-source frameworks as kafka and Druid, throughput is high and computational capability is strong, distributed extending capability is provided, and large-scale scenarios are suited.
[0095] 3. Codes start the child thread to invoke services, it is possible to automatically obtain TraceIDs (link IDs) and spanIDs (node IDs) of the parent thread, whereby integrity of the entire link is guaranteed, the difficult point of link transmission across threads is solved, and no hard coding is required for link transmission across threads.
[0096] As understandable by persons ordinarily skilled in the art, realization of the entire or partial steps of the aforementioned embodiments can be completed by hardware, or by a program instructing relevant hardware, the program can be stored in a computer-readable storage medium, and the storage medium can be a read-only memory, a magnetic disk, or an optical disk, etc.
[0097] The embodiments of the present application are described with reference to flowcharts and/or block diagrams of the embodied method, device (system), and computer program product in the embodiments of the present application. As should be understood, it is possible to realize each flow and/or block in the flowcharts and/or block diagrams, and the combination of flows and/or blocks in the flowcharts and/or block diagrams by computer program instructions. These computer program instructions can be supplied to a general computer, a dedicated computer, an embedded processor or the processor of any other programmable data processing device to generate a machine, so as to generate a device for realizing the functions specified in one or more flow(s) of the flowcharts and/or one or more block(s) of the block diagrams by the instructions executed by the computer or the processor of any other programmable data processing device.
[0098] These computer program instructions can also be stored in a computer-readable memory capable of guiding a computer or any other programmable data processing device to operate in specific modes, which enables the instructions stored in the computer-readable memory to generate Date recue/Date received 2024-04-19 a product containing instructing device that realizes the functions specified in one or more flow(s) of the flowcharts and/or one or more block(s) of the block diagrams.
[0099] These computer program instructions can also be loaded to a computer or any other programmable data processing device, enabling to execute a series of operational steps on the computer or the any other programmable device to generate computer-realized processing, so that the instructions executed on the computer or the any other programmable device supply steps for realizing the functions specified in one or more flow(s) of the flowcharts and/or one or more block(s) of the block diagrams.
[0100] Although preferred embodiments in the embodiments of the present invention have been described, it is still possible for persons skilled in the art to make additional modifications and amendments to these embodiments upon learning the basic inventive concept.
Accordingly, the attached Claims are meant to subsume the preferred embodiments and all modifications and amendments that fall within the scope of the embodiments of the present application.
[0101] Apparently, it is possible for persons skilled in the art to make various modifications and variations to the present invention without departing from the spirit and scope of the present invention. Thusly, should such modifications and variations to the present invention fall within the range of the Claims and equivalent technology of the present invention, the present invention is also meant to cover such modifications and variations.
[0102] What the above describes is merely directed to preferred embodiments of the present invention, and is not meant to restrict the present invention. Any modification, equivalent substitution, and improvement makeable within the spirit and principle of the present invention shall all be covered by the protection scope of the present invention.
[0103] What is not described in detail in this description belongs to the prior art that is well known to those skilled in the art.
Date recue/Date received 2024-04-19

Claims (75)

Claims:
1. A method comprising:
requesting a first service;
the collection framework module generating the link ID for present invoking, and generating a first node ID for a current request;
the first service invoking a second service;
the collection framework module obtaining the link ID and the node ID of current invoking, generating a second node ID for the second service, and transmitting the link ID and the second node ID to the second service through parameters;
the second service processing a request and the collection framework module setting transmitted link ID and transmitted node ID as current link ID and current node ID;
the second service starting a child thread to invoke a third service, and a parent thread automatically passing link ID infomiation and node ID information to the child thread;
the collection framework module obtaining the link ID and the node ID of current invoking, generating a third node ID for the third service, and transmitting the link ID and the second node ID to the third service through the parameters;
the second service starting the child thread to invoke a fourth service, and the parent thread automatically passing the link ID infomiation and the node ID
infomiation to the child thread; and the collection framework module obtaining the link ID and the node ID of current invoking, generating a fourth node ID for the third service, and transmitting the link ID and the third node ID to the third service through the parameters.
2. The method of claim 1, wherein the data collecting comprises:

Date recue/Date received 2024-04-19 requesting the first service;
the collection framework module generating a TraceID for the present invoking, and generating a first SpanID for the current request;
the first service invoking the second service;
the collection framework module obtaining the TraceID and a SpanID of current invoking, generating a second SpanID for the second service, and transmitting the TraceID and the second SpanID to the second service through the parameters;
the second service processing the request and the collection framework module setting transmitted TraceID and SpanID as current TraceID and current SpanID;
the second service starting the child thread to invoke the third service, and the parent thread automatically passing TraceID infomiation and SpanID infomiation to the child thread;
the collection framework module obtaining the TraceID and the SpanID of current invoking, generating a third SpanID for the third service, and transmitting the TraceID and the second SpanID to the third service through the parameters;
the second service starting the child thread to invoke the fourth service and the parent thread automatically passing the TraceID infomiation and the SpanID
infomiation to the child thread; and the collection framework module obtaining the TraceID and the SpanID of current invoking, generating a fourth SpanID for the third service, and transmitting the TraceID and the third SpanID to the third service through the parameters.
3. The method of claim 1, further comprises a data analysis processing comprising:
the collection framework module collecting the service invoking data, and sending the service invoking data to the message queue module;

Date recue/Date received 2024-04-19 the computing center module drawing the service invoking data out of the message queue module, and aggregately storing the service invoking data; and the monitoring center module reading the monitor data from the computing center module, and providing the monitoring functions that include invoking link presentation, searching, monitoring, and alarming.
4. The method of claim 3, wherein the data analysis processing comprises:
the collection framework module collecting the service invoking data, and sending the service invoking data to the message queue module of a Kafka architecture;
the computing center module of a Druid architecture drawing the service invoking data out of the message queue module of the Kafka architecture, and aggregately storing the service invoking data; and the monitoring center module reading the monitor data from the computing center module of the Druid architecture, and providing the monitoring functions that include invoking the link presentation, searching, monitoring, and alarming.
5. A method applied in the device of any one of claims Error! Reference source not found. to Error! Reference source not found., wherein the method comprises data collecting comprising:
requesting a first service;
the collection framework module generating the link ID for present invoking, and generating a first node ID for a current request;
the first service invoking a second service;
the collection framework module obtaining the link ID and the node ID of current invoking, generating a second node ID for the second service, and transmitting the link ID and the second node ID to the second service through parameters;

Date recue/Date received 2024-04-19 the second service processing a request and the collection framework module setting transmitted link ID and transmitted node ID as current link ID and current node ID;
the second service starting a child thread to invoke a third service, and a parent thread automatically passing link ID infomiation and node ID information to the child thread;
the collection framework module obtaining the link ID and the node ID of current invoking, generating a third node ID for the third service, and transmitting the link ID and the second node ID to the third service through the parameters;
the second service starting the child thread to invoke a fourth service, and the parent thread automatically passing the link ID infomiation and the node ID
infomiation to the child thread; and the collection framework module obtaining the link ID and the node ID of current invoking, generating a fourth node ID for the third service, and transmitting the link ID and the third node ID to the third service through the parameters.
6. The method of claim 5, wherein the data collecting comprises:
requesting the first service;
the collection framework module generating a TraceID for the present invoking, and generating a first SpanID for the current request;
the first service invoking the second service;
the collection framework module obtaining the TraceID and a SpanID of current invoking, generating a second SpanID for the second service, and transmitting the TraceID and the second SpanID to the second service through the parameters;
the second service processing the request and the collection framework module setting transmitted TraceID and SpanID as current TraceID and current SpanID;

Date recue/Date received 2024-04-19 the second service starting the child thread to invoke the third service, and the parent thread automatically passing TraceID infomiation and SpanID infomiation to the child thread;
the collection framework module obtaining the TraceID and the SpanID of current invoking, generating a third SpanID for the third service, and transmitting the TraceID and the second SpanID to the third service through the parameters;
the second service starting the child thread to invoke the fourth service and the parent thread automatically passing the TraceID infomiation and the SpanID
infomiation to the child thread; and the collection framework module obtaining the TraceID and the SpanID of current invoking, generating a fourth SpanID for the third service, and transmitting the TraceID and the third SpanID to the third service through the parameters.
7. The method of claim 5, further comprises a data analysis processing comprising:
the collection framework module collecting the service invoking data, and sending the service invoking data to the message queue module;
the computing center module drawing the service invoking data out of the message queue module, and aggregately storing the service invoking data; and the monitoring center module reading the monitor data from the computing center module, and providing the monitoring functions that include invoking link presentation, searching, monitoring, and alarming.
8. The method of claim 7, wherein the data analysis processing comprises:
the collection framework module collecting the service invoking data, and sending the service invoking data to the message queue module of a Kafka architecture;
Date recue/Date received 2024-04-19 the computing center module of a Druid architecture drawing the service invoking data out of the message queue module of the Kafka architecture, and aggregately storing the service invoking data; and the monitoring center module reading the monitor data from the computing center module of the Druid architecture, and providing the monitoring functions that include invoking the link presentation, searching, monitoring, and alarming.
9. A method of any one of claims Error! Reference source not found. to Error!
Reference source not found., comprises data collecting comprising:
requesting a first service;
the collection framework module generating the link ID for present invoking, and generating a first node ID for a current request;
the first service invoking a second service;
the collection framework module obtaining the link ID and the node ID of current invoking, generating a second node ID for the second service, and transmitting the link ID and the second node ID to the second service through parameters;
the second service processing a request and the collection framework module setting transmitted link ID and transmitted node ID as current link ID and current node ID;
the second service starting a child thread to invoke a third service, and a parent thread automatically passing link ID information and node ID information to the child thread;
the collection framework module obtaining the link ID and the node ID of current invoking, generating a third node ID for the third service, and transmitting the link ID and the second node ID to the third service through the parameters;

Date recue/Date received 2024-04-19 the second service starting the child thread to invoke a fourth service, and the parent thread automatically passing the link ID infomiation and the node ID
infomiation to the child thread; and the collection framework module obtaining the link ID and the node ID of current invoking, generating a fourth node ID for the third service, and transmitting the link ID and the third node ID to the third service through the parameters.
10. The method of claim 9, wherein the data collecting comprises:
requesting the first service;
the collection framework module generating a TraceID for the present invoking, and generating a first SpanID for the current request;
the first service invoking the second service;
the collection framework module obtaining the TraceID and a SpanID of current invoking, generating a second SpanID for the second service, and transmitting the TraceID and the second SpanID to the second service through the parameters;
the second service processing the request and the collection framework module setting transmitted TraceID and SpanID as current TraceID and current SpanID;
the second service starting the child thread to invoke the third service, and the parent thread automatically passing TraceID infomiation and SpanID infomiation to the child thread;
the collection framework module obtaining the TraceID and the SpanID of current invoking, generating a third SpanID for the third service, and transmitting the TraceID and the second SpanID to the third service through the parameters;
the second service starting the child thread to invoke the fourth service and the parent thread automatically passing the TraceID infomiation and the SpanID
infomiation to the child thread; and Date recue/Date received 2024-04-19 the collection framework module obtaining the TraceID and the SpanID of current invoking, generating a fourth SpanID for the third service, and transmitting the TraceID and the third SpanID to the third service through the parameters.
11. The method of claim 9, further comprises a data analysis processing comprising:
the collection framework module collecting the service invoking data, and sending the service invoking data to the message queue module;
the computing center module drawing the service invoking data out of the message queue module, and aggregately storing the service invoking data; and the monitoring center module reading the monitor data from the computing center module, and providing the monitoring functions that include invoking link presentation, searching, monitoring, and alarming.
12. The method of claim 11, wherein the data analysis processing comprises:
the collection framework module collecting the service invoking data, and sending the service invoking data to the message queue module of a Kafka architecture;
the computing center module of a Druid architecture drawing the service invoking data out of the message queue module of the Kafka architecture, and aggregately storing the service invoking data; and the monitoring center module reading the monitor data from the computing center module of the Druid architecture, and providing the monitoring functions that include invoking the link presentation, searching, monitoring, and alarming.
13. The method of any one of claims 9 to 12, wherein monitored contents are selected according to mode of configuration based on practical requirements, to collect plural types of the service invoking data.
14. The method of any one of claims 9 to 13, wherein the data collecting and the data analysis processing is realized via other modes.

Date recue/Date received 2024-04-19
15. The method of any one of claims 9 to 14, wherein assigning functions to different functional modules for completion based on actual requirements, to divide internal structure into the different functional modules to complete entire or partial functions.
16. A method applied in the equipment of any one of claims Error! Reference source not found. to Error! Reference source not found., wherein the method comprises data collecting comprising:
requesting a first service;
the collection framework module generating the link ID for present invoking, and generating a first node ID for a current request;
the first service invoking a second service;
the collection framework module obtaining the link ID and the node ID of current invoking, generating a second node ID for the second service, and transmitting the link ID and the second node ID to the second service through parameters;
the second service processing a request and the collection framework module setting transmitted link ID and transmitted node ID as current link ID and current node ID;
the second service starting a child thread to invoke a third service, and a parent thread automatically passing link ID infonnation and node ID information to the child thread;
the collection framework module obtaining the link ID and the node ID of current invoking, generating a third node ID for the third service, and transmitting the link ID and the second node ID to the third service through the parameters;
the second service starting the child thread to invoke a fourth service, and the parent thread automatically passing the link ID infonnation and the node ID
infomiation to the child thread; and Date recue/Date received 2024-04-19 the collection framework module obtaining the link ID and the node ID of current invoking, generating a fourth node ID for the third service, and transmitting the link ID and the third node ID to the third service through the parameters.
17. The method of claim 16, wherein the data collecting comprises:
requesting the first service;
the collection framework module generating a TraceID for the present invoking, and generating a first SpanID for the current request;
the first service invoking the second service;
the collection framework module obtaining the TraceID and a SpanID of current invoking, generating a second SpanID for the second service, and transmitting the TraceID and the second SpanID to the second service through the parameters;
the second service processing the request and the collection framework module setting transmitted TraceID and SpanID as current TraceID and current SpanID;
the second service starting the child thread to invoke the third service, and the parent thread automatically passing TraceID infomiation and SpanID infomiation to the child thread;
the collection framework module obtaining the TraceID and the SpanID of current invoking, generating a third SpanID for the third service, and transmitting the TraceID and the second SpanID to the third service through the parameters;
the second service starting the child thread to invoke the fourth service and the parent thread automatically passing the TraceID infomiation and the SpanID
infomiation to the child thread; and the collection framework module obtaining the TraceID and the SpanID of current invoking, generating a fourth SpanID for the third service, and transmitting the TraceID and the third SpanID to the third service through the parameters.
Date recue/Date received 2024-04-19
18. The method of claim 16, further comprises a data analysis processing comprising:
the collection framework module collecting the service invoking data, and sending the service invoking data to the message queue module;
the computing center module drawing the service invoking data out of the message queue module, and aggregately storing the service invoking data; and the monitoring center module reading the monitor data from the computing center module, and providing the monitoring functions that include invoking link presentation, searching, monitoring, and alarming.
19. The method of claim 18, wherein the data analysis processing comprises:
the collection framework module collecting the service invoking data, and sending the service invoking data to the message queue module of a Kafka architecture;
the computing center module of a Druid architecture drawing the service invoking data out of the message queue module of the Kafka architecture, and aggregately storing the service invoking data; and the monitoring center module reading the monitor data from the computing center module of the Druid architecture, and providing the monitoring functions that include invoking the link presentation, searching, monitoring, and alarming.
20. A method applied in the memory of any one of claims Error! Reference source not found. to Error! Reference source not found., wherein the method comprises data collecting comprising:
requesting a first service;
the collection framework module generating the link ID for present invoking, and generating a first node ID for a current request;
the first service invoking a second service;

Date recue/Date received 2024-04-19 the collection framework module obtaining the link ID and the node ID of current invoking, generating a second node ID for the second service, and transmitting the link ID and the second node ID to the second service through parameters;
the second service processing a request and the collection framework module setting transmitted link ID and transmitted node ID as current link ID and current node ID;
the second service starting a child thread to invoke a third service, and a parent thread automatically passing link ID infomiation and node ID information to the child thread;
the collection framework module obtaining the link ID and the node ID of current invoking, generating a third node ID for the third service, and transmitting the link ID and the second node ID to the third service through the parameters;
the second service starting the child thread to invoke a fourth service, and the parent thread automatically passing the link ID infomiation and the node ID
infomiation to the child thread; and the collection framework module obtaining the link ID and the node ID of current invoking, generating a fourth node ID for the third service, and transmitting the link ID and the third node ID to the third service through the parameters.
21. The method of claim 20, wherein the data collecting comprises:
requesting the first service;
the collection framework module generating a TraceID for the present invoking, and generating a first SpanID for the current request;
the first service invoking the second service;
the collection framework module obtaining the TraceID and a SpanID of current invoking, generating a second SpanID for the second service, and transmitting the TraceID and the second SpanID to the second service through the parameters;

Date recue/Date received 2024-04-19 the second service processing the request and the collection framework module setting transmitted TraceID and SpanID as current TraceID and current SpanID;
the second service starting the child thread to invoke the third service, and the parent thread automatically passing TraceID infomiation and SpanID infomiation to the child thread;
the collection framework module obtaining the TraceID and the SpanID of current invoking, generating a third SpanID for the third service, and transmitting the TraceID and the second SpanID to the third service through the parameters;
the second service starting the child thread to invoke the fourth service and the parent thread automatically passing the TraceID infomiation and the SpanID
infomiation to the child thread; and the collection framework module obtaining the TraceID and the SpanID of current invoking, generating a fourth SpanID for the third service, and transmitting the TraceID and the third SpanID to the third service through the parameters.
22. The method of claim 20, further comprises a data analysis processing comprising:
the collection framework module collecting the service invoking data, and sending the service invoking data to the message queue module;
the computing center module drawing the service invoking data out of the message queue module, and aggregately storing the service invoking data; and the monitoring center module reading the monitor data from the computing center module, and providing the monitoring functions that include invoking link presentation, searching, monitoring, and alarming.
23. The method of claim 22, wherein the data analysis processing comprises:
the collection framework module collecting the service invoking data, and sending the service invoking data to the message queue module of a Kafka architecture;

Date recue/Date received 2024-04-19 the computing center module of a Druid architecture drawing the service invoking data out of the message queue module of the Kafka architecture, and aggregately storing the service invoking data; and the monitoring center module reading the monitor data from the computing center module of the Druid architecture, and providing the monitoring functions that include invoking the link presentation, searching, monitoring, and alarming.
24. A method applied in the system of any one of claims Error! Reference source not found. to Error! Reference source not found., wherein the method comprises data collecting comprising:
requesting a first service;
the collection framework module generating the link ID for present invoking, and generating a first node ID for a current request;
the first service invoking a second service;
the collection framework module obtaining the link ID and the node ID of current invoking, generating a second node ID for the second service, and transmitting the link ID and the second node ID to the second service through parameters;
the second service processing a request and the collection framework module setting transmitted link ID and transmitted node ID as current link ID and current node ID;
the second service starting a child thread to invoke a third service, and a parent thread automatically passing link ID information and node ID information to the child thread;
the collection framework module obtaining the link ID and the node ID of current invoking, generating a third node ID for the third service, and transmitting the link ID and the second node ID to the third service through the parameters;

Date recue/Date received 2024-04-19 the second service starting the child thread to invoke a fourth service, and the parent thread automatically passing the link ID infomiation and the node ID
infomiation to the child thread; and the collection framework module obtaining the link ID and the node ID of current invoking, generating a fourth node ID for the third service, and transmitting the link ID and the third node ID to the third service through the parameters.
25. The method of claim 24, wherein the data collecting comprises:
requesting the first service;
the collection framework module generating a TraceID for the present invoking, and generating a first SpanID for the current request;
the first service invoking the second service;
the collection framework module obtaining the TraceID and a SpanID of current invoking, generating a second SpanID for the second service, and transmitting the TraceID and the second SpanID to the second service through the parameters;
the second service processing the request and the collection framework module setting transmitted TraceID and SpanID as current TraceID and current SpanID;
the second service starting the child thread to invoke the third service, and the parent thread automatically passing TraceID infomiation and SpanID infomiation to the child thread;
the collection framework module obtaining the TraceID and the SpanID of current invoking, generating a third SpanID for the third service, and transmitting the TraceID and the second SpanID to the third service through the parameters;
the second service starting the child thread to invoke the fourth service and the parent thread automatically passing the TraceID infomiation and the SpanID
infomiation to the child thread; and Date recue/Date received 2024-04-19 the collection framework module obtaining the TraceID and the SpanID of current invoking, generating a fourth SpanID for the third service, and transmitting the TraceID and the third SpanID to the third service through the parameters.
26. The method of claim 24, further comprises a data analysis processing comprising:
the collection framework module collecting the service invoking data, and sending the service invoking data to the message queue module;
the computing center module drawing the service invoking data out of the message queue module, and aggregately storing the service invoking data; and the monitoring center module reading the monitor data from the computing center module, and providing the monitoring functions that include invoking link presentation, searching, monitoring, and alarming.
27. The method of claim 26, wherein the data analysis processing comprises:
the collection framework module collecting the service invoking data, and sending the service invoking data to the message queue module of a Kafka architecture;
the computing center module of a Druid architecture drawing the service invoking data out of the message queue module of the Kafka architecture, and aggregately storing the service invoking data; and the monitoring center module reading the monitor data from the computing center module of the Druid architecture, and providing the monitoring functions that include invoking the link presentation, searching, monitoring, and alarming.
28. A method applied in the device of any one of claims Error! Reference source not found. to Error! Reference source not found., wherein the method comprises data collecting comprising:
requesting a first service;

Date recue/Date received 2024-04-19 the collection framework module generating the link ID for present invoking, and generating a first node ID for a current request;
the first service invoking a second service;
the collection framework module obtaining the link ID and the node ID of current invoking, generating a second node ID for the second service, and transmitting the link ID and the second node ID to the second service through parameters;
the second service processing a request and the collection framework module setting transmitted link ID and transmitted node ID as current link ID and current node ID;
the second service starting a child thread to invoke a third service, and a parent thread automatically passing link ID infomiation and node ID information to the child thread;
the collection framework module obtaining the link ID and the node ID of current invoking, generating a third node ID for the third service, and transmitting the link ID and the second node ID to the third service through the parameters;
the second service starting the child thread to invoke a fourth service, and the parent thread automatically passing the link ID infomiation and the node ID
infomiation to the child thread; and the collection framework module obtaining the link ID and the node ID of current invoking, generating a fourth node ID for the third service, and transmitting the link ID and the third node ID to the third service through the parameters.
29. The method of claim 28, wherein the data collecting comprises:
requesting the first service;
the collection framework module generating a TraceID for the present invoking, and generating a first SpanID for the current request;
the first service invoking the second service;

Date recue/Date received 2024-04-19 the collection framework module obtaining the TraceID and a SpanID of current invoking, generating a second SpanID for the second service, and transmitting the TraceID and the second SpanID to the second service through the parameters;
the second service processing the request and the collection framework module setting transmitted TraceID and SpanID as current TraceID and current SpanID;
the second service starting the child thread to invoke the third service, and the parent thread automatically passing TraceID infomiation and SpanID infomiation to the child thread;
the collection framework module obtaining the TraceID and the SpanID of current invoking, generating a third SpanID for the third service, and transmitting the TraceID and the second SpanID to the third service through the parameters;
the second service starting the child thread to invoke the fourth service and the parent thread automatically passing the TraceID infomiation and the SpanID
infomiation to the child thread; and the collection framework module obtaining the TraceID and the SpanID of current invoking, generating a fourth SpanID for the third service, and transmitting the TraceID and the third SpanID to the third service through the parameters.
30. The method of claim 28, further comprises a data analysis processing comprising:
the collection framework module collecting the service invoking data, and sending the service invoking data to the message queue module;
the computing center module drawing the service invoking data out of the message queue module, and aggregately storing the service invoking data; and the monitoring center module reading the monitor data from the computing center module, and providing the monitoring functions that include invoking link presentation, searching, monitoring, and alarming.

Date recue/Date received 2024-04-19
31. The method of claim 30, wherein the data analysis processing comprises:
the collection framework module collecting the service invoking data, and sending the service invoking data to the message queue module of a Kafka architecture;
the computing center module of a Druid architecture drawing the service invoking data out of the message queue module of the Kafka architecture, and aggregately storing the service invoking data; and the monitoring center module reading the monitor data from the computing center module of the Druid architecture, and providing the monitoring functions that include invoking the link presentation, searching, monitoring, and alarming.
32. A method of any one of claims Error! Reference source not found. to Error!
Reference source not found., comprises data collecting comprising:
requesting a first service;
the collection framework module generating the link ID for present invoking, and generating a first node ID for a current request;
the first service invoking a second service;
the collection framework module obtaining the link ID and the node ID of current invoking, generating a second node ID for the second service, and transmitting the link ID and the second node ID to the second service through parameters;
the second service processing a request and the collection framework module setting transmitted link ID and transmitted node ID as current link ID and current node ID;
the second service starting a child thread to invoke a third service, and a parent thread automatically passing link ID information and node ID information to the child thread;

Date recue/Date received 2024-04-19 the collection framework module obtaining the link ID and the node ID of current invoking, generating a third node ID for the third service, and transmitting the link ID and the second node ID to the third service through the parameters;
the second service starting the child thread to invoke a fourth service, and the parent thread automatically passing the link ID infomiation and the node ID
infomiation to the child thread; and the collection framework module obtaining the link ID and the node ID of current invoking, generating a fourth node ID for the third service, and transmitting the link ID and the third node ID to the third service through the parameters.
33. The method of claim 32, wherein the data collecting comprises:
requesting the first service;
the collection framework module generating a TraceID for the present invoking, and generating a first SpanID for the current request;
the first service invoking the second service;
the collection framework module obtaining the TraceID and a SpanID of current invoking, generating a second SpanID for the second service, and transmitting the TraceID and the second SpanID to the second service through the parameters;
the second service processing the request and the collection framework module setting transmitted TraceID and SpanID as current TraceID and current SpanID;
the second service starting the child thread to invoke the third service, and the parent thread automatically passing TraceID infomiation and SpanID infomiation to the child thread;
the collection framework module obtaining the TraceID and the SpanID of current invoking, generating a third SpanID for the third service, and transmitting the TraceID and the second SpanID to the third service through the parameters;
Date recue/Date received 2024-04-19 the second service starting the child thread to invoke the fourth service and the parent thread automatically passing the TraceID infomiation and the SpanID
infomiation to the child thread; and the collection framework module obtaining the TraceID and the SpanID of current invoking, generating a fourth SpanID for the third service, and transmitting the TraceID and the third SpanID to the third service through the parameters.
34. The method of claim 32, further comprises a data analysis processing comprising:
the collection framework module collecting the service invoking data, and sending the service invoking data to the message queue module;
the computing center module drawing the service invoking data out of the message queue module, and aggregately storing the service invoking data; and the monitoring center module reading the monitor data from the computing center module, and providing the monitoring functions that include invoking link presentation, searching, monitoring, and alarming.
35. The method of claim 34, wherein the data analysis processing comprises:
the collection framework module collecting the service invoking data, and sending the service invoking data to the message queue module of a Kafka architecture;
the computing center module of a Druid architecture drawing the service invoking data out of the message queue module of the Kafka architecture, and aggregately storing the service invoking data; and the monitoring center module reading the monitor data from the computing center module of the Druid architecture, and providing the monitoring functions that include invoking the link presentation, searching, monitoring, and alarming.

Date recue/Date received 2024-04-19
36. The method of any one of claims 32 to 35, wherein monitored contents are selected according to mode of configuration based on practical requirements, to collect plural types of the service invoking data.
37. The method of any one of claims 32 to 36, wherein the data collecting and the data analysis processing is realized via other modes.
38. The method of any one of claims 32 to 37, wherein assigning functions to different functional modules for completion based on actual requirements, to divide internal structure into the different functional modules to complete entire or partial functions.
39. A method applied in the equipment of any one of claims Error! Reference source not found. to Error! Reference source not found., wherein the method comprises data collecting comprising:
requesting a first service;
the collection framework module generating the link ID for present invoking, and generating a first node ID for a current request;
the first service invoking a second service;
the collection framework module obtaining the link ID and the node ID of current invoking, generating a second node ID for the second service, and transmitting the link ID and the second node ID to the second service through parameters;
the second service processing a request and the collection framework module setting transmitted link ID and transmitted node ID as current link ID and current node ID;
the second service starting a child thread to invoke a third service, and a parent thread automatically passing link ID infonnation and node ID information to the child thread;

Date recue/Date received 2024-04-19 the collection framework module obtaining the link ID and the node ID of current invoking, generating a third node ID for the third service, and transmitting the link ID and the second node ID to the third service through the parameters;
the second service starting the child thread to invoke a fourth service, and the parent thread automatically passing the link ID infomiation and the node ID
infomiation to the child thread; and the collection framework module obtaining the link ID and the node ID of current invoking, generating a fourth node ID for the third service, and transmitting the link ID and the third node ID to the third service through the parameters.
40. The method of claim 39, wherein the data collecting comprises:
requesting the first service;
the collection framework module generating a TraceID for the present invoking, and generating a first SpanID for the current request;
the first service invoking the second service;
the collection framework module obtaining the TraceID and a SpanID of current invoking, generating a second SpanID for the second service, and transmitting the TraceID and the second SpanID to the second service through the parameters;
the second service processing the request and the collection framework module setting transmitted TraceID and SpanID as current TraceID and current SpanID;
the second service starting the child thread to invoke the third service, and the parent thread automatically passing TraceID infomiation and SpanID infomiation to the child thread;
the collection framework module obtaining the TraceID and the SpanID of current invoking, generating a third SpanID for the third service, and transmitting the TraceID and the second SpanID to the third service through the parameters;

Date recue/Date received 2024-04-19 the second service starting the child thread to invoke the fourth service and the parent thread automatically passing the TraceID infomiation and the SpanID
infomiation to the child thread; and the collection framework module obtaining the TraceID and the SpanID of current invoking, generating a fourth SpanID for the third service, and transmitting the TraceID and the third SpanID to the third service through the parameters.
41. The method of claim 39, further comprises a data analysis processing comprising:
the collection framework module collecting the service invoking data, and sending the service invoking data to the message queue module;
the computing center module drawing the service invoking data out of the message queue module, and aggregately storing the service invoking data; and the monitoring center module reading the monitor data from the computing center module, and providing the monitoring functions that include invoking link presentation, searching, monitoring, and alarming.
42. The method of claim 41, wherein the data analysis processing comprises:
the collection framework module collecting the service invoking data, and sending the service invoking data to the message queue module of a Kafka architecture;
the computing center module of a Druid architecture drawing the service invoking data out of the message queue module of the Kafka architecture, and aggregately storing the service invoking data; and the monitoring center module reading the monitor data from the computing center module of the Druid architecture, and providing the monitoring functions that include invoking the link presentation, searching, monitoring, and alarming.

Date recue/Date received 2024-04-19
43. A method applied in the memory of any one of claims Error! Reference source not found. to Error! Reference source not found., wherein the method comprises data collecting comprising:
requesting a first service;
the collection framework module generating the link ID for present invoking, and generating a first node ID for a current request;
the first service invoking a second service;
the collection framework module obtaining the link ID and the node ID of current invoking, generating a second node ID for the second service, and transmitting the link ID and the second node ID to the second service through parameters;
the second service processing a request and the collection framework module setting transmitted link ID and transmitted node ID as current link ID and current node ID;
the second service starting a child thread to invoke a third service, and a parent thread automatically passing link ID infomiation and node ID information to the child thread;
the collection framework module obtaining the link ID and the node ID of current invoking, generating a third node ID for the third service, and transmitting the link ID and the second node ID to the third service through the parameters;
the second service starting the child thread to invoke a fourth service, and the parent thread automatically passing the link ID infomiation and the node ID
infomiation to the child thread; and the collection framework module obtaining the link ID and the node ID of current invoking, generating a fourth node ID for the third service, and transmitting the link ID and the third node ID to the third service through the parameters.
44. The method of claim 43, wherein the data collecting comprises:
Date recue/Date received 2024-04-19 requesting the first service;
the collection framework module generating a TraceID for the present invoking, and generating a first SpanID for the current request;
the first service invoking the second service;
the collection framework module obtaining the TraceID and a SpanID of current invoking, generating a second SpanID for the second service, and transmitting the TraceID and the second SpanID to the second service through the parameters;
the second service processing the request and the collection framework module setting transmitted TraceID and SpanID as current TraceID and current SpanID;
the second service starting the child thread to invoke the third service, and the parent thread automatically passing TraceID infomiation and SpanID infomiation to the child thread;
the collection framework module obtaining the TraceID and the SpanID of current invoking, generating a third SpanID for the third service, and transmitting the TraceID and the second SpanID to the third service through the parameters;
the second service starting the child thread to invoke the fourth service and the parent thread automatically passing the TraceID infomiation and the SpanID
infomiation to the child thread; and the collection framework module obtaining the TraceID and the SpanID of current invoking, generating a fourth SpanID for the third service, and transmitting the TraceID and the third SpanID to the third service through the parameters.
45. The method of claim 43, further comprises a data analysis processing comprising:
the collection framework module collecting the service invoking data, and sending the service invoking data to the message queue module;

Date recue/Date received 2024-04-19 the computing center module drawing the service invoking data out of the message queue module, and aggregately storing the service invoking data; and the monitoring center module reading the monitor data from the computing center module, and providing the monitoring functions that include invoking link presentation, searching, monitoring, and alarming.
46. The method of claim 45, wherein the data analysis processing comprises:
the collection framework module collecting the service invoking data, and sending the service invoking data to the message queue module of a Kafka architecture;
the computing center module of a Druid architecture drawing the service invoking data out of the message queue module of the Kafka architecture, and aggregately storing the service invoking data; and the monitoring center module reading the monitor data from the computing center module of the Druid architecture, and providing the monitoring functions that include invoking the link presentation, searching, monitoring, and alarming.
47. A method applied in the system of any one of claims Error! Reference source not found. to Error! Reference source not found., wherein the method comprises data collecting comprising:
requesting a first service;
the collection framework module generating the link ID for present invoking, and generating a first node ID for a current request;
the first service invoking a second service;
the collection framework module obtaining the link ID and the node ID of current invoking, generating a second node ID for the second service, and transmitting the link ID and the second node ID to the second service through parameters;

Date recue/Date received 2024-04-19 the second service processing a request and the collection framework module setting transmitted link ID and transmitted node ID as current link ID and current node ID;
the second service starting a child thread to invoke a third service, and a parent thread automatically passing link ID infomiation and node ID information to the child thread;
the collection framework module obtaining the link ID and the node ID of current invoking, generating a third node ID for the third service, and transmitting the link ID and the second node ID to the third service through the parameters;
the second service starting the child thread to invoke a fourth service, and the parent thread automatically passing the link ID infomiation and the node ID
infomiation to the child thread; and the collection framework module obtaining the link ID and the node ID of current invoking, generating a fourth node ID for the third service, and transmitting the link ID and the third node ID to the third service through the parameters.
48. The method of claim 47, wherein the data collecting comprises:
requesting the first service;
the collection framework module generating a TraceID for the present invoking, and generating a first SpanID for the current request;
the first service invoking the second service;
the collection framework module obtaining the TraceID and a SpanID of current invoking, generating a second SpanID for the second service, and transmitting the TraceID and the second SpanID to the second service through the parameters;
the second service processing the request and the collection framework module setting transmitted TraceID and SpanID as current TraceID and current SpanID;

Date recue/Date received 2024-04-19 the second service starting the child thread to invoke the third service, and the parent thread automatically passing TraceID infomiation and SpanID infomiation to the child thread;
the collection framework module obtaining the TraceID and the SpanID of current invoking, generating a third SpanID for the third service, and transmitting the TraceID and the second SpanID to the third service through the parameters;
the second service starting the child thread to invoke the fourth service and the parent thread automatically passing the TraceID infomiation and the SpanID
infomiation to the child thread; and the collection framework module obtaining the TraceID and the SpanID of current invoking, generating a fourth SpanID for the third service, and transmitting the TraceID and the third SpanID to the third service through the parameters.
49. The method of claim 47, further comprises a data analysis processing comprising:
the collection framework module collecting the service invoking data, and sending the service invoking data to the message queue module;
the computing center module drawing the service invoking data out of the message queue module, and aggregately storing the service invoking data; and the monitoring center module reading the monitor data from the computing center module, and providing the monitoring functions that include invoking link presentation, searching, monitoring, and alarming.
50. The method of claim 49, wherein the data analysis processing comprises:
the collection framework module collecting the service invoking data, and sending the service invoking data to the message queue module of a Kafka architecture;

Date recue/Date received 2024-04-19 the computing center module of a Druid architecture drawing the service invoking data out of the message queue module of the Kafka architecture, and aggregately storing the service invoking data; and the monitoring center module reading the monitor data from the computing center module of the Druid architecture, and providing the monitoring functions that include invoking the link presentation, searching, monitoring, and alarming.
51. A method applied in the device of any one of claims Error! Reference source not found. to Error! Reference source not found., wherein the method comprises data collecting comprising:
requesting a first service;
the collection framework module generating the link ID for present invoking, and generating a first node ID for a current request;
the first service invoking a second service;
the collection framework module obtaining the link ID and the node ID of current invoking, generating a second node ID for the second service, and transmitting the link ID and the second node ID to the second service through parameters;
the second service processing a request and the collection framework module setting transmitted link ID and transmitted node ID as current link ID and current node ID;
the second service starting a child thread to invoke a third service, and a parent thread automatically passing link ID information and node ID information to the child thread;
the collection framework module obtaining the link ID and the node ID of current invoking, generating a third node ID for the third service, and transmitting the link ID and the second node ID to the third service through the parameters;
Date recue/Date received 2024-04-19 the second service starting the child thread to invoke a fourth service, and the parent thread automatically passing the link ID infomiation and the node ID
infomiation to the child thread; and the collection framework module obtaining the link ID and the node ID of current invoking, generating a fourth node ID for the third service, and transmitting the link ID and the third node ID to the third service through the parameters.
52. The method of claim 51, wherein the data collecting comprises:
requesting the first service;
the collection framework module generating a TraceID for the present invoking, and generating a first SpanID for the current request;
the first service invoking the second service;
the collection framework module obtaining the TraceID and a SpanID of current invoking, generating a second SpanID for the second service, and transmitting the TraceID and the second SpanID to the second service through the parameters;
the second service processing the request and the collection framework module setting transmitted TraceID and SpanID as current TraceID and current SpanID;
the second service starting the child thread to invoke the third service, and the parent thread automatically passing TraceID infomiation and SpanID infomiation to the child thread;
the collection framework module obtaining the TraceID and the SpanID of current invoking, generating a third SpanID for the third service, and transmitting the TraceID and the second SpanID to the third service through the parameters;
the second service starting the child thread to invoke the fourth service and the parent thread automatically passing the TraceID infomiation and the SpanID
infomiation to the child thread; and Date recue/Date received 2024-04-19 the collection framework module obtaining the TraceID and the SpanID of current invoking, generating a fourth SpanID for the third service, and transmitting the TraceID and the third SpanID to the third service through the parameters.
53. The method of claim 51, further comprises a data analysis processing comprising:
the collection framework module collecting the service invoking data, and sending the service invoking data to the message queue module;
the computing center module drawing the service invoking data out of the message queue module, and aggregately storing the service invoking data; and the monitoring center module reading the monitor data from the computing center module, and providing the monitoring functions that include invoking link presentation, searching, monitoring, and alarming.
54. The method of claim 53, wherein the data analysis processing comprises:
the collection framework module collecting the service invoking data, and sending the service invoking data to the message queue module of a Kafka architecture;
the computing center module of a Druid architecture drawing the service invoking data out of the message queue module of the Kafka architecture, and aggregately storing the service invoking data; and the monitoring center module reading the monitor data from the computing center module of the Druid architecture, and providing the monitoring functions that include invoking the link presentation, searching, monitoring, and alarming.
55. A method comprising:
collecting service invoking data, by a collection framework module;
performing link series connection by the collection framework module;

Date recue/Date received 2024-04-19 receiving by a message queue module, in real time, the service invoking data from the collection framework module;
subscribing the service invoking data from the message queue module by a computing center module;
storing the service invoking data in real time by the computing center module;
reading monitor data stored by the computing center module by a monitoring center module;
providing monitoring functions by the monitoring center module;
reading the monitor data stored by the computing center module;
providing the monitoring functions that include invoking link presentation, searching, monitoring, and alarming; and wherein the message queue module and the computing center module are deployed in a distributed mode.
56. The method of claim 55, wherein the collection framework module is configured to collect the service invoking data including link IDs, node IDs, service names, request parameters, server IPs, and response times.
57. The method of claim 55, wherein the collection framework module is configured to set up a link ID and a node ID or generate a new link ID and a new node ID for a current service based on the link ID and the node ID transmitted from an invoker.
58. The method of claim 56 or 57, wherein the link ID is a TraceID, and the node ID is a SpanID.
59. The method of claim 55, wherein the message queue module uses a Kafka architecture.
60. The method of claim 55, wherein the computing center module uses a Druid architecture.
61. A method of any one of claims 55 to 57, comprises data collecting comprising:

Date recue/Date received 2024-04-19 requesting a first service;
the collection framework module generating the link ID for present invoking, and generating a first node ID for a current request;
the first service invoking a second service;
the collection framework module obtaining the link ID and the node ID of current invoking, generating a second node ID for the second service, and transmitting the link ID and the second node ID to the second service through parameters;
the second service processing a request and the collection framework module setting transmitted link ID and transmitted node ID as current link ID and current node ID;
the second service starting a child thread to invoke a third service, and a parent thread automatically passing link ID infomiation and node ID information to the child thread;
the collection framework module obtaining the link ID and the node ID of current invoking, generating a third node ID for the third service, and transmitting the link ID and the second node ID to the third service through the parameters;
the second service starting the child thread to invoke a fourth service, and the parent thread automatically passing the link ID infomiation and the node ID
infomiation to the child thread; and the collection framework module obtaining the link ID and the node ID of current invoking, generating a fourth node ID for the third service, and transmitting the link ID and the third node ID to the third service through the parameters.
62. The method of claim 61, wherein the data collecting comprises:
requesting the first service;
the collection framework module generating a TraceID for the present invoking, and generating a first SpanID for the current request;

Date recue/Date received 2024-04-19 the first service invoking the second service;
the collection framework module obtaining the TraceID and a SpanID of current invoking, generating a second SpanID for the second service, and transmitting the TraceID and the second SpanID to the second service through the parameters;
the second service processing the request and the collection framework module setting transmitted TraceID and SpanID as current TraceID and current SpanID;
the second service starting the child thread to invoke the third service, and the parent thread automatically passing TraceID infomiation and SpanID infomiation to the child thread;
the collection framework module obtaining the TraceID and the SpanID of current invoking, generating a third SpanID for the third service, and transmitting the TraceID and the second SpanID to the third service through the parameters;
the second service starting the child thread to invoke the fourth service and the parent thread automatically passing the TraceID infomiation and the SpanID
infomiation to the child thread; and the collection framework module obtaining the TraceID and the SpanID of current invoking, generating a fourth SpanID for the third service, and transmitting the TraceID and the third SpanID to the third service through the parameters.
63. The method of claim 61, further comprises a data analysis processing comprising:
the collection framework module collecting the service invoking data, and sending the service invoking data to the message queue module;
the computing center module drawing the service invoking data out of the message queue module, and aggregately storing the service invoking data; and Date recue/Date received 2024-04-19 the monitoring center module reading the monitor data from the computing center module, and providing the monitoring functions that include invoking link presentation, searching, monitoring, and alarming.
64. The method of claim 63, wherein the data analysis processing comprises:
the collection framework module collecting the service invoking data, and sending the service invoking data to the message queue module of a Kafka architecture;
the computing center module of a Druid architecture drawing the service invoking data out of the message queue module of the Kafka architecture, and aggregately storing the service invoking data; and the monitoring center module reading the monitor data from the computing center module of the Druid architecture, and providing the monitoring functions that include invoking the link presentation, searching, monitoring, and alarming.
65. The method of any one of claims 55 to 64, wherein monitored contents are selected according to mode of configuration based on practical requirements, to collect plural types of the service invoking data.
66. The method of any one of claims 55 to 65, wherein the data collecting and the data analysis processing is realized via other modes.
67. The method of any one of claims 55 to 66, wherein assigning functions to different functional modules for completion based on actual requirements, to divide internal structure into the different functional modules to complete entire or partial functions.
68. A method applied in the equipment of any one of claims Error! Reference source not found. to Error! Reference source not found., wherein the method comprises data collecting comprising:
requesting a first service;

Date recue/Date received 2024-04-19 the collection framework module generating the link ID for present invoking, and generating a first node ID for a current request;
the first service invoking a second service;
the collection framework module obtaining the link ID and the node ID of current invoking, generating a second node ID for the second service, and transmitting the link ID and the second node ID to the second service through parameters;
the second service processing a request and the collection framework module setting transmitted link ID and transmitted node ID as current link ID and current node ID;
the second service starting a child thread to invoke a third service, and a parent thread automatically passing link ID infomiation and node ID information to the child thread;
the collection framework module obtaining the link ID and the node ID of current invoking, generating a third node ID for the third service, and transmitting the link ID and the second node ID to the third service through the parameters;
the second service starting the child thread to invoke a fourth service, and the parent thread automatically passing the link ID infomiation and the node ID
infomiation to the child thread; and the collection framework module obtaining the link ID and the node ID of current invoking, generating a fourth node ID for the third service, and transmitting the link ID and the third node ID to the third service through the parameters.
69. The method of claim 68, wherein the data collecting comprises:
requesting the first service;
the collection framework module generating a TraceID for the present invoking, and generating a first SpanID for the current request;
the first service invoking the second service;

Date recue/Date received 2024-04-19 the collection framework module obtaining the TraceID and a SpanID of current invoking, generating a second SpanID for the second service, and transmitting the TraceID and the second SpanID to the second service through the parameters;
the second service processing the request and the collection framework module setting transmitted TraceID and SpanID as current TraceID and current SpanID;
the second service starting the child thread to invoke the third service, and the parent thread automatically passing TraceID infomiation and SpanID infomiation to the child thread;
the collection framework module obtaining the TraceID and the SpanID of current invoking, generating a third SpanID for the third service, and transmitting the TraceID and the second SpanID to the third service through the parameters;
the second service starting the child thread to invoke the fourth service and the parent thread automatically passing the TraceID infomiation and the SpanID
infomiation to the child thread; and the collection framework module obtaining the TraceID and the SpanID of current invoking, generating a fourth SpanID for the third service, and transmitting the TraceID and the third SpanID to the third service through the parameters.
70. The method of claim 68, further comprises a data analysis processing comprising:
the collection framework module collecting the service invoking data, and sending the service invoking data to the message queue module;
the computing center module drawing the service invoking data out of the message queue module, and aggregately storing the service invoking data; and the monitoring center module reading the monitor data from the computing center module, and providing the monitoring functions that include invoking link presentation, searching, monitoring, and alarming.

Date recue/Date received 2024-04-19
71. The method of claim 70, wherein the data analysis processing comprises:
the collection framework module collecting the service invoking data, and sending the service invoking data to the message queue module of a Kafka architecture;
the computing center module of a Druid architecture drawing the service invoking data out of the message queue module of the Kafka architecture, and aggregately storing the service invoking data; and the monitoring center module reading the monitor data from the computing center module of the Druid architecture, and providing the monitoring functions that include invoking the link presentation, searching, monitoring, and alarming.
72. A method applied in the memory of any one of claims Error! Reference source not found. to Error! Reference source not found., wherein the method comprises data collecting comprising:
requesting a first service;
the collection framework module generating the link ID for present invoking, and generating a first node ID for a current request;
the first service invoking a second service;
the collection framework module obtaining the link ID and the node ID of current invoking, generating a second node ID for the second service, and transmitting the link ID and the second node ID to the second service through parameters;
the second service processing a request and the collection framework module setting transmitted link ID and transmitted node ID as current link ID and current node ID;
the second service starting a child thread to invoke a third service, and a parent thread automatically passing link ID information and node ID information to the child thread;

Date recue/Date received 2024-04-19 the collection framework module obtaining the link ID and the node ID of current invoking, generating a third node ID for the third service, and transmitting the link ID and the second node ID to the third service through the parameters;
the second service starting the child thread to invoke a fourth service, and the parent thread automatically passing the link ID infomiation and the node ID
infomiation to the child thread; and the collection framework module obtaining the link ID and the node ID of current invoking, generating a fourth node ID for the third service, and transmitting the link ID and the third node ID to the third service through the parameters.
73. The method of claim 72, wherein the data collecting comprises:
requesting the first service;
the collection framework module generating a TraceID for the present invoking, and generating a first SpanID for the current request;
the first service invoking the second service;
the collection framework module obtaining the TraceID and a SpanID of current invoking, generating a second SpanID for the second service, and transmitting the TraceID and the second SpanID to the second service through the parameters;
the second service processing the request and the collection framework module setting transmitted TraceID and SpanID as current TraceID and current SpanID;
the second service starting the child thread to invoke the third service, and the parent thread automatically passing TraceID infomiation and SpanID infomiation to the child thread;
the collection framework module obtaining the TraceID and the SpanID of current invoking, generating a third SpanID for the third service, and transmitting the TraceID and the second SpanID to the third service through the parameters;
Date recue/Date received 2024-04-19 the second service starting the child thread to invoke the fourth service and the parent thread automatically passing the TraceID infomiation and the SpanID
infomiation to the child thread; and the collection framework module obtaining the TraceID and the SpanID of current invoking, generating a fourth SpanID for the third service, and transmitting the TraceID and the third SpanID to the third service through the parameters.
74. The method of claim 72, further comprises a data analysis processing comprising:
the collection framework module collecting the service invoking data, and sending the service invoking data to the message queue module;
the computing center module drawing the service invoking data out of the message queue module, and aggregately storing the service invoking data; and the monitoring center module reading the monitor data from the computing center module, and providing the monitoring functions that include invoking link presentation, searching, monitoring, and alarming.
75. The method of claim 74, wherein the data analysis processing comprises:
the collection framework module collecting the service invoking data, and sending the service invoking data to the message queue module of a Kafka architecture;
the computing center module of a Druid architecture drawing the service invoking data out of the message queue module of the Kafka architecture, and aggregately storing the service invoking data; and the monitoring center module reading the monitor data from the computing center module of the Druid architecture, and providing the monitoring functions that include invoking the link presentation, searching, monitoring, and alarming.

Date recue/Date received 2024-04-19
CA3235906A 2019-01-18 2019-09-20 Microservice full-link monitoring system and method Pending CA3235906A1 (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
CN201910048998.5A CN111464373A (en) 2019-01-18 2019-01-18 Micro-service full-link monitoring system and method
CN201910048998.5 2019-01-18
CA3168303A CA3168303A1 (en) 2019-01-18 2019-09-20 Microservice full-link monitoring system and method

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
CA3168303A Division CA3168303A1 (en) 2019-01-18 2019-09-20 Microservice full-link monitoring system and method

Publications (1)

Publication Number Publication Date
CA3235906A1 true CA3235906A1 (en) 2020-07-23

Family

ID=71614006

Family Applications (2)

Application Number Title Priority Date Filing Date
CA3235906A Pending CA3235906A1 (en) 2019-01-18 2019-09-20 Microservice full-link monitoring system and method
CA3168303A Pending CA3168303A1 (en) 2019-01-18 2019-09-20 Microservice full-link monitoring system and method

Family Applications After (1)

Application Number Title Priority Date Filing Date
CA3168303A Pending CA3168303A1 (en) 2019-01-18 2019-09-20 Microservice full-link monitoring system and method

Country Status (3)

Country Link
CN (1) CN111464373A (en)
CA (2) CA3235906A1 (en)
WO (1) WO2020147336A1 (en)

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111934793B (en) * 2020-07-31 2022-08-02 中国工商银行股份有限公司 Internet architecture full link monitoring method and device
CN112330147A (en) * 2020-11-04 2021-02-05 北京思特奇信息技术股份有限公司 Service acceptance information monitoring method and device and storage medium
CN112486786B (en) * 2020-11-12 2022-08-09 贝壳技术有限公司 Calling link tracking method and device
CN112311894B (en) * 2020-11-12 2024-07-19 北京沃东天骏信息技术有限公司 Method, apparatus, electronic device, and computer-readable medium for generating information
CN112527537B (en) * 2020-11-30 2023-10-27 北京百度网讯科技有限公司 Quality monitoring method, device, equipment and medium of online service system
CN114629944B (en) * 2020-12-11 2024-05-14 来未来科技(浙江)有限公司 Method for statically analyzing full-link call condition of micro-service system
CN112770137B (en) * 2020-12-31 2022-06-17 重庆空间视创科技有限公司 Micro-service-based data acquisition method
CN113114533B (en) * 2021-04-08 2023-04-07 中国工商银行股份有限公司 Network time consumption display method and device for distributed service invocation
CN115314542A (en) * 2021-04-21 2022-11-08 深圳联友科技有限公司 Link tracking method and system based on Socket communication protocol
CN113157478B (en) * 2021-04-21 2024-05-10 多点(深圳)数字科技有限公司 Distributed system configured data acquisition and service alarm system
CN113111374B (en) * 2021-05-13 2022-09-23 上海交通大学 Industrial micro-service system of end edge cloud, data interaction method and medium
CN115473839B (en) * 2021-06-11 2024-03-05 北京字跳网络技术有限公司 Buried point-based data processing method, device, equipment and storage medium
CN113986955B (en) * 2021-11-01 2024-03-19 华青融天(北京)软件股份有限公司 Service chain determining method and device, electronic equipment and medium
CN114172949A (en) * 2021-12-10 2022-03-11 航天信息股份有限公司 Micro-service link monitoring and tracking method and system
CN114710430A (en) * 2022-04-06 2022-07-05 深圳依时货拉拉科技有限公司 Bidirectional communication control method, computer readable storage medium and computer device
CN116737514B (en) * 2023-08-15 2023-12-22 南京国睿信维软件有限公司 Automatic operation and maintenance method based on log and probe analysis
CN117743093B (en) * 2023-12-20 2024-08-06 北京优特捷信息技术有限公司 Data quality evaluation method, device, equipment and medium of call chain

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9203765B2 (en) * 2013-08-30 2015-12-01 Cisco Technology, Inc. Flow based network service insertion using a service chain identifier
US10069891B2 (en) * 2015-09-30 2018-09-04 Bank Of America Corporation Channel accessible single function micro service data collection process for light analytics
CN105608188A (en) * 2015-12-23 2016-05-25 北京奇虎科技有限公司 Data processing method and data processing device
CN107038162B (en) * 2016-02-03 2021-03-02 北京嘀嘀无限科技发展有限公司 Real-time data query method and system based on database log
US20180026856A1 (en) * 2016-07-21 2018-01-25 Cisco Technology, Inc. Orchestrating micro-service deployment based on network policy health
CN106487596B (en) * 2016-10-26 2019-12-13 宜人恒业科技发展（北京）有限公司 Distributed service tracking implementation method
CN106656604A (en) * 2016-12-23 2017-05-10 郑州云海信息技术有限公司 Microservice request management method, microservice controller and high-concurrence microservice architecture
US10841181B2 (en) * 2017-02-24 2020-11-17 Ciena Corporation Monitoring and auto-correction systems and methods for microservices
CN106790718A (en) * 2017-03-16 2017-05-31 北京搜狐新媒体信息技术有限公司 Service call link analysis method and system
CN108696400A (en) * 2017-04-12 2018-10-23 北京京东尚科信息技术有限公司 network monitoring method and device
CN108153850A (en) * 2017-06-01 2018-06-12 广州舜飞信息科技有限公司 A kind of user behavior statistical analysis technique and system
CN107135276A (en) * 2017-06-28 2017-09-05 北京中电普华信息技术有限公司 A kind of full link monitoring methods, devices and systems under micro services framework
CN107766205B (en) * 2017-10-10 2019-11-22 武汉大学 A kind of monitoring system and method towards the tracking of micro services calling process
CN108183927A (en) * 2017-11-22 2018-06-19 链家网（北京）科技有限公司 The monitoring method and system that a kind of distributed system link calls
CN107979508B (en) * 2017-11-24 2020-08-04 深圳乐信软件技术有限公司 Micro-service test method and device
CN108173915A (en) * 2017-12-21 2018-06-15 中国联合网络通信集团有限公司 Call chain processing method and processing device

Also Published As

Publication number Publication date
CA3168303A1 (en) 2020-07-23
CN111464373A (en) 2020-07-28
WO2020147336A1 (en) 2020-07-23

Similar Documents

Publication Publication Date Title
CA3235906A1 (en) Microservice full-link monitoring system and method
US20200090172A1 (en) Containerization of network services
US10909028B1 (en) Multi-version regression tester for source code
US9792194B2 (en) Performance regression manager for large scale systems
US20170046146A1 (en) Autonomously healing microservice-based applications
US9712410B1 (en) Local metrics in a service provider environment
US8707275B2 (en) Simulation environment for distributed programs
US10871918B2 (en) Writing composite objects to a data store
US10756959B1 (en) Integration of application performance monitoring with logs and infrastructure
US10552296B2 (en) Human-readable, language-independent stack trace summary generation
CN113220431B (en) Cross-cloud distributed data task scheduling method, device and storage medium
CN111124830B (en) Micro-service monitoring method and device
US20170083433A1 (en) Touch free disaster recovery
US20200136908A1 (en) Autodiscovery with Dynamic Configuration Launching
Bellavista et al. Adaptive Fault-Tolerance for Dynamic Resource Provisioning in Distributed Stream Processing Systems.
US10970055B2 (en) Identifying software and hardware bottlenecks
US20180150385A1 (en) Enabling non-blocking runtime application debugging for a single threaded server environment
US10621063B2 (en) System and method for dynamic domain-specific sequence diagram visualization
US20170091076A1 (en) Debugging remote vertex code on test machine
Choochotkaew et al. AutoDECK: automated declarative performance evaluation and tuning framework on kubernetes
CN116097258A (en) Ensuring secure provisioning of blockchain infrastructure
EP3362899B1 (en) Automatic system disaster recovery
Buzato et al. Optimizing Microservices Performance and Resource Utilization through Containerized Grouping: An Experimental Study
Chistyakov A software architecture for large multi-simulation Experiments over ad hoc networks using NS-3 discrete-event network simulator
Penberthy et al. Monitoring and Observability