Filebeat Autodiscover Configuration

Elastic Stack Beats
#1

Can anyone shed some light on where exactly in the YAML config the configuration property "cleanup_timeout" is supposed to sit?

We're using Filebeat Autodiscover for Kubernetes and unfortunately the documentation around exactly what options can sit at what level in the YAML is patchy at best. The only mention of it in the filebeat.reference.yaml file is here:

image
image702×289 10.4 KB

However, in the documentation here - https://www.elastic.co/guide/en/beats/filebeat/current/configuration-autodiscover.html - it states that this item is a property of the Provider, does that mean that the config I have is correct?

image
image782×295 6.79 KB

Please help!

#2

cleanup_timeout is used in kubernetes autodiscover to wait some time before the
configurations associated to stopped containers are removed. As it states in https://www.elastic.co/guide/en/beats/filebeat/current/configuration-autodiscover.html the property is defined in the provider configuration.

There is a similar option for add_docker_metadata (hence the same name).

#3

So, have I configured it correctly then?

Also, are you guys going to update the filebeat.reference.yaml so that it explicitly shows the two places where you can use that property?

#4

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.