From 91e5f8ca42e1b6539ba54a97450b06bab3e94ba2 Mon Sep 17 00:00:00 2001 From: Adriana Villela Date: Thu, 20 Jun 2024 14:43:54 -0400 Subject: [PATCH] update intro + prettify --- .../operator/troubleshooting/target-allocator.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/content/en/docs/kubernetes/operator/troubleshooting/target-allocator.md b/content/en/docs/kubernetes/operator/troubleshooting/target-allocator.md index 7e33717a5576..cbd1d1419d19 100644 --- a/content/en/docs/kubernetes/operator/troubleshooting/target-allocator.md +++ b/content/en/docs/kubernetes/operator/troubleshooting/target-allocator.md @@ -5,9 +5,10 @@ cSpell:ignore: bleh targetallocator If you’ve enabled [Target Allocator](/docs/kubernetes/operator/target-allocator/) service -discovery on the [OpenTelemetry Operator](/docs/kubernetes/operator), and your -metrics aren’t getting scraped, there are a few troubleshooting steps that you -can take to help you understand what’s going on and restore normal operation. +discovery on the [OpenTelemetry Operator](/docs/kubernetes/operator), and the +Target Allocator is failing to discover scrape targets, there are a few +troubleshooting steps that you can take to help you understand what’s going on +and restore normal operation. ## Troubleshooting steps @@ -182,8 +183,8 @@ You might also be wondering about the `otel-collector` entry. The Target Allocator automatically scrapes metrics from the OTel Collector as well. We can take a deeper look into `serviceMonitor/opentelemetry/sm-example/0`, to -see what scrape targets are getting picked up by running `curl` against the value of -the `_link` output above: +see what scrape targets are getting picked up by running `curl` against the +value of the `_link` output above: ```shell curl localhost:8080/jobs/serviceMonitor%2Fdefault%2Fmy-app%2F0/targets | jq