From 61a64b57e02b113fba28cca00d97b0e89a160f00 Mon Sep 17 00:00:00 2001 From: iamveritas Date: Fri, 18 Dec 2020 15:29:37 +0200 Subject: [PATCH 1/2] update link to chain plug-in to be relative --- .../06_logging/20_third_party_logging/20_zipkin_tracer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/01_nodeos/06_logging/20_third_party_logging/20_zipkin_tracer.md b/docs/01_nodeos/06_logging/20_third_party_logging/20_zipkin_tracer.md index bae8b4e17b1..cda3287fa0e 100644 --- a/docs/01_nodeos/06_logging/20_third_party_logging/20_zipkin_tracer.md +++ b/docs/01_nodeos/06_logging/20_third_party_logging/20_zipkin_tracer.md @@ -9,7 +9,7 @@ The `Zipkin service` is a [distributed tracing system](https://zipkin.io/). It h ### How To Enable Zipkin Tracer -EOSIO makes available `Zipkin tracer` through the [core `chain_plugin`](https://developers.eos.io/manuals/eos/v2.0/nodeos/plugins/chain_plugin/index/?query=chain%20plugin&page=1#gatsby-focus-wrapper). To enable the `Zipkin tracer` you must set the `telemetry-url` parameter for the `chain_plugin`. There are two additional parameters you can set: `telemetry-service-name` and `telemetry-timeout-us`. All three available parameters are detailed below: +EOSIO makes available `Zipkin tracer` through the [core `chain_plugin`](../../plugins/chain_plugin/index/?query=chain%20plugin&page=1#gatsby-focus-wrapper). To enable the `Zipkin tracer` you must set the `telemetry-url` parameter for the `chain_plugin`. There are two additional parameters you can set: `telemetry-service-name` and `telemetry-timeout-us`. All three available parameters are detailed below: * `telemetry-url` specifies the url of the Zipkin service, e.g. [http://127.0.0.1:9411/api/v2/spans](http://127.0.0.1:9411/api/v2/spans) if it is installed in the local environment. * `telemetry-service-name` specifies the Zipkin `localEndpoint.serviceName` sent with each span. From 9ffd6a8e4f97d3a4b40c4076ba32c6ebd541061f Mon Sep 17 00:00:00 2001 From: iamveritas Date: Fri, 18 Dec 2020 15:59:08 +0200 Subject: [PATCH 2/2] clean up link --- .../06_logging/20_third_party_logging/20_zipkin_tracer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/01_nodeos/06_logging/20_third_party_logging/20_zipkin_tracer.md b/docs/01_nodeos/06_logging/20_third_party_logging/20_zipkin_tracer.md index cda3287fa0e..fef052ab791 100644 --- a/docs/01_nodeos/06_logging/20_third_party_logging/20_zipkin_tracer.md +++ b/docs/01_nodeos/06_logging/20_third_party_logging/20_zipkin_tracer.md @@ -9,7 +9,7 @@ The `Zipkin service` is a [distributed tracing system](https://zipkin.io/). It h ### How To Enable Zipkin Tracer -EOSIO makes available `Zipkin tracer` through the [core `chain_plugin`](../../plugins/chain_plugin/index/?query=chain%20plugin&page=1#gatsby-focus-wrapper). To enable the `Zipkin tracer` you must set the `telemetry-url` parameter for the `chain_plugin`. There are two additional parameters you can set: `telemetry-service-name` and `telemetry-timeout-us`. All three available parameters are detailed below: +EOSIO makes available `Zipkin tracer` through the [core `chain_plugin`](../../03_plugins/chain_plugin). To enable the `Zipkin tracer` you must set the `telemetry-url` parameter for the `chain_plugin`. There are two additional parameters you can set: `telemetry-service-name` and `telemetry-timeout-us`. All three available parameters are detailed below: * `telemetry-url` specifies the url of the Zipkin service, e.g. [http://127.0.0.1:9411/api/v2/spans](http://127.0.0.1:9411/api/v2/spans) if it is installed in the local environment. * `telemetry-service-name` specifies the Zipkin `localEndpoint.serviceName` sent with each span.