使用docker-compose 一键部署你的分布式调用链跟踪框架skywalking

小馬文玩 發表於 2018-9-18 08:18:00

使用docker-compose 一键部署你的分布式调用链跟踪框架skywalking

一旦你的程序docker化之后，你会遇到各种问题，比如原来采用的本地记日志的方式就不再方便了，虽然你可以挂载到宿主机，但你使用 --scale 的话，会导致
记录日志异常，所以最好的方式还是要做日志中心化，另一个问题，原来一个请求在一个进程中的痉挛失败，你可以在日志中巡查出调用堆栈，但是docker化之后，
原来一个进程的东西会拆成几个微服务，这时候最好就要有一个分布式的调用链跟踪，类似于wcf中的svctraceview工具。
 
一：搭建skywalking
　　gihub地址是：https://github.com/apache/incubator-skywalking 从文档中大概看的出来，大体分三个部分：存储，收集器，探针，存储这里就选用推荐的
elasticsearch。收集器准备和es部署在一起，探针就有各自语言的实现了，总之这里就有三个docker container： es，kibana，skywalking，如果不用容器编排工具
的话就比较麻烦。
      下面是本次搭建的一个目录结构：
<img src="https://img2018.cnblogs.com/blog/214741/201809/214741-20180918072342742-1443167483.png" alt=""> 
1.  elasticsearch.yml
    es的配置文件，不过这里有一个坑，就是一定要将 network.publish_host： 0.0.0.0 ，否则skywalking会连不上 9300端口。
<div class="cnblogs_code">
<pre>network.publish_host: 0.0.0.0
transport.tcp.port: 9300
network.host: 0.0.0.0</pre>
</div>
 
2. elasticsearch.dockerfile
    在up的时候，将这个es文件copy到容器的config文件夹下。
<div class="cnblogs_code">
<pre>FROM elasticsearch:5.6.4

EXPOSE 9200 9300

COPY elasticsearch.yml /usr/share/elasticsearch/config/</pre>
</div>
 
3. application.yml
   skywalking的配置文件，这里也有一个坑：连接es的地址中，配置的 clustername一定要修改成和es的clustername保持一致，否则会连不上，这里容器之间用link
进行互联，所以es的ip改成elasticsearch就可以了，其他的ip改成0.0.0.0 。 
 
<div class="cnblogs_code"><img id="code_img_closed_3e44bfb8-180f-4f54-91c8-e1425b4d0bd2" class="code_img_closed" src="https://images.cnblogs.com/OutliningIndicators/ContractedBlock.gif" alt=""><img id="code_img_opened_3e44bfb8-180f-4f54-91c8-e1425b4d0bd2" class="code_img_opened" style="display: none" src="https://images.cnblogs.com/OutliningIndicators/ExpandedBlockStart.gif" alt="">
<div id="cnblogs_code_open_3e44bfb8-180f-4f54-91c8-e1425b4d0bd2" class="cnblogs_code_hide">
<pre># Licensed to the Apache Software Foundation (ASF) under one
# or more contributor license agreements.See the NOTICE file
# distributed with this work for additional information
# regarding copyright ownership.The ASF licenses this file
# to you under the Apache License, Version 2.0 (the
# "License"); you may not use this file except in compliance
# with the License.You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

#cluster:
#zookeeper:
# hostPort: localhost:2181
# sessionTimeout: 100000
naming:
jetty:
host: 0.0.0.0
port: 10800
contextPath: /
cache:
#guava:
caffeine:
remote:
gRPC:
host: 0.0.0.0
port: 11800
agent_gRPC:
gRPC:
host: 0.0.0.0
port: 11800
#Set these two setting to open ssl
#sslCertChainFile: $path
#sslPrivateKeyFile: $path

