Internship report skywalking distributed link tracking?

Overview of internship content

Skywalking Distributed Link Tracking ：

What is? skywaling Distributed Link Tracking ？ Distributed link tracking refers to the performance monitoring tool of distributed application system , Designed for microservices , Cloud native architecture and container based （K8S ,docker ） Architecture and Design .

Skywaling Provide distributed tracking , Service grid telemetry analysis , Measurement aggregation and visualization integration solution

Skywaling  Overall architecture analysis ：

In this picture , The overall architecture is divided into four parts ：

1. Upper part agent ： Responsible for... From the application , Collect link information , Send to skywaling OAP The server .

2、 Lower part SkyWalking OAP ： Responsible for receiving Agent Sent Tracing Data and information , And then analyze it (Analysis Core), To external storage (Storage), Finally, provide the query (Query) function ;

3、 Right section Storage：Tracing data storage , At present, we support ES、MySQL、Sharding Sphere、TiDB、H2 Multiple memories , At present, the most widely used is ES, The main consideration is SkyWalking The development team's own production environment uses ES Mainly ;

4、 Left part SkyWalking UI： Responsible for providing the console , Look at the links and so on ;

 
SkyWalking Environment construction and deployment （ Pictures come from the Internet ）

 

First, we download the software package , Start building one by one SkyWalking OAP and SkyWalking UI service ; Start a Spring Boot application , And configuration SkyWalking Agent; For the time being, data storage uses its default H2 Database storage , Later we will use other storage ;

SkyWalking Three concepts in

service (Service) ： Represents a series or set of workloads that provide the same behavior for requests , In the use of Agent when , You can define the name of the service , We can see Spring Boot The application service is "11-springboot", Is that we are in the environment variable SW_AGENT_NAME As defined in ;

Service instance (Service Instance) ： Each of the above set of workloads is called an instance , A service instance is actually a real process on the operating system ;

Here we can see Spring Boot The service of the application is {agent_name}-pid:{pid}@{hostname}, from Agent Automatic generation ;

Endpoint (Endpoint) ： For the request path received by a specific service , Such as HTTP Of URI Path and gRPC The class name of the service + Method signature ;

We can see Spring Boot An endpoint of the application , by API Interface /index;