分布式应用监控与链路追踪：SkyWalking

「爱情、让人受尽委屈。」 2022-11-04 05:27 202阅读 0赞

点击上方“程序猿技术大咖”，关注并选择“设为星标”

回复“加群”获取入群讨论资格！

SkyWalking 是一个应用性能监控系统，特别为微服务、云原生和基于容器（Docker, Kubernetes, Mesos）体系结构而设计。除了应用指标监控以外，它还能对分布式调用链路进行追踪。类似功能的组件还有：Zipkin、Pinpoint、CAT等。

上几张图，看看效果，然后再一步一步搭建并使用。

![8bcb4bca6eb864bfc016c03434609d41.png][]

![f2b9abeeed3734465cbbd1f64e5e46c7.png][]

![8f98e6601c4bc4a6e1de485b98e88c23.png][]

![15dae059c938a5cbb6ed9551ef7939ae.png][]

1.  概念与架构

SkyWalking是一个开源监控平台，用于从服务和云原生基础设施收集、分析、聚合和可视化数据。

SkyWalking提供了一种简单的方法来维护分布式系统的清晰视图，甚至可以跨云查看。它是一种现代APM，专门为云原生、基于容器的分布式系统设计。

SkyWalking从三个维度对应用进行监视：service（服务）, service instance（实例）, endpoint（端点）

服务和实例就不多说了，端点是服务中的某个路径或者说URI

> SkyWalking allows users to understand the topology relationship between Services and Endpoints, to view the metrics of every Service/Service Instance/Endpoint and to set alarm rules.

SkyWalking允许用户了解服务和端点之间的拓扑关系，查看每个服务/服务实例/端点的度量，并设置警报规则。

## 1.1.  架构 ##

![0d3ecad2f9bb8c753fca6c194ee09bb6.png][]

SkyWalking逻辑上分为四个部分：Probes（探针）, Platform backend（平台后端）, Storage（存储）, UI。

这个结构就很清晰了，探针就是Agent负责采集数据并上报给服务端，服务端对数据进行处理和存储，UI负责展示：

![b4bfc1c8b9218bbb3369cca0f5eb0b05.png][]

## 2.  下载与安装 ##

SkyWalking有两中版本，ES版本和非ES版。如果我们决定采用ElasticSearch作为存储，那么就下载es版本。

https://skywalking.apache.org/downloads/

https://archive.apache.org/dist/skywalking/

![db599458e5c70874c2aad0b82ca33c6c.png][]

![11720e2c018f27441d4170e7941cf862.png][]

agent目录将来要拷贝到各服务所在机器上用作探针

bin目录是服务启动脚本

config目录是配置文件

oap-libs目录是oap服务运行所需的jar包

webapp目录是web服务运行所需的jar包

接下来，要选择存储了，支持的存储有：

*  H2
 *  ElasticSearch 6, 7
 *  MySQL
 *  TiDB
 *  InfluxDB

作为监控系统，首先排除H2和MySQL，这里推荐InfluxDB，它本身就是时序数据库，非常适合这种场景

但是InfluxDB我不是很熟悉，所以这里先用ElasticSearch7

https://github.com/apache/skywalking/blob/master/docs/en/setup/backend/backend-storage.md

## 2.1.  安装ElasticSearch ##

https://www.elastic.co/guide/en/elasticsearch/reference/7.10/targz.html

# 启动./bin/elasticsearch -d -p pid# 停止pkill -F pid

![67465a9cfa72b5ca10b0f24066c19b68.png][]

ElasticSearch7.x需要Java 11以上的版本，但是如果你设置了环境变量JAVA\_HOME的话，它会用你自己的Java版本

通常，启动过程中会报以下三个错误：

[1]: max file descriptors [4096] for elasticsearch process is too low, increase to at least [65535][2]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144][3]: the default discovery settings are unsuitable for production use; at least one of [discovery.seed_hosts, discovery.seed_providers, cluster.initial_master_nodes] must be configured

解决方法：

在 /etc/security/limits.conf 文件中追加以下内容：

* soft nofile 65536* hard nofile 65536* soft nproc  4096* hard nproc  4096

可通过以下四个命令查看修改结果：

ulimit -Hnulimit -Snulimit -Huulimit -Su

