diff --git a/docs/en/concepts-and-designs/overview.md b/docs/en/concepts-and-designs/overview.md index 3a1d503403f7e20f0451fc003df07d526623e5cb..613e98521450ba8ee6e2fca6d486396c645a8ed6 100644 --- a/docs/en/concepts-and-designs/overview.md +++ b/docs/en/concepts-and-designs/overview.md @@ -30,7 +30,7 @@ In addition, you can integrate ## Architecture SkyWalking is logically split into four parts: Probes, Platform backend, Storage and UI. - + - **Probe**s collect data and reformat them for SkyWalking requirements (different probes support different sources). - **Platform backend**, supports data aggregation, analysis and drives process flow from probes to the UI. The analysis includes diff --git a/docs/en/setup/backend/backend-ui-setup.md b/docs/en/setup/backend/backend-ui-setup.md index 25f6e9dc6450f730697b10c3742befa7af1737cd..d5939fcf43bde1c6d582c402f240b8490189eff6 100644 --- a/docs/en/setup/backend/backend-ui-setup.md +++ b/docs/en/setup/backend/backend-ui-setup.md @@ -37,7 +37,7 @@ In Java, .NetCore, Node.js, Istio agents/probe, you should set the gRPC service Before deploying Skywalking in your distributed environment, you should know how agents/probes, backend, UI communicates with each other: - + - All native agents and probes, either language based or mesh probe, are using gRPC service (`core/default/gRPC*` in `application.yml`) to report data to the backend. Also, jetty service supported in JSON format. - UI uses GraphQL (HTTP) query to access the backend also in Jetty service (`core/default/rest*` in `application.yml`). diff --git a/docs/en/setup/backend/spring-sleuth-setup.md b/docs/en/setup/backend/spring-sleuth-setup.md index e42699f485b5cf9f3120a62878f6bdbeb4f95401..7eb5a5df8116cc38b5713afc23580e890af91b98 100644 --- a/docs/en/setup/backend/spring-sleuth-setup.md +++ b/docs/en/setup/backend/spring-sleuth-setup.md @@ -43,16 +43,16 @@ If you also has some customized meter at the agent side, please read [meter docu 1. Open the dashboard view, click `edit` button to edit the templates. - ![Click edit button](http://skywalking.apache.org/screenshots/8.0.0/spring-sleuth-setup-ui-20200723-01.png) + ![Click edit button](https://skywalking.apache.org/screenshots/8.0.0/spring-sleuth-setup-ui-20200723-01.png) 1. Create a new template. Template type: `Standard` -> Template Configuration: `Spring` -> Input the Template Name. - ![Create template](http://skywalking.apache.org/screenshots/8.0.0/spring-sleuth-setup-ui-20200723-02.png) + ![Create template](https://skywalking.apache.org/screenshots/8.0.0/spring-sleuth-setup-ui-20200723-02.png) 1. Click `view` button, Finally get the spring sleuth dashboard. - ![Save template](http://skywalking.apache.org/screenshots/8.0.0/spring-sleuth-setup-ui-20200723-03.png) - ![Spring Sleuth Dashboard](http://skywalking.apache.org/screenshots/8.0.0/spring-sleuth-setup-ui-20200725-04.png) + ![Save template](https://skywalking.apache.org/screenshots/8.0.0/spring-sleuth-setup-ui-20200723-03.png) + ![Spring Sleuth Dashboard](https://skywalking.apache.org/screenshots/8.0.0/spring-sleuth-setup-ui-20200725-04.png) ## Supported meter diff --git a/docs/en/setup/service-agent/java-agent/agent-optional-plugins/Kotlin-Coroutine-plugin.md b/docs/en/setup/service-agent/java-agent/agent-optional-plugins/Kotlin-Coroutine-plugin.md index 27c200193b18969d70bdc499f051931de82d6e87..91929600c7fe7c79efe653c48570e78c9c5cd957 100644 --- a/docs/en/setup/service-agent/java-agent/agent-optional-plugins/Kotlin-Coroutine-plugin.md +++ b/docs/en/setup/service-agent/java-agent/agent-optional-plugins/Kotlin-Coroutine-plugin.md @@ -18,11 +18,11 @@ We run a Kotlin coroutine based gRPC server without this coroutine plugin. You can find, the one call (client -> server1 -> server2) has been split two tracing paths. 01. Server1 without exit span and server2 tracing path. -![Without kotlin plugin1](http://skywalking.apache.org/screenshots/7.0.0/kotlin/coroutine/without-coroutine-plugin-server1.jpg) +![Without kotlin plugin1](https://skywalking.apache.org/screenshots/7.0.0/kotlin/coroutine/without-coroutine-plugin-server1.jpg) 02. Server2 tracing path. -![Without kotlin plugin2](http://skywalking.apache.org/screenshots/7.0.0/kotlin/coroutine/without-coroutine-plugin-server2.jpg) +![Without kotlin plugin2](https://skywalking.apache.org/screenshots/7.0.0/kotlin/coroutine/without-coroutine-plugin-server2.jpg) ### Run with the plugin Without changing codes manually, just install the plugin. We can find the spans be connected together. We can get all info of one client call. -![With kotlin plugin](http://skywalking.apache.org/screenshots/7.0.0/kotlin/coroutine/run-with-coroutine-plugin.jpg) +![With kotlin plugin](https://skywalking.apache.org/screenshots/7.0.0/kotlin/coroutine/run-with-coroutine-plugin.jpg) diff --git a/docs/en/ui/README.md b/docs/en/ui/README.md index 981ae083cfe68c170d120e6489f7bfc344e08deb..2ede7b9ccfdccd8cbdd554771d575fbe03f3bafc 100644 --- a/docs/en/ui/README.md +++ b/docs/en/ui/README.md @@ -4,11 +4,11 @@ cluster. The latest introduction video could be found on the Youtube -[![RocketBot UI](http://img.youtube.com/vi/mfKaToAKl7k/0.jpg)](http://www.youtube.com/watch?v=mfKaToAKl7k) +[![RocketBot UI](https://img.youtube.com/vi/mfKaToAKl7k/0.jpg)](http://www.youtube.com/watch?v=mfKaToAKl7k) SkyWalking dashboard includes the following part. - + 1. **Feature Tab Selector Zone**. The key features are list there. The more details will be introduced below. 1. **Reload Zone**. Control the reload mechanism, including reload periodically or manually. @@ -25,11 +25,11 @@ Dashboard provide metrics of service, service instance and endpoint. There are a Service, Instance and Dashboard selector could reload manually rather than reload the whole page. NOTICE, the **Reload Zone** wouldn't reload these selectors. - + Two default dashboards are provided to visualize the metrics of service and database. - + User could click the `lock` button left aside the `Service/Instance/Endpoint Reload` button to custom your own dashboard. @@ -87,7 +87,7 @@ Check the entity named as `ui_template` in your storage. ## Topology Topology map shows the relationship among the services and instances with metrics. - + * Topology shows the default global topology including all services. * **Service Selector** provides 2 level selectors, service group list and service name list. The group name is separated from @@ -100,7 +100,7 @@ or global(include all services). ## Trace Query Trace query is a typical feature as SkyWalking provided distributed agents. - + * **Trace Segment List** is not the trace list. Every trace has several segments belonging to different services. If query by all services or by trace id, different segments with same trace id could be list there. @@ -112,7 +112,7 @@ Profile is an interaction feature. It provides the method level performance diag To start the profile analysis, user need to create the profile task - + 1. Select the specific service. 1. Set the endpoint name. This endpoint name typically is the operation name of the first span. Find this on the trace @@ -135,7 +135,7 @@ Typically, we analysis spans having long self duration, if the span and its chil After choose the right span, and click the `analysis` button, you will see the stack based analysis result. The slowest methods have been highlighted. - + ### Advanced features 1. Since 7.1.0, the profiled trace collects the HTTP request parameters for Tomcat and SpringMVC Controller automatically. @@ -144,7 +144,7 @@ have been highlighted. Since 8.3.0, SkyWalking provides log query for the browser monitoring. Use [Apache SkyWalking Client JS](https://github.com/apache/skywalking-client-js) agent would collect metrics and error logs. - + ## Alarm Alarm page lists all triggered alarm. Read the backend setup documentation to know how to set up the alarm rule or integrate