#Set your own token to active auth
#authentication: xxxxxx
agent_jetty:
jetty:
host: 0.0.0.0
port: 12800
contextPath: /
analysis_register:
default:
analysis_jvm:
default:
analysis_segment_parser:
default:
bufferFilePath: ../buffer/
bufferOffsetMaxFileSize: 10M
bufferSegmentMaxFileSize: 500M
bufferFileCleanWhenRestart: true
ui:
jetty:
host: 0.0.0.0
port: 12800
contextPath: /
storage:
elasticsearch:
clusterName: elasticsearch
clusterTransportSniffer: true
clusterNodes: elasticsearch:9300
indexShardsNumber: 2
indexReplicasNumber: 0
highPerformanceMode: true
ttl: 7
#storage:
#h2:
# url: jdbc:h2:~/memorydb
# userName: sa
configuration:
default:
# namespace: xxxxx
# alarm threshold
applicationApdexThreshold: 2000
serviceErrorRateThreshold: 10.00
serviceAverageResponseTimeThreshold: 2000
instanceErrorRateThreshold: 10.00
instanceAverageResponseTimeThreshold: 2000
applicationErrorRateThreshold: 10.00
applicationAverageResponseTimeThreshold: 2000
# thermodynamic
thermodynamicResponseTimeStep: 50
thermodynamicCountOfResponseTimeSteps: 40</pre>
</div>
View Code</div>
 
4.  skywalking.dockerfile
      接下来就是 skywalking的下载安装，使用dockerfile流程化。
<div class="cnblogs_code">
<pre>FROM centos:7

LABEL username="hxc@qq.com"

WORKDIR /app

RUN yum install -y wget && \
yum install -y java-1.8.0-openjdk

ADD http://mirrors.hust.edu.cn/apache/incubator/skywalking/5.0.0-RC2/apache-skywalking-apm-incubating-5.0.0-RC2.tar.gz /app

RUN tar -xf apache-skywalking-apm-incubating-5.0.0-RC2.tar.gz && \
mv apache-skywalking-apm-incubating skywalking

RUN ls /app

#copy文件
COPY application.yml /app/skywalking/config/application.yml

WORKDIR /app/skywalking/bin

USER root

RUNecho "tail -f /dev/null" >> /app/skywalking/bin/startup.sh

CMD ["/bin/sh","-c","/app/skywalking/bin/startup.sh" ]</pre>
</div>
 
5. docker-compose.yml
    最后就是将这三个容器进行编排，要注意的是，因为收集器会将数据放入到es中，所有一定要将es的data挂载到宿主机的大硬盘下，否则你的空间会不足的。
<div class="cnblogs_code">
<pre>version: '3.1'

services:

#elastic 镜像
elasticsearch:
build:
 context: .
 dockerfile: elasticsearch.dockerfile
# ports:
# - "9200:9200"
# - "9300:9300"
volumes:
 - "/data/es2:/usr/share/elasticsearch/data"

#kibana 可视化查询，暴露 5601
kibana:
image: kibana
links:
 - elasticsearch
ports:
 - 5601:5601
depends_on:
 - "elasticsearch"

#skywalking
skywalking:
build:
 context: .
 dockerfile: skywalking.dockerfile
ports:
 - "10800:10800"
 - "11800:11800"
 - "12800:12800"
 - "8080:8080"
links:
 - elasticsearch
depends_on:
 - "elasticsearch"</pre>
</div>
 
二：一键部署
      要部署在docker中，你还得需要安装docker-ce 和 docker-compose，大家可以参照官方安装一下。
 
1. Docker-ce 的安装
<div class="cnblogs_code">
<pre>sudo yum remove docker \
docker-client \
docker-client-latest \
docker-common \
docker-latest \
docker-latest-logrotate \
docker-logrotate \
docker-selinux \
docker-engine-selinux \
docker-engine

sudo yum install -y yum-utils \
device-mapper-persistent-data \
lvm2

sudo yum-config-manager \
--add-repo \
https://download.docker.com/linux/centos/docker-ce.repo

sudo yum install docker-ce</pre>
</div>
 
然后启动一下docker 服务，可以看到版本是18.06.1
<div class="cnblogs_code">
<pre># service docker start
Redirecting to /bin/systemctl startdocker.service
# docker -v
Docker version 18.06.1-ce, build e68fc7a</pre>
</div>
 
2. docker-compose的安装
<div class="cnblogs_code">
<pre>sudo curl -L "https://github.com/docker/compose/releases/download/1.22.0/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose

