SpringCloud - Zipkin服务链路追踪

最新推荐文章于 2024-06-24 19:18:47 发布

Andy_Health

最新推荐文章于 2024-06-24 19:18:47 发布

阅读量203

点赞数

分类专栏：微服务文章标签： SpringCloud

原文链接：https://blog.csdn.net/mingwei_cheng/article/details/80997169

版权

微服务专栏收录该内容

19 篇文章 0 订阅

订阅专栏

zipkin的主要功能是收集来自各个系统的监控数据

zipkin主要四个模块：
1. Collector 接受或者收集各个应用传输的数据
2. Storage：负责存储接收到的数据，默认是存储在内存当中的，也可以支持存在MySQL当中
3. API：负责查询Storage中存储的数据，主要是提供给Web UI来使用
4. Web：主要是提供简单的web界面

工作流程
一个应用的代码发起HTTP get请求，经过Trace框架拦截，然后

把当前调用链的Trace信息添加到HTTP Header里面
记录当前调用的时间戳
发送HTTP请求，把trace相关的header信息携带上
调用结束之后，记录当前调用花费的时间
然后把上面流程产生的信息汇集成一个span，把这个span信息上传到zipkin的Collector模块

Zipkin

随着业务越来越复杂，系统也随之进行各种拆分，特别是随着微服务架构和容器技术的兴起，看似简单的一个应用，后台可能有几十个甚至几百个服务在支撑；一个前端的请求可能需要多次的服务调用最后才能完成；当请求变慢或者不可用时，我们无法得知是哪个后台服务引起的，这时就需要解决如何快速定位服务故障点，Zipkin分布式跟踪系统就能很好的解决这样的问题。

下载Zipkin

在目前的新版本中，Zipkin已独立成一个jar包，我们只需要下载它，用‘java -jar zipkin.jar’命令去运行它就好了，运行成功，我们访问http://localhost:9411/zipkin/ 注意这里最后一定要有‘/’不然会报404，或者你可以直接访问http://localhost:9411 出现如下界面，就表示，你的Zipkin服务启动成功了。
在这里插入图片描述

创建两个相互调用程序

只有在对外暴露的接口被调用时，Zipkin才会收集数据，这就是为什么叫服务追踪了。
创建两个新Model，我将他们命名为Service-Hey，Service-Hello。两个项目的pom.xml文件的依赖一致，我就只贴出Service-Hey的pom.xml文件了。

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>

    <groupId>cn.pony</groupId>
    <artifactId>service_hello</artifactId>
    <version>0.0.1-SNAPSHOT</version>
    <packaging>jar</packaging>

    <name>service_hello</name>
    <description>Demo project for Spring Boot</description>

    <parent>
        <groupId>org.springframework.boot</groupId>
        <artifactId>spring-boot-starter-parent</artifactId>
        <version>2.0.3.RELEASE</version>
        <relativePath/> <!-- lookup parent from repository -->
    </parent>

    <properties>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
        <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
        <java.version>1.8</java.version>
        <spring-cloud.version>Finchley.RELEASE</spring-cloud.version>
    </properties>

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

        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter-test</artifactId>
            <scope>test</scope>
        </dependency>
    </dependencies>

    <dependencyManagement>
        <dependencies>
            <dependency>
                <groupId>org.springframework.cloud</groupId>
                <artifactId>spring-cloud-dependencies</artifactId>
                <version>${spring-cloud.version}</version>
                <type>pom</type>
                <scope>import</scope>
            </dependency>
        </dependencies>
    </dependencyManagement>

    <build>
        <plugins>
            <plugin>
                <groupId>org.springframework.boot</groupId>
                <artifactId>spring-boot-maven-plugin</artifactId>
            </plugin>
        </plugins>
    </build>

</project>

而后，我们修改Service-Hey的启动类。

@SpringBootApplication
@RestController
public class ServiceHeyApplication {

    public static void main(String[] args) {
        SpringApplication.run(ServiceHeyApplication.class, args);
    }

    private static final Logger LOG = Logger.getLogger(ServiceHeyApplication.class.getName());


    @Autowired
    private RestTemplate restTemplate;

    @Bean
    public RestTemplate getRestTemplate(){
        return new RestTemplate();
    }

