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

Improve document (#2259)

This commit is contained in:
Song Kun 2019-02-19 19:03:00 +08:00 committed by 吴晟 Wu Sheng
parent 479ee33244
commit b4eb06e1fb
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -6,12 +6,12 @@ It is more like a modern APM, specially designed for cloud native, container bas
## Why use SkyWalking?
SkyWalking provides solutions for observing and monitoring distributed system, in many different scenarios. First of all,
like traditional ways, SkyWalking provides auto instrument agents for service, such as Java, C#
and NodeJS. At the same time, it provides manual instrument SDKs for Go(Not yet), C++(Not yet).
and Node.js. At the same time, it provides manual instrument SDKs for Go(Not yet), C++(Not yet).
Also with more languages required, risks in manipulating codes at runtime, cloud native infrastructures grow
more powerful, SkyWalking could use Service Mesher infra probes to collect data for understanding the whole distributed system.
In general, it provides observability capabilities for **service**(s), **service instance**(s), **endpoint**(s).
The concepts of Service, Instance and Endpoint are used everywhere today, so let's be clear about what they mean in SkyWalking first.
The concepts of Service, Instance and Endpoint are used everywhere today, so let's make it clear about what they mean in SkyWalking first.
- **Service**. Represent a set/group of workloads to provide the same behaviours for incoming requests. You can define the service
name when you are using instrument agents or SDKs. Or SkyWalking uses the name you defined in platform such as Istio.