From a8da1868564c9851a8f23d35e563a09cab2df2e7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Carlos=20P=C3=A9rez-Aradros=20Herce?= Date: Tue, 3 Jul 2018 10:30:48 +0200 Subject: [PATCH] Clarify autodiscover docs in relation to startup process (#7468) Autodiscover reacts to already existing containers first, then it starts listening for changes of that initial state. --- libbeat/docs/shared-autodiscover.asciidoc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/libbeat/docs/shared-autodiscover.asciidoc b/libbeat/docs/shared-autodiscover.asciidoc index 300da5da00c7..4b07e6a9e9ae 100644 --- a/libbeat/docs/shared-autodiscover.asciidoc +++ b/libbeat/docs/shared-autodiscover.asciidoc @@ -15,6 +15,9 @@ Autodiscover providers work by watching for events on the system and translating events with a common format. When you configure the provider, you can use fields from the autodiscover event to set conditions that, when met, launch specific configurations. +On start, {beatname_uc} will scan existing containers and launch the proper configs for them. Then it will watch for new +start/stop events. This ensures you don't need to worry about state, but only define your desired configs. + [float] ===== Docker