Skywalking is an application performance monitoring tool for distributed systems, designed for microservices, cloud native architectures, and container-based (Docker, K8s, Mesos) architectures. SkyWalking is an observational analytics platform and application performance management system. Provides integrated solutions for distributed tracking, service grid telemetry analysis, measurement aggregation and visualization. Supports Java,.NET Core, PHP, NodeJS, Golang, LUA probes and Service Mesh built by Envoy + Istio.

First, the basic environment

Windos Java JDK: 1.8 Skywalking: 8.3 Elasticsearch: 6.7 (Data Storage) Nodejs: 14.15 Kibana: 6.7 (ES Data Visualization)

Two, installation, configuration, startup

All services are installed on the local PC. The default software configurations are used. You can modify the software configuration files if necessary.

ES + Kibana 2.1

1. Decompress the package

Elasticsearch -6.7.0\bin\ elasticSearch. bathttp://localhost:9200/Verify startup

3. Execute kibana-6.7.2-windows-x86_64\bin\ kibana. bat filehttp://localhost:5601/Verify startup

2.2 Skywalking

The main directory structure is as follows:

  • The bin directory stores startup scripts, including oapService.sh and webAppService. sh
  • Config is the oAP service configuration, including an application. Yml configuration
  • The Agent is the Agent of Skywalking and is used to collect service system logs
  • The WebApp directory is a configuration of the UI service on skyWalking’s front end

The overall structure is as follows:

Throughout skywalking’s system, there are four characters:

  • Skywalking Agent is bound to the business system and is responsible for collecting various monitoring data
  • Skywalking OAPService is responsible for processing monitoring data, such as receiving monitoring data from Skywalking Agent and storing it in the database. Accept skyWalking WebApp’s front-end request, query data from the database, and return data to the front-end. Skywalking OAPServices typically exist as clusters.
  • Skywalking WebApp, front end interface for presenting data.
  • A database used to store monitoring data, such as mysql, ElasticSearch, etc.

2.2.1 Configuration Change

Change the stored database: apache-Skywalking -apm-bin\config\application.yml

#selector: ${SW_STORAGE:h2} #selector: ${SW_STORAGE:h2}Copy the code

Start: Run the apapache – Skywalking -apm-bin\bin\startup.bat file and http://localhost:8080/ to verify the startup

JVM service usage

Override configuration items by adding JVM startup parameters:

Javaagent :D:\software\apache-skywalking-apm-bin\agent\skywalking-agent.jar # Agent service name, usually corresponds to project service name - Dskywalking. Agent. The service_name = you - service - nameCopy the code

For more configuration items, see apache-Skywalking -apm-bin\agent\config\agent.config

After completing the above steps, set JVM startup parameters in the boot class configuration screen of IDEA (add multiple services separately).

Start the service, refresh the Skywalking page and see [Current service] is not empty, then it succeeds