    @RequestMapping("/hello")
    public String hello(){
        LOG.log(Level.INFO, "hey开始调用跟踪了");
        return "你好呀，这里是service-hey";
    }
    @RequestMapping("/hey")
    public String info(){
        LOG.log(Level.INFO, "hey开始调用跟踪了");
        return restTemplate.getForObject("http://localhost:9009/info",String.class);
    }

    @Bean
    public Sampler defaultSampler(){
        return Sampler.ALWAYS_SAMPLE;
    }
}

修改Service-Hello的启动类

@SpringBootApplication
@RestController
public class ServiceHelloApplication {

    public static void main(String[] args) {
        SpringApplication.run(ServiceHelloApplication.class, args);
    }

    private static final Logger LOG = Logger.getLogger(ServiceHelloApplication.class.getName());


    @Autowired
    private RestTemplate restTemplate;

    @Bean
    public RestTemplate getRestTemplate(){
        return new RestTemplate();
    }

    @RequestMapping("/hello")
    public String hello(){
        LOG.log(Level.INFO, "开始调用跟踪service-hello");
        return restTemplate.getForObject("http://localhost:9008/hey", String.class);
    }
    @RequestMapping("/info")
    public String info(){
        LOG.log(Level.INFO, "开始调用跟踪service-hello");
        return "你好呀，这里是service-hello";

    }
    @Bean
    public Sampler defaultSampler(){
        return Sampler.ALWAYS_SAMPLE;
    }
}

开始追踪

启动两个项目，访问http://localhost:9009/hello，出现:

你好呀，这里是service-hello

然后，我们再打开Zipkin的管理界面，http://localhost:9411/zipkin/，选择依赖分析，可以发现服务之间的依赖关系：在这里插入图片描述
选择查找调用链，可以看到具体服务相互调用的数据：

点击下面蓝色的链接，可以看到更为详细的信息：

1. docker安装zipkin

1.搜索镜像

docker search zipkin

2. 拉取镜像

不使用标签，直接拉去最新版

docker pull openzipkin/zipkin

3. 启动镜像

docker run -d --restart always -p 9411:9411 --name zipkin openzipkin/zipkin

4. 访问

浏览器访问http://IP:9411/zipkin/

5. zipkin 基于数据库

STORAGE_TYPE=mysql MYSQL_USER=root MYSQL_PASS=***MYSQL_HOST=*.*.*.* MYSQL_TCP_PORT=3306 nohup java -jar  zipkin-server-2.12.9-exec.jar &

/*
 Navicat Premium Data Transfer

 Source Server         : ***
 Source Server Type    : MySQL
 Source Server Version : 50711
 Source Host           : ***
 Source Schema         : zipkin

 Target Server Type    : MySQL
 Target Server Version : 50711
 File Encoding         : 65001

 Date: 21/07/2021 14:05:09
*/

SET NAMES utf8mb4;
SET FOREIGN_KEY_CHECKS = 0;