修改 /etc/sysctl.conf 文件，追加以下内容：

vm.max_map_count=262144

修改es配置文件 elasticsearch.yml 取消注释，保留一个节点

cluster.initial_master_nodes: ["node-1"]

为了能够ip:port方式访问，还需修改网络配置

network.host: 0.0.0.0

修改完是这样的：

![552484980124857764b098f6bccac348.png][]

![0fc5055bbd8f01d85495e7c9d33ac9f8.png][]

至此，ElasticSearch算是启动成功了

一个节点还不够，这里用三个节点搭建一个集群

192.168.100.14  config/elasticsearch.yml

cluster.name: my-monitornode.name: node-1network.host: 192.168.100.14http.port: 9200discovery.seed_hosts: ["192.168.100.14:9300", "192.168.100.15:9300", "192.168.100.19:9300"]cluster.initial_master_nodes: ["node-1"]

192.168.100.15  config/elasticsearch.yml

cluster.name: my-monitornode.name: node-2network.host: 192.168.100.15http.port: 9200discovery.seed_hosts: ["192.168.100.14:9300", "192.168.100.15:9300", "192.168.100.19:9300"]cluster.initial_master_nodes: ["node-1"]

192.168.100.19  config/elasticsearch.yml

cluster.name: my-monitornode.name: node-3network.host: 192.168.100.19http.port: 9200discovery.seed_hosts: ["192.168.100.14:9300", "192.168.100.15:9300", "192.168.100.19:9300"]cluster.initial_master_nodes: ["node-1"]

同时，建议修改三个节点config/jvm.options

-Xms2g-Xmx2g

依次启动三个节点

pkill -F pid./bin/elasticsearch -d -p pid

![1a4783906c5ab88375437a742a2535de.png][]

![1ddb54f167a5f1977802a1648bcfbef4.png][]

![015beb4e0bad5190dd8c150f01f76963.png][]

接下来，修改skywalking下config/application.yml 中配置es地址即可

storage:  selector: ${SW_STORAGE:elasticsearch7}  elasticsearch7:    nameSpace: ${SW_NAMESPACE:""}    clusterNodes: ${SW_STORAGE_ES_CLUSTER_NODES:192.168.100.14:9200,192.168.100.15:9200,192.168.100.19:9200}

## 2.2.  安装Agent ##

https://github.com/apache/skywalking/blob/v8.2.0/docs/en/setup/service-agent/java-agent/README.md

将agent目录拷贝至各服务所在的机器上

scp -r ./agent chengjs@192.168.100.12:~/

这里，我将它拷贝至各个服务目录下

![a5275b50f5c8e96b5863d0e2b940577b.png][]

plugins是探针用到各种插件，SkyWalking插件都是即插即用的，可以把optional-plugins中的插件放到plugins中

修改 agent/config/agent.config 配置文件，也可以通过命令行参数指定

主要是配置服务名称和后端服务地址

agent.service_name=${SW_AGENT_NAME:user-center}collector.backend_service=${SW_AGENT_COLLECTOR_BACKEND_SERVICES:192.168.100.17:11800}

当然，也可以通过环境变量或系统属性的方式来设置，例如：

export SW_AGENT_COLLECTOR_BACKEND_SERVICES=127.0.0.1:11800

最后，在服务启动的时候用命令行参数 -javaagent 来指定探针

java -javaagent:/path/to/skywalking-agent/skywalking-agent.jar -jar yourApp.jar

例如：

java -javaagent:./agent/skywalking-agent.jar -Dspring.profiles.active=dev -Xms512m -Xmx1024m -jar demo-0.0.1-SNAPSHOT.jar

# 3.  启动服务 #

修改 webapp/webapp.yml 文件，更改端口号及后端服务地址

server:  port: 9000collector:  path: /graphql  ribbon:    ReadTimeout: 10000    # Point to all backend's restHost:restPort, split by ,    listOfServers: 127.0.0.1:12800

启动服务

bin/startup.sh

或者分别依次启动

bin/oapService.shbin/webappService.sh

查看logs目录下的日志文件，看是否启动成功

浏览器访问 http://127.0.0.1:9000

# 4. 告警 #

![dd8059d3513a4ebafb2097258da7825b.png][]

编辑 alarm-settings.yml 设置告警规则和通知

https://github.com/apache/skywalking/blob/v8.2.0/docs/en/setup/backend/backend-alarm.md

重点说下告警通知

![8bbc032a9d6f2ad8681a2b5864206072.png][]

![8f2351fc8c2a437893477a02370cfc3b.png][]

为了使用钉钉机器人通知，接下来，新建一个项目

<?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 https://maven.apache.org/xsd/maven-4.0.0.xsd">    <modelVersion>4.0.0</modelVersion>    <parent>        <groupId>org.springframework.boot</groupId>        <artifactId>spring-boot-starter-parent</artifactId>        <version>2.4.0</version>        <relativePath/>     </parent>    <groupId>com.wt.monitor</groupId>    <artifactId>skywalking-alarm</artifactId>    <version>1.0.0-SNAPSHOT</version>    <name>skywalking-alarm</name>    <properties>        <java.version>1.8</java.version>    </properties>    <dependencies>        <dependency>            <groupId>org.springframework.boot</groupId>            <artifactId>spring-boot-starter-web</artifactId>        </dependency>        <dependency>            <groupId>com.aliyun</groupId>            <artifactId>alibaba-dingtalk-service-sdk</artifactId>            <version>1.0.1</version>        </dependency>        <dependency>            <groupId>commons-codec</groupId>            <artifactId>commons-codec</artifactId>            <version>1.15</version>        </dependency>        <dependency>            <groupId>com.alibaba</groupId>            <artifactId>fastjson</artifactId>            <version>1.2.75</version>        </dependency>        <dependency>            <groupId>org.projectlombok</groupId>            <artifactId>lombok</artifactId>            <optional>true</optional>        </dependency>    </dependencies>    <build>        <plugins>            <plugin>                <groupId>org.springframework.boot</groupId>                <artifactId>spring-boot-maven-plugin</artifactId>            </plugin>        </plugins>    </build></project>

可选依赖（不建议引入）

<dependency    <groupId>org.apache.skywalking</groupId>    <artifactId>server-core</artifactId>    <version>8.2.0</version></dependency>

定义告警消息实体

package com.wt.monitor.skywalking.alarm.domain;import lombok.Data;import java.io.Serializable;/** * @author ChengJianSheng * @date 2020/12/1 */@Datapublic class AlarmMessageDTO implements Serializable {    private int scopeId;    private String scope;    /**     * Target scope entity name     */    private String name;    private String id0;    private String id1;    private String ruleName;    /**     * Alarm text message     */    private String alarmMessage;    /**     * Alarm time measured in milliseconds     */    private long startTime;}

发送钉钉机器人消息

package com.wt.monitor.skywalking.alarm.service;import com.dingtalk.api.DefaultDingTalkClient;import com.dingtalk.api.DingTalkClient;import com.dingtalk.api.request.OapiRobotSendRequest;import com.taobao.api.ApiException;import lombok.extern.slf4j.Slf4j;import org.apache.commons.codec.binary.Base64;import org.springframework.beans.factory.annotation.Value;import org.springframework.stereotype.Service;import javax.crypto.Mac;import javax.crypto.spec.SecretKeySpec;import java.io.UnsupportedEncodingException;import java.net.URLEncoder;import java.security.InvalidKeyException;import java.security.NoSuchAlgorithmException;/** * https://ding-doc.dingtalk.com/doc#/serverapi2/qf2nxq * @author ChengJianSheng * @data 2020/12/1 */@Slf4j@Servicepublic class DingTalkAlarmService {    @Value("${dingtalk.webhook}")    private String webhook;    @Value("${dingtalk.secret}")    private String secret;    public void sendMessage(String content) {        try {            Long timestamp = System.currentTimeMillis();            String stringToSign = timestamp + "\n" + secret;            Mac mac = Mac.getInstance("HmacSHA256");            mac.init(new SecretKeySpec(secret.getBytes("UTF-8"), "HmacSHA256"));            byte[] signData = mac.doFinal(stringToSign.getBytes("UTF-8"));            String sign = URLEncoder.encode(new String(Base64.encodeBase64(signData)),"UTF-8");            String serverUrl = webhook + "&timestamp=" + timestamp + "&sign=" + sign;            DingTalkClient client = new DefaultDingTalkClient(serverUrl);            OapiRobotSendRequest request = new OapiRobotSendRequest();            request.setMsgtype("text");            OapiRobotSendRequest.Text text = new OapiRobotSendRequest.Text();            text.setContent(content);            request.setText(text);            client.execute(request);        } catch (ApiException e) {            e.printStackTrace();            log.error(e.getMessage(), e);        } catch (NoSuchAlgorithmException e) {            e.printStackTrace();            log.error(e.getMessage(), e);        } catch (UnsupportedEncodingException e) {            e.printStackTrace();            log.error(e.getMessage(), e);        } catch (InvalidKeyException e) {            e.printStackTrace();            log.error(e.getMessage(), e);        }    }}

