[filebeat] autodiscover remove input after corresponding service restart #12962
Labels
bug
containers
Related to containers use case
Metricbeat
Metricbeat
module
Team:Integrations
Label for the Integrations team
Filebeat: 7.2.0 docker container
OS: Ubuntu 18.04.2 LTS
Parity: docker container
config filebeat.yml:
filebeat.txt
2019-07-18T06:34:14.349Z DEBUG [autodiscover] autodiscover/autodiscover.go:230 Got a stop event: map[config:[0xc0002290b0] container:{"id":"44e30ae98d153681ab77c05346100a78278c39b266e965ae8d0119891194b05a","image":{"name":"parity/parity:v2.4.5"},"labels":{"MAINTAINER":"Parity Technologies \u003cdevops-team@parity.io\u003e"},"name":"parity"} docker:{"container":{"id":"44e30ae98d153681ab77c05346100a78278c39b266e965ae8d0119891194b05a","image":"parity/parity:v2.4.5","labels":{"MAINTAINER":"Parity Technologies \u003cdevops-team@parity.io\u003e"},"name":"parity"}} host:172.17.0.3 id:44e30ae98d153681ab77c05346100a78278c39b266e965ae8d0119891194b05a meta:{"container":{"id":"44e30ae98d153681ab77c05346100a78278c39b266e965ae8d0119891194b05a","image":{"name":"parity/parity:v2.4.5"},"name":"parity"},"docker":{"container":{"labels":{"MAINTAINER":"Parity Technologies \u003cdevops-team@parity.io\u003e"}}}} port:8545 provider:7614a03c-df13-4169-8cbe-1afceb242df3 stop:true]
and filebeat stop processing parity logs despite the fact parity is running and healthy and its logs are ok
it looks like filebeat process stop event after parity start and think container is down
here is full log of this:
filebeat_parity.log
Steps to reproduce:
The text was updated successfully, but these errors were encountered: