Replace the URL width https (#6392)
This commit is contained in:
Juntao Zhang
GitHub
parent
3c980c2609
commit
b70c9bef67
|
|
@ -30,7 +30,7 @@ In addition, you can integrate
|
|||
## Architecture
|
||||
SkyWalking is logically split into four parts: Probes, Platform backend, Storage and UI.
|
||||
|
||||
<img src="http://skywalking.apache.org/assets/frame-v8.jpg?u=20200423"/>
|
||||
<img src="https://skywalking.apache.org/assets/frame-v8.jpg?u=20200423"/>
|
||||
|
||||
- **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
|
||||
|
|
|
|||
|
|
@ -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:
|
||||
|
||||
<img src="http://skywalking.apache.org/doc-graph/communication-net.png"/>
|
||||
<img src="https://skywalking.apache.org/doc-graph/communication-net.png"/>
|
||||
|
||||
- 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`).
|
||||
|
|
|
|||
|
|
@ -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.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Create a new template. Template type: `Standard` -> Template Configuration: `Spring` -> Input the Template Name.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Click `view` button, Finally get the spring sleuth dashboard.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Supported meter
|
||||
|
||||
|
|
|
|||
|
|
@ -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.
|
||||
|
||||
|
||||
02. Server2 tracing path.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -4,11 +4,11 @@ cluster.
|
|||
|
||||
The latest introduction video could be found on the Youtube
|
||||
|
||||
[](http://www.youtube.com/watch?v=mfKaToAKl7k)
|
||||
[](http://www.youtube.com/watch?v=mfKaToAKl7k)
|
||||
|
||||
SkyWalking dashboard includes the following part.
|
||||
|
||||
<img src="http://skywalking.apache.org/ui-doc/7.0.0/dashboard.png"/>
|
||||
<img src="https://skywalking.apache.org/ui-doc/7.0.0/dashboard.png"/>
|
||||
|
||||
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.
|
||||
|
||||
<img src="http://skywalking.apache.org/ui-doc/7.0.0/dashboard-reload.png"/>
|
||||
<img src="https://skywalking.apache.org/ui-doc/7.0.0/dashboard-reload.png"/>
|
||||
|
||||
Two default dashboards are provided to visualize the metrics of service and database.
|
||||
|
||||
<img src="http://skywalking.apache.org/ui-doc/7.0.0/dashboard-default.png"/>
|
||||
<img src="https://skywalking.apache.org/ui-doc/7.0.0/dashboard-default.png"/>
|
||||
|
||||
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.
|
||||
|
||||
<img src="http://skywalking.apache.org/ui-doc/8.4.0/topology.png"/>
|
||||
<img src="https://skywalking.apache.org/ui-doc/8.4.0/topology.png"/>
|
||||
|
||||
* 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.
|
||||
|
||||
<img src="http://skywalking.apache.org/ui-doc/7.0.0/trace.png"/>
|
||||
<img src="https://skywalking.apache.org/ui-doc/7.0.0/trace.png"/>
|
||||
|
||||
* **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
|
||||
|
||||
<img src="http://skywalking.apache.org/ui-doc/7.0.0/profile-create.png" width="440px"/>
|
||||
<img src="https://skywalking.apache.org/ui-doc/7.0.0/profile-create.png" width="440px"/>
|
||||
|
||||
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.
|
||||
|
||||
<img src="http://skywalking.apache.org/ui-doc/7.0.0/profile-result.png"/>
|
||||
<img src="https://skywalking.apache.org/ui-doc/7.0.0/profile-result.png"/>
|
||||
|
||||
### 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.
|
||||
|
||||
<img src="http://skywalking.apache.org/ui-doc/8.3.0/log.png"/>
|
||||
<img src="https://skywalking.apache.org/ui-doc/8.3.0/log.png"/>
|
||||
|
||||
## Alarm
|
||||
Alarm page lists all triggered alarm. Read the backend setup documentation to know how to set up the alarm rule or integrate
|
||||
|
|
|
|||
Loading…
Reference in New Issue