From fe625644c92d9805ea6480b2cbb266975f12350b Mon Sep 17 00:00:00 2001 From: Adriana Villela <50256412+avillela@users.noreply.github.com> Date: Fri, 10 May 2024 11:02:24 -0400 Subject: [PATCH] Update content/en/blog/2024/prom-and-otel/index.md Co-authored-by: Patrice Chalin --- content/en/blog/2024/prom-and-otel/index.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/content/en/blog/2024/prom-and-otel/index.md b/content/en/blog/2024/prom-and-otel/index.md index d9ced428757a..8bb90222e1a2 100644 --- a/content/en/blog/2024/prom-and-otel/index.md +++ b/content/en/blog/2024/prom-and-otel/index.md @@ -593,8 +593,9 @@ annotations you’ve added to your pods and namespaces. There are a few more Collector components you can implement to monitor Kubernetes, including Kubernetes-specific ones as well as general-use -processors, such as the batch, memory limiter, and resource processors. You can -read more about them [here](docs/kubernetes/collector/components/). +processors, such as the batch, memory limiter, and resource processors. To learn +more, see [Important Components for +Kubernetes](/docs/kubernetes/collector/components/). After you’ve configured the components in your Collector config file, you need to enable them within the [pipelines](/docs/collector/configuration/#pipelines)