From 4c873f272ab34aa9c963aeee2cb3556b2da44de2 Mon Sep 17 00:00:00 2001 From: Severin Neumann Date: Fri, 16 Jun 2023 22:54:25 +0200 Subject: [PATCH] fix link on what is opentelemetry page (#2882) --- content/en/docs/what-is-opentelemetry.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/what-is-opentelemetry.md b/content/en/docs/what-is-opentelemetry.md index d90115e82..f089152fb 100644 --- a/content/en/docs/what-is-opentelemetry.md +++ b/content/en/docs/what-is-opentelemetry.md @@ -27,7 +27,7 @@ must emit [traces](/docs/concepts/signals/traces/)), to an Observability back-end. There are a number of Observability back-ends out there, ranging from self-hosted open source tools (e.g. [Jaeger](https://www.jaegertracing.io/) and [Zipkin](https://zipkin.io/)), to -[commercial offerings](http://localhost:1313/ecosystem/vendors/). +[commercial offerings](/ecosystem/vendors/). In the past, the way in which code was instrumented would vary, as each Observability back-end would have its own instrumentation libraries and agents