4. Configuration information

It can be used to set the data storage. If it is local, it can also be used as the default without modification. It is only used to view the effect of integrating skywalking with springboot project without modification.

4.1 OAP configuration file

config/application.yml

  INFO 2020-02-13 14:57:36:310 main SnifferConfigInitializer : Config file found in C:\Users\ke\Desktop\apache-skywalking-apm-6.6.0\apache-skywalking-apm-bin\agent\config\agent.config.

5.2. Java command line startup mode

java -javaagent:C:\Users\ke\Desktop\apache-skywalking-apm-6.6.0\apache-skywalking-apm-bin\agent/skywalking-agent.jar=-Dskywalking.agent.service_name=service-myapp,-Dskywalking.collector.backend_service=localhost:11800 -jar service-myapp.jar

5.3. Script startup

Script writing (can be used after modification)

[root@basenode demo]# vi startup.sh 

#!/bin/sh
# SkyWalking Agent configuration
export SW_AGENT_NAME=springboot-skywalking-wudl #Agent name, usually ` spring application. name`
export SW_AGENT_COLLECTOR_BACKEND_SERVICES=192.168.1.180:11800 #Configure the Collector address.
export SW_AGENT_SPAN_LIMIT=2000 #Configure the maximum number of spans for the link. The default is 300. 
export JAVA_AGENT=-javaagent:/opt/module/skywalking-apm-bin-es7/agent/skywalking-agent.jar
java $JAVA_AGENT -jar /opt/module/demo/user-center-0.0.1-SNAPSHOT.jar #jar startup

function

[root@basenode demo]# sh startup.sh 
DEBUG 2021-09-12 18:01:30:050 main AgentPackagePath : The beacon class location is jar:file:/opt/module/skywalking-apm-bin-es7/agent/skywalking-agent.jar!/org/apache/skywalking/apm/agent/core/boot/AgentPackagePath.class. 
INFO 2021-09-12 18:01:30:051 main SnifferConfigInitializer : Config file found in /opt/module/skywalking-apm-bin-es7/agent/config/agent.config. 

  .   ____          _            __ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
  '  |____| .__|_| |_|_| |_\__, | / / / /
 =========|_|==============|___/=/_/_/_/
 :: Spring Boot ::        (v2.2.2.RELEASE)

2021-09-12 18:01:39.170  INFO 5590 --- [           main] c.wudl.usercenter.UserCenterApplication  : Starting UserCenterApplication v0.0.1-SNAPSHOT on basenode with PID 5590 (/opt/module/demo/user-center-0.0.1-SNAPSHOT.jar started by root in /opt/module/demo)
2021-09-12 18:01:39.177  INFO 5590 --- [           main] c.wudl.usercenter.UserCenterApplication  : The following profiles are active: dev
2021-09-12 18:01:43.948  INFO 5590 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat initialized with port(s): 9909 (http)
2021-09-12 18:01:44.050  INFO 5590 --- [           main] o.apache.catalina.core.StandardService   : Starting service [Tomcat]
2021-09-12 18:01:44.050  INFO 5590 --- [           main] org.apache.catalina.core.StandardEngine  : Starting Servlet engine: [Apache Tomcat/9.0.29]
2021-09-12 18:01:44.196  INFO 5590 --- [           main] o.a.c.c.C.[Tomcat].[localhost].[/]       : Initializing Spring embedded WebApplicationContext
2021-09-12 18:01:44.197  INFO 5590 --- [           main] o.s.web.context.ContextLoader            : Root WebApplicationContext: initialization completed in 4819 ms
2021-09-12 18:01:47.260  INFO 5590 --- [           main] o.s.s.concurrent.ThreadPoolTaskExecutor  : Initializing ExecutorService 'applicationTaskExecutor'
2021-09-12 18:01:47.956  INFO 5590 --- [           main] t.m.m.autoconfigure.MapperCacheDisabler  : Clear tk.mybatis.mapper.util.MsUtil CLASS_CACHE cache.
2021-09-12 18:01:47.956  INFO 5590 --- [           main] t.m.m.autoconfigure.MapperCacheDisabler  : Clear tk.mybatis.mapper.genid.GenIdUtil CACHE cache.
2021-09-12 18:01:47.957  INFO 5590 --- [           main] t.m.m.autoconfigure.MapperCacheDisabler  : Clear tk.mybatis.mapper.version.VersionUtil CACHE cache.
2021-09-12 18:01:47.957  INFO 5590 --- [           main] t.m.m.autoconfigure.MapperCacheDisabler  : Clear EntityHelper entityTableMap cache.
2021-09-12 18:01:48.365  INFO 5590 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat started on port(s): 9909 (http) with context path ''
2021-09-12 18:01:48.370  INFO 5590 --- [           main] c.wudl.usercenter.UserCenterApplication  : Started UserCenterApplication in 11.576 seconds (JVM running for 18.419)

6. Simple test

After that, you can go to the SkyWalking UI to check whether the link collection is successful.

1. First, use the browser to access http://127.0.0.1:8079/demo/echo Address and request the API provided by the Spring Boot application. Because we need to track the link.

2. Then, continue using the browser and open http://127.0.0.1:8080/ Address and enter the SkyWalking UI interface. As shown in the figure below:

Here, we will see three very important concepts in SkyWalking:

• Service: represents a series or set of workloads that provide the same behavior to requests. When using the Agent or SDK, you can define the name of the service. If not defined, SkyWalking will use the name you defined on the platform (e.g. Istio).

  Here, we can see that the service of the Spring Boot application is "demo application", that is, we are in the environment variable SW_ AGENT_ As defined in name +.

• Service instance: each workload in the above set of workloads is called an instance. Like pods in Kubernetes, a service instance is not necessarily a process on the operating system. But when you use Agent, a service instance is actually a real process on the operating system.

  Here, we can see that the service of Spring Boot application is {agent_name}-pid:{pid}@{hostname}, which is automatically generated by the Agent. About it, we are 「5.1 hostname」 In the section, there is further explanation, fat friends can have a look.

• Endpoint: the request path received by a specific service, such as the URI path of HTTP and the class name + method signature of gRPC service.

  Here, we can see an endpoint of the Spring Boot application, which is the API interface / demo/echo.

3. Then, click the "topology map" menu to enter the view topology map interface. As shown in the figure below:

4. After that, click the "tracking" menu to enter the interface of viewing link data. As shown in the figure below:

7. Others

To build a SkyWalking} cluster environment, the steps are as follows:

• The first step is to build a cluster of Elasticsearch services.
• The second step is to build a cluster of registration centers. At present, SkyWalking supports Zookeeper, Kubernetes, Consul and Nacos as registration centers.
• Step 3: build a cluster of SkyWalking OAP services, and refer to SkyWalking documentation - cluster management , register the SkyWalking OAP service with the registry.
• Step 4: start a Spring Boot application and configure SkyWalking Agent. In addition, set the SW of SkyWalking Agent_ AGENT_ COLLECTOR_ BACKEND_ For services} address, you need to set multiple address arrays of SkyWalking OAP services.
• Step 5: build a cluster of SkyWalking UI services and use Nginx for load balancing. In addition, set the SkyWalking UI's {collector ribbon. When listofservers} addresses, you also need to set multiple address arrays of SkyWalking OAP services.