Apache SkyWalking is an application performance monitoring tool for distributed systems, especially designed for microservices, cloud-native, and container-based architectures (Docker, K8s, Mesos).
SkyWalking is developed in a component-based manner and is easy to scale, with the following main components:
Skywalking Agent: Collects tracking and metric information and reports it, and sends data to Skywalking Collector via HTTP or gRPC
Skywalking Collector: A link data collector that integrates and analyzes the tracing and metric data sent by the agent, processes it through the Analysis Core module and falls into the relevant data storage, and performs secondary statistics and monitoring alarms through the Query Core module
Storage: Skywalking supports data storage using ElasticSearch, Mysql, TiDB, H2, etc. as storage media
UI: A web visualization platform used to display landed data, and currently officially adopts RocketBot as the main UI of SkyWalking
GitHub address:The hyperlink login is visible.
This article uses docker to deploy and install Skywalking, and I test the service docker version is: 19.03.13
Install ElasticSearch
This article uses es for storage, using ES version 6.8.13
About the required ES version:The hyperlink login is visible.
Install Apache SkyWalking OAP
As of version 6.6.0, we have divided the OAP image into two labels, XYZ-ES6 and XYZ-ES7. As the name suggests, it es6 intends to connect to Elasticsearch 6 and es7.
The LATEST tag points to ES6
Image address:The hyperlink login is visible.
Note:Be sure to add a labeled versionAlthough the default LATEST tag points to ES6, but if I don't add the tag in my test, the error will be as follows:
[Entrypoint] Apache SkyWalking Docker Image
Current image doesn't Elasticsearch 6
Port description
0.0.0.0/11800: gRPC APIs for Java, . NetCore, Node.js, Istio probes
0.0.0.0/12800: http rest APIs for SkyWalking UI requests, doing GraphQL queries
Install SkyWalking-UI
The command is as follows:
At this point, all the installations are complete, docker looks at the running containers, as follows:
Try accessing the UI panel: http://ip:8080/ as shown below:
(End)
|
Posted on 11/5/2020 12:03:37 PM
|
|
|
|
Landlord