Skip to content

Commit

Permalink
Clarify autodiscover docs in relation to startup process (#7468)
Browse files Browse the repository at this point in the history
Autodiscover reacts to already existing containers first, then it
starts listening for changes of that initial state.
  • Loading branch information
exekias authored and ruflin committed Jul 3, 2018
1 parent 4071bc7 commit a8da186
Showing 1 changed file with 3 additions and 0 deletions.
3 changes: 3 additions & 0 deletions libbeat/docs/shared-autodiscover.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down

0 comments on commit a8da186

Please # to comment.