kazusa
/
skywalking-java
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Refine concepts and designs (#6724)

This commit is contained in:
Wing 2021-04-10 16:56:09 +08:00 committed by GitHub
parent 5ba8f00205
commit 024f810495
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 21 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
docs/en/concepts-and-designs/service-mesh-probe.md
View File

@ -1,28 +1,28 @@
# 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?
The following explanation came from Istio documents.
> The term service mesh is often used to describe the network of microservices that make up such applications and the interactions between them.
The following explanation comes from Istio's documentation.
> 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.
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.
## Where does the probe collect data from?
Istio is a very typical Service Mesh design and implementor. It defines **Control Panel** and **Data Panel**,
which are widely used. Here is Istio Architecture:
Istio is a typical Service Mesh design and implementor. It defines **Control Panel** and **Data Panel**,
which are widely used. Here is the Istio Architecture:
![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
Envoy sidecar(Data Panel). The probe collects two telemetry entities from client side and server side per request.
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 the client end and the server end per request.
## 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
platform still works?
In this kind of probes, you can see that there is no trace related to them. So how does the SkyWalking
platform manage to work?
Service Mesh probes collects telemetry data from each request, so it knows the source, destination,
endpoint, latency and status. By those, backend can tell the whole topology map by combining these call
as lines, and also the metrics of each nodes through their incoming request. Backend asked for the same
metrics data from parsing tracing data. So, the right expression is:
**Service Mesh metrics are exact the metrics, what the traces parsers generate. They are same.**
The Service Mesh probe collects telemetry data from each request, so they know about information such as the source, destination,
endpoint, latency and status. From these information, the backend can tell the whole topology map by combining these calls
into lines, as well as the metrics of each node through their incoming requests. The backend requests for the same
metrics data by parsing the trace data. In short:
**The Service Mesh metrics work exactly the same way as the metrics that are generated by trace parsers.**

14
docs/en/concepts-and-designs/ui-overview.md
View File

@ -1,10 +1,10 @@
# Visualization
SkyWalking native UI provides the default visualization solution.
The SkyWalking native UI provides a default solution for visualization.
It provides observability related graphs
about overview, service, service instance, endpoint, trace and alarm,
including topology, dependency graph, heatmap, etc.
on overview, service, service instance, endpoint, trace, and alarm,
such as topology maps, dependency graphs, heatmaps, etc.
Also, we have already known, many of our users have integrated SkyWalking
into their products.
If you want to do that too, please use [SkyWalking query protocol](../protocols/README.md#query-protocol).
We know that many of our users have integrated SkyWalking
into their own products.
If you would like to do that too, please refer to the [SkyWalking query protocol](../protocols/README.md#query-protocol).