From c991c1c4adee7f2e76859096050fc80a9f7fc1ff Mon Sep 17 00:00:00 2001 From: Patrice Chalin Date: Fri, 12 Nov 2021 19:10:38 -0500 Subject: [PATCH] [website_docs] Link to website spec pages (#2276) Co-authored-by: Leighton Chen --- website_docs/getting-started.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website_docs/getting-started.md b/website_docs/getting-started.md index 4453c06eb8..d993f4bbb7 100644 --- a/website_docs/getting-started.md +++ b/website_docs/getting-started.md @@ -259,7 +259,7 @@ A major feature of distributed tracing is the ability to correlate a trace acros multiple services. However, those services need to propagate information about a trace from one service to the other. -To enable this propagation, OpenTelemetry has the concept of [propagators](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/context/api-propagators.md), +To enable this propagation, OpenTelemetry has the concept of [propagators]({{< relref "/docs/reference/specification/context/api-propagators" >}}), which provide a common method to encode and decode span information from a request and response, respectively. By default, `opentelemetry-python` is configured to use the [W3C Trace Context](https://www.w3.org/TR/trace-context/)