sudo chmod +x /usr/local/bin/docker-compose</pre>
</div>
 
3.  最后在centos上执行 docker-compopse up --build 就可以了，如果不想terminal上运行，可以加 -d 使用后台执行。
 
<div class="cnblogs_code"><img id="code_img_closed_d1ec156f-7b95-4891-808c-581a0b72f6fa" class="code_img_closed" src="https://images.cnblogs.com/OutliningIndicators/ContractedBlock.gif" alt=""><img id="code_img_opened_d1ec156f-7b95-4891-808c-581a0b72f6fa" class="code_img_opened" style="display: none" src="https://images.cnblogs.com/OutliningIndicators/ExpandedBlockStart.gif" alt="">
<div id="cnblogs_code_open_d1ec156f-7b95-4891-808c-581a0b72f6fa" class="cnblogs_code_hide">
<pre># docker-compose up --build
Creating network "docker_default" with the default driver
Building elasticsearch
Step 1/3 : FROM elasticsearch:5.6.4
---> 7a047c21aa48
Step 2/3 : EXPOSE 9200 9300
---> Using cache
---> 8d66bb57b09d
Step 3/3 : COPY elasticsearch.yml /usr/share/elasticsearch/config/
---> Using cache
---> 02b516c03b95
Successfully built 02b516c03b95
Successfully tagged docker_elasticsearch:latest
Building skywalking
Step 1/12 : FROM centos:7
---> 5182e96772bf
Step 2/12 : LABEL username="hxc@qq.com"
---> Using cache
---> b95b96a92042
Step 3/12 : WORKDIR /app
---> Using cache
---> afdf4efe3426
Step 4/12 : RUN yum install -y wget && yum install -y java-1.8.0-openjdk
---> Using cache
---> 46be0ca0f7b5
Step 5/12 : ADD http://mirrors.hust.edu.cn/apache/incubator/skywalking/5.0.0-RC2/apache-skywalking-apm-incubating-5.0.0-RC2.tar.gz /app

---> Using cache
---> d5c30bcfd5ea
Step 6/12 : RUN tar -xf apache-skywalking-apm-incubating-5.0.0-RC2.tar.gz && mv apache-skywalking-apm-incubating skywalking
---> Using cache
---> 1438d08d18fa
Step 7/12 : RUN ls /app
---> Using cache
---> b594124672ea
Step 8/12 : COPY application.yml /app/skywalking/config/application.yml
---> Using cache
---> 10eaf0805a65
Step 9/12 : WORKDIR /app/skywalking/bin
---> Using cache
---> bc0f02291536
Step 10/12 : USER root
---> Using cache
---> 4498afca5fe6
Step 11/12 : RUNecho "tail -f /dev/null" >> /app/skywalking/bin/startup.sh
---> Using cache
---> 1c4be7c6b32a
Step 12/12 : CMD ["/bin/sh","-c","/app/skywalking/bin/startup.sh" ]
---> Using cache
---> ecfc97e4c97d
Successfully built ecfc97e4c97d
Successfully tagged docker_skywalking:latest
Creating docker_elasticsearch_1 ... done
Creating docker_skywalking_1 ... done
Creating docker_kibana_1 ... done
Attaching to docker_elasticsearch_1, docker_kibana_1, docker_skywalking_1
elasticsearch_1| [2018-09-17T23:51:47,611] [] initializing ...
elasticsearch_1| [2018-09-17T23:51:47,729] using [1] data paths, mounts [], net usable_space , net total_space [22.1gb], spins? , types
elasticsearch_1| [2018-09-17T23:51:47,730] heap size [1.9gb], compressed ordinary object pointers [true]
elasticsearch_1| [2018-09-17T23:51:47,731] node name derived from node ID ; set to override
elasticsearch_1| [2018-09-17T23:51:47,732] version[5.6.4], pid[1], build, OS, JVM
elasticsearch_1| [2018-09-17T23:51:47,732] JVM arguments [-Xms2g, -Xmx2g, -XX:+UseConcMarkSweepGC, -XX:CMSInitiatingOccupancyFraction=75, -XX:+UseCMSInitiatingOccupancyOnly, -XX:+AlwaysPreTouch, -Xss1m, -Djava.awt.headless=true, -Dfile.encoding=UTF-8, -Djna.nosys=true, -Djdk.io.permissionsUseCanonicalPath=true, -Dio.netty.noUnsafe=true, -Dio.netty.noKeySetOptimization=true, -Dio.netty.recycler.maxCapacityPerThread=0, -Dlog4j.shutdownHookEnabled=false, -Dlog4j2.disable.jmx=true, -Dlog4j.skipJansi=true, -XX:+HeapDumpOnOutOfMemoryError, -Des.path.home=/usr/share/elasticsearch]
skywalking_1 | SkyWalking Collector started successfully!
elasticsearch_1| [2018-09-17T23:51:49,067] loaded module
elasticsearch_1| [2018-09-17T23:51:49,067] loaded module
elasticsearch_1| [2018-09-17T23:51:49,067] loaded module
elasticsearch_1| [2018-09-17T23:51:49,067] loaded module
elasticsearch_1| [2018-09-17T23:51:49,067] loaded module
elasticsearch_1| [2018-09-17T23:51:49,067] loaded module
elasticsearch_1| [2018-09-17T23:51:49,067] loaded module
elasticsearch_1| [2018-09-17T23:51:49,068] loaded module
elasticsearch_1| [2018-09-17T23:51:49,068] loaded module
elasticsearch_1| [2018-09-17T23:51:49,069] loaded module
elasticsearch_1| [2018-09-17T23:51:49,069] loaded module
elasticsearch_1| [2018-09-17T23:51:49,069] no plugins loaded
skywalking_1 | SkyWalking Web Application started successfully!
elasticsearch_1| [2018-09-17T23:51:51,950] using discovery type
kibana_1 | {"type":"log","@timestamp":"2018-09-17T23:51:53Z","tags":["status","plugin:kibana@5.6.11","info"],"pid":12,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
elasticsearch_1| [2018-09-17T23:51:53,456] initialized
elasticsearch_1| [2018-09-17T23:51:53,457] starting ...
kibana_1 | {"type":"log","@timestamp":"2018-09-17T23:51:53Z","tags":["status","plugin:elasticsearch@5.6.11","info"],"pid":12,"state":"yellow","message":"Status changed from uninitialized to yellow - Waiting for Elasticsearch","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1 | {"type":"log","@timestamp":"2018-09-17T23:51:53Z","tags":["status","plugin:console@5.6.11","info"],"pid":12,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1 | {"type":"log","@timestamp":"2018-09-17T23:51:53Z","tags":["error","elasticsearch","admin"],"pid":12,"message":"Request error, retrying\nHEAD http://elasticsearch:9200/ => connect ECONNREFUSED 172.21.0.2:9200"}
kibana_1 | {"type":"log","@timestamp":"2018-09-17T23:51:53Z","tags":["warning","elasticsearch","admin"],"pid":12,"message":"Unable to revive connection: http://elasticsearch:9200/"}
kibana_1 | {"type":"log","@timestamp":"2018-09-17T23:51:53Z","tags":["warning","elasticsearch","admin"],"pid":12,"message":"No living connections"}
kibana_1 | {"type":"log","@timestamp":"2018-09-17T23:51:53Z","tags":["status","plugin:metrics@5.6.11","info"],"pid":12,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1 | {"type":"log","@timestamp":"2018-09-17T23:51:53Z","tags":["status","plugin:elasticsearch@5.6.11","error"],"pid":12,"state":"red","message":"Status changed from yellow to red - Unable to connect to Elasticsearch at http://elasticsearch:9200.","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}
elasticsearch_1| [2018-09-17T23:51:53,829] publish_address {172.21.0.2:9300}, bound_addresses {0.0.0.0:9300}
elasticsearch_1| [2018-09-17T23:51:53,870] bound or publishing to a non-loopback or non-link-local address, enforcing bootstrap checks
kibana_1 | {"type":"log","@timestamp":"2018-09-17T23:51:53Z","tags":["status","plugin:timelion@5.6.11","info"],"pid":12,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1 | {"type":"log","@timestamp":"2018-09-17T23:51:53Z","tags":["listening","info"],"pid":12,"message":"Server running at http://0.0.0.0:5601"}
kibana_1 | {"type":"log","@timestamp":"2018-09-17T23:51:53Z","tags":["status","ui settings","error"],"pid":12,"state":"red","message":"Status changed from uninitialized to red - Elasticsearch plugin is red","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1 | {"type":"log","@timestamp":"2018-09-17T23:51:56Z","tags":["warning","elasticsearch","admin"],"pid":12,"message":"Unable to revive connection: http://elasticsearch:9200/"}
kibana_1 | {"type":"log","@timestamp":"2018-09-17T23:51:56Z","tags":["warning","elasticsearch","admin"],"pid":12,"message":"No living connections"}
elasticsearch_1| [2018-09-17T23:51:57,094] new_master {FC_bOh1}{FC_bOh1nS_uW6JKy_46iBg}{tNMEW5HYQm6O4aiqpU0uWA}{172.21.0.2}{172.21.0.2:9300}, reason: zen-disco-elected-as-master ([0] nodes joined)
elasticsearch_1| [2018-09-17T23:51:57,129] publish_address {172.21.0.2:9200}, bound_addresses {0.0.0.0:9200}
elasticsearch_1| [2018-09-17T23:51:57,129] started
elasticsearch_1| [2018-09-17T23:51:57,157] recovered [0] indices into cluster_state
elasticsearch_1| [2018-09-17T23:51:57,368] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:51:57,557] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:51:57,685] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:51:57,742] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:51:57,886] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:51:57,962] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:51:58,115] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:51:58,176] Cluster health status changed from to (reason: [1]] ...]).
elasticsearch_1| [2018-09-17T23:51:58,356] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:51:58,437] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:51:58,550] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:51:58,601] Cluster health status changed from to (reason: [1]] ...]).
elasticsearch_1| [2018-09-17T23:51:58,725] creating index, cause , templates [], shards [2]/[0], mappings
kibana_1 | {"type":"log","@timestamp":"2018-09-17T23:51:58Z","tags":["warning"],"pid":12,"kibanaVersion":"5.6.11","nodes":[{"version":"5.6.4","http":{"publish_address":"172.21.0.2:9200"},"ip":"172.21.0.2"}],"message":"You're running Kibana 5.6.11 with some different versions of Elasticsearch. Update Kibana or Elasticsearch to the same version to prevent compatibility issues: v5.6.4 @ 172.21.0.2:9200 (172.21.0.2)"}
elasticsearch_1| [2018-09-17T23:51:58,886] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:51:59,023] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:51:59,090] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:51:59,137] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:51:59,258] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:51:59,355] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:51:59,410] Cluster health status changed from to (reason: [1], [0]] ...]).
elasticsearch_1| [2018-09-17T23:51:59,484] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:51:59,562] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:51:59,633] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:51:59,709] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:51:59,761] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:51:59,839] Cluster health status changed from to (reason: [1]] ...]).
elasticsearch_1| [2018-09-17T23:51:59,980] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:00,073] Cluster health status changed from to (reason: [1], [0]] ...]).
elasticsearch_1| [2018-09-17T23:52:00,159] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:00,258] Cluster health status changed from to (reason: [1]] ...]).
elasticsearch_1| [2018-09-17T23:52:00,350] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:00,463] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:52:00,535] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:00,599] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:52:00,714] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:00,766] Cluster health status changed from to (reason: [1], [0]] ...]).
elasticsearch_1| [2018-09-17T23:52:00,801] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:00,865] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:52:00,917] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:00,985] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:52:01,034] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:01,116] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:52:01,207] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:01,289] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:52:01,388] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:01,491] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:52:01,527] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:01,613] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:52:01,723] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:01,761] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:52:01,844] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:01,914] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:52:01,986] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:02,067] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:52:02,096] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:02,174] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:52:02,221] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:02,281] Cluster health status changed from to (reason: [1]] ...]).
elasticsearch_1| [2018-09-17T23:52:02,337] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:02,421] Cluster health status changed from to (reason: [1]] ...]).
elasticsearch_1| [2018-09-17T23:52:02,558] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:02,590] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:52:02,637] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:02,694] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:52:02,732] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:02,787] Cluster health status changed from to (reason: [1]] ...]).
elasticsearch_1| [2018-09-17T23:52:02,849] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:02,916] Cluster health status changed from to (reason: [1]] ...]).
elasticsearch_1| [2018-09-17T23:52:03,030] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:03,062] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:52:03,096] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:03,123] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:52:03,154] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:03,180] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:52:03,199] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:03,221] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:52:03,240] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:03,268] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:52:03,286] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:03,333] Cluster health status changed from to (reason: [1]] ...]).
elasticsearch_1| [2018-09-17T23:52:03,376] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:03,422] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:52:03,440] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:03,466] Cluster health status changed from to (reason: [1]] ...]).
elasticsearch_1| [2018-09-17T23:52:03,487] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:03,510] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:52:03,527] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:03,553] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:52:03,572] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:03,590] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:52:03,613] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:03,633] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:52:03,683] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:03,731] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:52:03,767] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:03,796] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:52:03,809] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:03,829] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:52:03,847] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:03,867] Cluster health status changed from to (reason: [0]] ...]).
elasticsearch_1| [2018-09-17T23:52:03,908] creating index, cause , templates [], shards [2]/[0], mappings
kibana_1 | {"type":"log","@timestamp":"2018-09-17T23:52:03Z","tags":["status","plugin:elasticsearch@5.6.11","info"],"pid":12,"state":"yellow","message":"Status changed from red to yellow - No existing Kibana index found","prevState":"red","prevMsg":"Unable to connect to Elasticsearch at http://elasticsearch:9200."}
kibana_1 | {"type":"log","@timestamp":"2018-09-17T23:52:03Z","tags":["status","ui settings","info"],"pid":12,"state":"yellow","message":"Status changed from red to yellow - Elasticsearch plugin is yellow","prevState":"red","prevMsg":"Elasticsearch plugin is red"}
elasticsearch_1| [2018-09-17T23:52:03,953] [.kibana] creating index, cause , templates [], shards [1]/[1], mappings
elasticsearch_1| [2018-09-17T23:52:04,003] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:04,111] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:04,228] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:04,285] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:04,342] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:04,395] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:04,433] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:04,475] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:04,512] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:04,575] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:04,617] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:04,675] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:04,742] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:04,841] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:04,920] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:04,987] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:05,045] creating index, cause , templates [], shards [2]/[0], mappings
kibana_1 | {"type":"log","@timestamp":"2018-09-17T23:52:05Z","tags":["status","plugin:elasticsearch@5.6.11","info"],"pid":12,"state":"green","message":"Status changed from yellow to green - Kibana index ready","prevState":"yellow","prevMsg":"No existing Kibana index found"}
kibana_1 | {"type":"log","@timestamp":"2018-09-17T23:52:05Z","tags":["status","ui settings","info"],"pid":12,"state":"green","message":"Status changed from yellow to green - Ready","prevState":"yellow","prevMsg":"Elasticsearch plugin is yellow"}
elasticsearch_1| [2018-09-17T23:52:05,106] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:05,143] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:05,180] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:05,225] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:05,268] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:05,350] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:05,392] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:05,434] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:05,470] creating index, cause , templates [], shards [2]/[0], mappings
elasticsearch_1| [2018-09-17T23:52:05,544] creating index, cause , templates [], shards [2]/[0], mappings </pre>
</div>
View Code</div>
 
