CN111078504A - Distributed call chain tracking method and device, computer equipment and storage medium - Google Patents
Distributed call chain tracking method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN111078504A CN111078504A CN201911352761.2A CN201911352761A CN111078504A CN 111078504 A CN111078504 A CN 111078504A CN 201911352761 A CN201911352761 A CN 201911352761A CN 111078504 A CN111078504 A CN 111078504A
- Authority
- CN
- China
- Prior art keywords
- calling
- context object
- service
- request
- call chain
- 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
Links
- 238000000034 method Methods 0.000 title claims abstract description 56
- 238000012544 monitoring process Methods 0.000 claims abstract description 40
- 238000005192 partition Methods 0.000 claims abstract description 13
- 230000008569 process Effects 0.000 claims description 16
- 238000004590 computer program Methods 0.000 claims description 10
- 238000013500 data storage Methods 0.000 claims description 3
- 230000009471 action Effects 0.000 description 3
- 230000006872 improvement Effects 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 239000000306 component Substances 0.000 description 2
- 230000001419 dependent effect Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 108010015780 Viral Core Proteins Proteins 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 239000008358 core component Substances 0.000 description 1
- 238000013480 data collection Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
Images
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/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/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
-
- 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/323—Visualisation of programs or trace data
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Data Mining & Analysis (AREA)
- Mathematical Physics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a distributed call chain tracking method, a device, computer equipment and a storage medium, wherein the method comprises the following steps: when a request reaches a proxy gateway of the micro service, recording the log information of the current link, calling a context object and calling a context object ID; when one micro service calls other micro services, calling the dubbo service, automatically updating the ID of the calling context object, and recording the log information of the current link, the calling context object and the ID of the calling context object; pushing the call chain monitoring data obtained by the request to a corresponding partition through a producer service of kafka; then, the call chain monitoring data is stored to the elastic search through the kafka consumer service; and displaying the call chain monitoring data of the request in a zipkin interface mode. The invention can track the complete calling link of each request according to the ID of the calling link and collect the performance data of each service on the calling link, thereby improving the fault positioning speed.
Description
Technical Field
The present invention relates to the field of distributed service technologies, and in particular, to a method and an apparatus for tracking a distributed call chain, a computer device, and a storage medium.
Background
Under the framework of distributed services, the distributed services are interdependent and need to cooperate with each other to complete various service scenarios. For example, a request is initiated from a front end, and a final service is completed, so that many links are needed, and the links may be provided in a distributed service manner and are deployed on different servers. In such a complex distributed service scenario, help of a service tracking and analyzing tool is generally required for problem location, performance bottleneck query, exception log tracking, and the like.
At present, zipkin, a distributed tracking system sourced by Twitter, is used to collect timing data of services to solve the delay problem in the micro-service architecture, including data collection, storage, search and presentation. It is mainly to locate which problem in the service leads to a timeout, while the performance bottleneck of the system can be located quickly through the service invocation link.
zipkin represents the tracing of a request in a Trace (call chain) structure, and each Trace is split into a plurality of dependent spans (call context objects). In the microservice architecture, a user request may be handled by several services in the background, and then each service handling the request may be understood as a Span, and of course, the service may continue to request other services, and thus the Span is a tree structure.
zipkin is able to locate which problem in the service causes timeout, and at the same time, quickly locate the performance bottleneck of the system through the service invocation link, but is unable to collect log information of the service, such as error logs, service parameters of the request, processing results, and all sql (structured query language) statements executed by each invocation request.
In view of the above problems with the prior art, there is a need for optimization and improvement of the prior art.
Disclosure of Invention
The embodiment of the invention provides a distributed call chain tracking method, a distributed call chain tracking device, computer equipment and a storage medium, and aims to solve the problem that the conventional distributed call chain tracking method cannot acquire service log information.
In a first aspect, an embodiment of the present invention provides a distributed call chain tracking method, including:
when a user sends a request, embedding points through an interceptor to obtain a globally unique calling chain ID, and controlling the calling chain ID to accompany the whole calling chain process of the request;
when a request reaches a proxy gateway of the micro service, recording the log information of the current link, calling a context object and calling a context object ID;
when one micro service calls other micro services, calling the dubbo service, automatically updating the ID of the calling context object, and recording the log information of the current link, the calling context object and the ID of the calling context object;
pushing the call chain monitoring data obtained by the request to a corresponding partition through a producer service of kafka;
then, the call chain monitoring data is stored to the elastic search through the kafka consumer service;
and displaying the call chain monitoring data of the request in a zipkin interface mode.
Further, the displaying of the call chain monitoring data of the request in the form of a zipkin interface includes:
and presenting the hierarchical relation of each link in the call chain of the request in a tree structure form.
Further, the invoking context object includes: call chain ID, call context object ID, call method, service name, call time, call address, elapsed time, exception or error code.
Further, the log information includes all sql statements executed by the current link.
Further, the calling context object of the current link includes: the calling context object of the client and the calling context object of the server.
Further, when a micro-service calls another micro-service, the dubbo service is called, the calling context object ID is automatically updated, and the log information of the current link, the calling context object and the calling context object ID are recorded, including:
acquiring the ID of the calling context object of the previous link and acquiring the number of the calling context objects of the current link;
and numbering the calling context object of the current link according to the calling context object ID of the previous link to generate the calling context object ID of the current link.
Further, the numbering the calling context object of the current link according to the calling context object ID of the previous link to generate the calling context object ID of the current link includes:
and adding a new hierarchy number to the calling context object ID of the previous link, and giving the calling context object of the current link.
In a second aspect, an embodiment of the present invention provides a distributed call chain tracking apparatus, including:
the call chain tracking unit is used for embedding points through the interceptor when a user sends a request to obtain a globally unique call chain ID and controlling the call chain ID to accompany the whole process of the request;
the information recording unit is used for recording the log information, the calling context object and the calling context object ID of the current link when the request reaches the proxy gateway of the micro service;
the information updating unit is used for calling the dubbo service when one micro service calls other micro services, automatically updating the ID of the calling context object, and recording the log information of the current link, the calling context object and the ID of the calling context object;
the monitoring data pushing unit is used for pushing the calling chain monitoring data obtained by the request to the corresponding subarea through the kafka producer service;
the monitoring data storage unit is used for storing the calling chain monitoring data to the elastic search through the kafka consumer service;
and the monitoring data display unit is used for displaying the calling chain monitoring data of the request in a zipkin interface mode.
In a third aspect, an embodiment of the present invention provides a computer device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor implements the distributed call chain tracking method according to the first aspect when executing the computer program.
In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, where the computer-readable storage medium stores thereon a computer program, and the computer program, when executed by a processor, implements the distributed call chain tracking method according to the first aspect.
The embodiment of the invention provides a distributed call chain tracking method, a distributed call chain tracking device, computer equipment and a storage medium, wherein the method comprises the following steps: when a user sends a request, embedding points through an interceptor to obtain a globally unique calling chain ID, and controlling the calling chain ID to accompany the whole calling chain process of the request; when a request reaches a proxy gateway of the micro service, recording the log information of the current link, calling a context object and calling a context object ID; when one micro service calls other micro services, calling the dubbo service, automatically updating the ID of the calling context object, and recording the log information of the current link, the calling context object and the ID of the calling context object; pushing the call chain monitoring data obtained by the request to a corresponding partition through a producer service of kafka; then, the call chain monitoring data is stored to the elastic search through the kafka consumer service; and displaying the call chain monitoring data of the request in a zipkin interface mode. The method can track the complete calling link of each request according to the ID of the calling link and collect the performance data of each service on the calling link, thereby improving the fault positioning speed.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic flowchart of a distributed call chain tracking method according to an embodiment of the present invention;
fig. 2 is a schematic block diagram of a distributed call chain tracking apparatus according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It is also to be understood that the terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the specification of the present invention and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should be further understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
Referring to fig. 1, fig. 1 is a schematic flow chart of a distributed call chain tracking method according to an embodiment of the present invention, where the method includes steps S101 to S106:
s101, when a user sends a request, embedding points through an interceptor to obtain a globally unique calling chain ID, and controlling the calling chain ID to accompany the whole calling chain process of the request;
in this step, after the user sends a request, the interceptor httptraceinterposer performs Trace (call chain) embedding to obtain a globally unique TraceID (call chain ID), and the call chain ID can be concatenated with the call chain of the single request, so that the call chain ID accompanies the entire call chain process of the request.
S102, when a request reaches a proxy gateway of the micro service, recording the log information of the current link, calling a context object and calling a context object ID;
when a request reaches a proxy gateway of each service, a point is buried through an interceptor, a globally unique TraceID is obtained, and log information and Span (calling context object) information of the current link are recorded, wherein each Span has a Span Id (calling context object ID) for identification.
In one embodiment, the calling context object of the current link includes: the calling context object of the client and the calling context object of the server. Because a microservice serves as a client when sending a request and serves as a server when receiving the request in a link, the call context object of the current link includes both the call context object of the client and the call context object of the server. That is, one microservice may serve as a service consumer in one process or serve as a service provider in another process, so that information in the two processes needs to be recorded and recorded in the call context object of the current link.
The calling context object includes: call chain ID, call context object ID, call method (currentSpan), service name (ServiceName), call time (Date), call address (Addr), elapsed time (Destination), exception (isError), and error code (errorCode).
The log information includes all sql statements executed by the current link. In the embodiment of the invention, besides finding the performance problem of the micro-service, the sql sentence at the time can be restored, the specific sql-caused overtime can be seen, and the effect of service management can be more intuitively achieved by counting the error log of each request.
S103, when one micro service calls other micro services, calling the dubbo service, automatically updating the ID of the calling context object, and recording the log information of the current link, the calling context object and the ID of the calling context object;
in this step, when a micro service calls other micro services, a dubbo service is called, and the collection of the dubbo is to bury points through the rpcttracefilter. And meanwhile, the ID of the calling context object of the current link is automatically updated, and the calling context object and the ID of the calling context object of the current link are recorded. Thus, the call context objects of all links form a tree structure on the whole call chain.
Among them, dubbo is a high-performance, lightweight open source JavaRPC framework that provides three core capabilities: interface-oriented remote method invocation, intelligent fault tolerance and load balancing, and automatic registration and discovery of services. The major core components of dubbo are: remoting, namely a network communication framework, realizes a sync-over-async and request-response message mechanism; RPC, an abstraction of a remote procedure call, supports load balancing, disaster recovery, and clustering functions; registry, i.e., a service directory framework, is used for registration of services and service event publication and subscription.
In an embodiment, the invoking the dubbo service when a micro service invokes other micro services, automatically updating the invoking context object ID, and recording the invoking context object and the invoking context object ID of the current link includes:
acquiring the ID of the calling context object of the previous link and acquiring the number of the calling context objects of the current link;
and numbering the calling context object of the current link according to the calling context object ID of the previous link to generate the calling context object ID of the current link.
In the embodiment of the invention, each link has a superior-subordinate relationship, and certainly, more than one context object may be called in the current link, so that the context objects called in the current link need to be numbered in sequence, and the ID of the context object called in the current link is generated.
The step of numbering the calling context object of the current link according to the calling context object ID of the previous link to generate the calling context object ID of the current link comprises the following steps:
and adding a new hierarchy number to the calling context object ID of the previous link, and giving the calling context object of the current link.
Thus, a parent-child relationship is formed between the front Span and the back Span, namely, the calling context object of the previous link and the calling context object of the current link form a parent-child relationship, and the calling context object of the current link and the calling context object of the next link also form a parent-child relationship.
For example, if the calling context object ID of the previous link is 1 and the next level of the corresponding calling context object has three calling context objects, the corresponding calling context object IDs may be named 1.1,1.2 and 1.3, respectively. Whereas if the next level of 1.2 this call context object has two call context objects, it can be named 1.2.1 and 1.2.2, respectively.
S104, pushing the call chain monitoring data obtained by the request to a corresponding partition through a manufacturer service of kafka;
in this step, the call chain monitoring data obtained from the single request is pushed to the corresponding topic partition through the producer service of kafka.
S105, the call chain monitoring data is stored in the elastic search through the kafka consumer service;
and storing traceInfo to the elastic search through the kafka consumer service MQConsumer batch.
kafka is mq middleware developed based on java, and is dependent on zookeeper, and has the characteristics of high availability, high throughput and the like. It has the following advantages: the partition mechanism and the replay mechanism ensure that the message transmission has high reliability; stability, supporting clustering; high performance, high throughput; message broadcasting and unicasting are supported, and repeated consumption of messages can be realized according to reset offset.
Messages in kafka are classified by topic, through which the producer sends a message to kafka brooker (a server in a kafka cluster), and through which the consumer reads the message. the topics can be grouped in partitions on a physical level, and a plurality of different partitions are arranged under the same topic, and each partition physically corresponds to a directory (folder). partition is a physical concept in reality, while topic is a logical concept. The partition design allows the kafka throughput to be extended horizontally.
The ElasticSearch is a Lucene-based search server. It provides a distributed multi-user capable full-text search engine based on RESTful web interface. The Elasticsearch can be used to search various documents. The Elasticsearch is distributed, meaning that the index can be divided into shards, each shard can have 0 or more copies. Each node hosts one or more shards and acts as a coordinator delegating operations to the correct shard. The related data is typically stored in the same index, which consists of one or more master slices and zero or more copy slices.
And S106, displaying the call chain monitoring data of the request in a zipkin interface mode.
The main function of zipkin is to aggregate real-time monitoring data from various heterogeneous systems. The zipkin provides a web page for showing call chains, system dependencies, and the like in the zipkin. The embodiment of the invention can utilize the web page provided by zipkin to display the requested call chain monitoring data.
In the embodiment of the invention, the call chain monitoring data comprises log information of all links, call context objects, call context object IDs and call chain IDs of the current request.
In one embodiment, the step S106 includes:
and presenting the hierarchical relation of each link in the call chain of the request in a tree structure form.
That is, in the embodiment of the present invention, in order to more clearly show the whole process of the call chain, all links of the call chain of the current request may be shown in a tree structure, and since a hierarchical relationship exists between each link, the whole call process may be clearly shown in the tree structure.
Referring to fig. 2, fig. 2 is a schematic block diagram of a distributed call chain tracking apparatus 200 according to an embodiment of the present invention, where the apparatus 200 may include:
a call chain tracking unit 201, configured to perform point burying through an interceptor when a user sends a request, to obtain a globally unique call chain ID, and to control the call chain ID to accompany the call chain overall process of the request;
an information recording unit 202, configured to record log information of a current link, a call context object, and a call context object ID when a request reaches a proxy gateway of a microservice;
the information updating unit 203 is used for calling the dubbo service when one micro service calls other micro services, automatically updating the calling context object ID, and recording the log information of the current link, the calling context object and the calling context object ID;
the monitoring data pushing unit 204 is configured to push the call chain monitoring data obtained by the request to the corresponding partition through the producer service of the kafka;
the monitoring data storage unit 205 is used for storing the call chain monitoring data into an elastic search through the consumer service of kafka;
and the monitoring data display unit 206 is configured to display the call chain monitoring data of the request in a zipkin interface form.
In one embodiment, the monitoring data presentation unit 206 includes:
and the presentation unit is used for presenting the hierarchical relationship of each link in the call chain of the request in a tree structure form.
In one embodiment, the calling context object comprises: call chain ID, call context object ID, call method, service name, call time, call address, elapsed time, exception or error code.
In one embodiment, the log information includes all sql statements executed by the current link.
In one embodiment, the calling context object of the current link includes: the calling context object of the client and the calling context object of the server.
In an embodiment, the information updating unit 203 includes:
the acquiring unit is used for acquiring the ID of the calling context object of the previous link and acquiring the number of the calling context objects of the current link;
and the numbering unit is used for numbering the calling context object of the current link according to the calling context object ID of the previous link to generate the calling context object ID of the current link.
In one embodiment, the numbering unit comprises:
and the assigning unit is used for adding a new hierarchy number to the ID of the calling context object of the previous link and assigning the calling context object of the current link.
Since the embodiments of the apparatus portion and the method portion correspond to each other, please refer to the description of the embodiments of the method portion for the embodiments of the apparatus portion, which is not repeated here.
The invention also provides a computer-readable storage medium on which a computer program is stored, which, when executed by a processor, is adapted to implement the method provided by the above-mentioned embodiments. The storage medium may include: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The invention also provides a computer device, which may include a memory and a processor, wherein the memory stores a computer program, and the processor may implement the method provided by the above embodiment when calling the computer program in the memory. Of course, the computer device may also include various network interfaces, power supplies, and the like.
The embodiments are described in a progressive manner in the specification, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description. It should be noted that, for those skilled in the art, it is possible to make various improvements and modifications to the present invention without departing from the principle of the present invention, and those improvements and modifications also fall within the scope of the claims of the present invention.
It is further noted that, in the present specification, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
Claims (10)
1. A distributed call chain tracking method, comprising:
when a user sends a request, embedding points through an interceptor to obtain a globally unique calling chain ID, and controlling the calling chain ID to accompany the whole calling chain process of the request;
when a request reaches a proxy gateway of the micro service, recording the log information of the current link, calling a context object and calling a context object ID;
when one micro service calls other micro services, calling the dubbo service, automatically updating the ID of the calling context object, and recording the log information of the current link, the calling context object and the ID of the calling context object;
pushing the call chain monitoring data obtained by the request to a corresponding partition through a producer service of kafka;
then, the call chain monitoring data is stored to the elastic search through the kafka consumer service;
and displaying the call chain monitoring data of the request in a zipkin interface mode.
2. The distributed call chain tracking method according to claim 1, wherein the displaying of the call chain monitoring data of the current request in a zipkin interface form includes:
and presenting the hierarchical relation of each link in the call chain of the request in a tree structure form.
3. The distributed call chain tracking method of claim 1, wherein the call context object comprises: call chain ID, call context object ID, call method, service name, call time, call address, elapsed time, exception or error code.
4. The distributed call chain tracking method of claim 1, wherein the log information includes all sql statements executed by the current link.
5. The distributed call chain tracking method of claim 1, wherein the call context object of the current link comprises: the calling context object of the client and the calling context object of the server.
6. The distributed call chain tracking method according to claim 1, wherein the invoking dubbo service when a micro service invokes other micro services automatically updates the invoking context object ID and records the log information of the current link, the invoking context object and the invoking context object ID, comprises:
acquiring the ID of the calling context object of the previous link and acquiring the number of the calling context objects of the current link;
and numbering the calling context object of the current link according to the calling context object ID of the previous link to generate the calling context object ID of the current link.
7. The method as claimed in claim 6, wherein the step of numbering the context object of the current link according to the context object ID of the previous link to generate the context object ID of the current link comprises:
and adding a new hierarchy number to the calling context object ID of the previous link, and giving the calling context object of the current link.
8. A distributed call chain tracking apparatus, comprising:
the call chain tracking unit is used for embedding points through the interceptor when a user sends a request to obtain a globally unique call chain ID and controlling the call chain ID to accompany the whole process of the request;
the information recording unit is used for recording the log information, the calling context object and the calling context object ID of the current link when the request reaches the proxy gateway of the micro service;
the information updating unit is used for calling the dubbo service when one micro service calls other micro services, automatically updating the ID of the calling context object, and recording the log information of the current link, the calling context object and the ID of the calling context object;
the monitoring data pushing unit is used for pushing the calling chain monitoring data obtained by the request to the corresponding subarea through the kafka producer service;
the monitoring data storage unit is used for storing the calling chain monitoring data to the elastic search through the kafka consumer service;
and the monitoring data display unit is used for displaying the calling chain monitoring data of the request in a zipkin interface mode.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the distributed call chain tracking method of any one of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, having stored thereon a computer program which, when executed by a processor, implements the distributed call chain tracking method of any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911352761.2A CN111078504A (en) | 2019-12-25 | 2019-12-25 | Distributed call chain tracking method and device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911352761.2A CN111078504A (en) | 2019-12-25 | 2019-12-25 | Distributed call chain tracking method and device, computer equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111078504A true CN111078504A (en) | 2020-04-28 |
Family
ID=70317517
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911352761.2A Pending CN111078504A (en) | 2019-12-25 | 2019-12-25 | Distributed call chain tracking method and device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111078504A (en) |
Cited By (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111431773A (en) * | 2020-05-18 | 2020-07-17 | 江苏电力信息技术有限公司 | OpenTracing-based link tracking method |
| CN111538616A (en) * | 2020-04-30 | 2020-08-14 | 深圳前海微众银行股份有限公司 | Method, device and system for positioning abnormity and computer readable storage medium |
| CN111814145A (en) * | 2020-08-19 | 2020-10-23 | 深圳市富之富信息科技有限公司 | Request verification method and device based on log acquisition and computer equipment |
| CN111913789A (en) * | 2020-06-29 | 2020-11-10 | 浪潮通用软件有限公司 | Program tracking method, device and medium supporting micro-service architecture |
| CN111917844A (en) * | 2020-07-17 | 2020-11-10 | 中信银行股份有限公司 | Distributed service tracking method and device |
| CN111949491A (en) * | 2020-08-14 | 2020-11-17 | 中国工商银行股份有限公司 | SQL extraction method and device for MyBatis application program |
| CN112311894A (en) * | 2020-11-12 | 2021-02-02 | 北京沃东天骏信息技术有限公司 | Method, apparatus, electronic device, and computer-readable medium for generating information |
| CN112346872A (en) * | 2020-11-24 | 2021-02-09 | 中国工商银行股份有限公司 | Cloud computing capacity expansion method and device based on service call link |
| CN112491617A (en) * | 2020-11-27 | 2021-03-12 | 深圳乐信软件技术有限公司 | Link tracking method, device, electronic equipment and medium |
| CN113067717A (en) * | 2020-12-21 | 2021-07-02 | 开鑫金服(南京)信息服务有限公司 | Network request log chain tracking method, full link call monitoring system and medium |
| CN113114533A (en) * | 2021-04-08 | 2021-07-13 | 中国工商银行股份有限公司 | Network time consumption display method and device for distributed service invocation |
| CN113157592A (en) * | 2021-05-24 | 2021-07-23 | 杭州笨马网络技术有限公司 | Visual defect positioning method |
| WO2021151312A1 (en) * | 2020-08-07 | 2021-08-05 | 平安科技（深圳）有限公司 | Method for determining inter-service dependency, and related apparatus |
| CN113238844A (en) * | 2021-05-17 | 2021-08-10 | 上海中通吉网络技术有限公司 | Service arrangement execution path playback method |
| CN113472850A (en) * | 2021-05-31 | 2021-10-01 | 北京达佳互联信息技术有限公司 | Link data acquisition method, device, system, electronic equipment and storage medium |
| CN114116401A (en) * | 2021-11-30 | 2022-03-01 | 平安养老保险股份有限公司 | Method, device, equipment and medium for tracking and monitoring all links of cluster message |
| CN115037653A (en) * | 2022-06-28 | 2022-09-09 | 北京奇艺世纪科技有限公司 | Service flow monitoring method and device, electronic equipment and storage medium |
| CN115129491A (en) * | 2022-07-08 | 2022-09-30 | 盐城金堤科技有限公司 | Micro service request message tracking method, generating method, device, medium and equipment |
| CN116775440A (en) * | 2023-08-21 | 2023-09-19 | 青岛民航凯亚系统集成有限公司 | Log-level link tracking method and system based on airport production operation system |
| CN117639928A (en) * | 2023-12-04 | 2024-03-01 | 电子科技大学 | Online detection and correction method for mismatch of atmosphere optical communication transceiving optical axis |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150269326A1 (en) * | 2013-10-14 | 2015-09-24 | Medidata Solutions, Inc. | System and method for preserving causality of audits |
| CN106487596A (en) * | 2016-10-26 | 2017-03-08 | 宜人恒业科技发展（北京）有限公司 | Distributed Services follow the tracks of implementation method |
| CN109104302A (en) * | 2018-07-18 | 2018-12-28 | 杭州鑫合汇互联网金融服务有限公司 | A kind of full link tracing monitoring method |
| CN109756364A (en) * | 2018-12-07 | 2019-05-14 | 成都四方伟业软件股份有限公司 | A kind of micro services performance optimization system and analysis method based on log analysis |
| CN109992465A (en) * | 2017-12-29 | 2019-07-09 | 中国电信股份有限公司 | Service tracks method, apparatus and computer readable storage medium |
| CN110445643A (en) * | 2019-07-25 | 2019-11-12 | 泰康保险集团股份有限公司 | Asynchronous micro services call link tracking, device, medium and electronic equipment |
-
2019
- 2019-12-25 CN CN201911352761.2A patent/CN111078504A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150269326A1 (en) * | 2013-10-14 | 2015-09-24 | Medidata Solutions, Inc. | System and method for preserving causality of audits |
| CN106487596A (en) * | 2016-10-26 | 2017-03-08 | 宜人恒业科技发展（北京）有限公司 | Distributed Services follow the tracks of implementation method |
| CN109992465A (en) * | 2017-12-29 | 2019-07-09 | 中国电信股份有限公司 | Service tracks method, apparatus and computer readable storage medium |
| CN109104302A (en) * | 2018-07-18 | 2018-12-28 | 杭州鑫合汇互联网金融服务有限公司 | A kind of full link tracing monitoring method |
| CN109756364A (en) * | 2018-12-07 | 2019-05-14 | 成都四方伟业软件股份有限公司 | A kind of micro services performance optimization system and analysis method based on log analysis |
| CN110445643A (en) * | 2019-07-25 | 2019-11-12 | 泰康保险集团股份有限公司 | Asynchronous micro services call link tracking, device, medium and electronic equipment |
Non-Patent Citations (1)
| Title |
|---|
| 王伟军: "大数据分析", 重庆大学出版社, pages: 47 - 53 * |
Cited By (29)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111538616A (en) * | 2020-04-30 | 2020-08-14 | 深圳前海微众银行股份有限公司 | Method, device and system for positioning abnormity and computer readable storage medium |
| CN111431773A (en) * | 2020-05-18 | 2020-07-17 | 江苏电力信息技术有限公司 | OpenTracing-based link tracking method |
| CN111431773B (en) * | 2020-05-18 | 2022-01-28 | 江苏电力信息技术有限公司 | OpenTracing-based link tracking method |
| CN111913789A (en) * | 2020-06-29 | 2020-11-10 | 浪潮通用软件有限公司 | Program tracking method, device and medium supporting micro-service architecture |
| CN111917844A (en) * | 2020-07-17 | 2020-11-10 | 中信银行股份有限公司 | Distributed service tracking method and device |
| WO2021151312A1 (en) * | 2020-08-07 | 2021-08-05 | 平安科技（深圳）有限公司 | Method for determining inter-service dependency, and related apparatus |
| CN111949491A (en) * | 2020-08-14 | 2020-11-17 | 中国工商银行股份有限公司 | SQL extraction method and device for MyBatis application program |
| CN111949491B (en) * | 2020-08-14 | 2023-10-27 | 中国工商银行股份有限公司 | SQL extraction method and device of MyBatis application program |
| CN111814145A (en) * | 2020-08-19 | 2020-10-23 | 深圳市富之富信息科技有限公司 | Request verification method and device based on log acquisition and computer equipment |
| CN111814145B (en) * | 2020-08-19 | 2024-04-26 | 深圳市富之富信息科技有限公司 | Request verification method and device based on log acquisition and computer equipment |
| CN112311894A (en) * | 2020-11-12 | 2021-02-02 | 北京沃东天骏信息技术有限公司 | Method, apparatus, electronic device, and computer-readable medium for generating information |
| CN112346872B (en) * | 2020-11-24 | 2023-09-26 | 中国工商银行股份有限公司 | Cloud computing capacity expansion method and device based on service call link |
| CN112346872A (en) * | 2020-11-24 | 2021-02-09 | 中国工商银行股份有限公司 | Cloud computing capacity expansion method and device based on service call link |
| CN112491617A (en) * | 2020-11-27 | 2021-03-12 | 深圳乐信软件技术有限公司 | Link tracking method, device, electronic equipment and medium |
| CN113067717A (en) * | 2020-12-21 | 2021-07-02 | 开鑫金服(南京)信息服务有限公司 | Network request log chain tracking method, full link call monitoring system and medium |
| CN113114533A (en) * | 2021-04-08 | 2021-07-13 | 中国工商银行股份有限公司 | Network time consumption display method and device for distributed service invocation |
| CN113238844A (en) * | 2021-05-17 | 2021-08-10 | 上海中通吉网络技术有限公司 | Service arrangement execution path playback method |
| CN113157592A (en) * | 2021-05-24 | 2021-07-23 | 杭州笨马网络技术有限公司 | Visual defect positioning method |
| CN113472850B (en) * | 2021-05-31 | 2023-05-09 | 北京达佳互联信息技术有限公司 | Link data acquisition method, device, system, electronic equipment and storage medium |
| CN113472850A (en) * | 2021-05-31 | 2021-10-01 | 北京达佳互联信息技术有限公司 | Link data acquisition method, device, system, electronic equipment and storage medium |
| CN114116401A (en) * | 2021-11-30 | 2022-03-01 | 平安养老保险股份有限公司 | Method, device, equipment and medium for tracking and monitoring all links of cluster message |
| CN115037653A (en) * | 2022-06-28 | 2022-09-09 | 北京奇艺世纪科技有限公司 | Service flow monitoring method and device, electronic equipment and storage medium |
| CN115037653B (en) * | 2022-06-28 | 2023-10-13 | 北京奇艺世纪科技有限公司 | Service flow monitoring method, device, electronic equipment and storage medium |
| CN115129491A (en) * | 2022-07-08 | 2022-09-30 | 盐城金堤科技有限公司 | Micro service request message tracking method, generating method, device, medium and equipment |
| CN115129491B (en) * | 2022-07-08 | 2024-03-05 | 盐城天眼察微科技有限公司 | Micro-service request message tracking method, micro-service request message generating method, micro-service request message tracking device, micro-service request message generating medium and micro-service request message tracking equipment |
| CN116775440A (en) * | 2023-08-21 | 2023-09-19 | 青岛民航凯亚系统集成有限公司 | Log-level link tracking method and system based on airport production operation system |
| CN116775440B (en) * | 2023-08-21 | 2023-12-01 | 青岛民航凯亚系统集成有限公司 | Log-level link tracking method and system based on airport production operation system |
| CN117639928A (en) * | 2023-12-04 | 2024-03-01 | 电子科技大学 | Online detection and correction method for mismatch of atmosphere optical communication transceiving optical axis |
| CN117639928B (en) * | 2023-12-04 | 2024-05-14 | 电子科技大学 | Online detection and correction method for mismatch of atmosphere optical communication transceiving optical axis |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111078504A (en) | Distributed call chain tracking method and device, computer equipment and storage medium | |
| CN110636093B (en) | Microservice registration and discovery method, microservice registration and discovery device, storage medium and microservice system | |
| US10338958B1 (en) | Stream adapter for batch-oriented processing frameworks | |
| US9032011B2 (en) | Management of data object sharing among applications | |
| US20200304583A1 (en) | Input and output schema mappings | |
| US7970823B2 (en) | System for sharing data objects among applications | |
| TWI549080B (en) | The method, system and device for sending information of category information | |
| CN111143382B (en) | Data processing method, system and computer readable storage medium | |
| US10860604B1 (en) | Scalable tracking for database udpates according to a secondary index | |
| CN103685590A (en) | Method and system for obtaining IP (internet protocol) address | |
| CN110543512B (en) | Information synchronization method, device and system | |
| US20140089383A1 (en) | Method and system for automatic detecting and resolving apis | |
| US20100332582A1 (en) | Method and System for Service Contract Discovery | |
| CN113704790A (en) | Abnormal log information summarizing method and computer equipment | |
| CN114448686B (en) | Cross-network communication device and method based on micro-service | |
| CN110798358B (en) | Distributed service identification method and device, computer readable medium and electronic equipment | |
| US10713014B2 (en) | Multi-platform interface framework | |
| US10275467B2 (en) | Multi-level high availability model for an object storage service | |
| CN113472469B (en) | Data synchronization method, device, equipment and storage medium | |
| CN114398333A (en) | Incremental data real-time synchronization method and device, electronic equipment and storage medium | |
| CN113032477B (en) | Long-distance data synchronization method and device based on GTID and computing equipment | |
| US20190387075A1 (en) | Methods for exposing mainframe data as a web service and devices thereof | |
| US8005791B1 (en) | Methods and systems for publishing aggregated data to a business logic tier | |
| CN115051981B (en) | Zookeeper-based asynchronous downloading method and device | |
| US20220191104A1 (en) | Access management for a multi-endpoint data store |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200428 |