From 61d671e3b949d9798f328f96e8cf4ab5201cd0d2 Mon Sep 17 00:00:00 2001 From: Adriana Villela <50256412+avillela@users.noreply.github.com> Date: Fri, 21 Jun 2024 16:19:11 -0400 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Jacob Aronoff --- .../kubernetes/operator/troubleshooting/target-allocator.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/kubernetes/operator/troubleshooting/target-allocator.md b/content/en/docs/kubernetes/operator/troubleshooting/target-allocator.md index b64be3141935..45e0a396c4e2 100644 --- a/content/en/docs/kubernetes/operator/troubleshooting/target-allocator.md +++ b/content/en/docs/kubernetes/operator/troubleshooting/target-allocator.md @@ -177,7 +177,7 @@ Where `serviceMonitor/opentelemetry/sm-example/0` represents one of the Similarly, the `PodMonitor`, shows up as `podMonitor/opentelemetry/pm-example/0` in the `curl` output. -This is good news, because it tells us that the service discovery is working! +This is good news, because it tells us that the scrape config discovery is working! You might also be wondering about the `otel-collector` entry. The Target Allocator automatically scrapes metrics from the OTel Collector as well.