From 64f274fc5bce9c264e9de1f9fee9f2ab0b1ef909 Mon Sep 17 00:00:00 2001 From: Tigran Najaryan <4194920+tigrannajaryan@users.noreply.github.com> Date: Thu, 22 Feb 2024 10:05:35 -0500 Subject: [PATCH] Update docs/resource/README.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Juraci Paixão Kröhling --- docs/resource/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/resource/README.md b/docs/resource/README.md index 805d3a21c9..5dd529d264 100644 --- a/docs/resource/README.md +++ b/docs/resource/README.md @@ -124,7 +124,7 @@ thread in unicorn) to have its own instance.id. It's not recommended for a Collector to set `service.instance.id` if it can't unambiguously determine the service instance that is generating that telemetry. For instance, creating an UUID based on `pod.name` will -likely be wrong, as the Collector likely doesn't know whether there are multiple containers within that pod. +likely be wrong, as the Collector might not know from which container within that pod the telemetry originated. However, Collectors can set the `service.instance.id` if they can unambiguously determine the service instance for that telemetry. This is typically the case for scraping receivers, as they know the target address and port.