Sleuth+zipkin to track distributed service links

Why

Microservice architecture is a distributed architecture , It divides service units by business , A distributed system often has many services

unit . Due to the large number of service units , Business complexity , If Errors and exceptions have occurred , It's hard to locate . The main

Embodied in , A request may need to call many services , And the call complexity of internal services , Decide the problem is difficult

location . So in the microservice Architecture , Distributed link tracking must be implemented , To follow up on the services involved in a request ,

What is the order of participation , thus The steps to achieve each request are clearly visible , Something went wrong. , Positioning soon .

The link tracking component has Google Of Dapper,Twitter Of Zipkin, And Ali's Eagleeye （ Eagle eye ） etc. , it

We are all excellent open source components for link tracking .

Basic terminology

Span（ span ）： Basic work unit , Send a remote scheduling task There will be a Span,Span It's one

individual 64 position ID Uniquely identified ,Trace It's another one 64 position ID Uniquely identified ,Span There are other data messages

Rest , For example, abstract 、 Timestamp event 、Span Of ID、 And progress ID.

Trace（ track ）： A series of Span A tree structure of . Requesting a microservice system's API Interface ,

This API Interface , Multiple microservices need to be invoked , Calling each microservice produces a new Span, all

Generated by this request Span That makes up this Trace.

Annotation（ mark ）： Used to record an event in time , Some core annotations are used to define the opening of a request

Start and end . These annotations include the following ：

cs - Client Sent - Client sends a request , This annotation describes this Span The beginning of

sr - Server Received - The server gets the request and is ready to start processing it , If you take it sr subtract cs Time stamp

Then we can get the time of network transmission .

ss - Server Sent （ Server sends response ）– This annotation indicates the completion of the request processing ( When the request is returned to the customer

End ), If ss Time stamp subtraction of sr Time stamp , You can get the time requested by the server .

cr - Client Received （ Client receives response ）- here Span The end of , If cr Time stamp subtraction of

cs You can get the time consumed by the whole request by using the timestamp .

Project integration Sleuth+Zipkin

Import maven rely on

<dependency>
    <groupId>org.springframework.cloud</groupId>
    <artifactId>spring-cloud-starter-zipkin</artifactId>
</dependency>

<dependencyManagement>
    <dependencies>
        <dependency>
            <groupId>org.springframework.cloud</groupId>
            <artifactId>spring-cloud-dependencies</artifactId>
            <version>Greenwich.SR3</version>
            <type>pom</type>
            <scope>import</scope>
        </dependency>
    </dependencies>
</dependencyManagement>

properties The configuration file

spring.zipkin.base-url=http://121.37.191.188:9411/
spring.zipkin.discovery-client-enabled=false
spring.zipkin.sender.type=web
spring.sleuth.sampler.probability=1

test

 

summary

After the interface of the distributed microservice system has problems , You can use this Zipkin Check the specific problem