从上图中可以看到 es，kibana，skywalking都启动成功了，你也可以通过docker-compose ps 看一下是否都起来了，netstat 看一下宿主机开放了哪些端口。
<div class="cnblogs_code">
<pre># docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
9aa90401ca16 kibana "/docker-entrypoint.…" 2 minutes ago Up 2 minutes 0.0.0.0:5601->5601/tcp docker_kibana_1
c551248e32af docker_skywalking "/bin/sh -c /app/sky…" 2 minutes ago Up 2 minutes 0.0.0.0:8080->8080/tcp, 0.0.0.0:10800->10800/tcp, 0.0.0.0:11800->11800/tcp, 0.0.0.0:12800->12800/tcp docker_skywalking_1
765d38469ff1 docker_elasticsearch "/docker-entrypoint.…" 2 minutes ago Up 2 minutes 9200/tcp, 9300/tcp docker_elasticsearch_1
# netstat -tlnp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 192.168.122.1:53 0.0.0.0:* LISTEN 2013/dnsmasq
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1141/sshd
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 1139/cupsd
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 1622/master
tcp6 0 0 :::8080 :::* LISTEN 38262/docker-proxy
tcp6 0 0 :::10800 :::* LISTEN 38248/docker-proxy
tcp6 0 0 :::22 :::* LISTEN 1141/sshd
tcp6 0 0 ::1:631 :::* LISTEN 1139/cupsd
tcp6 0 0 :::11800 :::* LISTEN 38234/docker-proxy
tcp6 0 0 ::1:25 :::* LISTEN 1622/master
tcp6 0 0 :::12800 :::* LISTEN 38222/docker-proxy
tcp6 0 0 :::5601 :::* LISTEN 38274/docker-proxy
# </pre>
</div>
 
 然后就可以看一些8080端口的可视化UI，默认用户名密码admin，admin，一个比较耐看的UI就出来了。