-- ----------------------------
-- Table structure for zipkin_annotations
-- ----------------------------
DROP TABLE IF EXISTS `zipkin_annotations`;
CREATE TABLE `zipkin_annotations`  (
  `trace_id_high` bigint(20) NOT NULL DEFAULT 0 COMMENT 'If non zero, this means the trace uses 128 bit traceIds instead of 64 bit',
  `trace_id` bigint(20) NOT NULL COMMENT 'coincides with zipkin_spans.trace_id',
  `span_id` bigint(20) NOT NULL COMMENT 'coincides with zipkin_spans.id',
  `a_key` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL COMMENT 'BinaryAnnotation.key or Annotation.value if type == -1',
  `a_value` blob NULL COMMENT 'BinaryAnnotation.value(), which must be smaller than 64KB',
  `a_type` int(11) NOT NULL COMMENT 'BinaryAnnotation.type() or -1 if Annotation',
  `a_timestamp` bigint(20) NULL DEFAULT NULL COMMENT 'Used to implement TTL; Annotation.timestamp or zipkin_spans.timestamp',
  `endpoint_ipv4` int(11) NULL DEFAULT NULL COMMENT 'Null when Binary/Annotation.endpoint is null',
  `endpoint_ipv6` binary(16) NULL DEFAULT NULL COMMENT 'Null when Binary/Annotation.endpoint is null, or no IPv6 address',
  `endpoint_port` smallint(6) NULL DEFAULT NULL COMMENT 'Null when Binary/Annotation.endpoint is null',
  `endpoint_service_name` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL COMMENT 'Null when Binary/Annotation.endpoint is null',
  UNIQUE INDEX `trace_id_high`(`trace_id_high`, `trace_id`, `span_id`, `a_key`, `a_timestamp`) USING BTREE COMMENT 'Ignore insert on duplicate',
  INDEX `trace_id_high_2`(`trace_id_high`, `trace_id`, `span_id`) USING BTREE COMMENT 'for joining with zipkin_spans',
  INDEX `trace_id_high_3`(`trace_id_high`, `trace_id`) USING BTREE COMMENT 'for getTraces/ByIds',
  INDEX `endpoint_service_name`(`endpoint_service_name`) USING BTREE COMMENT 'for getTraces and getServiceNames',
  INDEX `a_type`(`a_type`) USING BTREE COMMENT 'for getTraces and autocomplete values',
  INDEX `a_key`(`a_key`) USING BTREE COMMENT 'for getTraces and autocomplete values',
  INDEX `trace_id`(`trace_id`, `span_id`, `a_key`) USING BTREE COMMENT 'for dependencies job'
) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Compressed;

-- ----------------------------
-- Table structure for zipkin_dependencies
-- ----------------------------
DROP TABLE IF EXISTS `zipkin_dependencies`;
CREATE TABLE `zipkin_dependencies`  (
  `day` date NOT NULL,
  `parent` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
  `child` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
  `call_count` bigint(20) NULL DEFAULT NULL,
  `error_count` bigint(20) NULL DEFAULT NULL,
  PRIMARY KEY (`day`, `parent`, `child`) USING BTREE
) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Compressed;

-- ----------------------------
-- Table structure for zipkin_spans
-- ----------------------------
DROP TABLE IF EXISTS `zipkin_spans`;
CREATE TABLE `zipkin_spans`  (
  `trace_id_high` bigint(20) NOT NULL DEFAULT 0 COMMENT 'If non zero, this means the trace uses 128 bit traceIds instead of 64 bit',
  `trace_id` bigint(20) NOT NULL,
  `id` bigint(20) NOT NULL,
  `name` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
  `remote_service_name` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `parent_id` bigint(20) NULL DEFAULT NULL,
  `debug` bit(1) NULL DEFAULT NULL,
  `start_ts` bigint(20) NULL DEFAULT NULL COMMENT 'Span.timestamp(): epoch micros used for endTs query and to implement TTL',
  `duration` bigint(20) NULL DEFAULT NULL COMMENT 'Span.duration(): micros used for minDuration and maxDuration query',
  PRIMARY KEY (`trace_id_high`, `trace_id`, `id`) USING BTREE,
  INDEX `trace_id_high`(`trace_id_high`, `trace_id`) USING BTREE COMMENT 'for getTracesByIds',
  INDEX `name`(`name`) USING BTREE COMMENT 'for getTraces and getSpanNames',
  INDEX `remote_service_name`(`remote_service_name`) USING BTREE COMMENT 'for getTraces and getRemoteServiceNames',
  INDEX `start_ts`(`start_ts`) USING BTREE COMMENT 'for getTraces ordering and range'
) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Compressed;

SET FOREIGN_KEY_CHECKS = 1;

Andy_Health

关注

0
点赞
踩
1

收藏

觉得还不错? 一键收藏
0
评论
SpringCloud - Zipkin服务链路追踪

zipkin的主要功能是收集来自各个系统的监控数据zipkin主要四个模块：1. Collector 接受或者收集各个应用传输的数据2. Storage：负责存储接收到的数据，默认是存储在内存当中的，也可以支持存在MySQL当中3. API：负责查询Storage中存储的数据，主要是提供给Web UI来使用4. Web：主要是提供简单的web界面工作流程一个应用的代码发起HTTP get请求，经过Trace框架拦截，然后把当前调用链的Trace信息添加到HTTP Header里面记录当前
复制链接

扫一扫

专栏目录