From 7089f18f6d3cd347f6559b36d719e740b2a28a2a Mon Sep 17 00:00:00 2001 From: Adriana Villela <50256412+avillela@users.noreply.github.com> Date: Thu, 19 Oct 2023 11:43:08 -0400 Subject: [PATCH] Update content/en/blog/2023/euwg-future-of-observability-panel/index.md Co-authored-by: Severin Neumann --- .../en/blog/2023/euwg-future-of-observability-panel/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/blog/2023/euwg-future-of-observability-panel/index.md b/content/en/blog/2023/euwg-future-of-observability-panel/index.md index 06323fae645c..96510bd73d97 100644 --- a/content/en/blog/2023/euwg-future-of-observability-panel/index.md +++ b/content/en/blog/2023/euwg-future-of-observability-panel/index.md @@ -54,7 +54,7 @@ case, including using custom processors. ## 4- Surprising Aspects of OpenTelemetry Adoption Challenges included convincing teams to adopt OpenTelemetry, especially when -components like Logs were not yet stable. The evolving nature of OpenTelemetry +components like [Logs](/docs/concepts/signals/logs/) were not yet stable. The evolving nature of OpenTelemetry made sometimes challenging to keep up with new features and updates while ensuring that teams did not lag behind.