<img src="https://img2018.cnblogs.com/blog/214741/201809/214741-20180918074134126-1704828704.png" alt="" width="1049" height="479">
 
三： net下的探针
　　从nuget上拉取一个SkyWalking.AspNetCore探针进行代码埋点，github地址：https://github.com/OpenSkywalking/skywalking-netcore
<img src="https://img2018.cnblogs.com/blog/214741/201809/214741-20180918074308225-422061726.png" alt="" width="889" height="412">
 
   在startup类中进行注入，在页面请求中进行一次cnblogs.com的请求操作，然后仔细观察一下调用链跟踪是一个什么样子？
<div class="cnblogs_code">
<pre>using System;
using System.Collections.Generic;
using System.Linq;
using System.Threading.Tasks;
using Microsoft.AspNetCore.Builder;
using Microsoft.AspNetCore.Hosting;
using Microsoft.AspNetCore.Http;
using Microsoft.Extensions.DependencyInjection;
using SkyWalking.Extensions;
using SkyWalking.AspNetCore;
using System.Net;

namespace WebApplication1
{
public class Startup
{
 // This method gets called by the runtime. Use this method to add services to the container.
 // For more information on how to configure your application, visit https://go.microsoft.com/fwlink/?LinkID=398940
 public void ConfigureServices(IServiceCollection services)
 {
 services.AddSkyWalking(option =>
 {
 // Application code is showed in sky-walking-ui
 option.ApplicationCode = "10001 测试站点";

 //Collector agent_gRPC/grpc service addresses.
 option.DirectServers = "192.168.23.183:11800";
 });
 }

 // This method gets called by the runtime. Use this method to configure the HTTP request pipeline.
 public void Configure(IApplicationBuilder app, IHostingEnvironment env)
 {
 if (env.IsDevelopment())
 {
 app.UseDeveloperExceptionPage();
 }

 app.Run(async (context) =>
 {
 WebClient client = new WebClient();

 var str = client.DownloadString("http://cnblogs.com");

 await context.Response.WriteAsync(str);
 });
 }
}
}</pre>
</div>
 
<img src="https://img2018.cnblogs.com/blog/214741/201809/214741-20180918080308653-925317684.png" alt="">
 
         可以看到这张图还是蛮漂亮的哈，也方便我们快速的跟踪代码，发现问题，找出问题，还有更多的功能期待你的挖掘啦。 好了，本篇就说到这里，希望对你有帮助。
 
Demo下载
  
来源：https://www.cnblogs.com/huangxincheng/p/9666930.html

頁: [1]

琼殿技术论坛's Archiver

使用docker-compose 一键部署你的分布式调用链跟踪框架skywalking