AlarmController.java

package com.wt.monitor.skywalking.alarm.controller;import com.alibaba.fastjson.JSON;import com.wt.monitor.skywalking.alarm.domain.AlarmMessageDTO;import com.wt.monitor.skywalking.alarm.service.DingTalkAlarmService;import lombok.extern.slf4j.Slf4j;import org.springframework.beans.factory.annotation.Autowired;import org.springframework.web.bind.annotation.PostMapping;import org.springframework.web.bind.annotation.RequestBody;import org.springframework.web.bind.annotation.RequestMapping;import org.springframework.web.bind.annotation.RestController;import java.text.MessageFormat;import java.util.List;/** * @author ChengJianSheng * @date 2020/12/1 */@Slf4j@RestController@RequestMapping("/skywalking")public class AlarmController {    @Autowired    private DingTalkAlarmService dingTalkAlarmService;    @PostMapping("/alarm")    public void alarm(@RequestBody List<AlarmMessageDTO> alarmMessageDTOList) {       log.info("收到告警信息: {}", JSON.toJSONString(alarmMessageDTOList));       if (null != alarmMessageDTOList) {           alarmMessageDTOList.forEach(e->dingTalkAlarmService.sendMessage(MessageFormat.format("-----来自SkyWalking的告警-----\n【名称】: {0}\n【消息】: {1}\n", e.getName(), e.getAlarmMessage())));       }    }}

![95bace3c1cab3b7a897e890d4f5e93fe.png][]

# 5.  文档 #

*  https://skywalking.apache.org/
 *  https://skywalking.apache.org/zh/ 
 *  https://github.com/apache/skywalking/tree/v8.2.0/docs
 *  https://archive.apache.org/dist/
 *  https://www.elastic.co/guide/en/elasticsearch/reference/master/index.html
 *  https://www.elastic.co/guide/en/elasticsearch/reference/7.10/modules-discovery-bootstrap-cluster.html
 *  https://www.elastic.co/guide/en/elasticsearch/reference/7.10/modules-discovery-hosts-providers.html

--------------------

感谢您的阅读，也欢迎您发表关于这篇文章的任何建议，关注我，技术不迷茫！

![a0451434a0c3d89eb120b376f0924a62.gif][]

*  [JDK1.8新特性(四)：函数式接口][JDK1.8]
 *  [微服务架构下该如何技术选型呢？][Link 1]
 *  [2021 年，中台的“瓜”你还吃吗？][2021]  
    
 *  [MySQL性能优化(七)：MySQL执行计划，真的很重要，来一起学习吧][MySQL_MySQL]
 *  [从 CI/CD 持续集成部署到 DevOps 研发运维一体化][CI_CD _ DevOps]

![573a259f9cefded6d71817299c707517.gif][]

喜欢就点个"在看"呗，留言、转发朋友圈

