Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
killuaz丶x
SkyWalking
提交
024f8104
S
SkyWalking
项目概览
killuaz丶x
/
SkyWalking
与 Fork 源项目一致
Fork自
apache / SkyWalking
通知
1
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
S
SkyWalking
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
未验证
提交
024f8104
编写于
4月 10, 2021
作者:
W
Wing
提交者:
GitHub
4月 10, 2021
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Refine concepts and designs (#6724)
上级
5ba8f002
变更
2
隐藏空白更改
内联
并排
Showing
2 changed file
with
21 addition
and
21 deletion
+21
-21
docs/en/concepts-and-designs/service-mesh-probe.md
docs/en/concepts-and-designs/service-mesh-probe.md
+14
-14
docs/en/concepts-and-designs/ui-overview.md
docs/en/concepts-and-designs/ui-overview.md
+7
-7
未找到文件。
docs/en/concepts-and-designs/service-mesh-probe.md
浏览文件 @
024f8104
# Service Mesh Probe
# Service Mesh Probe
Service Mesh probes use the extendable mechanism provided in Service Mesh implementor, like Istio.
Service Mesh probes use the extendable mechanism provided in
the
Service Mesh implementor, like Istio.
## What is Service Mesh?
## What is Service Mesh?
The following explanation c
ame from Istio documents
.
The following explanation c
omes from Istio's documentation
.
> The term
service mesh is often used to describe the network
of microservices that make up such applications and the interactions between them.
> The term
"service mesh" is often used to describe the networks
of microservices that make up such applications and the interactions between them.
As a service mesh grows in size and complexity, it can become harder to understand and manage.
As a service mesh grows in size and complexity, it can become harder to understand and manage.
Its requirements can include discovery, load balancing, failure recovery, metrics, and monitoring, and often more complex operational requirements
Its requirements can include discovery, load balancing, failure recovery, metrics, and monitoring, and often more complex operational requirements
such as A/B testing, canary releases, rate limiting, access control, and end-to-end authentication.
such as A/B testing, canary releases, rate limiting, access control, and end-to-end authentication.
## Where does the probe collect data from?
## Where does the probe collect data from?
Istio is a
very
typical Service Mesh design and implementor. It defines
**Control Panel**
and
**Data Panel**
,
Istio is a typical Service Mesh design and implementor. It defines
**Control Panel**
and
**Data Panel**
,
which are widely used. Here is Istio Architecture:
which are widely used. Here is
the
Istio Architecture:
![
Istio Architecture
](
https://istio.io/latest/docs/ops/deployment/architecture/arch.svg
)
![
Istio Architecture
](
https://istio.io/latest/docs/ops/deployment/architecture/arch.svg
)
Service Mesh probe can choose to collect data from
**Data Panel**
. In Istio, it means collecting telemetry data from
The
Service Mesh probe can choose to collect data from
**Data Panel**
. In Istio, it means collecting telemetry data from
Envoy sidecar
(Data Panel). The probe collects two telemetry entities from client side and server side
per request.
Envoy sidecar
(Data Panel). The probe collects two telemetry entities from the client end and the server end
per request.
## How does Service Mesh make backend work?
## How does Service Mesh make backend work?
From the probe, you can see there must have no trace related in this kind of probe, so why
SkyWalking
In this kind of probes, you can see that there is no trace related to them. So how does the
SkyWalking
platform
still works
?
platform
manage to work
?
Service Mesh probes collects telemetry data from each request, so it know
s the source, destination,
The Service Mesh probe collects telemetry data from each request, so they know about information such a
s the source, destination,
endpoint, latency and status.
By those, backend can tell the whole topology map by combining these call
endpoint, latency and status.
From these information, the backend can tell the whole topology map by combining these calls
as lines, and also the metrics of each nodes through their incoming request. Backend asked
for the same
into lines, as well as the metrics of each node through their incoming requests. The backend requests
for the same
metrics data
from parsing tracing data. So, the right expression is
:
metrics data
by parsing the trace data. In short
:
**
Service Mesh metrics are exact the metrics, what the traces parsers generate. They are same
.**
**
The Service Mesh metrics work exactly the same way as the metrics that are generated by trace parsers
.**
docs/en/concepts-and-designs/ui-overview.md
浏览文件 @
024f8104
# Visualization
# Visualization
SkyWalking native UI provides the default visualization solu
tion.
The SkyWalking native UI provides a default solution for visualiza
tion.
It provides observability related graphs
It provides observability related graphs
about overview, service, service instance, endpoint, trace
and alarm,
on overview, service, service instance, endpoint, trace,
and alarm,
including topology, dependency graph, heatmap
, etc.
such as topology maps, dependency graphs, heatmaps
, etc.
Also, we have already known, many of our users have integrated SkyWalking
We know that many of our users have integrated SkyWalking
into their products.
into their own products.
If you want to do that too, please use
[
SkyWalking query protocol
](
../protocols/README.md#query-protocol
)
.
If you would like to do that too, please refer to the
[
SkyWalking query protocol
](
../protocols/README.md#query-protocol
)
.
\ No newline at end of file
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录