Skip to content
This repository was archived by the owner on Aug 2, 2022. It is now read-only.

[docs] Correct link to the chain plugin #9797

Merged
merged 1 commit into from
Dec 17, 2020
Merged

Conversation

gleehokie
Copy link
Contributor

Change Description

Change link to chain plugin docs from 2.0 to 2.1

Change Type

Select ONE:

  • Documentation
  • Stability bug fix
  • Other
  • Other - special case

Testing Changes

Select ANY that apply:

  • New Tests
  • Existing Tests
  • Test Framework
  • CI System
  • Other

Consensus Changes

  • Consensus Changes

API Changes

  • API Changes

Documentation Additions

  • Documentation Additions

Change link from 2.0 to 2.1
@gleehokie gleehokie requested a review from iamveritas December 16, 2020 23:19
@iamveritas iamveritas merged commit bc14b47 into develop Dec 17, 2020
@@ -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`](https://developers.eos.io/manuals/eos/v2.1/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:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@iamveritas this link to chain plugin should be relative (same repo, docs scope): ../../03_plugins/chain_plugin/index.md, then whether it's v2.0, v2.1, or release is irrelevant. Filed issue #9804 to address this and two other link problems.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants