From 77df5fbe9e038dd61dd830b776ada4aed696c422 Mon Sep 17 00:00:00 2001 From: Paschalis Tsilias Date: Wed, 10 Jan 2024 02:57:33 +0200 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Clayton Cornell <131809008+clayton-cornell@users.noreply.github.com> --- .../sources/flow/reference/components/loki.source.docker.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/sources/flow/reference/components/loki.source.docker.md b/docs/sources/flow/reference/components/loki.source.docker.md index 1c2175e6b555..3dd327f70a80 100644 --- a/docs/sources/flow/reference/components/loki.source.docker.md +++ b/docs/sources/flow/reference/components/loki.source.docker.md @@ -131,11 +131,11 @@ fully qualified name) to store its _positions file_. The positions file stores the read offsets so that if there is a component or Agent restart, `loki.source.docker` can pick up tailing from the same spot. -In case the targets argument contains multiple entries with the same container +If the target's argument contains multiple entries with the same container ID (for example as a result of `discovery.docker` picking up multiple exposed -ports or networks) `loki.source.docker` will deduplicate them, and only keep +ports or networks), `loki.source.docker` will deduplicate them, and only keep the first of each container ID instances, based on the -`__meta_docker_container_id` label. As such, the Docker daemon will be queried +`__meta_docker_container_id` label. As such, the Docker daemon is queried for each container ID only once, and only one target will be available in the component's debug info.