环境

1.Spring Cloud版本：Hoxton.RELEASE
2.zipkin版本：2.12.9（下载地址：https://dl.bintray.com/openzipkin/maven/io/zipkin/java/zipkin-server/）
3.RabbitMQ版本：3.8.3（rabbitmq：https://www.rabbitmq.com/install-windows.html erlang：https://www.erlang.org/downloads 注意rabbitmq和erlang对应版本，参考https://www.rabbitmq.com/which-erlang.html）
4.mysql版本：8.0.19

使用zipkin

1.下载地址见开头
2.在对应模块下的pom文件引入依赖：

        <!--链路追踪-->
        <dependency>
            <groupId>org.springframework.cloud</groupId>
            <artifactId>spring-cloud-sleuth-zipkin</artifactId>
        </dependency>

3.在属性文件中加上：

spring:
    zipkin: #指定zipkinServer的路径 使用消息队列后则不需要
        base-url: http://localhost:9411
        sender:
            type: web
    sleuth:
        sampler:
          probability : 1 #用来指定采样请求的百分比（默认为 0.1，即 10%）

4.进入命令行窗口使用命令行启动zipkin.jar

java -jar zipkin.jar

通过消息中间件实现链路追踪

1.首先安装好rabbitmq，安装过程此处略过，下载地址见开头
2.在对应模块下的pom文件引入依赖：

        <!--通过消息中间件实现链路追踪-->
        <dependency>
            <groupId>org.springframework.cloud</groupId>
            <artifactId>spring-cloud-stream-binder-rabbit</artifactId>
        </dependency>

3.在属性文件中加上：

spring:
#  zipkin: #指定zipkinServer的路径 使用消息队列后则不需要
#    base-url: http://localhost:9411
#    sender:
#      type: web
  sleuth:
    sampler:
      probability: 1 #用来指定采样请求的百分比（默认为 0.1，即 10%）

4.进入命令行窗口使用命令行启动zipkin.jar

java -jar zipkin.jar --zipkin.collector.rabbitmq.addresses=127.0.0.1 --zipkin.collector.rabbitmq.username=hyl --zipkin.collector.rabbitmq.password=123456

zipkin.collector.rabbitmq.addresses指定host，zipkin.collector.rabbitmq.username是rabbitmq的账号 zipkin.collector.rabbitmq.password是rabbitmq的密码
5.验证，进入rabbitmq的界面：

出现zipkin的队列

出现zipkin的队列则表示成功

持久化到mysql8

1.安装mysql，安装过程此处略过
2.创建一个名为 zipkin_db 的数据库，并执行以下脚本：

CREATE TABLE IF NOT EXISTS zipkin_spans (
  `trace_id_high` BIGINT NOT NULL DEFAULT 0 COMMENT 'If non zero, this means the trace uses 128 bit traceIds instead of 64 bit',
  `trace_id` BIGINT NOT NULL,
  `id` BIGINT NOT NULL,
  `name` VARCHAR(255) NOT NULL,
  `parent_id` BIGINT,
  `debug` BIT(1),
  `start_ts` BIGINT COMMENT 'Span.timestamp(): epoch micros used for endTs query and to implement TTL',
  `duration` BIGINT COMMENT 'Span.duration(): micros used for minDuration and maxDuration query'
) ENGINE=InnoDB ROW_FORMAT=COMPRESSED CHARACTER SET=utf8 COLLATE utf8_general_ci;

ALTER TABLE zipkin_spans ADD UNIQUE KEY(`trace_id_high`, `trace_id`, `id`) COMMENT 'ignore insert on duplicate';
ALTER TABLE zipkin_spans ADD INDEX(`trace_id_high`, `trace_id`, `id`) COMMENT 'for joining with zipkin_annotations';
ALTER TABLE zipkin_spans ADD INDEX(`trace_id_high`, `trace_id`) COMMENT 'for getTracesByIds';
ALTER TABLE zipkin_spans ADD INDEX(`name`) COMMENT 'for getTraces and getSpanNames';
ALTER TABLE zipkin_spans ADD INDEX(`start_ts`) COMMENT 'for getTraces ordering and range';

