From 75e8ce3114154523e51c1bccdea0170cb4f84b2b Mon Sep 17 00:00:00 2001 From: Manny <90020131+MannyPamintuanAtCare@users.noreply.github.com> Date: Mon, 13 Dec 2021 13:20:07 -0600 Subject: [PATCH] Updating opentelemetry getting-started hyperlink Per @abernix's [great suggestion](https://github.com/apollographql/federation/pull/1302#pullrequestreview-830585446), this PR does the following, - Updates the link to "Getting Started" to the [most recent link provided in the OTel-JS Repo](https://github.com/open-telemetry/opentelemetry-js/blob/main/README.md?plain=1#L5) - This change in linking is documented in OTel-JS [commit #2493](https://github.com/open-telemetry/opentelemetry-js/pull/2493) --- docs/source/opentelemetry.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/opentelemetry.mdx b/docs/source/opentelemetry.mdx index ff9f41441..00b6c12a6 100644 --- a/docs/source/opentelemetry.mdx +++ b/docs/source/opentelemetry.mdx @@ -208,7 +208,7 @@ Our example telemetry configuration assumes that Zipkin is running locally, and To prepare for production, we probably at least want to conditionally set the `url` option for the `ZipkinExporter` and replace our `SimpleSpanProcessor` with a `BatchSpanProcessor`. -You can learn more about the settings available to these and other OpenTelemetry objects in the [getting started guide](https://github.com/open-telemetry/opentelemetry-js/tree/main/getting-started). +You can learn more about the settings available to these and other OpenTelemetry objects in the [getting started guide](https://opentelemetry.io/docs/instrumentation/js/getting-started/). ## GraphQL-specific spans