[8bcb4bca6eb864bfc016c03434609d41.png]: /images/20221023/47358bd37456473f9785c68df69f8613.png
[f2b9abeeed3734465cbbd1f64e5e46c7.png]: /images/20221023/23b17becb48144b4a72ab2fcdeb33123.png
[8f98e6601c4bc4a6e1de485b98e88c23.png]: /images/20221023/8cc1f134c4fd416c829db8ef8cfcd474.png
[15dae059c938a5cbb6ed9551ef7939ae.png]: /images/20221023/f7c2590fda7b4996bba8165ee3c849a1.png
[0d3ecad2f9bb8c753fca6c194ee09bb6.png]: /images/20221023/16cfd1e9d66847168b25e37afa4b627d.png
[b4bfc1c8b9218bbb3369cca0f5eb0b05.png]: /images/20221023/e194fe9f87384dfd87742ce8f17bd891.png
[db599458e5c70874c2aad0b82ca33c6c.png]: /images/20221023/d7aefe378fec447aa8e9c3ea6d098b25.png
[11720e2c018f27441d4170e7941cf862.png]: /images/20221023/44c8cc816c4c4f2abbefac2fe5b5dc7e.png
[67465a9cfa72b5ca10b0f24066c19b68.png]: /images/20221023/a631f96413674b3799ea3f61bbd38c4e.png
[552484980124857764b098f6bccac348.png]: /images/20221023/10933f6e84e245d793c9f248d3ce2bbf.png
[0fc5055bbd8f01d85495e7c9d33ac9f8.png]: /images/20221023/5d7f0f2ecb204754a62d9b2dd46568d2.png
[1a4783906c5ab88375437a742a2535de.png]: /images/20221023/818c33e7d4c948ee818b3aca9960a550.png
[1ddb54f167a5f1977802a1648bcfbef4.png]: /images/20221023/94c5be4f8f3c482782733ebacfe20557.png
[015beb4e0bad5190dd8c150f01f76963.png]: /images/20221023/469341212e7941fc884a96416656edd4.png
[a5275b50f5c8e96b5863d0e2b940577b.png]: /images/20221023/71a911cf355c4f989da7ac796729f28c.png
[dd8059d3513a4ebafb2097258da7825b.png]: /images/20221023/4ff781a36cb1424b9446b8f4e7cbf784.png
[8bbc032a9d6f2ad8681a2b5864206072.png]: /images/20221023/c3a16c4ae2534ab79b7a19900e0a86ea.png
[8f2351fc8c2a437893477a02370cfc3b.png]: /images/20221023/b62cbf0dfa4644eeb0d481e427337803.png
[95bace3c1cab3b7a897e890d4f5e93fe.png]: /images/20221023/6e544fbe12844e588ca9f11e364d8849.png
[a0451434a0c3d89eb120b376f0924a62.gif]: /images/20221023/457dd71ae34e48449f9178b2bf548810.png
[JDK1.8]: http://mp.weixin.qq.com/s?__biz=MzA5MzUwOTY4NQ%3D%3D&chksm=905d88fba72a01ed52ba7e5403ba39bbb4386bd23a7906db45d831311c7216ecbd5a7efeff8d&idx=1&mid=2247485857&scene=21&sn=be80b248bcc6c080755953219a1f2b78#wechat_redirect
[Link 1]: http://mp.weixin.qq.com/s?__biz=MzA5MzUwOTY4NQ%3D%3D&chksm=905d95a1a72a1cb7e807a2bb4868b24c676a6ae577027e50173957e8ac41c14e8561301650cb&idx=1&mid=2247488763&scene=21&sn=53eef5681236ce04ac52e2f6ee028485#wechat_redirect
[2021]: http://mp.weixin.qq.com/s?__biz=MzA5MzUwOTY4NQ%3D%3D&chksm=905d95afa72a1cb92db3eea077f886d6ea9c9a516093b4cdab52e566d56c0253c82f5a0b6090&idx=1&mid=2247488757&scene=21&sn=03bd6e5e245cc2637bbfc3c1656fcea6#wechat_redirect
[MySQL_MySQL]: http://mp.weixin.qq.com/s?__biz=MzA5MzUwOTY4NQ%3D%3D&chksm=905d8838a72a012e057b5671b8a429c1dacbfcd15bc480ee020c59a1f636e906fcd5edca659d&idx=1&mid=2247485794&scene=21&sn=cef01641815309e84aa2fbbd692bf5b4#wechat_redirect
[CI_CD _ DevOps]: http://mp.weixin.qq.com/s?__biz=MzA5MzUwOTY4NQ%3D%3D&chksm=905d958aa72a1c9c2566746c07ba923a2a469891a29ff711e1c5d71a505a633046d51b12f886&idx=1&mid=2247488720&scene=21&sn=0d1ad0f479331e49d30c7a079454b519#wechat_redirect
[573a259f9cefded6d71817299c707517.gif]: /images/20221023/e66214865b614f15b65244a9f445d09f.png