CREATE TABLE IF NOT EXISTS zipkin_annotations (
  `trace_id_high` BIGINT NOT NULL DEFAULT 0 COMMENT 'If non zero, this means the trace uses 128 bit traceIds instead of 64 bit',
  `trace_id` BIGINT NOT NULL COMMENT 'coincides with zipkin_spans.trace_id',
  `span_id` BIGINT NOT NULL COMMENT 'coincides with zipkin_spans.id',
  `a_key` VARCHAR(255) NOT NULL COMMENT 'BinaryAnnotation.key or Annotation.value if type == -1',
  `a_value` BLOB COMMENT 'BinaryAnnotation.value(), which must be smaller than 64KB',
  `a_type` INT NOT NULL COMMENT 'BinaryAnnotation.type() or -1 if Annotation',
  `a_timestamp` BIGINT COMMENT 'Used to implement TTL; Annotation.timestamp or zipkin_spans.timestamp',
  `endpoint_ipv4` INT COMMENT 'Null when Binary/Annotation.endpoint is null',
  `endpoint_ipv6` BINARY(16) COMMENT 'Null when Binary/Annotation.endpoint is null, or no IPv6 address',
  `endpoint_port` SMALLINT COMMENT 'Null when Binary/Annotation.endpoint is null',
  `endpoint_service_name` VARCHAR(255) COMMENT 'Null when Binary/Annotation.endpoint is null'
) ENGINE=InnoDB ROW_FORMAT=COMPRESSED CHARACTER SET=utf8 COLLATE utf8_general_ci;

ALTER TABLE zipkin_annotations ADD UNIQUE KEY(`trace_id_high`, `trace_id`, `span_id`, `a_key`, `a_timestamp`) COMMENT 'Ignore insert on duplicate';
ALTER TABLE zipkin_annotations ADD INDEX(`trace_id_high`, `trace_id`, `span_id`) COMMENT 'for joining with zipkin_spans';
ALTER TABLE zipkin_annotations ADD INDEX(`trace_id_high`, `trace_id`) COMMENT 'for getTraces/ByIds';
ALTER TABLE zipkin_annotations ADD INDEX(`endpoint_service_name`) COMMENT 'for getTraces and getServiceNames';
ALTER TABLE zipkin_annotations ADD INDEX(`a_type`) COMMENT 'for getTraces';
ALTER TABLE zipkin_annotations ADD INDEX(`a_key`) COMMENT 'for getTraces';

CREATE TABLE IF NOT EXISTS zipkin_dependencies (
  `day` DATE NOT NULL,
  `parent` VARCHAR(255) NOT NULL,
  `child` VARCHAR(255) NOT NULL,
  `call_count` BIGINT
) ENGINE=InnoDB ROW_FORMAT=COMPRESSED CHARACTER SET=utf8 COLLATE utf8_general_ci;

ALTER TABLE zipkin_dependencies ADD UNIQUE KEY(`day`, `parent`, `child`);

（可参考官方sql：https://github.com/openzipkin/zipkin/blob/master/zipkin-storage/mysql-v1/src/main/resources/mysql.sql）
3.进入命令行窗口使用命令行启动zipkin.jar

java -jar zipkin.jar --MYSQL_HOST=127.0.0.1 --MYSQL_TCP_PORT=3306 --MYSQL_USER=root --MYSQL_PASS=123456 --MYSQL_DB=zipkin_db --STORAGE_TYPE=mysql

注：通过消息中间件实现链路追踪和持久化到mysql8两者是相互独立的步骤不一定要联合使用。

如果想要同时使用rabbitmq和mysql8，将两者的参数合二为一即可：

java -jar zipkin.jar --zipkin.collector.rabbitmq.addresses=127.0.0.1 --zipkin.collector.rabbitmq.username=hyl --zipkin.collector.rabbitmq.password=123456 --MYSQL_HOST=127.0.0.1 --MYSQL_TCP_PORT=3306 --MYSQL_USER=root --MYSQL_PASS=123456 --MYSQL_DB=zipkin_db --STORAGE_TYPE=mysql