kazusa
/
skywalking
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix some dead links (#6934)

This commit is contained in:
Zhenxu Ke 2021-05-13 09:26:28 +08:00 committed by GitHub
parent 85a993faf5
commit a6828e7da2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.github/workflows/e2e.storages.yaml vendored
View File

@ -50,7 +50,7 @@ jobs:
${{ runner.os }}-maven- ${{ runner.os }}-maven-
- name: Build OpenSearch - name: Build OpenSearch
if: matrix.storage == 'opensearch' if: env.SKIP_CI != 'true' && matrix.storage == 'opensearch'
run: bash test/e2e/e2e-test/docker/build-opensearch.sh run: bash test/e2e/e2e-test/docker/build-opensearch.sh
- name: Run E2E Test - name: Run E2E Test

4
docs/en/setup/envoy/metrics_service_setting.md
View File

@ -50,7 +50,7 @@ static_resources:
A more complete static configuration, can be observed [here](config.yaml). A more complete static configuration, can be observed [here](config.yaml).
Note that Envoy can also be configured dynamically through [xDS Protocol](https://github.com/envoyproxy/data-plane-api/blob/main/xds_protocol.rst). Note that Envoy can also be configured dynamically through [xDS Protocol](https://github.com/envoyproxy/envoy/blob/v1.18.2/api/xds_protocol.rst).
As mentioned above, SkyWalking also builds the topology of services from the metrics, this is because Envoy also carries the service metadata along with the metrics, to feed the Envoy such metadata, another configuration part is as follows: As mentioned above, SkyWalking also builds the topology of services from the metrics, this is because Envoy also carries the service metadata along with the metrics, to feed the Envoy such metadata, another configuration part is as follows:
@ -65,7 +65,7 @@ node:
## Configure Envoy to send metrics to SkyWalking with Istio ## Configure Envoy to send metrics to SkyWalking with Istio
Typically, Envoy can be also used under Istio's control, where the configurations are much more simple because Istio composes the configurations for you and sends them to Envoy via [xDS Protocol](https://github.com/envoyproxy/data-plane-api/blob/master/xds_protocol.rst). Typically, Envoy can be also used under Istio's control, where the configurations are much more simple because Istio composes the configurations for you and sends them to Envoy via [xDS Protocol](https://github.com/envoyproxy/envoy/blob/v1.18.2/api/xds_protocol.rst).
Istio also automatically injects the metadata such as service name and instance name into the bootstrap configurations. Istio also automatically injects the metadata such as service name and instance name into the bootstrap configurations.
Under this circumstance, emitting the metrics to SyWalking is as simple as adding the option `--set meshConfig.defaultConfig.envoyMetricsService.address=<skywalking.address.port.11800>` to Istio install command, for example: Under this circumstance, emitting the metrics to SyWalking is as simple as adding the option `--set meshConfig.defaultConfig.envoyMetricsService.address=<skywalking.address.port.11800>` to Istio install command, for example: