[Filebeat] Enabling add_docker_metadata results in no output

[kholia]

If I enable add_docker_metadata processor, then no output file is getting created.

If I disable this processor, then Filebeat generates the output file as usual.

After running filebeat -e -d '*', I see 2018-05-18T05:58:16.149Z DEBUG [add_docker_metadata] add_docker_metadata/add_docker_metadata.go:111 Error while extracting container ID from source path: index is out of range for field 'source' error message in the output log.

Question: Can a failed processor result in no output?

I am running Filebeat 6.2.4 on a Ubuntu 16.04.3 LTS box.

Docker seems to be functioning normally on this box. Executing docker ps is quick and doesn't hang.

Kernel information,

$ uname -a
Linux ip-192-168-44-10 4.4.0-108-generic #131-Ubuntu SMP Sun Jan 7 14:34:49 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Docker information,

$ docker version
Client:
 Version:	17.12.0-ce
 API version:	1.35
 Go version:	go1.9.2
 Git commit:	c97c6d6
 Built:	Wed Dec 27 20:11:19 2017
 OS/Arch:	linux/amd64

Server:
 Engine:
  Version:	17.12.0-ce
  API version:	1.35 (minimum version 1.12)
  Go version:	go1.9.2
  Git commit:	c97c6d6
  Built:	Wed Dec 27 20:09:53 2017
  OS/Arch:	linux/amd64
  Experimental:	false

I am attaching my Filebeat configuration to help reproduce this issue. I suspect that it may not reproduce on an another system. Let's see.

[adriansr]

@kholia can you attach the debug output too?

[kholia]

Sure, here is the debug output.